Skip to content
Now booking 2026–2027
EN BM
Saif Muhtar Business Systems Educator
Saif Muhtar Business Systems Educator

Case study · the proof behind the teaching

Inside RumahHQ: a company that stopped running on its owner's phone.

RumahHQ is the company where Saif built and tested the Business Operating System (BOS) he now teaches, and the case behind his blueprint's construction track. This is how it moved from WhatsApp, spreadsheets and memory to one system of record, connected workflows and AI agents under human approval, with every workflow held to a written acceptance test.

See every workflow Invite Saif to speak
Company
RumahHQ · CIDB G4 design-and-build
Workflows
8 of 8 live
The rule
A person approves every consequential action
A finished front porch with feature lighting at dusk
RumahHQ project, Ijok

Saif Muhtar

20+

years in construction before teaching

What this system built: RumahHQ

  • 230+

    homes completed

  • 10+

    years building homes

  • 90+

    builders and engineers

  • 4.9★

    from 125 Google reviews

Company figures from rumahhq.com, as of 18 Sept 2026. Not Saif's personal record.

Context

A growing company with the owner in the middle.

RumahHQ designs and builds homes on clients' own land: drawings, local authority approval, LPPSA or bank financing, construction and handover. Every project touches clients, consultants, subcontractors, suppliers and lenders.

After 20+ years in construction, Saif was the link between all of them. Every enquiry, quotation and claim waited for him.

What a normal week looked like before the rebuild:

The original problem

  • Leads spread across WhatsApp and spreadsheets
  • Quotations need repeated data entry
  • Site updates are hard to track
  • Purchasing decisions happen informally
  • Customers keep asking for progress
  • Management reports consolidated by hand
  • Every decision comes back to the owner

The projects

Real homes, real projects.

Every workflow on this page exists to get houses like these designed, financed, built and handed over. Real RumahHQ projects, not illustrations.

  • A completed single-storey bungalow with a grey tiled roof
    RumahHQ project, Ijok
  • Steel roof trusses installed over the walls
    RumahHQ project, Ijok
  • A completed double-storey house with a covered car porch
    RumahHQ project, Saujana
  • A completed double-storey bungalow behind a white fence
    RumahHQ project, Kubu Gajah
  • A three-storey house at handover stage
    RumahHQ project, Hulu Langat

Saif's contribution

Designed the process first, then chose the tools.

Saif mapped how work moved through the company, wrote down the target process for each workflow, and set one rule for the tools: One Tool, One Role, Zero Overlap. One system of record holds the truth; one orchestration layer moves data; agents do routine work; people approve.

  • What Saif did

    The operating model, the process map for each workflow, the approval rules and the order of rollout.

  • What the team did

    Configured the system of record, tested each workflow against its acceptance test, and runs it every day.

  • Where partners helped

    Technology partners helped with the integrations between systems.

The construction track

What the blueprint asks of a construction company.

Construction is an excellent teaching case because it exercises every cycle at once: long sales cycles, customer financing, technical scope, permits, many subcontractors, heavy working capital and long warranties. These are the controls the blueprint sets for each step. They are the standard for any contractor, not claims about RumahHQ.

  1. Qualify

    Land status, financing route and approval readiness confirmed before design time is spent

  2. Scope and price

    Priced only from complete drawings and a bill of quantities; exclusions listed

  3. Contract

    Payment schedule tied to verified progress milestones; variation procedure agreed

  4. Approvals

    Clear split between contractor, client and qualified professionals (architect, engineer) for authority submissions

  5. Procurement

    Approved suppliers and subcontractors; materials received and checked against specification

  6. Delivery

    Daily site report with photos; weekly progress against schedule; safety briefing records

  7. Claims

    Progress claim submitted only with inspection evidence; collection owner named

  8. Handover

    Defect inspection checklist, as-built documents, warranty start date

  9. Warranty

    Defect log with response times through the defect liability period

Source: the BOS blueprint, Part 6, construction track.

Component 9 · Information & technology

RumahHQ's technology setup, at concept level.

These four layers are how RumahHQ installs component 9 and AI with guardrails. Roles and tools, not internal details. Walkthroughs of the real screens are part of in-house programmes.

RumahHQ operating system, concept level Enquiries from the website, WhatsApp and referrals reach a first-contact agent. An orchestration layer moves data into one system of record holding customers, quotations, projects, purchasing, claims and documents. AI agents draft follow-ups and reports. A guardrail check and human approval sit between every agent and the client. A management dashboard reads from the system of record. Website forms WhatsApp Referrals & walk-ins First-contact agent answers, qualifies, records Orchestration n8n · triggers, schedules System of record · ERPNext customers · quotations · projects · purchasing claims · documents · defects AI agents follow-ups · reports · drafts Guardrail check blocks unsafe outbound content Human approval owner & managers decide Client Management dashboard pipeline · progress · cash · claims
Concept level only. Every consequential action passes through human approval. Principle: One Tool, One Role, Zero Overlap.

  • 01

    One Tool, One Role, Zero Overlap

    Each tool has one job. Nothing holds a second copy of the truth.

  • 02

    One system of record

    Customers, quotations, projects, purchasing, claims and documents in one place.

  • 03

    Human approval

    Agents draft. A guardrail checks. A person decides before anything reaches a client.

Status

Every workflow, honestly labelled.

The problem each one replaced, the acceptance test it had to pass, and how it runs today.

RumahHQ workflows

8 of 8 live

Legend

Live
Passed its acceptance test; in daily use by the team.

  1. Lead & WhatsApp agent

    Before Enquiries lost in chats; slow replies

    Acceptance test Every enquiry is in the system with source and owner within 5 minutes

    Status: Live

  2. Quotation & BQ

    Before Repeated data entry; inconsistent quotes

    Acceptance test A quotation is generated from agreed BQ data without re-typing

    Status: Live

  3. Contract & financing documents

    Before Missing documents delay drawdowns

    Acceptance test A checklist shows every document per project and its status

    Status: Live

  4. Procurement & subcontractors

    Before Informal purchasing; no approval trail

    Acceptance test Purchases above a threshold need a recorded approval

    Status: Live

  5. Site reporting

    Before The office chases site for updates

    Acceptance test A daily photo report lands on the project record by 6 pm

    Status: Live

  6. Progress claims & drawdowns

    Before Claims late; cash flow invisible

    Acceptance test Claim status per project is visible on the dashboard

    Status: Live

  7. Defects & handover

    Before Defects tracked on paper

    Acceptance test Each defect has an owner, a due date and a closure photo

    Status: Live

  8. Management dashboard

    Before The owner consolidates reports by hand

    Acceptance test Pipeline, progress and claims refresh without manual work

    Status: Live

The mapping

Every workflow, mapped to the BOS.

The BOS components each RumahHQ workflow mainly serves. This is Saif's teaching mapping, not a maturity score.

  • Teaching mapping

    Lead & WhatsApp agent

    • 04Growth
    • 09Information & technology

  • Teaching mapping

    Quotation & BQ

    • 02Commercial model
    • 04Growth

  • Teaching mapping

    Contract & financing documents

    • 10Governance & risk
    • 07Finance

  • Teaching mapping

    Procurement & subcontractors

    • 05Fulfilment
    • 07Finance

  • Teaching mapping

    Site reporting

    • 05Fulfilment
    • 11Execution rhythm

  • Teaching mapping

    Progress claims & drawdowns

    • 07Finance

  • Teaching mapping

    Defects & handover

    • 06Customer success
    • 05Fulfilment

  • Teaching mapping

    Management dashboard

    • 11Execution rhythm
    • 09Information & technology

Results

Measured, or marked as being assessed.

A workflow being live is not the same as a proven result. Each figure is published only with its baseline, its period and its limits. Until then it reads “being assessed”.

Being assessed

Baselines are being recorded for each workflow. Figures will appear here with their baseline, period and limits, never before.
Baseline
How the work ran before the workflow.
Period
The weeks or months a figure covers.
Limits
What the figure does not show.

Lessons

What we learned, including what did not work at first.

  1. Process before tools.

    A workflow nobody has written down cannot be automated. It only gets faster at being inconsistent.

  2. One source of truth beats more apps.

    Every extra app that holds its own copy of a customer becomes another place where the truth goes stale.

  3. Approval is a feature, not a bottleneck.

    Staff trusted the agents once they could see that nothing reached a client without a person saying yes.

  4. Adoption takes longer than building.

    Configuring a workflow took days; changing the habit around it took weeks. Train supervisors first.

  5. Start where the owner is the bottleneck.

    Enquiries and follow-ups gave the earliest relief, because that work used to wait for one phone.

Next

Hear the full story on stage, or build your own in a workshop.

Saif walks through this case, mistakes included, in keynotes, workshops and in-house programmes, in English or Bahasa Malaysia.

Invite Saif to speak Bring the programme to your team
Explore the BOS