Springbok already runs on procedures. Aaron's PAC team has 15 standards. Mark's progressors have 14. Listings has its checks. Sian and John literally build playbooks for a living. Vision 3 turns that culture into the Hub itself: every skill is a procedure, every dashboard is an instrument, every builder action is a checklist item.
Open any role description in your business. Aaron's PAC manual: 15 numbered procedures. Mark's progression team: 14. Listings: full QA flow. Sian writes them, John approves them, Stephen enforces them. The natural language of your company is numbered, ordered, named. We're not inventing a new metaphor — we're naming the one already there. The difference: a procedure used to be a PDF in a folder. Now it's a procedure that runs.
SOP 4.2.7 lives in SweetProcess. Sian trains it in a workshop. Aaron reminds his team. By Tuesday, half the team has drifted from it. By Friday, Sian and Aaron are coaching the same gap again. The procedure is a document that hopes to be followed.
SOP 4.2.7 is a procedure in the Hub. It runs every night against every PAC call. It produces a coaching note for each rep. Sian sees the patterns by Monday. Aaron 1:1s the right reps. The procedure is now a process that enforces itself.
Their day-job vocabulary stays exactly the same — procedure, standard, KPI, checklist, audit. The Hub layout mirrors the Springbok manual: Volume → Section → Procedure. Each procedure has steps, references, owners, KPIs, and a status (DRAFT / STAGING / IN-FORCE).
A PAC opens the Hub at 9:01 am. The Hub presents one thing: today's checklist. It looks like a flight crew's pre-flight — because the metaphor matters. Items are pre-ticked where AI has already done the work. Items still open are the ones requiring the human. Then it gets out of the way.
Their job is writing procedures. Their day is structured around them. The Hub doesn't ask them to learn "modules" or "skills" — it asks them to write more procedures, exactly like they already do. The vocabulary fits the role. Adoption friction approaches zero for the two pilot builders.
A procedure that runs on every call cannot be drifted from. A PAC can't skip step 4.2 because step 4.2 is the AI checking step 4.2. Stephen and Aaron stop spending 1:1 time enforcing standards — the Hub does that — and start spending it on the things that need a human (motivation, edge cases, hiring).
FloraCare runs on procedures (CQC-mandated). Acquisitions runs on procedures (your screening criteria). Future businesses will run on procedures. Same Hub, same metaphor, different volumes of the manual. The brand also scales: "Springbok Group runs on a single operations manual" is a story buyers like.
Marketing thrives on creative ambiguity. Shehnaz's team won't love being framed as "procedure operators" — and "Procedure 7.4: Generate Ad Variants" might feel reductive of the work. We can soften by allowing certain sections to be more flexible (Volume 7 = Marketing, with looser structure), but the Manual identity is a commitment.
The serif fonts, numbered sections, ruled paper feel — they communicate "serious operational document." That's a feature for Sian, John, Mark, Ellen. It might feel old to a 22-year-old PAC trainee. We can give the user-track a more modern surface, but if you mix metaphors too much you lose the cohesion.
Once your Hub looks like a manual, an out-of-date procedure looks worse than no procedure. You'll need a quarterly review cadence (Sian + John already do something like this, so it's incremental). But it's a real ongoing investment.
Volume 1 of the Springbok Operations Manual — Procedures 1.1 through 4.7 — go live in the Hub.
Sian and John each pick three procedures to "make executable" first.
Leo gets Volume 5 (Acquisitions) and writes the screening procedure that already exists in his head.
Tuesday 9:01 am, 50 PACs and progressors open their morning checklist.