Five fields on every enquiry
- Budget (max)
- Configuration
- Preferred location
- Possession by
- Finance required
They render on the web form and the phone form, filter in list views, and come back through the API.
Buyer enquiries, listings, site visits, bookings and the money against them. The real estate app renames a Lead to an Enquiry and brings the five fields you would have added by hand anyway, and in the hosted app it adds listings matched to your buyers.
No per-agent fee, unlimited users, self-hosted. The app installs from Settings, Apps, in a click.
Nothing here is a separate module you have to keep in sync. The buyer who enquired is the buyer on the deal, on the invoice, and on the snag ticket eight months later.
Portal enquiries, walk-ins and referrals land in one list with the source recorded against each, so you can filter the enquiry list by channel.
Capture budget, configuration, preferred location, possession date and whether finance is needed, then assign the buyer to an agent.
In the hosted app each buyer's requirement lists the properties that fit its budget, type, bedrooms, city and localities, and each property lists the buyers it suits. Self-hosted, the shortlisting is the agent's.
In the hosted app a site visit is its own record, tied to the property and the enquiry; self-hosted, it is a task with a due date. Either way, log what happened from the phone while you are still at the property.
Send an itemised cost sheet the buyer opens on a private link, with no account to create.
Raise the token or booking invoice and record part payments as they arrive. Agreements and KYC stay on the buyer record, and snags after possession become tickets with response targets.
The real estate app is a file in the repository, so this list is exactly what you get. Every item is an ordinary record you can rename, edit or delete afterwards.
They render on the web form and the phone form, filter in list views, and come back through the API.
Enough to separate an investor from an end user and a partner from a walk-in, without inventing a taxonomy on day one.
Ready to drop onto a cost sheet or an invoice. Change the prices to yours before you send one.
Optionally the app also seeds sample buyers, deals and tickets so you can see the shape of it. Every seeded row is tagged, so you can delete the lot in one action when you are done.
Each one is checked against the source rather than written from a feature list. The next section is the other half of that promise.
In the hosted app, the real estate app adds a Property record: for sale or to let, type, status, price, bedrooms, area, city and locality, the owner, photos and files, on a board by status. It is free on every plan and uses none of your plan's custom objects.
In the hosted app, a buyer's requirement lists the listings that fit it and a listing lists the buyers it suits. A new or re-priced listing notifies the agents whose buyers it now fits, and a match you dismiss stays gone.
Three deal pipelines arrive with the app, each stage yours to rename. In the hosted app, winning a deal marks its property sold or let.
Portal, walk-in, referral or campaign, recorded against the enquiry so you can work out what a booking from each channel actually costs you.
An agent works the enquiries assigned to them or that they created. Administrators see every enquiry in the organisation. This is enforced in the API, not hidden in the interface.
Move a buyer to another agent and the new owner is notified. The record itself carries the change, so nothing is lost when the desk changes hands.
Developers, brokerages and partners kept as accounts with their own contacts, deals, tickets and invoices hanging off them.
An itemised estimate the buyer opens through a tokenised URL with no login, rendered from your own template with your own terms.
Raise booking amounts, record several part payments against one document, and watch the balance follow.
A monthly or quarterly schedule generates its own invoice, nightly, without anyone remembering to do it.
Files attach to the buyer, the deal, the ticket or the invoice, rather than sitting in an inbox nobody else can search.
Complaints after handover get a first-response and a resolution target, counted against your working week rather than the clock.
Revenue goals by period and a leaderboard that ranks the team. On the web app and the phone.
The Flutter app talks to the same API as the web app, so a visit outcome logged at the property is on the record before you reach the car.
Add or drop agents as the market moves. There is no seat count and no per-user fee, which matters in a trade where headcount is seasonal.
If one of these is the thing your week turns on, this is the wrong CRM for you today, and knowing that now is worth more than a demo that avoids the subject.
Listings are records in the hosted app, but a developer's towers, units, holds and live availability are not modelled, and the self-hosted edition has no Property record at all.
A visit has a date, a typed time and an outcome, on a board by status. Nothing lays out an agent's week, and nothing sends a reminder before a visit.
No portal integration pulls enquiries in on its own, and commissions per channel partner are not tracked. Enquiries arrive through your own form, the API, or by hand.
Schedules run on dates, monthly or quarterly. A plan that triggers on foundation or slab completion is not something the product can express.
The lead model, the visibility rules and the real estate app are all in the open repository.
Listings, yes, in the hosted app: each property is a record with its status, price, details, owner and photos, matched against your buyers' requirements, free on every plan. The self-hosted edition has no Property record. A developer's towers, units and holds are not modelled anywhere, so if that is your stock, this is the wrong tool today.
Yes. An agent sees the enquiries assigned to them or that they created, and administrators see every enquiry in the organisation. The rule is enforced in the API, so it holds for the phone and for anything you build against the API too.
Yes. The Flutter app covers leads, deals, tasks, tickets, invoices and goals against the same API as the web app, so an agent can log a visit outcome standing at the property.
Yes. Save the list as a CSV and use Import on the leads list (Enquiries, once the app is installed on the web), on the web or the phone. You see every row it would create and every row error first, and nothing is written until you commit, which then writes the whole file or none of it. Up to 5,000 rows a file.
Yes. They are drawn as a board on the web app and the phone: a new enquiry starts in the No stage lane, and you drag it, or move it from its menu, through the app's stages towards Booked. An admin can rename, add or remove stages in Settings. Deal stages are editable the same way, so the deal side can use your own words too.
There is a free plan on the hosted app, and the core CRM is open source and free to self-host. Either way there is no per-agent fee. That matters most in a trade where your agent count moves with the market and a per-seat licence charges you for the peak.
Install the real estate app, put the whole desk on it, and pay nothing per agent. Self-host it and the buyer data never leaves your server.