Sell units in a development — project inventory, a buyer pipeline from first interest to Won, formal offers, and payment milestones you track as the build progresses.
Three things decide whether this guide fits the way you sell:
If all three fit, read on.
A unit sale runs one track — publish → interest → qualify → offer → reserve → contract → payments → won — and the workspace mirrors it. This guide follows the track in order, then covers the tools that run alongside it.
| # | Step | Where you are |
|---|---|---|
| 1 | Publish the project and its unit inventory | Projects |
| 2 | Buyers register interest and visit | Sales Pipeline · Showings · Calendar |
| 3 | Decide on formal offers — accept, counter, decline | Offers |
| 4 | Record sales events through the stages to Won | Sales Pipeline |
| 5 | Track the milestone schedule as payments arrive | Finance |
| 6 | Keep the deal's paper and conversations in one place | Documents · Messages |
Running alongside: Developer Services and Readiness Packages when you're preparing a financing request, Assessments to track those applications, Analytics for the numbers, Settings for the account.
The distance between a new account and a project buyers can act on is four steps:
When you log in, you land on Overview. Its financing strip, project list and quick links help you choose where to work next; the separate Recently viewed rail lets you return to properties and listings you opened earlier.
The full map, in sidebar order. Route paths live here — everywhere else in this guide, sections refer to the sidebar label.
| # | Label | Href | What it is |
|---|---|---|---|
| 1 | Overview | /dashboard/developer | Portfolio at a glance — projects, units, verification |
| 2 | Sales Pipeline | /dashboard/developer/pipeline | Every buyer interest, staged to Won or Lost |
| 3 | Projects | /dashboard/developer/projects | Development projects and their unit inventory |
| 4 | Showings | /dashboard/developer/showings | Buyer-requested unit visits |
| 5 | Offers | /dashboard/developer/offers | Formal buyer offers and your decisions |
| 6 | Calendar | /dashboard/developer/calendar | Appointment workspace |
| 7 | Assessments | /dashboard/developer/assessments | Financing assessment tracker |
| 8 | Developer Services | /dashboard/developer/services | Project-financing preparation |
| 9 | Readiness Packages | /dashboard/developer/readiness-packages | Document Readiness Room |
| 10 | Finance | /dashboard/developer/financials | Project Ledger — offline payment milestones |
| 11 | Analytics | /dashboard/developer/analytics | Performance metrics — needs the analytics feature |
| 12 | Documents | /dashboard/developer/documents | Unit-linked transaction documents |
| 13 | Messages | /dashboard/developer/messages | Deal conversations — badge shows unread |
| 14 | Settings | /dashboard/developer/settings | Account configuration |
Note: Ask AI sits near the top of the sidebar; Upgrade Plan appears at the bottom when a plan upgrade is available. Analytics requires the analytics feature to be enabled in your subscription.
The Overview is where the day starts. It answers one question — what does the portfolio look like right now? — and routes you to wherever the answer points: project count, total units, units sold, units under commitment (reserved, contract signed, or payments in progress), your verification status, a link strip into the financing tools, a project list, and quick links into the pipeline and messages.
Two tiles deserve a careful reading before you quote them to anyone:
One number that does deserve respect: Units Sold is maintained from real recorded sales events. If it looks wrong, fix the underlying deal in the pipeline — the metric follows the record, not the other way around.
Treat the Overview as the entry point, not the report: the operational truth lives one click deeper, in the pipeline and the ledger.
Projects is where a sale becomes possible at all — nothing in this workspace moves until a unit exists in a published project. Your job here has three parts: build the public record buyers judge, stock the inventory they buy, and set the payment schedule they'll eventually pay against.
The public record. A project is the buyer-facing page — name, headline, description, type, status, location, price range, cover and gallery images, brochure PDF, features and amenities. Buyers decide whether to register interest based on what's here, so write it for them, not for yourself. Creating a project is a four-step form — Project Identity, Location, Inventory & Finance, Marketing & Media — ending at Publish to Directory. Published projects are browsable by buyers and get a View Public Page link on the project detail page; open it and read your own listing the way a buyer does.
The inventory. Inside the project, each unit carries its own number, type, floor, size, bed/bath, parking, kitchens, features, price and optional floor-plan image. The common inventory states are Available, Held, Reserved and Sold; as the pipeline advances, unit rows can also show interest pending, contract signed or payments in progress. Search and status filters help you work a large building. This inventory is the record the pipeline writes to: when a Won event lands, the unit here is marked Sold. One guardrail to know before you need it: a unit can't be deleted once it has buyer interests, payment records, documents or messages attached — the platform will tell you to mark it Held instead, so deal history is never destroyed.
The payment plan. The Payment plan tab is the milestone schedule buyers will eventually pay against — named milestones as percentages or fixed amounts, each with a due date or due rule and notes. You save draft versions and use Publish as default to make one the project default; every save creates a new version. The part that matters: changing the default only affects buyers who come after it. Snapshots already recorded on existing deals stay as they were, so you can restructure the plan mid-project — repricing the back half of a phase, say — without rewriting deals in progress.
Finding your work scales with the portfolio: grid or list view, search by name, city or address, and filters for status, city, price range, total-unit range, bedrooms, bathrooms, parking, kitchens and unit type — twelve projects per page.
Two smaller mechanics worth knowing:
Once a project is published, it starts producing work: interests land in Sales Pipeline, visit requests appear in Showings, and formal offers arrive in Offers.
This is the surface you'll live in — the working file on every buyer, not just a stage board. Open it in the morning and it answers the questions that run a sales operation: who needs a call today, which deals are stalling, and what's actually in play.
Work it three ways: Board for the stage-by-stage picture, Table for a flat list of the same leads, and Invitations for the buyer invitations you've sent. Search covers buyer name, unit and project; filters narrow by project, owner, source and stage.
The summary strip reads like a briefing: Active units · asking value (the asking-price total for units with an open lead — inventory in play, not revenue), Recorded sold value (final sale prices actually recorded on sold units), overdue follow-ups, and unassigned active leads. The last two are your chase list — a lead sitting with a stale next-action date is a deal quietly going cold.
Each lead card shows buyer, unit and project, the current price source — Final sale, Agreed, Presented or Asking — source, owner, next action and date, payment health, and last activity. Open a card and it becomes the deal's file: Message buyer, open the project, assign an owner, edit the lead source, set a next action and follow-up date, review the terms originally presented to the buyer, record agreed price and milestones with notes, view and record offline milestone payments, schedule an appointment, add internal notes, and see any other interests on the same unit. Terms and stage live here — a message thread is a conversation, not the deal record.
Stages are events, not positions. You don't drag a card; you record what happened: open the lead → Record sales event → pick the stage, date and details. The nine stages:
| Stage | Meaning |
|---|---|
| New | A buyer has registered interest in a unit |
| Contacted | You recorded that you reached out |
| Qualified | You recorded that the buyer meets your qualification criteria |
| Reservation pending | The reservation step is pending; the unit is not committed yet |
| Reserved | Unit committed to this buyer — competing interests marked lost |
| Contract signed | You recorded that a contract was signed outside estateTT |
| Payments in progress | The milestone schedule is being tracked |
| Won | Final sale price recorded; unit marked Sold |
| Lost | You recorded the lead as lost; a reason can be saved |
Recording an event keeps the pipeline honest. Record sales event asks for a reservation reference when you choose Reserved, the final sale price for Won, and a reason for Lost. You are recording what happened outside the platform; estateTT does not verify its legal effect.
Understand Reserved before you use it. A unit can only be committed once: recording Reserved commits it to this buyer and marks competing interests Lost. If you're still talking to multiple buyers, keep the unit Held while you continue the conversations; don't record Reserved until you're ready to commit. Later, the Won event captures the final sale price and marks the unit Sold in inventory.
Invite buyer fills the pipeline instead of waiting for it: pick a published project, optionally name an available unit or let the buyer choose, set a source, add a message, send. An invitation is not a lead — nothing is reserved, nothing is staged. Only after the buyer joins and selects a unit does an interest exist. Invitations can be copied, resent or revoked from the Invitations view, and if the email doesn't land, a shareable link still works.
A deal that reaches Payments in progress moves its money tracking to Finance; a Won deal updates unit inventory and the Overview counts automatically.
If a buyer asks what a mortgage payment could look like, point them to the public mortgage centre and repayment calculator for general planning. Neither tool is a lender quote or an approval.
Showings answers one narrow question honestly: which unit visits are on the books? It's a read-only list of buyer-requested and scheduled visits — project, unit, buyer, scheduled time, and the current stage of that buyer's interest — sorted by visit date.
It doesn't book tours and doesn't score the buyer afterward; scheduling happens in Calendar or on the lead card, and what a visit meant for the deal is your call to record in Sales Pipeline. What it does is keep every committed visit visible in one place, so nobody's tour quietly falls off the schedule — and so you can see, before a visit, whether you're showing a unit to a New lead or a Qualified one.
This inbox is where a buyer puts a price on a specific unit. Each card shows project, unit, buyer, amount and status; your job is to decide how to respond, and each choice moves the negotiation differently.
| Action | What happens |
|---|---|
| Accept offer | The offer shows Accepted, the agreed terms are recorded on the buyer's deal, the deal advances to Reservation pending, and the buyer is notified |
| Send counter — enter an amount | The offer shows Awaiting buyer and the buyer is notified to respond |
| Decline | The offer shows Declined and the buyer is notified; they may submit a new offer afterward |
Accept and decline each ask for a confirmation click. The statuses tell you whose move it is: Pending is on you; Awaiting buyer means you countered and the buyer has the next move. Accepted closes this offer round and advances the deal; Declined and Withdrawn end the current offer, not necessarily the relationship. If the buyer counters back, the offer returns to Pending and it's your turn again. A buyer can withdraw a pending offer — you're notified and it shows Withdrawn — and can submit again afterward.
Offers arrive through the front door you set up in Projects: a buyer expresses interest in a published unit, opens their interest record, and submits from the Your offer panel there. These are formal offers on the deal record — not figures dropped into a chat. (Chat has its own place; see Messages.)
Each offer card keeps its own negotiation history — who offered, countered, accepted, declined or withdrew, the amount, and when — under the current figure. That's the record both sides work from, so the back-and-forth stays documented instead of living in phone calls.
What accepting does — and doesn't: the platform records the accepted price, not a reservation or signed legal agreement. Acceptance moves the deal to Reservation pending. Later, record Reserved in Sales Pipeline via Record sales event when the reservation paperwork is complete; that event commits the unit and marks competing interests lost. estateTT records the events you report — it does not execute or verify legal agreements.
When a financing application exists, its paperwork lives here. This is your Document Readiness Room — created from a refinance or construction application you started in Developer Services, and organized into Overview, Documents, Checklist Review, Access, and Activity.
The room turns the application checklist into work you can manage. Requirements are specific to the jurisdiction you selected, not one universal list. In Overview, each document is grouped as Available now / On request / Already provided / Outstanding, so you can see what is still missing before sharing. Upload a file against its requirement; if a document changes, replace it there and keep the version history with the checklist item.
Sharing is the point — and it's deliberately gated. A room is private by default. When lender visibility is enabled for your account, the Access tab lets you keep it private, share with selected banks, or accept directory contact requests. Before publishing, you must review and confirm the anonymous lender preview, so you can see what a lender would see before anyone sees it. Document grants are separate from your contact details: you release specific file versions explicitly, can revoke them later, and approved lender contact requests are answered on your terms. No lender sees a file you haven't released.
An optional estateTT AI review can check the package checklist against the attached files and return findings with suggested follow-ups — a second pair of eyes on completeness, available with the relevant entitlement and credits. It doesn't change your sharing, your checklist scores, or document access, and it is not a lender, legal, valuation, title, or tax judgment.
Financing assessments is the tracker for the refinance and construction applications you started in Developer Services. Each row shows status, date, estimated value or cost, readiness score and reference — the queue of financing work in flight.
Open a record to see the jurisdiction-specific checklist, attached files, outstanding items, progress and audit findings; you can also use Print/PDF to keep a copy. When a document is missing or needs replacing, the checklist shows which requirement to address. Critical blockers are surfaced on Developer Services so they are easy to find again.
A readiness score summarizes document availability against the applicable checklist. It is not lender approval and does not predict whether a loan will be granted. This is a financing-preparation record, not a property valuation or pricing report; it does not tell you what a unit is worth. If your lender asks for a professional valuation, browse the professional directory and confirm which providers the lender accepts.
This is the project-financing preparation hub — where a refinance or construction request starts. Equity refinance helps you assemble a request around project equity; Construction loan organizes the facts and documents for a new build or renovation. The links to Assessments and Readiness Packages take you from the application into its tracking and document workspace. If an active application has a critical blocker, an Action required card appears here.
Each wizard gathers jurisdiction, property/project and financial information, then shows the checklist for the jurisdiction you selected and saves the application. Its checklist and uploaded files carry into the Document Readiness Room, where you manage access and releases.
Use Developer Services to prepare and organize a financing request. The platform doesn't provide funding, approve loans, match or guarantee a lender, underwrite, or make legal, tax, or valuation decisions; the lender makes its own decision.
The Project Ledger — the schedule pre-construction actually pays on. Each unit's milestone rows ("Deposit", "Foundation Complete", "Handover") carry paid date, method, reference and status: Pending, Awaiting verification, Paid, Overdue, Cancelled, Refunded.
The money itself never touches estateTT — payments happen directly between you and the buyer. What the ledger gives you is a two-step record of each one: the Record Offline Payment form captures date, method, reference and an optional evidence link, which sets the row to Awaiting verification; then you open the row's Audit Trail and Confirm funds received offline marks it Paid. As the project owner you perform both steps — the first records an offline payment report, and the second records your confirmation that the funds arrived. The Audit Trail keeps those actions and their dates distinct.
Working the ledger is built for a long schedule: search by project, unit, buyer, milestone or reference; filter by project, milestone, payment method, currency and status. The summary separates confirmed collection from pending collection by currency, alongside milestone and overdue counts. Only Paid rows count as collected; Awaiting verification remains pending until you confirm it. An Overdue row means its due date has passed while still unpaid — use the count to decide which records need follow-up first. Export Ledger produces a CSV using your current filters, and each row opens an Audit Trail showing who recorded the payment, who confirmed receipt, the dates, method, reference and proof link.
Two habits keep it trustworthy: record payments as they clear, not in batches at month-end; and export monthly — reconciliation is far easier ongoing than reconstructed at year-end.
Boundary: the ledger tracks milestones and statuses — it does not process, hold, or release funds. Collection is between you and the buyer.
The numbers behind the operation — requires the analytics feature in your subscription; eligible users see it, others don't.
Pick a 6, 12 or 24-month window, optionally narrow to one project, and read it top to bottom: a summary, then Sales Velocity (monthly units sold and time to close), Project Performance, Pipeline Funnel (how many interests sit at each stage), Pricing Trends, and a Project Details table.
The four summary cards answer different questions: Recorded Revenue uses final prices you entered; Pipeline Value counts unique units with an open buyer interest at asking price; Conversion Rate compares closed interests to all recorded interests; Avg. Time to Close measures from unit creation to its recorded close date, where both dates exist. Analytics Pipeline Value is lead-linked; the Overview tile is an unsold-inventory figure, so they answer different questions and need not match.
The Pipeline Funnel shows how many interests sit at each stage. Pair that view with follow-up dates and lost reasons in Sales Pipeline to investigate where attention is needed; the chart doesn't tell you why a buyer stopped or predict what will close.
Two honesty rules the numbers keep, and you should too: Recorded Revenue only counts deals where a final sale price was explicitly recorded — closed units without a final price are excluded and the page says so — and multi-currency figures are kept separate rather than blended into a fake total. This is retrospective reporting of what happened, not a forecast or a valuation.
Use Calendar to plan and track appointments around buyer visits and deal follow-ups; use Showings for the dedicated list of scheduled unit visits. Calendar helps you manage the day, while the pipeline records what happened to the buyer's deal.
Work it as a calendar: Month, Week, Day or Agenda views, Today to get back, search and event-type/status filters, upcoming events, and an attention/follow-up queue so items needing a response surface on their own instead of relying on memory.
Creating is deliberately lightweight: click a slot or New appointment, set a title, date/time or all-day, add guests by email, a meeting link, location, description and a colour. One mechanic matters: guests receive a real invitation and must accept before the appointment is confirmed — an event with invitees isn't on their calendar until they've responded. The event detail shows each participant's response and notes; you can edit your own solo appointments, and moving or rescheduling some shared events asks participants to reconfirm, so a change you make doesn't silently become a meeting they never agreed to.
There are two document stores, and picking the right one is most of the job:
Rule of thumb: if it belongs to one buyer's transaction on one unit, use Documents; if it describes the project as a whole, use Agreement & Docs. The register may show execution or finalization status, but estateTT stores and tracks documents — it does not sign them. Uploading a signed agreement makes it retrievable; it does not create or execute the agreement.
Use Messages when a buyer asks about a unit, a timeline changes, or you need to follow up — it keeps the conversation together. The list is ordered by latest activity and searchable by contact name; each thread shows its unread count, the sidebar badge totals unread messages, and opening a thread marks it read. New messages arrive live while you're in the conversation.
There are two ways to start. New Engagement lets you search for a contact you can message on estateTT. From a pipeline lead, Message buyer opens a thread addressed to that buyer. That starts the conversation; it does not link the thread to the lead. Keep stage, terms and next action current on the Sales Pipeline card; use Record sales event when the stage changes, and the relevant lead-card control for terms or follow-up.
Inside a thread, the tools are built for real deal work:
Two behaviors that surprise people if nobody warns them:
For pre-construction, there's a discipline worth adopting on top of the tooling: keep promises and milestones on-platform. Construction timelines shift — when they do, a documented commitment survives better than a phone call. "We discussed it" is a negotiation; a message thread is a record.
Use Settings to update your developer verification profile, personal contact details and avatar, and review your developer subscription plan and its included features. Analytics access appears here as part of the plan; AI package-review credits are a separate add-on, not part of the developer plan.
Why is a sold deal still in Sales Pipeline? Won is the final pipeline stage, so the lead remains there as the deal record. Check the project inventory to confirm the unit is marked Sold.
Payment not showing as Paid? Recording it sets the row to Awaiting verification. Open that payment's Audit Trail and select Confirm funds received offline after you confirm the money arrived.
Can't close a deal? Check your permissions; contact support if it persists.
An offer says "Awaiting buyer" and has no actions? It's a counter you sent — the buyer's answer is pending. If they counter back, the offer returns to Pending and your actions reopen.
Accepted an offer but the unit isn't reserved? Working as designed — accepting moves the deal to Reservation pending. Record the Reserved sales event when the reservation paperwork is done; that's what commits the unit.
Sent a phone number or email and the buyer didn't get it? Messages containing contact details are replaced by [REDACTED]. Do not rely on a message containing contact details to reach the buyer; coordinate through the platform's available appointment and conversation tools.
Invited a buyer but nothing appeared in the pipeline? An invitation isn't a lead yet — the interest is created when the buyer joins and selects a unit. Track or resend the invitation from the Invitations view; if the email didn't arrive, copy the share link and send it yourself.
Can't delete a unit? Once a unit has buyer interests, payment records, documents or messages attached, deletion is blocked to protect the deal history — mark it Held instead.
For support, use the contact page or email support@estatett.com.