Real estate transaction portal

One deal record.Every party.Nothing goes dark at closing.

Buyer, seller, renter, agent, and lender all work the same deal — each seeing only what's theirs to see — embedded on the agent's own site instead of one more login to remember.

Agent trackLender trackRatifiedInspectionWalkthroughApplicationUnderwritingCD IssuedClear to CloseClosingNekst / CloseSimple stop herePost-Close HubKept, not archived
The problem

A transaction is one thing. It is never stored as one thing.

01
It lives in five places at once

Contracts in email, status in text messages, loan detail in a lender portal nobody else can open, invoices wherever they landed.

02
Everyone has a different partial view

The buyer, the seller, the agent, and the lender each hold one corner of the same transaction, and none of them match.

03
Then it all disappears

Most transaction tools go dark the day the deal closes — exactly when the record starts mattering for taxes, warranty claims, and referrals.

The approach

Four decisions the whole product is built on

None of these is a feature you bolt on afterwards — each one changes the data model, so they were settled before the first screen was built.

Two timelines, never blended

Agent-side and lender-side progress tracked separately — each side edits its own and sees the other's locked.

Sensitivity decided by document type

HOST, LINK-OUT, or NEVER TOUCH resolved from what the document is, checked at the upload layer.

Delivered inside the agent's own site

The portal installs where clients already trust the agent, not as one more destination to remember.

Two-sided, free-rider pricing

Whoever creates a deal pays; the counterpart they invite rides free on that deal. Growth happens deal by deal.

Role-scoped access

The same deal, through three different lenses

Switch the lens and watch sections lock and disappear. What a role can't see isn't hidden in the browser — it never leaves the server.

Same deal record — switch the lens

1247 Maple CourtUnder contract
7 of 7 sections visible
  • Agent timeline
    Ratified → Inspection → Walkthrough → Closing
    Can edit
  • Lender timeline
    Application → Underwriting → CD → Clear to Close
    View only
  • Document vault
    Contracts, inspections, invoices
    Can edit
  • Funds needed at closing
    Closing costs, seller credits, gift letters
    View only
  • Client-facing notes
    Updates written for the client
    Can edit
  • Internal notes
    Agent ↔ lender coordination
    Can edit
  • Private vendor notes
    How that inspector actually performed
    Can edit

Everything on this deal is in reach for this role.

Sign in as Agent
Compliance by design

Every document sorts itself into one of three tiers

This is a coordination layer, not a repository for regulated financial paperwork. Wire instructions sit in the third lane specifically because of wire-fraud liability — that lane has no override, for anyone.

HOST

Stored directly in the vault, auto-categorised.

  • Ratified contract
  • Inspection report
  • Vendor invoice
  • Title sheet
LINK-OUT

Status summary in-app; the file stays on the lender's system.

  • Pre-approval letter
  • Loan Estimate
  • Closing Disclosure
NEVER TOUCH

Structurally impossible to upload, preview, or cache. No override.

Upload layer
  • Bank statementBlocked
  • Pay stubBlocked
  • Tax returnBlocked
  • Wire instructionsBlocked
  • Loan application (1003)Blocked
After closing

The part where every other tool switches itself off

Closing is where competing products end and this one keeps going: the archive stays, reminders start, and the record is still there when the referral conversation happens two years later.

ListingUnder contractClosingAfter closing
Nekst
Goes dark at closing
CloseSimple
Closing window only
Homebot
Post-close only
EliteHomePortal
Listing through post-close

Coverage as described in each product's own positioning (PRD §2). The gap this fills isn't a missing feature — it's the span.