Sales & deals

Bookings & Deal Pipeline

From a hold on a unit to a signed contract and a paid tranche — one pipeline for every agent.

Booking timer, Kanban deal stages, auto-generated contracts and invoices, a cancellation log with reasons — the deal lives on the unit, not in a chat thread.

Hold timer locks the unit instantly
Kanban: Pending → Closing → Paid
Contracts and invoices in three minutes
Cancellation log with reasons
Manager sees every agent's deals

See pricing

Who uses it

Bookings & Deals — who uses it

The same module, four different screens — the developer sets it up, the manager watches, the agent uses it, the buyer sees the result.

Developer Hub— Developer & management company

Set hold rules, deal stages and cancellation reasons
Configure contract and invoice templates
Decide who can hold, book and cancel

01 · Holds

Lock the unit the moment the buyer says yes

The problem

The buyer agrees on the phone. The agent messages the office. Someone updates the sheet — later. Meanwhile another agent sells the same unit.

With DomusHub

The agent places a hold from the unit card. The unit is locked for everyone with a visible timer; when the deposit lands, the hold becomes a booking. When it does not, the unit returns to stock by itself.

Hold rules per project: duration, deposit, who can place one
Timer and owner visible to the whole team
Automatic release on expiry

02 · Pipeline

One board for every agent's deals

The problem

The head of sales asks how many deals are closing this month and gets six answers from six agents, each from a different spreadsheet.

With DomusHub

Every deal sits on one Kanban across all agents and projects: Pending, Closing, Paid. Filter by agent, project or status. Open the deal panel for notes and history.

Kanban across all agents and projects
Deal panel with internal notes and timeline
Filters by status, agent, project, date

03 · Documents

Contracts and invoices from system data, not copy-paste

The problem

A reservation agreement is assembled by hand from the last one. A typo in the passport number, a wrong tranche amount, a forgotten discount — and the legal team rewrites it.

With DomusHub

Contracts, offers and invoices are generated from the deal: buyer, unit, price, payment plan. Three minutes instead of an hour and a half, and no field typed twice.

Templates per project and per language
Data from the deal, the unit and the plan
Invoices follow the payment schedule automatically

04 · Control

Know why deals fall apart

The problem

A booking is cancelled and nobody knows why. Three months later the same reason kills three more deals, and there is no record to notice the pattern.

With DomusHub

Every cancellation is logged with a reason, an author and a date. Managers see the pattern; finance sees which deposits to refund; the unit is back in stock immediately.

Cancellation reasons configured per project
Audit log on every deal change
Dashboard: conversion from hold to paid, per agent

What's inside

What's inside: Bookings & Deals

Shipped capabilities behind this module. Every one comes with what you actually see on screen.

Bookings & holds
A timer on the unit instead of a promise in a chat.
On screen:Agent places a hold, the unit locks with a visible countdown (47:12 left). If the deposit doesn't arrive the hold auto-expires and the unit returns to stock. Two agents cannot promise the same unit.
Deal pipeline
Kanban across every agent — Pending, Closing, Paid.
On screen:The sales director opens one board and sees all deals by stage and by agent, with the deal panel showing schedule, notes and documents without leaving the column.
Contract & invoice generation
Assembled from system data, not copy-paste.
On screen:Sale agreement for unit B-12 generated in three seconds with the buyer's passport data, the agreed discount and the right schedule — the three things most often mistyped when a contract is built by hand.
Cancellations & audit log
Every status change has a name and a timestamp.
On screen:A unit went back to available on the 14th. The log says who released it, when, and against which cancellation reason — the question that otherwise takes three people and a chat search.
Notification triggers
The system chases, so the manager doesn't.
On screen:Hold about to expire, tranche coming due, construction update published, deal moved to Closing — each one a rule you set once rather than a reminder someone keeps in their head.
Dashboards & investor reports
Live numbers instead of a three-day report build.
On screen:Revenue, conversion, sold versus reserved versus available, agent leaderboard — and the export the board asks for, generated from the same data the sales team works in.

Everything DomusHub does

Go deeper

Real Estate CRMWhy developers choose this over a generic CRM Definition in the glossary/glossary/soft-hold

Questions about this module

Can the hold require a deposit?

Yes. Each project defines whether a hold is free for a set number of hours or requires a booking deposit, and how long it lasts. When the deposit is marked paid, the hold becomes a booking.

Do we need a separate CRM for leads?

Not for the sales process. Leads, clients, holds, bookings and deals are in DomusHub. If your marketing team already runs a CRM for advertising leads, it can be connected via API so qualified leads land with the right agent.