What this is
The product register has no property template, available or planned.
More detail
Sales teams of developers and agencies work on the shared modules, which cover what happens before and after the deal: request, answer, task, deadline, approval, decision record. Not in the code, and no setting adds it:
- Unit grid, booking and apartment status — no module.
- Listing export to property portals — no connector.
- Legal opinions on contracts: the platform extracts deadlines and obligations, a lawyer concludes.
- Mailings to buyers: the platform never writes first.
Modules and AI employees
AI employees with work here: sales, legal assistant, project management, finance and marketing. Modules usually switched on for a property sales team:
- Sales: requests as leads, deals by property and stage.
- Knowledge base: confirmed answers on stages, deadlines, documents and purchase terms.
- Projects: tasks, deadlines and dependencies per property.
- Contracts: a register, versions and obligation deadlines.
- Finance: plan and actuals per property, invoices for approval.
- Analytics: monthly figures with a source for every number.
More detail
Same in every industry
Company isolation in the database, a closed permission register, a decision journal the application cannot change or erase, and two-person sign-off where needed. AI employees only prepare drafts; payments, signatures and decisions about people stay with staff. A customer gets a staff member’s reply or, in the website chat when it is on, the verbatim text of a confirmed answer.
Basis: the registry of modules and industry templates; product documentation. This page describes what exists in this build, not what is planned.