Skip to content
Brokers, agencies, developers

The CRM for brokers who live on follow-up

Buyer enquiries, site visits, bookings and the money against them, on one record. Applying the real estate pack renames a Lead to an Enquiry and brings the five fields you would have added by hand anyway.

No per-agent fee, unlimited users, self-hosted. The pack applies from Settings in a click.

The sale, end to end

From enquiry to handover, on one record.

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.

  1. Enquiry

    Portal enquiries, walk-ins and referrals all land in one list, with the source recorded against each so you can tell which channel is paying for itself.

  2. Qualify

    Capture budget, configuration, preferred location, possession date and whether finance is needed, then assign the buyer to an agent.

  3. Site visit

    Schedule the visit as a task with a due date, and log what happened straight after from the phone while you are still at the property.

  4. Negotiation

    Move the deal through the pipeline and send an itemised cost sheet the buyer opens on a private link, with no account to create.

  5. Booking

    Raise the token or booking invoice, record part payments as they arrive, and see what is still outstanding on the deal.

  6. Handover

    Keep agreements and KYC on the buyer record, and track post-possession snags as tickets with response targets.

What the pack sets up

Configured for the trade, in one click.

The real estate pack 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.

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.

Four tags to sort a buyer by

  • Hot
  • Investor
  • End user
  • Channel partner

Enough to separate an investor from an end user and a partner from a walk-in, without inventing a taxonomy on day one.

Six billable lines, priced

  • Buyer representation fee
  • Seller listing commission
  • Property valuation
  • Home staging
  • Documentation and registration support
  • Property management (monthly)

Ready to drop onto a cost sheet or an invoice. Change the prices to yours before you send one.

Optionally the pack 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.

What a brokerage runs on

Twelve things that work today.

Each one is checked against the source rather than written from a feature list. The next section is the other half of that promise.

Enquiries with the source on every one

Portal, walk-in, referral or campaign, recorded against the enquiry so you can work out what a booking from each channel actually costs you.

Agents see only their own book

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.

Reassignment when someone leaves

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.

Builders and channel partners as accounts

Developers, brokerages and partners kept as accounts with their own contacts, deals, tickets and invoices hanging off them.

Cost sheets on a private link

An itemised estimate the buyer opens through a tokenised URL with no login, rendered from your own template with your own terms.

Token and booking invoices

Raise booking amounts, record several part payments against one document, and watch the balance follow.

Payment plans that raise themselves

A monthly or quarterly schedule generates its own invoice, nightly, without anyone remembering to do it.

Agreements and KYC on the record

Files attach to the buyer, the deal, the ticket or the invoice, rather than sitting in an inbox nobody else can search.

Post-possession snags as tickets

Complaints after handover get a first-response and a resolution target, counted against your working week rather than the clock.

Targets per agent, with a leaderboard

Revenue goals by period and a leaderboard that ranks the team. On the web app and the phone.

The phone does the site visit

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.

No per-agent licence

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.

Not here

Eight things a broker will ask for and not find.

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.

Property and unit inventory

Towers, units and live availability are not modelled. Today you track buyers, enquiries and deals: the people side of the sale, not the stock.

A stage board for enquiries

The pack defines a seven-stage enquiry pipeline, from New enquiry through to Booked, and those rows really are created. Neither the web app nor the phone has a screen that draws them yet, so today an enquiry carries a status rather than sitting in a column.

Custom deal stages

Deals move through six fixed stages: Prospecting, Qualification, Proposal, Negotiation, Closed Won and Closed Lost. You cannot rename or add to them.

Bulk import of your existing list

The importer is written and tested on the backend, with per-row error reporting, and neither client can reach it yet. Moving an existing book in means the API or a database load, not a file upload in the interface.

A site-visit calendar

A per-agent calendar of visits does not exist. A visit is a task with a due date, so the list sorts by when it is owed, and nothing lays out a week or sends a reminder before it.

Buyer-to-property matching

Nothing shortlists automatically against budget, configuration and location. The fields are captured and the filtering is yours to do.

Listing portal capture and partner commissions

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.

Construction-linked payment plans

Schedules run on dates, monthly or quarterly. A plan that triggers on foundation or slab completion is not something the product can express.

Questions

The ones brokers ask

Check any of it

The lead model, the visibility rules and the real estate pack are all in the open repository.

Does it manage property inventory?

No. BottleCRM manages buyers, enquiries, site visits, deals and payments. Towers, units and live availability are not modelled, so if your bottleneck is stock rather than buyers, this is the wrong tool today.

Can each agent see only their own leads?

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.

Does it work on a phone during a site visit?

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.

Can we import our existing enquiry list?

Not through the interface yet. The importer exists on the backend, with per-row validation and error reporting, and no screen in either client calls it. Today you would move an existing book in through the API. We would rather say that than let you find out after signing up.

Do the enquiry stages in the pack actually do anything?

They exist as configuration and the API serves them, and no screen draws them yet. What works today is the enquiry status, the six deal stages, and the custom fields the pack adds, all of which show up on the web app and the phone.

What does it cost?

The core CRM is open source and free to self-host, with 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.

Run every deal from enquiry to handover.

Apply the real estate pack, put the whole desk on it, and pay nothing per agent. Self-host it and the buyer data never leaves your server.

No credit card · No per-agent fee · MIT licensed