Ten scenarios. Different industries, different revenue stages, different problems — each showing what a Shadow Run or ScaleKorp OS install looks like when structure replaces owner dependency. Read the one that sounds like your business.
All case studies are illustrative. Specific identifying details are anonymised by default. Results are specific to each engagement. Individual outcomes vary based on business complexity, team execution, market conditions, and factors outside ScaleKorp's control.
Shadow Run · Electrical · WA
He knew every job in his head. Then he got sick for two weeks.
The situation
Mark had built a solid electrical contracting business over seven years. Eight staff, consistent work, good reputation. Revenue sitting just under $600,000 and growing steadily. The problem wasn't the work. The problem was that everything — every quote, every scheduling decision, every supplier relationship, every client expectation — lived in Mark's head. When he was on site, the business ran. When he wasn't, it waited. When he got sick for two weeks, three jobs were delayed, one client relationship broke down, and a staff member resigned because nobody could make a decision without him. Revenue that month dropped 40%.
The pain
“I kept thinking I just needed to work harder. Get more organised. Be more available. But I was already working 70-hour weeks. There was nothing left to give. The business wasn't growing. It was just getting more dependent on me.”
What was installed
A trades operating model pack — quoting standards so any senior staff member could price a job without Mark. Scheduling ownership transferred to an ops lead with clear rules for exceptions. Client communication templates in Talk, removing Mark from routine touchpoints. A weekly financial snapshot on Desk replacing the monthly EOFY surprise. Supplier relationships documented and distributed.
The outcome
Within 90 days Mark reduced his working week from 71 hours to 46. The business ran a full week without him present for the first time. Two staff members were promoted into defined roles. One new hire was onboarded entirely from documentation — Mark was not involved. Revenue held at $580,000 on materially fewer hours. The business stopped being Mark's job and started being Mark's asset.
ScaleKorp OS · Facility services · Perth
$1.8 million in revenue. No idea which jobs were actually profitable.
The situation
A commercial facility services operator with 28 staff across multiple service lines had grown to $1.8 million in annual revenue. Revenue was real. Margin was a mystery. The business invoiced consistently, chased debtors inconsistently, and had never tracked job-level profitability. The owner knew some jobs were good and some were bad. She did not know which ones, or by how much, or why. End of financial year, the accountant would deliver a number. That was the only moment financial reality became visible.
The pain
“We were busy all year. I assumed busy meant profitable. Then the accountant told me our net margin was 4.2%. I had 28 people working hard for 4.2%. And I didn't even know which jobs were the problem until it was too late to fix them.”
What was installed
Facility services operating model pack with job-level cost tracking connected to accounting software. A weekly financial snapshot on Desk — three numbers reviewed every Monday morning. Invoice follow-up automated through Talk, removing the receivables backlog that had been building for 18 months. Two service lines repriced after profitability became visible. One service line discontinued entirely. Staff accountability framework tied job performance to payment processing.
The outcome
Net margin improved from 4.2% to 11.8% within two operating quarters — not by growing revenue, but by stopping the margin leakage that had been invisible for years. The receivables backlog cleared in six weeks. Cash flow became visible four weeks forward. The owner stopped finding out how the business was doing at tax time and started knowing every Monday.
Shadow Run · Landscaping · Victoria
Six staff. Zero accountability. Everyone worked hard. Nobody owned anything.
The situation
A landscaping and grounds maintenance business with six full-time staff and solid recurring commercial contracts. Revenue at $480,000. The owner, David, couldn't understand why the business wasn't growing. The team worked hard. Clients were mostly happy. The pipeline was full. The issue was rework. Jobs were being revisited, corrected, or re-done at the business's cost because nobody owned quality standards. Each crew member had a different interpretation of what "done" meant. Client complaints went to David. Staff disputes went to David. Scheduling conflicts went to David. Every exception went to David.
The pain
“I'd finish a 10-hour day and feel like I'd done nothing. Because everything that actually moved the business forward — I hadn't touched. I'd spent the whole day being a referee.”
What was installed
General service operating model pack — role clarity with three staff moved into defined ownership of schedule, quality sign-off, and client communications. Job completion standards documented and distributed. A rework tracking system that made the cost of quality failures visible on Desk, not just to David. An escalation path through Talk that meant 80% of decisions never reached David. Weekly team meeting structure replacing ad hoc morning conversations.
The outcome
Rework rate dropped by more than half within the first operating quarter. David's direct involvement in day-to-day decisions reduced from constant to two structured touchpoints per week. Revenue grew 22% in the following six months — not because of new marketing, but because capacity consumed by rework and re-decisions was freed up.
ScaleKorp OS · Property services · Queensland
The business had grown. The systems hadn't.
The situation
A property services business — maintenance, inspections, and trades coordination — at $1.4 million revenue with 14 staff and growing. The owner, James, had built real momentum. New contracts were arriving. The team was capable. But every growth step created a new problem. New staff meant new onboarding chaos. New contracts meant scheduling conflicts. More revenue meant more cash flow unpredictability, not less. The business was growing faster than its systems could absorb.
The pain
“I kept hiring people to solve problems and it kept creating new ones. I thought I needed better people. I didn't need better people. I needed a system for the people I had to work in.”
What was installed
Property services operating model pack with a management layer — for the first time, James had a second-in-command with a defined charter, not just a trusted employee doing whatever needed doing. Staff onboarding documentation reducing time-to-productive from six weeks to twelve days. A capacity planning framework making hiring decisions data-driven. Multi-entity financial structure separating operating business from asset holdings. Weekly pipeline review on Desk replacing the monthly catch-up that was always too late.
The outcome
Two new hires in the following quarter — both onboarded without James present. Pipeline visibility improved from monthly to weekly. One contract repriced after capacity analysis revealed disproportionate margin consumption. James attended his first holiday in three years without receiving a single operational call.
Shadow Run · Plumbing · South Australia
Winning every job. Making money on none of them.
The situation
A plumbing contracting business with four staff and a pricing problem nobody wanted to name. The owner, Ryan, was winning almost every quote. Which sounds like success. It wasn't. When you win 90% of quotes in a trade business, you are the cheapest. And Ryan was — not by design, but because his quoting process was entirely intuitive. No cost model. No labour calculation. No margin floor. Just a number that felt right. Some jobs made money. Most broke even. A few quietly destroyed the profit from everything else that month. Ryan didn't know which was which until the accountant told him, six months after the damage was done.
The pain
“I was working harder than I ever had and I had nothing to show for it. My accountant kept asking why my revenue was up but my take-home wasn't. I didn't have an answer. I didn't even know how to find one.”
What was installed
Trades operating model pack with a quoting framework and minimum margin floor built in. Job cost tracking connecting quoted price to actual labour and materials. A simple go/no-go filter in Talk taking less than two minutes to apply. Two service types discontinued after the cost model revealed they had never been profitable. A weekly number on Desk — one number — telling Ryan whether the week was ahead or behind before the month closed.
The outcome
Quote win rate dropped from 90% to 58% within three months. Net margin increased from approximately 6% to 17% over the same period. Ryan stopped winning jobs he couldn't afford to win. Revenue grew 14% the following year on fewer total jobs — because the jobs were the right ones.
ScaleKorp OS · HVAC · New South Wales
Ready to hire a manager. No system for a manager to manage.
The situation
An HVAC and mechanical services business with 11 staff and $1.1 million revenue. The owner, Chen, had the right idea: bring in a senior operations manager. He had the budget. He had the candidate. He made the hire. Six months later the manager resigned. No documented processes to follow. No clear authority to make decisions. No data to manage from. No accountability structure the team respected. The manager had been given a title and a salary but no system to manage within.
The pain
“I hired someone good and I set them up to fail. Not because they weren't capable. Because I handed them a role without handing them anything to run. I realised I didn't need a manager. I needed a management layer first.”
What was installed
HVAC operating model pack — before making the next hire, the management layer was built first. Role charters defining what the operations manager would own. A weekly operating rhythm of meetings producing decisions, not status updates. KPI dashboard on Desk built for the manager to run from, not for the owner to monitor. An escalation framework in Talk defining exactly what came to the owner and what didn't. Subcontractor compliance documentation removing a major liability.
The outcome
A new operations manager hired four months later into a fully structured role. Within eight weeks, running daily operations independently. Business revenue grew 31% in the following year — the first year the owner was not the primary operational constraint.
ScaleKorp OS · Multi-service operator · WA
Wanted to acquire a business. His own wasn't ready to absorb one.
The situation
A multi-service operator at $2.3 million revenue had an acquisition opportunity. A competitor willing to sell. The numbers worked. The logic was sound. But the business ran on the owner's presence and informal processes. Adding another team, another client base, and more complexity to that would not compound returns. It would compound chaos.
The pain
“My accountant kept saying the numbers work. The advisors kept asking how I'd onboard their staff, who would own quality across both businesses, how I'd manage cash across two client bases. I didn't have answers. I was about to buy a problem and put it next to my existing problems.”
What was installed
OS install first — before any acquisition. Operating model consolidated across all service lines. Management layer with clear ownership of each vertical. Financial reporting unified across entities on Desk. An integration playbook built in advance. A 90-day integration plan template ready before the acquisition completed.
The outcome
The acquisition completed fourteen months after the initial opportunity — after the OS install was complete. Integration ran to plan. The acquired team onboarded in three weeks. Combined revenue reached $3.1 million in the first full operating year. "Last time I tried to grow I created chaos. This time I had a system that absorbed it."
ScaleKorp OS · Exit readiness · Security · WA
$3.4 million revenue. Not one buyer got past first-round diligence.
The situation
A security services business with 41 staff and $3.4 million revenue. Three potential acquirers in 18 months. All three withdrew during diligence. The feedback was consistent: revenue was real. The business was not transferable. Client relationships were personal — held by the owner, not by contracts. Financial reporting was built for tax, not for transaction. Key staff had no documented roles or succession paths. Buyers were not paying for revenue. They were paying for a business that could operate without its previous owner. This one couldn't.
The pain
“I had spent twelve years building this. Three buyers looked at it and said no. Not because it wasn't profitable. Because on paper it didn't exist without me. Everything real about the business was in my relationships, my knowledge, my presence. None of it was in the business itself.”
What was installed
Exit-readiness operating model pack — client contracts formalised and moved from personal to institutional relationships. Key staff documented in structured roles with defined authority and succession paths. Management reporting on Desk rebuilt for external scrutiny. Data room prepared and sequenced for the next diligence process. Owner dependency materially reduced through operational handover to two senior managers.
The outcome
Eighteen months after starting exit-readiness provisioning, a fourth approach resulted in a completed transaction. The buyer completed diligence in eleven weeks — compared to average four weeks before withdrawal in the three previous attempts. The business sold. The previous version could not have.
Shadow Run · Pest control · Queensland
Staff turnover was destroying his business. He thought it was a people problem. It wasn't.
The situation
Eight staff. $520,000 revenue. Seven staff departures in 18 months. The owner, Ben, had spent months refining his recruitment process, changing job ads, raising pay rates. Nothing changed the retention pattern.
The pain
“I genuinely thought I was just unlucky with people. Then someone asked me what the right ones would actually be walking into. I couldn't answer. There were no systems. No standards. No structure for them to operate within. I wasn't hiring bad people. I was putting good people into a situation that didn't work.”
What was installed
Specialist services operating model pack — staff onboarding documentation with every role, every standard, every expectation written down before the next hire. A quality sign-off process removing ambiguity about what "done correctly" looked like. A client relationship structure attaching clients to the business, not to individuals. A performance framework on Desk making expectations visible before problems developed. Pay structure reviewed and simplified.
The outcome
Zero staff departures in the nine months following the OS install. Two new hires onboarded — both productive within two weeks, both still employed. First full-time admin person onboarded from documentation in four days without the owner present. Revenue grew 19% in the following year, driven entirely by capacity unlocked when the turnover cycle stopped.
ScaleKorp OS · Construction · New South Wales
Strong revenue. Great reputation. A business that would fail the moment he stepped back.
The situation
$2.1 million revenue. Twelve-year reputation for quality delivery. Owner at 54, not looking to sell — looking to work less. Every attempt to step back had ended the same way. Something went wrong. A client escalated. A cost blew out. Michael was pulled back in. Not because his team was incapable. Because the standard lived in his head, not in the business.
The pain
“I've built something real. I'm proud of it. But I'm 54 and I'm still working like I'm 34. The business needs me in the same way it needed me ten years ago. Nothing has changed. I've built a job, not a business. A very good job. But still a job.”
What was installed
Construction operating model pack — quality standards documented at the job level, so what Michael knew intuitively was written down and embedded in delivery. Project management framework with clear ownership at each stage. Financial control pack with margin visibility by project on Desk, not just by quarter. Two senior project leads given defined authority and accountability for the first time. A scale-readiness checklist — explicit conditions before any expansion.
The outcome
Within four months Michael took his first two-week holiday in eleven years. One client issue arose while he was away. His senior project lead resolved it without contacting Michael. The client was satisfied. Michael found out when he returned. "I came back to a business that had run itself for two weeks. Not perfectly. But properly. For the first time."
