For businesses with 5–50 staff that have outgrown spreadsheets and manual coordination

Your business does not need another tool. It needs one part of the operation to finally run properly.

If staff keep asking for updates, work depends on memory, customer information sits in multiple places, and nobody is fully sure who owns the next step, the problem is not usually the software.

It is the operating system underneath the work.

The Business Operating System Sprint is a fixed-price, four-week engagement where I rebuild one operational workflow into a clear system your team can actually run.

Process redesign, workflows, databases, forms, dashboards, reporting, automation, documentation and training may all be involved. But the technology is not the product. The product is a part of the business that stops relying on chasing, memory and guesswork.

Before
Staff chase updates and ask who owns the next step
Build
One workflow redesigned into a clear operating system
After
The team knows where work lives and what needs action

"Thaha understood our needs quickly and was able to advise on ways to improve the design."

— Claire Given, Equipmii

Operating system problem

The symptoms are usually familiar.

The business is moving, but too much of the movement depends on people remembering, asking, chasing and patching the gaps.

Updates live in people, not the system
Managers have to ask staff what changed because the workflow does not make progress visible.
Ownership is unclear
The next step exists somewhere between email, chat, spreadsheet notes and someone’s memory.
Reporting takes too long
The information exists, but producing a useful answer still means chasing, cleaning and checking.
Processes depend on specific employees
When the person who knows how it works is unavailable, the process slows down or stops.
Simple test: if the business works only because people keep checking, reminding and explaining, the operating system is doing too little.

The symptoms usually look small until they start controlling the business.

symptom

Staff keep asking for updates

Managers become the reporting system because the actual system does not show what is happening clearly.

symptom

Nobody owns the next step

Work moves through email, chat, spreadsheets and calls, but the next action is not obvious or assigned.

symptom

Customer information lives in more than one place

One person checks the CRM, another checks a spreadsheet, someone else remembers the real story.

symptom

Reporting takes hours

The data exists somewhere, but producing a useful answer still means chasing people and cleaning information manually.

symptom

Processes depend on specific employees

If the person who knows the process is unavailable, the process slows down or stops.

symptom

Software does not talk to the way the business works

The tools are there, but the workflow around them is still held together by manual coordination.

One operational area rebuilt into a reliable way of working.

The sprint focuses on one business area. Not the whole company. Not a vague transformation project. One workflow that matters enough to fix properly.

For that area, I map what actually happens, remove unclear handoffs, design the records and statuses, build the views and dashboards, add useful automation where it helps, and document how the team should run the process.

Enquiry to quote
Lead intake to follow-up
Order tracking
Client onboarding
Recruitment or hiring workflow
Service delivery handover
Customer support escalation
Stock, assets or internal requests
Reporting and management visibility
Approval or review workflows

You leave with a working operating system, not a slide deck.

Workflow review and process map
Redesigned stages, ownership, statuses and handoffs
Central records for the work being managed
Forms or intake routes so work enters cleanly
Dashboards and views for staff and managers
Reporting that shows progress, blockers and workload
Automation for reminders, updates and repeated steps where useful
Documentation so the team knows how to use the system
Handover session and practical training
Post-handover fixes and adjustments
The exact build depends on the workflow. The point is not to force your business into a template. The point is to build the operating system that this part of the business actually needs.

Choose the right level of help.

lower-friction diagnostic

Operating System Audit

For cautious buyers who want clarity before committing to a build.

Review of one workflow
Diagnosis of current gaps
Practical operating system roadmap
Recommended records, dashboards and automation opportunities
Build estimate and next-step plan

Best when you know something is broken but want a clear plan before implementation.

Recommended
best value

Business Operating System Sprint

The core fixed-price four-week engagement to rebuild one operational workflow into a usable business operating system.

Typical first sprint
Around $2,000

Final scope confirmed after review.

Discovery and process mapping
Workflow redesign
System structure and records
Forms, dashboards, views and reporting
Useful automation where appropriate
Documentation, handover and training
Post-handover adjustment period

Best when one part of the business is important enough to stop patching and fix properly.

larger operational change

Business Operating System Programme

For businesses that need multiple workflows or departments rebuilt over time.

Multi-workflow roadmap
Phased implementation
System governance
Team adoption support
Reporting across departments
Ongoing improvement cycles

Best when several areas are held together by spreadsheets, disconnected tools and staff memory.

Why not just buy better software?

Software can store information. It does not automatically create a business operating system.

Most businesses already have enough tools. The issue is usually how the work moves between people, records, decisions and follow-ups.

A useful operating system answers questions like:

Where does this work start?
What information must be captured?
Who owns the next step?
What status means the work is blocked?
What should managers see without asking staff?
Which updates should happen automatically?
What does the team do when something changes?
How does the process continue when someone is away?

The tool matters. But the workflow matters more.

How the sprint works.

01

Diagnose the workflow

We review how the work currently moves, where it gets stuck, who is involved and what information is missing.

02

Design the operating system

We define stages, ownership, records, views, dashboards, reporting and what should or should not be automated.

03

Build the system

I build the workflow in the most sensible tools for the job, using your existing stack where possible.

04

Test with real examples

We test real work through the system and adjust the parts that create confusion.

05

Train and hand over

Your team gets documentation, a handover session and a practical way to run the workflow after the sprint.

good fit

Good fit if the business has grown faster than the way work is managed.

You have 5–50 staff and work is becoming harder to coordinate.
One operational area creates repeated confusion or chasing.
Managers cannot see progress without asking people.
Customer, project or task information is spread across tools.
You want a practical system your team can actually use.
not a fit

Not a fit if you only want another tool installed.

You want software installed without process changes.
You expect one sprint to rebuild the entire company.
Your team will not participate in clarifying the workflow.
You want generic automation without ownership or reporting.
You are looking for a cheap template rather than a working operating system.

Questions before booking a review.

Is this automation?

Not mainly. Automation may be part of the solution, but the sprint is about fixing how one part of the business operates.

Do we need to change software?

Not necessarily. I usually start with the tools you already use and only recommend changes if the current setup cannot support the workflow.

What can be done in four weeks?

One clearly scoped operational workflow can usually be mapped, redesigned, built, tested and handed over. Multiple departments usually need a programme.

Who is this for?

Founders, Managing Directors, COOs and Operations Managers in small businesses that have outgrown spreadsheets, disconnected tools and manual coordination.

What do we own at the end?

The process, structure, documentation and system built for your business. The setup should be clear enough for your team to run and improve.

Why is the Sprint recommended?

It is the best balance between diagnosis and implementation. The audit gives clarity, the programme handles larger change, but the sprint fixes one meaningful workflow without turning it into a long project.

business operating system sprint

Fix the workflow your team keeps working around.

Bring the area that creates the most chasing, confusion or manual reporting. I’ll help decide whether it needs an audit, a focused sprint or a larger operating system programme.