Figure 1 — System Architecture Overview: OFFRPORTL Real Estate Offer Management Platform

Listing Agent
Buyer's Agent
Seller
Buyer
↓
↓
↓
↓
OFFRPORTL Web Portal — Core Platform (React · Cloud-Hosted)
Listing Module
Create listing → Generate share link or token-gated H&B link → Attach seller contact info
Offer Submission Module
Accept PDF upload via share link → Parse via AI Extraction Engine → Store to Database
Review & Decision Module
Side-by-side comparison → AI scoring → Accept / Reject / Counter / H&B actions
Post-Acceptance Module
Amendment proposals → Termination workflow → Reinstatement → Closing & audit trail
AI Extraction Engine
LLM parses uploaded offer PDFs. Extracts: price, closing date, earnest money, financing type, contingencies, concessions, attorney, and special stipulations. Returns structured JSON to portal.
Email Service (Resend API)
Sends transactional emails for: offer submission, counter offers, acceptance, rejection, amendments, terminations, reinstatements, H&B calls, view reminders, and backup offer notifications.
In-App Notification Service
Real-time bell icon notifications with unread badge count. Delivered to all authenticated portal users: listing agents, buyer agents, sellers, and buyers. Acknowledgement tracked per user.
MLS / Syndication (Bridge API)
Enables buyer agents to search MLS-listed properties directly without requiring a listing agent account. Property data auto-populates the offer submission form.
Database
Stores all Listing, Offer, User, ViewReminder, and TransactionCoordinator entity records. Append-only audit arrays. All data timestamped server-side.
File Storage
Cloud storage for all uploaded PDFs: offer documents, counter offer documents, amendment PDFs, termination documents, reinstatement proposals, and binding contracts.
Stripe Payment Service
Manages subscription billing for listing agents. Enforces feature gating by subscription tier (Basic, Starter, Pro). Webhook integration for real-time status updates.
Key Architectural Claims (Patent Reference)
1. Dual Entry Path
Buyer agents can submit offers via (a) a listing-agent-generated share link or (b) a direct MLS property search — eliminating dependency on listing agent participation to initiate the offer workflow.
2. Unified Multi-Party Platform
A single cloud-hosted portal serves all four transaction parties (listing agent, buyer agent, seller, buyer) with role-differentiated access, real-time notifications, and a shared audit trail.
Fig. 1 — OFFRPORTL System Architecture Overview. The platform is organized into four functional modules (Listing, Offer Submission, Review & Decision, Post-Acceptance) supported by five service layers (AI Extraction, Email, In-App Notifications, MLS/Bridge API, Stripe). All data persisted to cloud-hosted Database and File Storage. Four actor types interact with the portal via role-differentiated access controls.