The flagship · survey, build, operate
Your people spend their week re-typing what your systems already know.
Orders land in one tool, invoices in another, the truth in someone's inbox. That gap is where your margin goes. BusinessOS closes it — mapped first, then automated, then run for you.
- Survey first — you keep the map either way
- Built into the tools you already run
- One honest number, monthly
- Weeks 1–2 · Survey
Interviews, process walk-throughs, system access, document trails.
- Week 3 · Model
Verticals, workflows and stack written up, then validated with your team.
- Week 4 · Prioritise
Opportunities costed and ranked, walked through in one working session.
- Then · Build or stop
No build commitment. The document is yours either way.
Three stages
Survey. Build. Operate.
Each stage is a decision point, not a contract you're locked into. Most clients run the survey, act on two or three register items, and keep us on for the operating layer. Some run the survey and take it to their own team. Both are fine outcomes.
- Stage 01 · weeks 1–2
The survey
Two weeks inside your operation. We chart how orders, approvals, invoices and tickets actually move — the real map, not the org chart. You get the map whether you continue or not.
- Stage 02 · weeks 3–10
The build
AI and automation applied where the map says it pays — inside the tools you already use. Staged, tested, reversible. Nothing rips out what works.
- Intake & quoting
- Invoicing & follow-up
- Scheduling & dispatch
- Reporting & month-end
- Stage 03 · ongoing
The route, kept
We operate it, monitor it, and keep tuning it. Every month you get one honest number: hours back, days shorter, tickets gone. If the number stalls, we fix the route.
Stage 01 deliverable
The map is the thing you actually buy.
Two weeks in, you get a single sheet: every path work takes through your business, traced end to end. Solid where it moves by itself. Dotted where a person is retyping something a computer already knows.
The dotted runs are the whole argument. Count them, cost them, and the build plan writes itself. You keep the sheet whether you continue or not.
- Paths traced
- 5 of 5
- Steps walked
- 38
- Manual re-entry points
- 6
- Costed findings
- 23
Five paths, one sheet
Redrawn from a live client map. Stages are generic — the real ones are yours.
- Moves by itself
- Someone retypes it
- Handoff
- Where it lands
Six things we write down
The paths5 traced
Every route work takes from first contact to money in the bank, walked with the people who do it — not the version in the process document.
The steps38 steps
Who does what, in what order, with which keystrokes — including the handoffs nobody wrote down.
The systems9 stages
Every application in play, and how far across the operation each one actually reaches. Usually further and messier than anyone expects.
The re-entry points6 found
Each place a person retypes something a computer already holds, with the minutes it costs and how often it happens.
What already worksleave alone
The paths that are already clean. Named explicitly, so nobody spends money improving them.
The ranked register23 findings
A, B or C. This is the layer that becomes the build plan — and the one clients quote back to us two years later.
We don't publish anyone's map. Yours stays yours.
What lands on the last day
- D1
- Operating model — verticals, workflows and stack in plain language, diagrammed.
- D2
- Friction inventory — every stall point named, with hours per week attached.
- D3
- Opportunity register — ranked A/B/C, value against effort.
- D4
- 60-day plan — the first two builds, scoped and priced.
- D5
- IRAP package — the project framed the way the program reads it.
Fit check
- 10–200 staff, somewhere in Alberta, processes that grew by accident.
- Work moves between systems by hand, and month-end takes a week it shouldn't.
- You'd rather see the map before buying the software.
- You already know exactly what to build — skip to implementation.
"They spent the first month asking questions instead of selling us software. The list they came back with was uncomfortable and completely correct."
"Quotes that took a morning now take eleven minutes."
- 31 hrs
- saved weekly
- 9 days
- faster collections
- 0
- new tools to learn
Start with the map. Decide about building later.
Not sure? The survey stands alone — you keep the map either way.