You already forked Schefren's "Your OS" for yourself — Shepherd OS at shepherd-os.pages.dev. Vision 1 is the same architecture, but for the company. Modules instead of skills. Subroutines instead of agents. Boot-in dashboards instead of "how do I find anything." The mental model your builders inherit is yours.
shepherd@springbok-os ~% system status ──────────────────────────────────────────────── SPRINGBOK GROUP OS v0.1 READY Builders online : Sian · John · Leo Modules production : 12 Modules staging : 3 Users active today : 47 / 64 KPI delta this week: BR% +2.1 CANX% −0.8 £+£18.4k
Every Springbok role is a function: input lead → output instruction, input instruction → output exchange, input call → output coaching note. Roles, KPIs, SOPs — these are interfaces between functions. An OS doesn't just decorate that truth; it enforces it. Builders ship modules. Modules expose services. Users invoke services. Everything is observable.
A module is a self-contained capability with a clear input, output, and KPI it moves. Example: PAC Call Coach takes a transcript, returns a coaching note, moves BR%. It runs every night without a human pressing a button.
A service is a module exposed to a user. The PAC team doesn't know there's a module — they just see "your last 5 calls coached" in their morning brief. The OS hides the engineering and shows the value.
Only registered builders — Sian, John, Leo today. Each builder has a namespace (/builders/sian/) and can only ship into their own. The OS won't let them touch each other's code or data.
You. Every install passes through /staging first. You approve from a single screen. No skill goes live to users without you having seen it. No surprises.
A builder lands on the Hub, signs in with their Springbok email, and is dropped straight into their console. Same shell as yours, scoped to their business. The whole experience is built on the assumption they'll spend ≤2 hours a week here — the rest of their week is their actual job.
Single sign-on with Springbok email. Console opens to their namespace. Pre-loaded with 5–8 starter modules curated for their role.
One screen of integrations. Click "Connect Simbacloud." Click "Connect SpeechIQ." Click "Connect Fireflies." OAuth handled, credentials encrypted, scoped to their namespace only.
Type a one-line description of the module they want ("score every PAC call, flag below-threshold ones to me"). The OS scaffolds it. Builder reviews + tweaks. Submits to staging.
You approve in staging. Module moves to /production. Goes live in users' dashboards. Builder sees usage stats and the KPI it's moving in real time.
A PAC, a progressor, a listings admin — they don't see modules or builders or staging. They see one screen tailored to their role: what AI did for them overnight, what's flagged for them today, what KPI they own and where it's at. Five second reads, then back to work.
Shepherd OS exists. The team seeing the same shell when they log in is a continuity move — they know it works for you, so they trust it. Zero "what is this thing" learning curve at the top.
They build CRM modules in Simbacloud daily. The OS framing maps perfectly to how they already work — you're not asking them to learn a new metaphor, you're naming the one they use.
When you acquire next year, the new business gets a namespace and boots into the same OS. Same Hub URL, same shell, same governance. Acquisitions integrate in days, not months.
A PAC who sees "modules" and "namespaces" and "staging" might think "this isn't for me." We can soften the user track to disguise it (the morning brief mockup above already does), but the builder track is unmistakably operator-flavoured. If you have builders who are non-technical (someday Shelly at FloraCare, maybe), they'll need extra hand-holding.
If a buyer walks Springbok next year and your team's morning Hub looks like a mission control terminal, it might not match the "premium estate agency" brand. Vision 5 (Boardroom) handles this better. Vision 3 (Operations Manual) splits the difference.
Three builders boot in (Sian, John, Leo). Their starter modules pre-loaded.
One user-facing morning brief lands in 50 inboxes Tuesday 9am.
You see the Shepherd console showing the whole thing breathing.