Elicon
← ALL REFERENCE ENGAGEMENTS
REFERENCE ENGAGEMENT
Real Estate

Transaction CRM for a Boutique Brokerage

Model the real deal lifecycle — listing to close — instead of bending a generic CRM around it.

  • Next.js
  • Postgres
  • Stripe
  • DocuSign API

Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.

THE SITUATION

The problem.

A brokerage whose workflow — listings, showings, offers, escrow, closing — never fits off-the-shelf CRMs, and whose customisations break on every upgrade. The engagement models the transaction lifecycle as first-class objects, connects listings, e-signature and payments, and gives buyers a portal that can never expose internal notes.

Generic CRMs lack the objects the business runs on, and customisation breaks with every vendor upgrade.

  • ·Showings, contingencies and co-brokers either don't exist as objects or need fragile custom fields.
  • ·Contracts and deadlines live in email, so missed dates are found late.

APPROACH

How we'd run it.

  1. 01Model the transaction as the core record, with offers, contingencies and milestones hanging off it.
  2. 02Sync listings nightly without overwriting fields agents maintain.
  3. 03Bind e-signature envelopes to the transaction so the executed version is always the one shown.
  4. 04Give buyers a separate portal that reads only a whitelisted view of their transaction.

ARCHITECTURE

What gets built.

Transaction model

The transaction is the aggregate root. Offers are immutable records — a counter creates a new one — so the negotiation history is a fact rather than an edit log.

Deadline engine

Contingency and statutory deadlines computed from contract dates using rule sets per transaction type, with escalating reminders, recomputed whenever a governing date changes.

Buyer portal

A separate surface with its own query layer that can only read a whitelisted projection. Internal fields are not hidden in the interface — they never enter the response.

DECISIONS

The trade-offs.

Build rather than customise, after an honest comparison

When a workflow needs objects a platform lacks, bolting them on breaks at every upgrade.

TRADE-OFFHigher upfront cost than another subscription, and the brokerage owns maintenance.

Immutable offers, with counters as new records

Negotiation history is evidence. Editing an offer destroys the record of what was proposed and when.

TRADE-OFFMore rows and a slightly more complex read model for the current offer.

A separate projection for the buyer portal instead of interface-level filtering

Hiding a field in the interface is one careless change away from a leak. If the data never reaches the response, the mistake isn't available.

TRADE-OFFTwo read paths to maintain.

STACK

Typical stack.

APPLICATION
Next.jsTypeScriptPostgresTailwind
INTEGRATIONS
Listings feedDocuSign APIStripe
DOMAIN
Deadline rule engineImmutable offer recordsField-level merge
SECURITY
Role-based accessIsolated portal projectionAudit trail

Work of this shape usually runs as Agent Ops Sprint →

SIMILAR PROBLEM?

Tell us what you're dealing with.

One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.

Talk to an engineer →