Most of your team is not technical. They drive valuations, manage progressions, write listings. They do not want a console. The Concierge greets each person by name, asks what they need, and quietly does the rest.
Underneath, this is the same OS as Vision 1 — modules, builders, namespaces, governance. The difference is in the doorway. The Concierge greets every person personally, anticipates what they need, and never makes them feel like they're being handed engineering. The hard system is hidden behind a friend's voice.
No login flows, no settings menus, no jargon. Everyone gets the same homepage: their name, the date, three things ready for them today, one thing flagged for attention. Nothing else competes for the eye.
Sian, John, Leo see a checklist, not a console. "Here are 4 starter skills already built for you. Here's how to add a 5th — describe it in a sentence and I'll scaffold the rest." Building feels like writing a brief, not coding.
The first time Sian opens the Hub, she doesn't see Claude Code. She sees a personal welcome, a 4-step checklist, and starter skills already pre-loaded. The whole onboarding is designed to take ≤20 minutes — about as long as a cup of tea.
A negotiator, a progressor, a listings admin — none of them sees a builder console. They see one card-shaped homepage, in plain English. Their name. The date. What's ready. What's flagged. That's it.
You've already built call-coaching, daily briefings, director dashboards. The technology works. The question is whether 50+ people will actually use it. Soft + friendly + named-greeting wins adoption every time vs. terminal-flavoured tools. The Concierge optimises for the harder problem.
Springbok isn't a fintech. It's a property company that prides itself on speed, certainty, and trust. The Concierge feels like that brand — calm, hospitable, ready when you need it. The Operating System feels like AWS. You'd brand-align better here.
Sian is brilliant at L&D but she's not a developer. The Concierge keeps her in tea-and-checklist territory while still letting her ship real skills. She'll build more, not less, because the surface doesn't fight her.
If Sian or Leo wants to do something the Concierge doesn't suggest, they have to "drop into advanced mode" — which most people won't, even when they should. You'd lose some of the operator-class control that Vision 1 surfaces by default. We mitigate with an "advanced" toggle, but most builders won't flip it.
Every new module needs a friendly card and a plain-English description. That's design work. With Vision 1, modules can ship with technical names and no one cares. Here, every module needs to be brought up to "Concierge politeness" before users see it. More polish, slightly slower iteration.
Stephen, Jenna, Shehnaz might find this too soft. Sales directors in particular like the data-density of mission control. They may want a "directors' view" that's denser. We can build one, but it's another surface to maintain.
Sian opens her welcome screen. Three steps already ticked.
Tomorrow, 50 people open their morning card and read three things in 90 seconds.
The OS is doing the work. Nobody can tell. That's the point.