Real estate CRM

Nestron: a real estate CRM with rules the business can read

Agents lose deals and create risk when agreements, terms and follow-ups live in memory and chat threads.

View live productBook a consultation
Nestron dashboard with property and buyer counts, a pipeline chart by stage, recent activity and a buyer intent heatmap
Built for
Real estate teams managing listings, buyers and agents
Core modules
Properties, buyers, compensation, projects, follow-ups, automations
Pipeline
New, Enquiry, Site Visit, Negotiation, Closed

The problem in the real world

A real estate team juggles listings, buyers and agents, and the commercial terms that connect them. Who agreed what commission, in writing or on a call? Has this buyer signed anything before touring a property?

Those answers usually sit in someone's phone. When a seller says something verbally and nobody writes it down, or a buyer tours a home with no agreement in place, the business carries the risk without knowing it.

Follow-ups are the second leak. A hot buyer waits for a callback, a listing goes quiet for a month, and nobody is assigned to notice.

The hard part

Commercial terms that are tracked, not remembered

The rule: Every listing should record what compensation the seller offered, how it was agreed and until when, and a verbal promise should look different from a written one.

Edge cases

  • A seller agrees on a call and nothing is written down yet.
  • The agreement is written, but it expires before the next offer.
  • The seller declines to offer anything, and the buyer must cover the fee directly.

How it is handled

Each listing has a terms record with a rate (a percentage or a flat amount), the channel it was agreed on, notes, the seller, an expiry date and a status. A "Verbal only" flag marks anything not yet documented. The compensation screen counts how many listings have terms recorded, so the gaps are visible as a number.

Life of a compensation term

  1. Not started

    No conversation recorded

  2. Negotiating

    Often flagged Verbal only

  3. Agreed

    Written down, with an expiry date

  4. Expired

    Needs renewal before any new offer

  • Exit: Seller declinedRecorded as a decision, so the buyer-pays case is not mistaken for a gap.
Nestron compensation screen with listings that have terms recorded, buyers with a live agreement, and a list of open compliance risks
From the product's demo workspace. Names and figures are sample data.

No showing without a signed agreement

The rule: A buyer cannot tour a property until a representation agreement is signed and still in date.

Edge cases

  • The agreement was sent but never returned.
  • The buyer has no agreement at all.
  • A signed agreement is about to expire.

How it is handled

The product states the rule on screen: showings are blocked until the agreement is returned. An automation sends the agreement for signature and alerts the agent when a showing is booked without one, and another sends a renewal email when an agreement is within 14 days of expiry. Open risks are listed by buyer, with the reason beside each name.

Booking a showing

  1. A showing is booked

    For a buyer on a listing.

  2. Is there a live signed agreement?

    Signed and still live.

  3. Yes: the showing goes ahead

    Nothing for the agent to chase.

  4. No: the agreement is sent for signature

    The agent is alerted at the same time.

  5. Blocked until it is returned

    Listed as a compliance risk meanwhile.

Follow-ups driven by rules the team can read

The rule: When something happens in the pipeline, the right person is told or assigned automatically, and the team can see exactly what each rule does.

Edge cases

  • A hot buyer needs a senior closer quickly.
  • A listing gets no enquiries for 30 days.
  • A follow-up goes overdue and both the owner and their manager should know.

How it is handled

Rules are built as a trigger, a condition and an action. The demo lists nine, each with a switch to pause it, a Run now button and a run history. Each rule shows its own success rate, which makes a failing rule easy to spot. The run counts in the demo are sample data and not a usage claim.

Trigger, condition, action

  • Property added

    Condition
    Budget and city match
    Action
    WhatsApp message to Hot buyers

  • Buyer marked Hot

    Condition
    One condition
    Action
    Assign to a senior closer

  • Property goes cold

    Condition
    No enquiries for 30 days
    Action
    Price-review task for the supplier

  • Follow-up becomes overdue

    Condition
    One condition
    Action
    Notify the owner and manager in app

  • Showing booked without an agreement

    Condition
    None
    Action
    Send the agreement for signature

Five of the nine rules shown in the demo workspace.

Nestron automations screen with nine rules, each showing its trigger, condition and action chain, a pause switch, a run count and a success rate
From the product's demo workspace. Names and figures are sample data.

How it fits together

  • Listings and suppliers

    Properties added by the team

  • Buyer enquiries

    Enquiries, intent, showings

  • Project progress

    Milestones that buyers follow

Nestron

  • Pipeline
  • Compensation and agreements
  • Rules engine
  • Follow-ups

  • WhatsApp and email

    Buyer messages, digests, renewals

  • Tasks and assignments

    Follow-ups and closers

  • In-app alerts

    Overdue work, compliance risks

What this means for your business

  • Gates before an action

    Blocking a showing until a document is signed is the same pattern as holding a dispatch until a purchase order is approved, or a payout until KYC is complete. We build the gate and the dashboard that shows what is stuck.

  • Rules the owner can read

    A trigger, condition and action list gives a business owner control without a developer. The same structure runs reorder alerts in inventory, payment chasers in billing and approval routing in ERP.

  • Quiet-record detection

    A listing with no enquiries for 30 days creates a task. Stale quotes, idle leads and dormant accounts are the same signal in any CRM, and catching them is cheap once the rule exists.

Tech notes
  • Observed from the running product: a single-page application on Vercel that includes a Reset demo data control, so the demo workspace is seeded and resettable.
  • Messaging channels shown in rules are WhatsApp, email and in-app notification. Document signing is shown as an automation action.
  • This is the thinnest of the three studies. We did not review the source, so inventory locking, payment plans and de-duplication of leads are not described here. They were not visible in the product.
  • Screens are from the demo workspace. Every name, property and figure is sample data.

Have logic this messy in your operations? Let's talk.

Book a consultationContact us