What it does
Every line below is something the system enforces today, not a roadmap item wearing a present tense.
Your process, not ours
Declare your own client and owner pipelines, rename and reorder stages, and decide which fields are required on which form. No deploy, no ticket.
Roles that match your structure
Agents, managers and admins to start with — then add senior and junior agents, or whatever your agency actually calls them. One person can hold several roles and switch between the views.
Decide who sees what
Every listing, only their own, or only their team’s — set per role, and enforced in the query rather than hidden in the interface.
Your own website, included
A public site on your domain, with your logo and colours, listing what you choose to show. Enquiries arrive as leads and follow your routing rules.
Automations you write yourself
A claimed client, a new match, a recorded transaction — pick the trigger, add the conditions, choose who hears about it. Dry-run it before it goes live.
Matching that shows its reasoning
Clients matched to listings and listings matched to the unclaimed pool, with a visible reason for every match. A filter with a score, not a black box.
In the field, on a phone
The four things an agent needs between viewings: the number, the details, a status change, and the note they would otherwise forget by evening.
Isolation you can audit
Every agency’s data is separated in the database itself, not only in application code — and the separation is covered by tests that fail the build.