Scope
What we run, what you keep, and the line between them.
01 — The steps
How an engagement runs
-
01
Discover
Thirty minutes on the workflow, the tools and the numbers. We look for work that is repeated, unowned, or blocking your team — and we tell you plainly if we are not the right fit.
Day 0 · 30 minutes
-
02
Design
We write the standard: what the output looks like, who reviews it, how fast it turns around and what it costs. Delivered inside two working days, including what we would not take on yet.
Days 1–2 · in writing
-
03
Pilot
One workflow runs first, with weekly reviews. Small scope on purpose: it proves the standard, the reporting and the people before anything scales.
Weeks 1–3
-
04
Run
The workflow moves to steady state and the scope widens — a second function, a second market, a second team — each time with a named owner on both sides.
Week 4+
-
05
Improve
A weekly report, a monthly numbers page and a quarterly reset where we recommend what to stop, what to automate and what deserves more of your budget.
Every quarter
02 — The rhythm
The week, in three rituals
- Monday, 20 minutes — one plan across every discipline: what is committed, what is at risk, what we are deliberately not touching.
- Wednesday — exceptions only. What broke, what slipped, what needs a decision. Anything fixable never reaches the meeting.
- Friday — one page of numbers: cash, pipeline, work delivered, tickets open, hours against plan. Same eight numbers every week, so a trend is visible.
The value is not the meetings. It is that every discipline knows when its output is consumed by the next one — which is why delivery survives holidays, handovers and growth.
03 — In writing
What you always have
Standard
What a correct output looks like, in plain language.
Owners
One name on your side, one on ours, per workflow.
Report
Weekly: what moved, what slipped, what is next — numbers, not adjectives.