Business OS
Stop running your business between spreadsheets and disconnected tools.
A Business OS is custom business operations software: it connects your records, your work and your decisions in one operational system built around your company. Your existing tools stay where they work; the system keeps them in step, gives every task an owner and turns the weekly report into something you open rather than build.
Every task with an owner, every number with a source.
-
Onboarding Waiting on client
Ashby & Co: engagement letter signed, ID documents outstanding
Owner: Priya
-
Delivery Needs approval
Marlow Studio: scope change requested, above the approval limit
Owner: Sam
-
Billing Ready to send
Northgate: milestone two signed off, invoice drafted
Owner: Leah
-
Sales Follow-up due
Two proposals unopened after five days
Owner: Omar
01 The weekly chase
Your people have become the integration.
Each tool is fine on its own. The trouble is the space between them, and the hours someone spends carrying information across it.
- 01
Collecting status
Someone messages each project lead on a Friday to ask where things stand, then waits for the answers. - 02
Reconciling records
The CRM says the deal closed at one price, the project tool has another scope and the invoice has a third. - 03
Finding the latest number
Three versions of the pipeline spreadsheet circulate, and the meeting starts with which one is right. - 04
Chasing owners
Nobody knows who is waiting on whom, so approvals sit until someone senior notices and asks.
02 Before and after
From people as connectors to shared records with owners.
Illustrative map of a typical service business. Which links can be automated depends on what each tool’s API and your access allow; we confirm each one before building it.
An operations manager
copies, chases and reconciles by hand
- Sources
- CRM, project tool, accounting, email, forms
- Shared records
- Client · Project · Invoice, one version each
- Actions
- Assign, approve, remind, create the invoice
- Owners
- A named person for every step and every exception
03 What changes
Four things you will notice in the first workflow.
Less duplicate work
A client, project or invoice is entered once and kept in step across the tools that need it, so people stop copying between tabs.Clearer ownership
Every piece of work has a named owner and a next step, so a handoff can’t quietly fall between sales and delivery.Faster approvals
Requests reach the right person with the context attached and can be approved in one place, instead of waiting in an inbox.Reliable visibility
Reports come from the records the work runs on, so the numbers on Monday are the numbers, and each one traces back to its source.
04 A connected workflow
Lead to report, with the exceptions handled.
Illustrative: a fictional accounting and advisory firm. The happy path is easy; what makes a system trustworthy is what happens when a step doesn’t go to plan.
-
01 · Lead
A referral arrives by email and is logged with its source.
Exception: Already a client? It joins their record instead of becoming a duplicate. -
02 · Sale
The proposal is accepted and the deal is marked won in the CRM.
Exception: A discount beyond the agreed limit waits for a partner’s approval first. -
03 · Onboarding
The client record, engagement letter and document checklist are created, with an owner.
Exception: Documents missing after a set number of days: a reminder goes out, then the owner is told. -
04 · Delivery
The project is set up in your project tool from the agreed scope.
Exception: A scope change is recorded against the project and priced before work starts on it. -
05 · Billing
A signed-off milestone becomes a draft invoice in your accounting software.
Exception: If the accounting connection fails, the invoice is queued and finance is alerted rather than it vanishing. -
06 · Reporting
Pipeline, work in progress and billing are reported from the same records.
Exception: Records with missing fields are listed for their owners instead of skewing the totals.
05 Dashboard or system
Reporting alone won’t repair a broken process.
A dashboard tells you an approval is late. It can’t route the approval, remind the approver or record the decision. Sometimes seeing is enough; often it isn’t.
If your processes work and you only need to see them, a custom dashboard is the smaller, cheaper answer.
| Question | Read-only dashboard | Operational system |
|---|---|---|
| What it does | Shows numbers from your tools | Shows the numbers and lets people act on them |
| When something is wrong | You see it, then go and fix it elsewhere | The exception has an owner and a next step in the same place |
| Handoffs between teams | Not covered | Triggered from the record, with context attached |
| Approvals | Not covered | Routed to the right person, with a record of the decision |
| Data quality | Reports whatever the tools contain | Checks records as they are created and flags gaps to their owners |
| Right when | The processes work and you only need to see them | The work itself breaks between tools |
06 Who it helps
The same records, a different week for each role.
Founder
One view of pipeline, work in progress and billing that you trust without asking for it, and fewer decisions waiting on you because the routine ones follow rules you set.Operations
Handoffs, reminders and approvals run from the record, so you spend the week on exceptions instead of chasing status.Sales
A won deal starts onboarding without a briefing email, and you can see when a client you sold to is waiting on delivery.Delivery
Projects arrive with the agreed scope, the client’s documents and an owner, and changes are recorded before the work grows.
07 How it is put together
Connections, data, access and rollout, in plain terms.
The technical work, explained at the level you need to make decisions about it.
- 01
Integration
We connect to each tool through what it supports: a documented API, webhooks, scheduled exports or, at worst, a file drop. What is possible depends on the tool, your plan and the access your administrator can grant. We confirm each link before promising it. - 02
Data mapping
We agree which tool is the source of truth for each field, such as the client name, the price or the status, and how records in different tools are matched, so the system never has two competing answers. - 03
Access and permissions
Roles decide who sees which clients, figures and documents, and who can approve what. Connections use accounts and keys you own, with the least access each one needs. - 04
Migration
Spreadsheets and old records are cleaned, deduplicated and moved in on a dry run first, checked with the people who know the data, then moved for real. - 05
Phased rollout
One workflow goes live first, run alongside the old way briefly, then the old way is switched off. The next workflow starts only once the first is in daily use.
08 Start small
Start with one costly workflow.
Pick the workflow that wastes the most time or money today, usually onboarding, the sales-to-delivery handoff or the weekly report. Build it, use it for real, and expand only once it has proved itself.
If a tool turns out to be the problem rather than the gaps between tools, replacing it is a separate decision. Our keep, connect or replace guide covers how we make it.
What stays
- Your CRM, project tool and accounting software, where they do their job
- Email, calendars and the chat your team already uses
- The people who own each stage of the work
What changes
- Copying records between tools by hand
- The weekly status chase and the spreadsheet report
- Approvals by email and handoffs by memory
09 Is this for you
When a Business OS is worth building.
It is a real investment of time on both sides. These are the signs it will pay its way, and the signs it won’t.
A good fit when
- You run a growing service business on several decent tools that don’t share records.
- Someone spends hours each week assembling reports from exports.
- Handoffs between sales, delivery and finance depend on people remembering.
- You can name the one workflow that costs you most today.
Probably not when
- You use one or two tools and the numbers already add up.
- Your core tools have no API or export and can’t be changed.
- You want a read-only dashboard and your processes work well.
- You are looking to replace every tool at once.
10 Questions
Before you map anything.
What exactly is a Business OS?
Can you connect every tool we use?
Isn’t this just a dashboard?
Do we have to stop using our CRM or project tool?
How do you handle permissions and sensitive data?
Where do we start?
Map your tools and workflows
Map the tools and the gaps between them.
List the tools you use and the workflow that costs you most. A partner replies within one business day, and the first call ends with a map of what can connect, what can’t and where to start.
- A partner reads every enquiry
- A 45-minute working call
- A written scope you can decide on
Or write to us at [email protected]
Internal tools & dashboards