MTWIN by MPANDO

MPANDO Sales OS

Sales OS exists because property sales breaks general CRM assumptions: each unit is unique, sellable once, and has exactly one state at a time. This page describes what the system covers.

Short answer

MPANDO Sales OS is the operations layer of the MPANDO ecosystem. It manages unit inventory, customers, options and reservations, offers and approvals, payment plans, presentation history, analytics and commissions — and shares its inventory with the MTWIN digital twin so both show the same state.

Inventory as the core

Everything in Sales OS is organised around the unit. Each record carries block, floor, number, type, gross and net area, aspect, price and current state.

State moves through a defined lifecycle — available, on option, reserved, contracted, sold — and the system enforces that only one party can hold a unit at a time. That is the guarantee a spreadsheet cannot provide.

Options carry a duration. When it expires without progression, the unit returns to available automatically rather than sitting blocked because someone forgot to release it.

Commercial workflow

Offers are generated from the unit rather than typed from scratch, so price, area and payment terms cannot drift from the inventory record.

  • Pricing authority: who may discount, by how much, and what approval it passes through
  • Payment plan generation: deposit, instalments, interim payments and handover payment
  • Offer approval routing, with a record of who approved what and when
  • Presentation history: which unit was shown to which customer, and when
  • Commission and entitlement calculation across representative, team and external agency

Shared inventory with MTWIN

The reason Sales OS and MTWIN are described as one ecosystem is that they read the same inventory. A representative walking a buyer through the twin sees live price and availability on the same screen, and generates the offer from that same flow.

That removes the most common failure in property sales presentation: showing a unit enthusiastically and then discovering it was reserved that morning.

Multi-project and multi-channel

Sales OS supports multiple projects and phases in one deployment, with permissions separable per project and reporting available both per project and consolidated.

External sales channels can be given scoped access — for example an agency that sees only its own customers and its own entitlements, without visibility into the full pipeline.

Frequently asked questions

Can Sales OS run without MTWIN?+

Yes. Sales OS deploys independently. If MTWIN is added later it reads the same inventory, so no rebuild is required.

Can we import our existing inventory spreadsheet?+

Yes. Unit schedules import from spreadsheets once block, floor, type, area and price fields are made consistent — part of the setup step.

Does it handle multiple currencies?+

Currency presentation is configurable per market, which matters where a project is sold to both local and overseas buyers.

How are commissions calculated?+

Against configurable rules by representative, team and external channel. The stage at which commission is earned — reservation, contract or collection — is a setup decision.

Can agencies be given limited access?+

Yes, through role-based permissions scoped to their own customers and entitlements.

What reporting is available?+

Inventory position, sales velocity, pipeline by stage, representative performance and commission liability, available per project and consolidated.

Last updated: · Guides on mpandoglobal.com ↗

Map it against your sales process.

Share your project count, unit volume and current workflow, and we will scope the deployment.