The lead arrives in one place and lives in another
A portal enquiry, a WhatsApp message, a referral from a past client, a walk-in. Each enters through a different door, and the business only finds out later which door was worth keeping open.
Built from inside real estate · United Arab Emirates
OSSOT
The Real Estate Operating System
A real-estate business is not a transaction. It is a connected operation — leads, brokers, clients, deals, documents, compliance, commissions, and the relationships that outlast all of them. OSSOT is the system that runs it as one.
The operating problem
Nothing breaks in the deal. Everything breaks between the deals.
Ask a brokerage where it loses money and the answer is rarely the negotiation. It is the handover between people and systems — the places where the business has no memory.
What the broker knows, the company does not
Relationship history sits in a phone. When the broker leaves, the client relationship leaves with them — not because anyone intended it, but because the business never held the record.
Compliance is reconstructed, not recorded
The documentation exists. It just exists in an inbox, a drive and a WhatsApp thread, and someone spends a week assembling it whenever it is actually needed.
Commission is the last thing anyone trusts
Split across a referrer, a lister, a closer and a manager, then adjusted. When the calculation lives in a spreadsheet, every payout becomes a negotiation about arithmetic.
How OSSOT is built
Software that follows the operating model, not the other way round.
Most platforms entering real estate were built somewhere else first and adapted afterwards. The shape shows. They model a pipeline well and a business poorly, because a pipeline was the part the original product already understood.
OSSOT started from the other end — from the friction of running a real-estate operation, and from the fact that no two of them run the same way. A brokerage with sixty agents and a developer selling its own inventory are not the same business with different labels. They have different chains of custody over a client, different definitions of a stage, different money.
So the system is configured around the operating model rather than asking the operating model to bend around the system. That is the whole design position, and everything else follows from it.
Real Estate. Operated.
Five letters. Five parts of the same operation.
The name is the scope. Each letter is a part of the business the system has to carry, and not one of them works properly in isolation — which is the entire reason they belong in the same place.
- O Operations The daily running of the business. Process, ownership, approvals and the exceptions that quietly consume most of the week.
- S Sales Leads and pipelines, from the first enquiry to a signed deal, with the origin still attached when the commission is paid.
- S Service The client, investor and partner relationship — before the transaction, during it, and for the years afterwards that produce the next one.
- O Oversight Documents, identity, compliance and the record the business needs to produce on the day somebody asks for it.
- T Transactions Deals, commission structures and settlement, resolved by rule so that money reaches everyone entitled to it without an argument.
What it does
One operating record, across the whole chain.
Described at the level of what changes in the business. The implementation is deliberately not the subject.
01
Relationships that belong to the business
Every client, investor and tenant held as a company record with its full history — who introduced them, who has spoken to them, what they were shown, what they said no to and why.
02
Leads with an origin that survives
Capture from every channel a real-estate business actually uses, with the source intact all the way through to the commission, so you can tell which channels produce revenue rather than volume.
03
Pipelines that match your stages
Stage definitions are yours. Off-plan launch, secondary resale, leasing renewal and investor placement are different processes and are configured as such, not forced into one funnel.
04
Commission that computes itself
Multi-party splits — referrer, lister, closer, team lead, company — resolved by the rules you set, visible to the people they affect, and reconciled against what was actually collected.
05
Documents and compliance as a by-product
Identity, KYC, agreements and approvals captured inside the flow that needs them, so the compliance file assembles itself instead of being reconstructed under deadline.
06
Client and investor experience
A private view for the people you serve — their properties, their documents, their progress — so that keeping a client informed stops being a manual task performed by whoever remembers.
07
Partner and referral networks
Introducers, channel partners and referring brokers operating with defined visibility and traceable attribution, so a network can be paid correctly and therefore grown.
08
Operating reporting
Not a dashboard of activity. The questions management actually asks: where pipeline is stalling, which sources justify their cost, what is committed versus collected, and who is carrying the business.
Different businesses, different shapes
Configured around how you operate.
The same operating layer, arranged differently depending on what the business actually is.
- Lead to commission Real-estate brokerages
- Launch to sellout Property developers
- Tenancy to renewal Property management
- Entity to consolidated view Real-estate groups
- Enquiry to ongoing ownership Investor experience
- Introduction to settlement Partner and referral networks
- Process to governed workflow Real-estate operations teams
Connected experiences
The chain, end to end.
Each link is a place where most businesses hand off between systems and lose something. Holding them in one operating record is the point of the platform.
- Enquiry
- Broker
- Qualification
- Viewing
- Offer
- Documentation
- Compliance
- Transaction
- Commission
- Ongoing relationship
One operation
The same record, seen from wherever you sit in the business.
A lead arrives, a broker takes it, a client relationship forms, a deal progresses, documents accumulate, compliance attaches, a commission resolves, and the relationship carries on. In most companies each of those lives in a different place. Here they are one continuous record, and each role sees the part of it they are responsible for.
01
Broker
02
Operations
03
Compliance
04
Finance
05
Management
One operating record
Why the product is not published here
You will not find a full screenshot tour on this website, and that is deliberate rather than coy. Screens without your data in them prove very little, and the parts of OSSOT worth judging — how it holds your commission structures, your stages, your compliance obligations — only become legible against a real operating model. So the product is walked through properly in a working session once we know enough about the organisation for it to mean something. It is also, frankly, how we keep the operating detail out of a competitor’s hands.
What it is not
A CRM records the relationship. OSSOT runs the business around it.
OSSOT holds relationships, pipelines and contact history, and does it properly — that part is table stakes and we are not going to pretend otherwise. But a customer-relationship system is scoped, by definition, to the relationship. It is the right shape for a sales team and the wrong shape for a company.
The things that actually decide whether a real-estate business scales sit outside that scope. Whether the source of a lead is still attached when the commission is calculated. Whether the compliance file assembles itself or gets reconstructed the week somebody asks. Whether a broker leaving takes eleven years of client history with them. Whether the payout everyone agreed to is the payout the spreadsheet produces.
Those are operating questions, not relationship questions. They are answered by the system the business runs on, and that is a different category of thing — which is the entire reason this one has a different name.
Bespoke
When the operating model will not fit a product.
Some organisations do not have a configuration problem. A group running brokerage, development, management and investment under one roof does not operate like any single one of them, and no off-the-shelf product is going to describe it. That work is designed, not selected.
Why this exists
Fifteen years inside the market, before a line of it was written.
OSSOT was not specified in a product workshop. It came out of roughly fifteen years of working inside real estate in this region — long enough to watch the same failures repeat across very different companies, and to notice that they were never really software failures.
They were failures of memory and handover. The business could not remember what it already knew, and could not pass it cleanly between the people who needed it.
That is an unglamorous thing to build for. It is also the thing that decides whether a real-estate company scales or simply gets busier.
15
How we work
We do not run trials, and we do not sell by the month.
An operating layer is not a tool you evaluate for fourteen days. Changing how a business runs takes migration, configuration, training and a season of real use before anyone can judge it honestly. A vendor who lets you leave in thirty days has quietly told you they never intended to change how you operate.
So engagements begin at a minimum annual commitment, with quarterly, semi-annual or annual payment. Annual payment carries the most favourable terms. Commercial terms are structured around the organisation, platform scope, number of users, operational requirements and level of customisation.
And because a year is a real commitment on both sides, we qualify before we start. Not everyone should be a client, and finding that out early is worth more to both of us than a demo.
Insights
Written for operators, not for search engines.
Developer Operations
A launch sells out or it leaks, and that is decided before the doors open
Inventory release, allocation discipline and broker registration decide whether an off-plan launch clears or stalls. Written for a developer head of sales.
Brokerage Operations
Nobody loses attribution on purpose. It just does not survive to the payout.
Source attribution is captured at the enquiry and lost before the commission. The six places it dies in a brokerage, and what has to hold for it to survive.
Compliance
Trakheesi is not a form you submit. It is a state your system has to hold.
Every Trakheesi guide explains how to apply. This one is written for the operator who has to keep thousands of live advertisements compliant across channels.
Start a private conversation.
Tell us how your business runs today and what is failing. If OSSOT is the wrong answer, we will say so — that is a cheaper outcome for you than a year of finding out.