Skip to main content
Login
Apus Platform
Book a demo
All solutions
REAL ESTATE

Sell a finite inventory, then operate it for decades.

Unit status, contracts, payment stages and operating records sit on one customer — from the first reservation to the day residents move in.

Talk about real-estate operationsExplore capabilities
Status per unit Payments by stage Lifecycle past handover
Built for: Developers · Sales agencies · Project sales · Receivables accounting · Building management

Module scope, deployment model and each side's responsibilities are defined per company during the survey phase.

REAL ESTATE
Unit statusPer unit 
PaymentsBy contract stage 
LifecycleContinues past handover 

Readouts describe management scope, not performance figures.

OPERATIONAL REALITY

One customer, three systems that never speak to each other.

OPERATIONAL REALITYTARGET STATE

Unit list and contracts live apart

Which unit is reserved, deposited or signed sits in a spreadsheet; the contract and the receivable sit in accounting.

Status visible per unit
Reserved → deposit → signed → handed over

Payment stages follow construction, updated separately

Site milestones drive the payment stages, yet the two sides record them in different places.

Receivable gaps between stages
Reconciled against milestones

Handover ends the customer record

The file stops on handover day, while service charges and maintenance start again from zero.

The record continues past handover
Into service charges & maintenance

Outcomes describe capability direction; how much improves depends on your sales policy, handover rules and update discipline.

OPERATING CHAIN

Follow one project from land to the day residents move in.

Land-to-Handover
1Land & project setup
COVERED BY
ProjectsBudget
AGENT ON DUTYAmi Project
2Legal file & design
COVERED BY
DocumentsApprovals
AGENT ON DUTYAmi Contracts
3Launch & reservations
COVERED BY
CRMUnit status
AGENT ON DUTYAmi Sales
4Contracts & payment stages
COVERED BY
ContractReceivables
AGENT ON DUTYAmi Receivables
5Handover
COVERED BY
Sign-offUnit file
BUILT FOR THIS INDUSTRYAmi Handover
6Operations & service charges
COVERED BY
Building – EAMFinance
AGENT ON DUTYAmi Care

Configured to the product type (apartments, low-rise, land plots, rental), direct or agency distribution, and each project's handover rules.

The agents are not bolted onto this chain: each stage has one standing on that stage's own module, running inside the caller's permissions — so no two stages are joined by a connector.

See every agent
CAPABILITIES THAT FIT

Match the right capability to each stage of the customer lifecycle.

Customers – CRM

Buyers, brokers, interaction history and the status of each unit on one shared record.

Finance – staged receivables

Payment stages tied to contract milestones, deposits, agency commission and revenue recognition.

Project management – PM/PPM

Investment and construction progress, project budget, milestones tied straight to payment stages.

Building operations – EAM

Equipment, preventive maintenance, incidents and running cost after handover.

Documents – EDM

Contracts, addenda, legal files and handover records under approved version control.

BI & analytics

Sales velocity, cash flow by stage and operating cost per project.

Project marketing

Launch campaigns, budget per project and enquiries flowing into CRM.

Project entities in several countries share one inventory and payment-schedule model, and differ on revenue recognition. See it by market

A DAY IN OPERATIONS

A day on a project still selling — and on a building already handed over.

The same buyer moves from reservation to contract, to move-in day, then on to the service-charge invoice — on one record that does not stop at handover.

Project sales

Goal

Keep unit status and the buyer's file in the same place.

Modules
  • CRM
  1. Open the project's unit board: what is left, what is on reservation, what is signed.
  2. Log a reservation with its buyer and the broker behind it — the unit's status changes for the whole team at once.
  3. Turn the reservation into a deposit and then a contract; the buyer's file follows without being retyped.
  4. Track each agency's buyers and the basis on which commission is calculated per deal.
  5. Read sales velocity by phase and by launch to propose the policy for the next release.

Receivables accountant

Goal

Payment stages stay tied to the contract milestones and the build.

Modules
  • Finance
  • PM/PPM
  1. Open the payment stages falling due, filtered by project and by phase.
  2. Check the construction milestone just certified against the stage tied to it before any notice goes out.
  3. Issue payment notices in a batch to the buyers on the same stage, each with its own statement.
  4. Record the money in and handle the buyers who paid short or paid ahead of schedule.
  5. Open receivables by project and the forecast cash flow of the stages still to come.

Building management

Goal

Take handover and carry on operating off that same file.

Modules
  • Building operations – EAM
  • Documents – EDM
  1. Open the units due for handover this week and the snags still to be cleared.
  2. Write the handover record per unit and file the approved version on that unit's record.
  3. Take a resident's report and turn it into a work order for the technical team.
  4. Run preventive maintenance on the building's equipment: lifts, pumps, electrical systems.
  5. Close the service-charge period by unit area and pass it to finance to invoice.

Developer's board

Goal

Read the whole portfolio off one set of numbers, not four separate reports.

Modules
  • BI
  • PM/PPM
  1. Open the portfolio: investment progress, sales velocity and cash flow per project.
  2. Drill into a project slow on cash → down to the payment stage and the buyers who have not paid.
  3. Compare the investment cost spent with the approved project budget.
  4. Read the running cost of the buildings already handed over and carry it into the next project's case.
  5. Approve the files waiting on a signature in their controlled version.

Unit status is modelled on the shared CRM and finance records, not on a separate sales system. Your reservation policy, handover rules and service-charge basis are agreed during the survey phase.

AGENTS ALREADY DO

Reconciling, chasing due dates, summarising and rolling up — the repetitive work running through the day above.

PEOPLE STILL DECIDE

Approving spend, settling on a plan, signing — anything that needs judgement still stops with a person.

Operational readiness
CAPABILITY SCOPE

Start with one project on sale to standardise unit status and payment stages, then open it to the whole portfolio.

Apus connects customers, finance, projects and asset operations on one platform — the same core already running for multi-site operators.
Talk about implementation scope
HOW DELIVERY WORKS

A defined path, not an open-ended project.

  1. 01

    Survey & agree scope

    Map current processes, the systems in use, data owners and which modules to switch on.

  2. 02

    Standardise & configure

    Agree the standard processes, configure the system around them, fix roles and permissions.

  3. 03

    Migrate & run in parallel

    Load master data and opening balances from the templates, run in parallel, reconcile and fix gaps.

  4. 04

    Go-live & expand

    Run for real with an activation team, accept against a checklist, switch on further modules later.

Starting from a scope with clear boundaries is consistently faster and safer than switching everything on at once — expansion then happens on data that is already live.

Not the right fit at this stage if you need

  • To immediately replace a specialist system that is your system of record
  • Deep customisation outside the standard process before the system runs for real
  • Automated decisions replacing people at material control points
  • Multi-year historical data conversion before the source data is cleaned

Learn more

FREQUENTLY ASKED

What developers ask before consolidating their data.

How is the status of each unit managed?+

Reserved, deposited, signed and handed over are modelled on the shared CRM and finance records — not a separate sales system. The exact scope, especially phased inventory and reservation policy, is agreed during discovery.

Can it connect to external sales agencies?+

A data-exchange point for lead lists and reservation status can be designed. The mechanism, frequency and data ownership are defined per implementation.

Are service charges and maintenance after handover in scope?+

Operating cost, equipment maintenance and service-charge billing per building are in scope. A dedicated resident app is a different problem and needs separate confirmation.

Is revenue recognised on progress or at handover?+

Both are configurable, with deposits and staged receivables tracked alongside. The accounting policy applied remains your decision.

How long does implementation take and what does it cost?+

Duration depends on module count, legal entities and process complexity; the Essentials industry template commits to go-live in 90-120 days. The cost has three lines, all stated up front: implementation (one-off), capacity-based usage (recurring, never per user) and data migration (billed separately).

What happens to the data we hold in Excel or an older system?+

Apus provides standard import templates for master data, opening stock and opening receivables so your team can load them — that part is in the package. If you want Apus to map fields, clean and load for you, or to convert multi-year history, that is the separately billed data-migration line.

Start with one project currently on sale.

Map unit status, payment milestones, legal files and the handover routine with Apus before anything is configured.

Talk about real-estate operationsSee other industries
noindex