Four weeks to see where a property developer’s time was going.

The key point

Bringing sales in-house changed more than the sales team. A four-week diagnostic helped a property developer map where time was leaking, then connect CRM integration, its technology stack, SOPs and training into one programme of work. The clearest finding was not a missing tool: the same information was being typed again and again, and every agent ran the core steps their own way.

The shift: bringing sales inside the business

The developer was moving to an internal sales model. That meant taking on the systems and everyday processes that support enquiries, follow-up and handovers, as well as the people doing the selling.

Mileon worked into the developer’s existing environment. The starting point was a four-week diagnostic to understand how the work actually moved, where time was being lost and what needed to change around the new sales function.

Some of those processes run on legal deadlines. In NSW, an off-the-plan contract needs a disclosure statement attached, deposits and instalments sit in a trust or controlled money account for the contract period, and the buyer must receive a copy of the registered plan at least 21 days before settlement.⁠^[1]

Look at the workflow before choosing the system

A CRM decision is easier to make when the team can explain what it needs to keep track of. Which information should follow an enquiry? Who owns the next action? Where does a handover depend on someone remembering a conversation?

Some handovers cannot be left to memory at all. When a change makes what was first disclosed to an off-the-plan buyer inaccurate in a material particular, the developer must tell the buyer. A buyer materially prejudiced by the change can withdraw or claim compensation capped at 2% of the price, and has only 14 days from the notice to act.⁠^[1]

The diagnostic put those questions alongside the existing tools. It connected the search for time leaks with the practical requirements of internal sales, rather than treating each software decision as a separate project.

Map the whole journey, from enquiry to keys

The diagnostic started with the sales department and widened in its first week. The developer asked for the whole journey to be in scope: from a buyer’s first enquiry, through contracts and the solicitors on both sides, to the pre-settlement inspection and key handover. Sales administration and finance were added, because their work starts where a sale is agreed.

Over four weeks, Mileon interviewed more than a dozen people across sales, marketing, administration, legal and finance, read the documents they work from, and mapped each step of the work as it happens today, not as the process manual says it should.

Where the time was going

The pattern was the same across the journey: the systems were there, but the work between them was done by hand, and much of it depended on one person remembering. A few examples show the shape of it.

None of these steps is hard. Each one costs the same few minutes on every enquiry, and the cost adds up quickly across a sales team.

• The same activity was recorded three times: in the CRM, again in a shared weekly document, and once more out loud at the weekly sales meeting.
• When a lead failed to reach the CRM automatically, someone found it at the source and typed the buyer’s details in again.
• Each agent ran first contact, booking and follow-up their own way, and much of the follow-up happened by text from personal phones, with no record in the CRM.
• Official systems sat alongside personal spreadsheets, phone notes and private calendars, so no one could see the whole picture of a buyer or a week.

Connect the CRM, the stack and the way people work

The brief brought four connected pieces of work together. A new system would only be useful if the information, process and people around it were ready too.

Training is also a compliance task now: AUSTRAC lists training for the people doing AML/CTF work among a reporting entity’s obligations.⁠^[2]

• CRM integration: make the sales workflow and its required connections explicit.
• Technology modernisation: review the tools and data the new operating model depends on.
• SOPs: document responsibilities and the repeatable steps behind the work.
• Training: help the team use the system and follow the process in everyday situations.

Count only what the team can stand behind

The baseline is the record of how the work runs today, step by step, that any later change is measured against. Every figure in it came from the people doing the work or from the business’s own records. When a step was clearly real but nobody could say how often it happened, it was marked as not yet costed rather than filled with an estimate.

That made the baseline smaller than a consultant’s estimate would have been. The business saw it the day after the four weeks of fact finding closed, and any later saving can be measured against figures that came from its own people and records.

The useful unit of change is the whole workflow

For a developer bringing sales in-house, the CRM is one part of the change. The surrounding handovers, source information, working instructions and team capability deserve the same attention.

That is the role of the diagnostic: establish a shared picture of the work before committing to a build. Use it to decide what to connect, what to simplify and what the team needs to learn. Then measure the effect against a baseline the business recognises.

Bringing sales in-house also brings compliance with it. Since 1 July 2026, a developer that sells its own apartments, lots or house and land packages without an independent real estate agent has obligations under the AML/CTF Act.⁠^[3]

Read the AML/CTF guide for developers ↗