A signed Novo Match engagement activates a chain of stages, obligations, gates and handoffs. The dashboard had to control that chain—not simply restate what the founders already knew—while making every unconnected provider visible instead of declaring premature autonomy.
Evidence at publication: the client-safe dashboard, onboarding portal, Fireflies ingestion path, guarded Calendly connector and S0-S6 operating model are built. Full live operation still depends on client-owned Google, Close, messaging, email and real employer inputs, so the case is explicitly provider-ready.
The company
Lennert Körbs and Julius run Novo Match, a German social-recruiting and recruitment-marketing company serving employer SMBs. The business combines sales, employer onboarding, campaign setup, delivery quality, reporting, candidate handoff and guarantee management.
Demand and founder knowledge were present. So were useful tools, recruiting funnels, outbound activity and call-capture material. But the operating model still depended on people remembering what should happen next across WhatsApp, calls, audit documents and follow-up.
The constraint
Each new employer engagement creates a chain of obligations: sales context must reach delivery; assets and access must arrive; campaigns must be built and approved; candidate forwarding must be clear; reports must go out; guarantee clocks must remain visible.
When those obligations live in memory, the founders remain the exception handler for every project. Vendor dashboards may show isolated activity, but they do not encode Novo Match's full delivery standard or expose which missing dependency is blocking the next stage.
Why existing tools were not enough
A CRM can hold opportunities. A calendar can hold calls. A transcript platform can record a conversation. None of them automatically creates the project structure, approval deadline, asset gate, reporting cadence and guarantee state implied by a signed client.
The missing layer had to model Novo Match's own operating system. It also had to be provider-aware: a disconnected account should appear as pending, not be masked by a polished interface.
Transformation map
Before
Sales call + Fable audit + WhatsApp + vendor dashboard -> founder remembers handoff -> manual onboarding and follow-up
After
Sales handoff -> S0-S6 project state -> onboarding/access gates -> build and launch -> run/optimize -> reporting + guarantee clock -> retention or offboarding
The dashboard is the control surface for this sequence. It is not evidence that every provider in the sequence is already connected.
One workflow, end to end
- Input: A new employer moves from sales toward delivery with its call and project context.
- Project creation: The operating layer prepares the relevant S0-S6 state and assigns readiness requirements.
- Onboarding: The client-safe portal collects or displays access, assets and outstanding decisions.
- Handoff: Sales context, call material and delivery requirements become visible to the operating team rather than remaining with the founders.
- Gates: Approval deadlines, launch readiness, candidate-forwarding rules and missing provider connections stay explicit.
- Run and report: The model supports weekly-report obligations, KPI watcher rules and ongoing optimization state.
- Guarantee and retention: Guarantee/refund tracking and offboarding requirements remain part of the same project record.
This is the designed provider-ready path. It should become a normal live workflow only after client-owned connections and real employer submissions pass final QA.
What changed
- Built: A client-safe dashboard, employer onboarding portal, AI Brain surface and responsive mobile/tablet shell.
- Modeled: Novo Match's deeper operating lifecycle across S0-S6 stages, sales-to-delivery handoff, onboarding, build, launch, optimization, hiring/offboarding and guarantee/retention.
- Prepared: Operating tables for project state, reporting, handoff, readiness, access, assets, approvals and guarantee clocks.
- Connected in readiness: Fireflies ingestion/reporting and a guarded Calendly connector have defined paths.
- Preserved: The Fable 5 Sprint audit remains source context rather than being flattened into generic dashboard copy.
- Provider dependency remaining: Google Drive, Gmail, Calendar, Close, WhatsApp/Slack, email, real employer submissions and final provider QA are not represented as fully live.
- Financial result reported by client: None retained.
Proof
- Interface receipt: Overview, Onboarding, Sales Pipeline, Reports, Calls, Approvals, AI Brain, Connections, Alerts and Settings surfaces are present.
- Operating-model receipt: S0-S6 stages, weekly reporting rules, KPI watcher logic, sales handoff and guarantee/refund tracking are encoded in the source architecture.
- Integration receipt: Fireflies and Calendly have prepared or guarded paths; Composio supports the Google adapter route.
- State clarity: The system can distinguish ready, pending and client-dependent work.
- Boundary: There is no claim of autonomous campaign delivery, completed provider-wide activation or measured founder time saved.
Technology - revealed last
The foundation runs on a client-owned Hostinger VPS with HTTPS, Caddy, the Novo Match dashboard service, onboarding routes, workflow and QA tables, business-brain data paths, provider adapters, Fireflies ingestion/reporting, Composio Google Super adapter support and a guarded Calendly connector. The architecture anticipates Google Workspace, Close, WhatsApp, Slack and future outreach data without pretending those client-owned routes are active today.
Client quote
No source-backed verbatim client quote is published. The proof is the built operating model and its visible provider-readiness boundaries.
Next transformation
See how Care Networks separates authoritative recruitment records from a gated voice pilot. It shows a different recruitment business at a later state in selected provider lanes.
Get your AI blueprint
If your agency's delivery quality depends on founders remembering every handoff, gate and deadline, start by encoding the operating lifecycle. Book a free AI audit to map it before connecting providers.
Source record
OPENCLAW-DEEP-CLIENT-CASE-STUDIES.pdf, page 21.RECAST_CASE_STUDIES_2026_UPDATED.pdf, page 17, documentRA-CASES-001, version 2.0.RECAST_WEBSITE_MASTER_BLUEPRINT.md, sections 10.4, 11 and 58.