MOS Core
Four rails · every desk
The operating floor. Enquiry to signature, signed to handover, hazri to papers to payroll, and a command rail that sees all three. Hosted, role-gated, auto-refreshing.
Montera · Cockpit
Every desk.
One screen.
MOS is the operating system a design-and-build firm actually runs on. Enquiry to signature. Signed to handover. Hazri to payroll. Four rails, an agent layer that carries the repetitive half of the work, and one instrument panel over all of it.
What it is
MOS was not bought. It was built on the floor.
It started because the work was scattered. A pipeline in one tool, site updates in a group chat, materials in somebody’s head, and a weekly meeting to reassemble the picture badly.
So the firm built its own. Every desk got a screen that shows only that desk’s work, and above them all sits a cockpit that shows the whole business as gauges: speed, load, temperature, what is on fire. It is used every day by the people it was built for, which is the only real test software passes.
MOS is that system, packaged for other firms that run the same shape of work.
Fig. 01 · System map
Five layers, one database.
A CRM stores what happened. MOS runs what happens next. Read the frame from the outside in: the people who touch it, the agents that carry the repetitive half, the four rails the firm works on, the systems it plugs into, and the floor it all stands on.
Your firm
Interfaceshow a person meets it
- Phone app (PWA)
- Field link · PIN + device-bound
- Desk browser
- Vendor link
- Client link
Agent layerthe work that runs without being asked
- Intake agent
- Voice agent
- Mail intelligence
- Listening desk
- Vision
- Vendor coordinator
- Marketing mind
- Mechanic
- Media engine
MOS corefour rails, every desk in the firm
- Grow · enquiry → signature
- Deliver · signed → handover
- People & Money · hazri → payroll
- Command · see everything
Connectorsthe systems you already pay for
- WhatsApp Business
- Gmail / Workspace
- Google Calendar
- Google Drive
- Google Ads
- Slack
- Voice telephony
- Card payments
- Bank statement import
- Higgsfield
- Frontier models
Data & reliabilityone database, row-level locked, fully instrumented
- Postgres + row-level security
- Role and device grants
- Telemetry on every run
- Model cost per call
- Issue register
- Nightly systems scan
Fig. 01 · one hosted instance per firm · role and device grants at the row
Scope of supply
Seven parts
Agent layer
Intake · voice · mail · listening · vision
Nine named processes that carry the repetitive half of the work: qualify and book, draft the reply, transcribe the meeting, read the delivery note, chase the vendor, watch the numbers.
Field layer
Phone app · field links · hazri
Every man on ground reachable without an app install. A link with a PIN that binds to the first phone that opens it, a daily board of who is on which site, transport out and back, PPE, and a photo-led stock count.
Money layer
Cost heads · POs · invoices · payroll
Receipts to a cost head and a bill-of-quantities line, requests to purchase orders to delivery evidence, proforma and tax invoices in their own series, payroll computed off attendance rather than memory.
Media engine
Higgsfield · stills → motion
Plugged in since 18 September. Site photography becomes short motion for the firm's own marketing, generated server-side with the per-call cost written to telemetry. Image-to-video is wired; restyle and upscale stay switched off until the platform documents them.
Reliability suite
Telemetry · issue register · scan
Every cron, model call and agent run lands in one table with a status, a duration and a cost. The Systems desk turns failures into a register with fingerprints, so a bug that comes back is marked as returning rather than filed twice.
Install & operate
Rails first · then agents
Your sites, your people, your rate book loaded on the rails, then the agents switched on one at a time so each one earns its place. Continued operation, incident handling and iteration on real transcripts.
The agent stack
Nine processes. Each one gives the hour back and keeps the decision.
An agent here is not a chat window bolted to a database. It is a named process with a job, a cost per run in the telemetry table, and a written line it does not cross. The right-hand column is that line.
01
Intake agent
Enquiry → qualified → booked visit
Answers on WhatsApp and on the site at human speed, in the enquirer's language. Sizes the job into a ticket band, holds the thread, and books the visit against the team's real free/busy rather than a form's idea of next week.
Stops hereHands over the moment money, scope or a promise is in question.
02
Voice agent
The design consultation call
Outbound and inbound calls on a real number, with the enquirer's file in front of it: what they asked for, which community, what was quoted. The call is transcribed, summarised and attached to the client row.
Stops hereNever negotiates price and never confirms a date the calendar has not held.
03
Mail intelligence
Drafts in thread, never sends
Reads the mailbox, tracks the threads that matter, and writes the reply in the house voice with the attachment already on it — in the original thread, so the client sees a conversation and not a new message.
Stops hereEvery draft waits in Drafts for a person to read and send.
04
Listening desk
The meeting, written down
Rolling transcription of a live meeting or site walk, so decisions land as text with who said them, instead of in somebody's notebook.
Stops hereOwner-only by design; it is not a surveillance tool pointed at staff.
05
Vision
Photographs and documents → rows
Reads a delivery note, a petty-cash receipt, a passport page, a bill of quantities, a shelf of stock. What comes out is a row with a number and a cost head, not a file in a folder nobody opens.
Stops hereThe model describes; the code decides. Anything unreadable is flagged, never guessed.
06
Vendor coordinator
Packages, prices, chasing
Breaks a job into trade packages and takes them out to vendors blind — no client name, no rival's number, no target price — then levels what comes back into a comparison you can sign against.
Stops hereA purchase order is issued by a person against a budget line.
07
Marketing mind
Spend, search terms, content
Watches the advertising accounts and the search terms daily, proposes the change with the number that justifies it, and can apply it through the API rather than asking someone to find the right screen.
Stops hereTurning spend up is a human decision, taken one command at a time.
08
The mechanic
It repairs its own floor
Reads the telemetry, reproduces the failure, proposes the patch, and opens it for review. Staff report a bug from the screen it happened on and it arrives with the context already attached.
Stops hereNothing reaches production without a human merge.
09
Media engine
Higgsfield, server-side
Your own site photography animated into short motion for the firm's marketing, queued and polled server-side, with the cost of every call written next to it.
Stops hereNobody at work is put on a permanent display without consent.
The desks
Four rails
Every name below is a screen in the running system, not a roadmap. A person only ever sees the desks their role opens, and the rails are switched on in the order the firm needs them.
Grow
enquiry → signature
- Funnel
- Leads list
- The Floor
- Conversations
- Visits
- Design
- Design team
- Proposals
- Rates book
- Marketing
- Referral partners
Deliver
signed → handover
- Pre-construction
- Projects & programme
- Programme templates
- Operations floor
- Daily report-in
- Materials & buying
- Purchase orders
- Site stock
- Stock census
- Packages to price
- Vendors
- Service contracts
- Cost control
People & Money
hazri → papers → payroll
- Site people & hazri
- Transport & drivers
- Field day board
- PPE
- Petty cash receipts
- People & HR
- Offers & e-sign
- Hiring
- Payroll
- Papers collection
- Accounting intake
- Invoices & accounting
Command
see everything
- Cockpit
- Command deck
- The Wall
- Pulse
- The liaison line
- Listening desk
- Savings
- Adoption
- Access switches
- Assets & access
- Systems & telemetry
- Forge · the mechanic
- Site map
Six of them, up close
01
Cockpit
The whole firm as an instrument cluster.
Six gauges and a bank of warning lights. Messages in per hour. Men on ground. Enquiries today against a target of five a day. Things on fire. Sites reported. When a clock goes red it does not wait to be found. It lights up on the panel.
02
Command Deck
Every desk, one screen. Auto-refresh five minutes.
Four rails carry the business end to end. Grow runs enquiry to signature. Deliver runs signed to handover. People & Money runs hazri to papers to payroll. Command sees everything. Nobody has to remember where a thing lives.
03
Funnel
A phoned-in enquiry becomes a booked visit.
Capture is a phone number. Booking needs a slot, a community and a villa address, because the forty-eight-hour on-site promise needs a gate. Hand it to the agent and it carries the thread: qualify, book, brief the design call, quote, all of it visible on the Floor and on the project page.
04
The Floor
One row per client. Red clocks first.
Qualify, Book, Visit, Design, BOQ, Present, Decide. Every client sits in exactly one stage with a clock running on it, and the list sorts itself so the overdue ones are at the top. There is a breach-free streak counter, and it is honest about being at zero.
05
Conversations
Every thread, and who has the wheel.
The last word said, on every open thread, most recent first, refreshing every three minutes. Full transcript one click down. From the same row you can leave a note, set a category, or book the visit, without opening another tab.
06
Proposals
BOQ to published quote, with the clock attached.
Priced packages off the bill of quantities, lines fixed, previewed, then published with tracked links and forty-eight-hour codes. You know it was opened. The twenty-one-day decision window runs on the Floor where everyone can see it.
Live snapshot · 24 Sept 2026, 16:10 GST
It shows you the red first.
Counted off the running instance, not a marketing mock-up. The same table that carries these counts carries the failures, with a status and a cost on every row — which is the only reason a number on this page can be trusted at all.
8,040
machine runs · 7 days
866
model calls · 30 days
228
enquiries carried
457
vendors on file
141
workers on the roster
5
min refresh cycle
Operating doctrine
Instrument the hour before you try to buy it back.
An owner cannot hand off an hour nobody has measured. So MOS measures first: where the day actually goes, which is chasing a quote, re-asking a site for a photograph, and reassembling a picture that should have assembled itself.
Then it hands those hours to the agent layer, one at a time, each one earning its place against the number it was supposed to move. The intake agent qualifies and books. The design call gets briefed without being asked. The reply is drafted in the thread. The delivery note becomes a row with a cost head on it.
What is left on the owner’s desk is the decision, and the red clock next to it. That is the whole design goal.
Put the whole firm on one panel.
MOS is opening to a small number of firms. Six questions about how your work runs today, and we come back with the cockpit mapped against your own shape of business.
Six questions · about two minutes · no obligation