The Business Machine: Core Work
Working page for The Business Machine.
Core work
This page turns The Business Machine into a working session. The goal is to see the business clearly: how work actually moves, where it breaks, and what that costs you. Redesigning the business on paper is a separate exercise.
Every business is a machine. Inputs come in. Transformation happens. Outputs go out. The difference between a business that scales and one that just gets busier is whether the founder can see that machine clearly enough to improve it without being inside every step.
The ARCAS sequence for this chapter
- People and ownership - Who touches the work at each stage? Where do handoffs happen? Where does work wait for you specifically?
- System clarity - Is the process documented or does it live in people's heads? Can a new hire follow it? Can the team follow it when you are not available?
- Technology and AI leverage - Where could automation or AI remove repetitive steps - but only after the underlying process is clear and stable?
A founder you might recognise
Last year, the founder of a 24 person fitout company in Al Quoz was watching his team deliver good work and clients come back, while every project felt like the first one. There was no template for quoting, no standard handoff between the design team and the site crew, and no process for tracking change orders. The founder estimated every quote himself. He reviewed every design. He approved every material purchase above AED 1,000 (USD 270).
In one quarter the team ran three projects at once. Two finished late. One went over budget by AED 40,000 (USD 10,890) because a change order was approved by a site supervisor over WhatsApp without checking the original scope. The founder was in a client meeting when it happened. Nobody knew the approval limits because they were never written down.
He did not have a people problem. He had a machine visibility problem. The work moved, but nobody could see how it moved, and nobody knew the rules for when things went off track.
Mapping your machine
Step 1: Draw the value chain
Take a blank page. On the left, write "Client first contact." On the right, write "Delivered and paid." Now draw every step between those two points.
Include:
- How enquiries arrive (website, referral, cold outreach, social)
- What happens after first contact (who responds, how fast, what they say)
- How a prospect becomes a client (proposal, call, contract, handshake)
- How work is assigned (who decides, who does it, who checks it)
- How work is delivered (timeline, format, handoffs)
- How payment happens (invoicing, collection, follow-up)
Do not draw the ideal process. Draw the real one. Include the parts that are messy, inconsistent, or dependent on specific people.
Step 2: Identify the leaks
Now look at your map and mark every point where one of these happens:
- Bottleneck: Work waits for one person (usually you) before it can move forward
- Inconsistency: The quality or speed of work depends on who is doing it that day
- Invisible step: Something important happens that is not written down or acknowledged
- Rework loop: Work comes back because it was not right the first time
- Revenue leak: Value is delivered but not captured - unbilled time, scope creep, underpriced work
Most businesses have 3 to 5 significant leaks. You do not need to find all of them. You need to find the one that costs you the most.
One leak that catches UAE founders off guard is Emiratisation (the UAE programme that sets targets for hiring UAE nationals into private sector skilled jobs). If your company has 20 to 49 employees in one of the 14 targeted private sectors, MoHRE (Ministry of Human Resources and Emiratisation, the UAE body that runs labour rules including Emiratisation) measures a required Emirati hire count, not a percentage. The 2024 and 2025 SME-track targets carried financial contributions of AED 96,000 to AED 108,000 (USD 26,140 to USD 29,410) per missing UAE citizen target. This is a machine design problem, not a hiring problem. If you add headcount without planning roles that can absorb Emirati hires with structured onboarding, clear KPIs (key performance indicators, the numbers that tell you whether a specific part of the business is working), and a real progression path, you hit the requirement unprepared and the fine becomes a recurring structural cost. Factor it into your value chain the same way you factor in rent or insurance. It belongs on the map. Verify the current target and applicable sector list in Appendix G: UAE Compliance Essentials before planning headcount.
Step 3: Calculate the cost
Pick your biggest leak and estimate what it costs you per month. Be rough - precision is not the point. Awareness is.
- If the bottleneck is you reviewing every proposal: how many hours per week × your effective hourly rate = monthly cost of that bottleneck
- If inconsistent delivery causes rework: how many hours of rework per month × the cost of that time = monthly cost of rework
- If scope creep goes unbilled: estimate the average unbilled hours per project × number of projects per month = monthly revenue leak
Write that number down. It is the cost of an unclear machine.
Where to focus by team size
- 10 to 19 people: Map the value chain. You are the machine. See it clearly before trying to change it.
- 20 to 34 people: Identify the top 3 bottlenecks. At this size, the machine is straining and you need to fix the joints.
- 35 to 50 people: Document the full machine for your team leads. They need to see what you see.
Working prompts
Use these during your working session. Answer them honestly - they are designed to surface what is hidden.
People prompts
- If you were unreachable for two weeks, which parts of the value chain would stop completely?
- Which team members could describe the full journey from client contact to delivery - and which only know their piece?
- Where do people make decisions based on guessing what you would want, rather than a clear standard?
System prompts
- Which parts of your process exist only in someone's head?
- Where does "how we do it" change depending on who is doing it?
- If your best performer left tomorrow, which processes would suffer the most?
- What do you explain repeatedly to new hires that should already be written down?
Revenue prompts
- Do you know your actual cost to deliver each type of work - including your time?
- Where do clients get more than they paid for, and is that intentional?
- If you raised your prices 15% tomorrow, what would need to be true about your delivery for clients to say yes?
AI prompts
- Which repetitive steps in your value chain could be automated today without any risk to quality?
- Where does your team spend time on data entry, scheduling, formatting, or follow-up that a machine could handle?
- What would you automate if the process was clear and stable - and what is too messy to automate safely right now?
Founder exercise
This is the working session. Set aside 45 to 60 minutes. You can do this alone or with your most operationally aware team member.
Part A: The machine map (20 minutes)
Draw your value chain as described above. Use a whiteboard, a sheet of paper, or a digital tool. The format does not matter. The honesty does.
Include at minimum:
- Lead sources and volume (roughly)
- First response process and timeline
- Qualification and conversion steps
- Work assignment and kickoff
- Delivery milestones and checkpoints
- Invoicing and payment collection
- Post-delivery follow-up (if any)
Part B: The leak audit (15 minutes)
Mark every bottleneck, inconsistency, invisible step, rework loop, and revenue leak on your map. For each one, write:
- What happens here
- Who it depends on
- What it costs (time, money, or quality)
- How long it has been this way
Part C: The first move (10 minutes)
Choose one leak to address in the next 14 days. Pick the one where a fix is most achievable and the impact is most visible, even if it is not the biggest leak on the map.
Write down:
- The leak: What is happening
- The owner: Who will fix it (not you, if possible)
- The fix: What "better" looks like - specifically
- The signal: How you will know it is working within 14 days
Part D: Share it (5 minutes)
Share your machine map with at least one other person in the business, not for approval but to check if their version of reality matches yours. The gaps between your map and theirs are some of the most valuable data you will get.
Common mistakes
-
Mapping the ideal process instead of the real one. Your machine map is useless if it describes how things should work. Draw how they actually work, including the WhatsApp workarounds, the informal approvals, and the steps that only happen when you are paying attention.
-
Trying to fix everything at once. You found 5 leaks. You want to fix all 5. You will fix none. Pick the one with the highest cost and the most achievable fix. Get a win. Then move to the next one.
-
Mapping alone. The founder's version of the machine is always different from the team's version. The gaps between those versions are where the real problems live. Do Part D of the exercise. Share the map.
-
Confusing a busy machine with a working machine. Activity is not output. If your team is busy but revenue per worker is flat, the machine is consuming energy without converting it to value. Check your numbers before assuming the machine works.
When to move on
Move to the next chapter when you have drawn the machine, identified at least 3 leaks, calculated the cost of the biggest one, and chosen one fix with an owner and a 14-day timeline. You do not need a perfect map. You need a visible one that your team recognises as real.
ARCAS lens
The Business Machine is the first chapter for a reason. Before you can fix your time (Part 2), your team (Part 3), your systems (Part 4), or your AI readiness (Part 5), you need to see the machine clearly.
Most of what founders call "people problems" are actually machine problems. A team member who keeps making mistakes is usually working inside an unclear process. A client who keeps changing scope is usually working with an unclear value proposition. A salesperson who cannot close is usually selling an inconsistent experience.
Fix the machine first. Then everything else gets easier.
But first, you have to see it. The machine you cannot see is the machine you cannot improve.
Start now: Quick self-assessment
Rate each statement from 1 (never true) to 5 (always true):
| Statement | Your score |
|---|---|
| I can describe how work moves through my business from first contact to delivery in a clear, consistent way | |
| My team would describe the same process if asked independently | |
| A new hire could understand our core workflow within their first week | |
| I know exactly where work slows down or quality drops - and why | |
| I know the cost of our most significant operational bottleneck | |
| Our pricing reflects the value we deliver, not just the time we spend |
Score 24 or above: Your machine is visible. Move to the next chapter. Score 15 to 23: There are gaps worth closing. Work through the founder exercise above. Score below 15: This is where your biggest wins are hiding. Do the full working session before moving on.
Start of the reading sequence.
