Property developer and estate agency
What the platform takes over for a developer and what it lacks for that
What this actually is
There is no property industry template in the product register at all — neither available nor planned. The work runs on general modules switched on for the sales team of a developer or an agency.
This is worth saying before the contract rather than after: the product has no unit grid, no apartment reservation and no export to listing sites. It covers what happens BEFORE and AFTER the deal — the request, the answer, the task, the deadline, the approval and the trace of the decision.
Which modules are switched on
The set usually switched on for the sales team of a property:
- Sales: requests as leads, deals, a funnel per property.
- Knowledge base: confirmed answers about stages, deadlines, documents and purchase terms.
- Projects: tasks and deadlines per property, with dependencies between them.
- Contracts: a register, versions, and obligation deadlines taken from the document.
- Finance: plan and fact per property, invoices for approval.
- Analytics: monthly series with a source for every number.
Which AI employees work here
The lines of work that have something to do in this scenario:
- Sales — sorting an incoming request and drafting a reply.
- Legal assistant — deadlines and obligations extracted from a contract.
- Project management — overdue tasks on a property.
- Finance — a gap between plan and fact before an invoice is approved.
- Marketing — campaign results from uploaded exports.
What is not in this build
Not one of the lines below is «not configured yet»: it is not in the code, and no setting switches it on.
- Unit grid, reservation and apartment status — there is no module.
- Export of listings to external portals — there is no connector.
- A legal opinion on a contract: the platform extracts deadlines and obligations; a lawyer draws the conclusion.
- Mailings to buyers: the platform sends messages to nobody.
What is the same in every industry
Company isolation enforced by the database, a closed register of permissions, an immutable journal, and a second person signing off where the action calls for it. That is how the platform is built, and it does not depend on which modules are switched on.
In every industry an AI employee produces a draft. Sending a message, paying, signing and deciding about a person are things the platform does not do — in no mode and under no role.
Basis: docs/MODULE_TRUTH_TABLE.md §5i, §5m, packages/contracts/src/project.ts. This page describes what exists in this build, not what is planned.