Every tool needs your operating model in a specific form. Nobody checks whether it is.
Salesforce needs the sales process documented. BI needs the data structured. AI needs everything machine-readable. The consultant discovers the form gap inside the engagement. $75–140K per function. Six to eight weeks. At implementation rates for specification work. Across a portfolio, that is $1.4–2.9M per year in form conversion nobody budgeted.
Your initiatives in. Your readiness out.
Name your initiatives
Salesforce. Procurement consolidation. AI deployment. The platform knows the full specification requirement for each. What the process must look like. What the data must look like. What the systems must support.
Feed the operating model
Drop artifacts. Point to people. The AI reads documents and conducts conversations — whichever speaks, the AI listens and checks what it still needs. Every input narrows the gap. Every gap directs the next question. The AI stops when it has enough. The AI already knows what Salesforce needs, what BI needs, what AI deployment needs. It checks whether your portco provides it.
See exactly where the gaps are
Not “your portco is not ready.” Exactly which requirements are met, which are not, and what specific work closes each gap. Every finding traces to an artifact the AI read or an answer it qualified.
Where your transformation dollar goes
Most portcos at close spend 80% of every transformation dollar on readiness nobody budgeted. After operating model specification, 85% goes to actual transformation.
The consultant adapts. AI stops.
The consultant arrives, finds the operating model is not in form, and quietly spends two months fixing it. The timeline slips. The budget overruns. But progress is visible.
AI does not adapt. AI arrives, tries to read the operating model, and stops. Day one. The form gap that the consultant absorbed over two months is a day-one blocker with AI. The more your 100-day plan depends on AI, the more the form gap matters — and the more expensive it is to discover late.
The AI already knows what your initiative needs
Salesforce needs the sales process in documented form. BI needs the data in structured form. AI needs everything in machine-readable form. Every tool has a form requirement. The platform holds them all. You name the initiative. The AI checks the portco against it.
Artifacts talk. People talk. The AI listens.
Drop process documents, data exports, system configs. The AI reads everything and maps it against what your initiatives require. Where artifacts leave gaps, the AI conducts targeted conversations grounded in what it already read. Not a survey. Not a questionnaire. Specific follow-ups that reference the documents it analysed. The AI stops when it has enough.
Specify once. Unblock multiple initiatives.
Salesforce needs structured customer data. BI needs structured customer data. AI forecasting needs structured customer data. Three initiatives. One form gap. The platform shows where initiative requirements overlap. Close one gap, unblock three deployments. No consultant surfaces this because each one operates inside their own engagement.
Every finding traces to what the AI read
Thomas confirmed no approval process exists. Sandra confirmed thresholds are carried in memory. The data export shows POs approved outside the delegation matrix. Click any finding. See the artifact it came from or the conversation that confirmed it. Full traceability to named sources.
Your 100-day plan, annotated
The output mirrors your plan. Each initiative shows deploy, prep, or defer. Each gap traces to specific evidence. The readiness cost per initiative is quantified. The IC gets the budget adjustment. The operating partner gets the evidence. The implementation partner gets the work order. Generated automatically from what the AI collected.
Use cases
Pre-LOI readiness screen for industrial target
Scan corpus analysis of 47 classified roles across 5 functions. 89% compensating. Preliminary triage identified procurement and quality reporting as likely deployment blockers for the planned automation play. Deal team adjusted the transformation budget thesis before LOI submission.
Representative scenario based on typical engagement patterns.
Who is it for
Deal teams
Operating model DD at close. Know the readiness cost before it enters the deal model. Scope the 100-day plan from confirmed state, not assumptions.
Operating partners
Pre-deployment readiness across every function your playbook targets. Source readiness work at operational rates before the consultant arrives.
Implementation partners
Receive a defined scope from day one. No discovery phase. The process specification exists. The data structure is documented. Start transforming, not discovering.
Enterprise-grade data handling
Assessment data is isolated per engagement. No cross-client data sharing.
Documents and responses encrypted in transit and at rest.
See what your 100-day plan is missing
15-minute call. We walk through your portfolio’s readiness signals. No commitment.