The VCP — Value Creation Protocol

The methodology that carries
the intelligence. Not the people.

The VCP is Denacom’s engagement methodology and the software application that runs it. Five phases — configured to the gap profile the Readout surfaces. Focused engagements run in 90 days. Complex situations run longer. The scope, the team, and the timeline are defined before the contract is signed. The diagnostic intelligence is encoded in the system — any trained engagement lead can deliver it at quality, without founder involvement in every decision.

Five phases

The phase framework is a proven diagnostic and delivery structure — not a fixed pipeline every engagement runs through identically. The Readout defines which phases apply, in what depth, and over what timeline.

Day ranges shown reflect a focused engagement baseline. Complex engagements extend the timeline proportionally — the phase structure and overlap logic remain the same.

0
Days 0–7
Trigger — Engagement Configuration

Activation is not a sales process. The engagement lead is assigned within 24 hours. NDA and SOW are executed within 72. The value creation thesis is reviewed. Initial access is secured. The kickoff session is a pre-diagnosis briefing — not a discovery call.

Output: Signed scope document with success metrics tied to the value creation plan — not Denacom’s metrics.
1
Days 1–21
Diagnosis — Operational Baseline

Three simultaneous tracks: Commercial & Financial (revenue quality, EBITDA bridge, working capital), Operational (C-suite structured interviews, process mapping, capacity audit), and Data & Systems (what data exists, where it lives, whether it is trustworthy). The goal is an honest operational baseline — before anyone designs a solution.

Output: The Operational Gap Register — every material gap catalogued by area, severity (EBITDA impact), effort to close, and owner. No internal vs. external version. The PE firm sees it. Management sees it.
2
Days 14–45
Design — Build Specification

The Gap Register becomes a build plan. For each priority gap: the target operating model, the process change required, the operational infrastructure configuration that supports it, and the KPI that proves it is working. Maximum 12 KPIs per engagement. Every KPI traces to EBITDA or growth trajectory. No vanity metrics.

Output: The Operational Design Document — a build specification, not a recommendation deck. First data connections go live during Diagnosis, so design is validated against real data before the document is final.
3
Days 35–75
Build — Operational Infrastructure

Four sequential layers, each used by management as it goes live. No big reveal at the end. Layer 1: data connections — source systems connected, management sees their numbers in one place. Layer 2: process workflows — new workflows live, not documentation of old ones. Layer 3: performance dashboards — KPIs live, baseline vs. current visible. Layer 4: alerting and cadence — automated flags, weekly operational rhythm embedded.

Output: Functioning operational infrastructure, deployed in layers, in active use by management throughout.
4
Days 66–90
Stabilize — Clean Exit

Denacom exits cleanly. The operational infrastructure runs without us. Management operates independently for a minimum of two weeks with Denacom in standby before formal exit. The Exit Memo is not a victory lap — it is an honest accounting of what moved, what did not, and what the management team needs to execute next.

Output: Exit Memo: EBITDA impact vs. baseline, Gap Register closure status, infrastructure operational status, open items with named owners.

The intelligence is
in the system.

In a traditional consulting firm, diagnostic quality depends on the seniority of the person in the room. The VCP eliminates this dependency by encoding the methodology — the questions, the branching logic, the contradiction detection, the gap weighting — in the application itself. A trained engagement lead runs the VCP. The system tells them what to ask, what the answers mean, what gaps to prioritize, and what to build.

Capability Traditional consulting VCP encoding
Next question Knowing what question to ask next Adaptive branching logic — the AI probes vague answers, extends strong ones, and flags contradictions in real time
Contradiction detection Recognising when signals conflict across domains Cross-domain contradiction detection — automatic, flagged before the live session
Gap weighting Understanding what a gap means for EBITDA Gap weighting with EBITDA impact scoring and industry-calibrated benchmarks
Phase transition Knowing when discovery is complete Phase transition criteria — objective, not judgement-based
Build spec Briefing the execution team from memory Blueprint Register derived directly from diagnosis — no briefing, no context loss
Deliverable Knowing what to build and leave behind Build spec derived from diagnosis — no assumptions, no fixed product imposed

The VCP is what you sign
after seeing the Readout.

The Readout is free. No commitment before you see what the instrument produces.