OD-1 — CSO Ratification: Services-Firm-with-Products Identity Bet

Authored by: Chief Strategy Officer atom — client-side enterprise Date: 2026-07-01 Status: RATIFY-WITH-REFINEMENTS — Brian Handrigan ratifies the final Subject: Covington Place Partners — identity bet: Services-Firm-with-Products Input docs read: cpp-strategy-brief.md · CPP-MASTER-BRIEF.md v2 · icps.md v1.1 · bigfour-counter-map.md HONEST-VERB rule applies throughout.

Verdict

RATIFY-WITH-REFINEMENTS.

The services-firm-with-products bet is the structurally correct call at CPP's current stage. I am ratifying it — not rubber-stamping it. Three specific refinements are required before execution proceeds; they are detailed below. The ratification does not change the fundamental identity direction. The refinements address measurement discipline, one ICP-specific positioning gap, and a tactical hole in the no-pricing-on-site decision.

Gate 1 — Structural Competitive Diagnosis

The causal mechanism, not the positioning story.

The GSD brief names the bet correctly but does not fully surface the mechanism. Here it is in falsifiable form:

CPP's three products (AI Cost Optimization, AI Governance & Audit, AI Dev OS) are built on a grāmatr platform. They are not CPP's engineering output — they are grāmatr-powered surfaces that CPP distributes under an advisory brand. This is the key structural fact that determines which identity wins.

If CPP leads with product identity:

• The buyer evaluates CPP against Securiti.ai, Palo Alto Prisma AI, CloudZero, Apptio, and GitHub-adjacent AI dev tooling. These are well-funded, established SaaS players with brand recognition, G2 reviews, and dedicated AE/CS teams. CPP has none of those. Advisory-native product provenance is not a recognized SaaS buying signal — it's a consulting selling point. CPP loses this comparison on every axis a product buyer uses to evaluate.

If CPP leads with advisory identity:

• The buyer evaluates CPP against boutique AI consulting firms, the Big Four AI practice arms, and specialist boutiques like Slalom, West Monroe, and Kin + Carta. CPP's structural differentiators here — vendor-agnostic as a revenue-model fact, senior operators who held the executive chair, $3,500 entry price that demonstrates confidence in process over fee extraction — are real and observable, not narrative claims. CPP owns the whitespace: not a Big Four (too expensive, junior-staffed, vendor-compromised) and not a boutique SaaS vendor (no single-product agenda). This position is defensible.

The mechanism that makes services-with-products the winner: ICP-A (CEO/COO) authorizes the Workshop. The Workshop output (3–4 prioritized AI projects) is the opening brief for at least one of three product conversations. The CEO/COO then becomes the internal sponsor who opens the CFO, CISO, or CTO to a CPP product conversation — with the trust already transferred from the advisory engagement. The product sells with advisory context pre-loaded, not cold.

This mechanism is CPP's moat in the product conversation. A competing AI governance SaaS that reaches a CISO cold must overcome "I don't know these people." CPP's CISO conversation arrives after the CEO has already said "I trust them." That trust transfer is not replicable by a product-first competitor without CPP's advisory relationship.

Falsifiability condition: This advantage erodes when ICP-A (CEO/COO) does not become the internal sponsor for product conversations — specifically when the post-Workshop product conversation rate falls below 40% of engagements within 90 days. If that signal fires, the mechanism is broken and the identity bet requires reassessment. Not the website copy — the strategy.

Gate 2 — Irreversibility Classification and Pre-Committed Kill Criteria

Classification: Structurally reversible with a 12–18 month correction cost.

This is NOT a one-way door. The website identity, homepage structure, and narrative arc can change within 90 days if required. What takes 12–18 months to unwind: thought-leadership brand associations built under the advisory identity, market relationships formed under this framing, and any sales hire decisions made under this model (advisory sellers vs. product AEs are different profiles).

Asymmetric rigor applied accordingly. This is not a platform-scale irreversible bet — it does not require the same deliberation depth as a capital commitment or market exit. The asymmetric risk is modest: if the advisory-first identity is wrong, the cost is 12–18 months of sub-optimal GTM positioning, not organizational destruction.

Pre-committed kill criteria — named before ratification accrues political cost:

These four criteria must be monitored actively. If any two fire simultaneously, the identity bet requires a formal strategic review — not a website refresh, a strategy review.

Kill Criterion 1 — Advisory-to-product conversion rate below threshold. If fewer than 40% of AI Opportunity Sprint engagements produce a follow-on product conversation (formal discovery call with a functional buyer — CFO, CISO, or CTO) within 90 days of Workshop delivery, the trust-transfer mechanism is not functioning. The advisory identity is not opening product conversations as designed. Review trigger: after first 10 Workshop engagements.

Kill Criterion 2 — Sales cycle exceeds operational viability. If average time from first qualified contact to signed engagement (Workshop or product) exceeds 120 days, the advisory-first motion is too slow to sustain the firm on its current revenue base. Advisory sales cycles are inherently longer than product trials — this is a known tradeoff — but 120 days is the viability threshold for a two-founder firm. Review trigger: month 9.

Kill Criterion 3 — No named client proof by month 12. The site strategy launches without verified client names, logos, or outcome metrics. The GSD strategy compensates with founder credentials and third-party research. This is viable for 12 months. If CPP reaches month 12 with no publishable client outcomes (at minimum, one named client willing to provide a testimonial and one quantifiable outcome CPP can attribute), the advisory identity has no proof infrastructure and the trust claim becomes increasingly brittle. Review trigger: month 12, no earlier.

Kill Criterion 4 — Product ARR below 15% of total revenue at month 18. The bet is services-with-products, not pure-services. If product revenue has not reached 15% of total revenue by month 18, the products are functioning as advisory outputs (enriching the services engagement) but not as separately transacted product relationships. This may reflect early-stage dynamics rather than a positioning failure — but it requires a named decision: is CPP a services firm that creates proprietary tools for internal use, or a services firm that distributes products for revenue? That decision has a different identity implication.

Gate 3 — Resource Allocation Logic and Opportunity Cost

The portfolio governing principle (stated before BU advocacy opens):

At CPP's current stage, founder attention is the binding constraint — not capital, not headcount. Every allocation decision is fundamentally about Shea Long and Mike Burns' time and credibility.

Primary allocation: Advisory delivery and inbound pipeline generation.

• Shea Long leads Workshop facilitation and AI strategy advisory. This is his structural differentiator (operator background as CPO across Centene, ModivCare, Alivi) and the mechanism that creates product conversations.
• Mike Burns leads healthcare/transformation advisory, thought leadership authorship, and partner/ICP-A relationship development. His 30+ years of healthcare marketing and digital transformation is the credibility that makes the mid-market healthcare wedge defensible.
• Both must author the Mid-Market AI Priority Matrix (GSD OD-3 decision) before the site launches if it is to function as a thought-leadership asset rather than a placeholder. This is a 1–2 day founder time investment with durable pipeline return.

Secondary allocation: Product oversight and grāmatr relationship management.

• CPP is NOT the engineering team for its products. grāmatr builds the platform. CPP's product allocation is oversight, QA on advisory-product fit, and client-facing product delivery. This is a PARTNER model — correct for this stage.
• The strategic risk in this allocation: CPP's product differentiation depends on grāmatr's engineering roadmap, not CPP's own capability. If grāmatr's governance product falls short of the 48-hour regulator export claim, CPP's advisory brand absorbs the damage. This is a build/buy/partner classification issue that requires a separate governance relationship with grāmatr (SLA on product delivery, agreed positioning claims, escalation path if product falls short).

Opportunity cost named explicitly:

Advisory-first means Shea Long and Mike Burns are in Workshop facilitation and advisory delivery, not in product sales cycles with CFO/CISO/CTO buyers who arrive cold. Under a product-first model, a product demo could qualify a prospect in 45 minutes without founder involvement. Under advisory-first, Shea and Mike are the qualification mechanism — which does not scale past approximately 8–10 new client conversations per month between them.

This ceiling becomes the constraint that forces the first non-founder hire. When advisory demand exceeds founder bandwidth, the next allocation decision is: hire an advisory seller (extends the advisory-first model), hire a product AE (shifts toward product-first GTM), or hire a senior delivery operator (extends workshop and advisory delivery capacity without extending pipeline). The correct answer at month 12–18, assuming the first kill criteria are not triggering, is the delivery operator — to free founder time for pipeline generation and product oversight.

Gate 5 — Assumption Tracking with Observable Falsification Signals

Five load-bearing assumptions, ranked by consequence-of-being-wrong:

Assumption 1 (HIGHEST CONSEQUENCE) — ICP-A trust transfers to ICP-B/C/D product conversations. The entire cross-sell model depends on this. If the CEO/COO exits the Workshop satisfied but does not become an internal sponsor for product conversations, CPP must run independent, cold sales motions to CFO, CISO, and CTO — a significantly more expensive and slower motion.

• Falsification signal (leading): In post-Workshop follow-up, does the CEO/COO make an introduction to the relevant functional buyer within 30 days? A rate below 50% of engagements indicates the trust transfer is weak.
• Knowable now or must be monitored: Must be monitored from first 5 engagements.
• Pre-committed response if signal fires: Revise Workshop output format to include a specific "next conversation" brief designed for the CEO to hand to their CFO/CISO/CTO — make the trust transfer structural, not incidental.

Assumption 2 (HIGH CONSEQUENCE) — Advisory brand can be built without published client proof for 12 months. Founder credentials and third-party research sustain the advisory trust claim through early pipeline. But ICP-A buyers with budget authority will ask "who have you worked with?" If the absence of named clients creates systematic deal stalls, the thought-leadership-only proof strategy has hit its shelf life.

• Falsification signal (leading): In qualified sales discovery calls (first 10), what percentage specifically ask for client references and stall when none are available? If >40% stall on this question, the 12-month runway assumption is wrong.
• Knowable now or must be monitored: Must be monitored from first qualified conversations.
• Pre-committed response if signal fires: Accelerate pursuit of even one publishable client outcome. If no real engagements are complete, a documented case study from a founding advisory relationship (even if not formally a paid engagement) may bridge the gap. Do not fabricate or overstate.

Assumption 3 (HIGH CONSEQUENCE) — grāmatr product delivers on CPP's positioning claims. CPP's AI Governance & Audit product positions on the 48-hour regulator export and three-layer governance (content/logical/physical). These are specific, verifiable commitments. If grāmatr's product does not deliver these in practice, CPP's advisory brand absorbs the failure — the client does not distinguish between the platform and the advisory firm.

• Falsification signal (leading): In first 3 product engagements, does the regulator export deliver within the stated 48-hour window? Does the governance firmness ladder operate as described in sales conversations?
• Knowable now or must be monitored: Can be partially pre-validated (grāmatr internal QA) before the first client engagement. This should be done BEFORE product is sold to ICP-C buyers.
• Pre-committed response if signal fires: Halt product sales until delivery shortfall is corrected. Never sell a capability CPP cannot confirm grāmatr can deliver.

Assumption 4 (MODERATE CONSEQUENCE) — ICP-A mid-market buyers want advisory-first, not product-first. The model assumes the CEO/COO will not buy an AI governance platform without an advisory relationship first. This is likely true for the majority of mid-market operators in healthcare and telecom (risk-averse, process-oriented, trust-based purchasing). It may not be true for tech-adjacent mid-market companies or for CEOs who have already been through a digital transformation and are product-purchase-comfortable.

• Falsification signal (leading): In the first 20 ICP-A prospect interactions, what percentage arrive specifically asking about a product (governance, cost audit) rather than the advisory/Workshop entry point?
• Knowable now or must be monitored: Monitor from initial conversations. A rate above 30% arriving product-first suggests the ICP-A segment is more product-purchase-ready than assumed.
• Pre-committed response if signal fires: Add a direct product path for ICP-A buyers who arrive product-ready. Do not force them through an advisory engagement they didn't ask for. This is a GTM adjustment, not an identity change.

Assumption 5 (MODERATE CONSEQUENCE) — The no-pricing-on-site decision does not block CISO inbound. The CISO buyer (ICP-C) under regulatory urgency (EU AI Act August 2, 2026 deadline) is a motivated independent researcher. They will find CPP via content, evaluate the governance product, and want to self-qualify their budget before committing to a discovery call. No pricing information forces them to request a call — which is friction they may not accept under time pressure.

• Falsification signal (leading): In inbound product inquiries from ICP-C buyers, what percentage drop off before a discovery call is scheduled? A drop-off rate above 60% at the contact-us stage suggests the no-pricing friction is losing motivated buyers.
• Knowable now or must be monitored: Monitor from site launch. Track inquiry-to-call conversion rate by ICP type.
• Pre-committed response if signal fires: Add a "starting from" range or audit scope description for the AI Governance & Audit product. This is addressed in Refinement 2 below.

Gate 8 — Organizational Capability Alignment as Strategic Constraint

Confirmed capabilities:

• Advisory delivery: Shea Long (AI strategy, product, agentic workflows) + Mike Burns (healthcare marketing, digital transformation, fractional CSO/CMO). Real and credible. Non-replicable by competitors without matching operator backgrounds.
• SME bench: Named domains (Data Readiness, AI Governance, FinOps, Cultural Impact, Agentic Development) — depth and staffing model unconfirmed in public materials. Treating as project-by-project engagement model. This is a strategic constraint on advisory delivery scale.
• Product platform: grāmatr — PARTNER, correctly classified. CPP is a distribution channel and advisory wrapper, not the engineering team. This is appropriate at this stage; the capability is threshold (operational table stakes for delivering the product) and does not generate CPP-proprietary compounding knowledge in the platform engineering layer.

Strategic constraints named (not operational gaps):

Constraint 1 — Product sales capability is unstaffed. Under services-with-products, the advisory relationship opens the product conversation. In year 1, Shea Long and Mike Burns conduct product conversations that emerge from advisory engagements. This is sustainable for the first 10–15 product relationships. It is not sustainable at 30+. CPP currently lacks a dedicated product sales capability (quota-carrying AE experienced in B2B SaaS with ICP-C/D buying patterns). This becomes a binding constraint on product revenue growth at approximately month 12–18.

Build/buy/partner: BUILD — hire a product AE with B2B SaaS governance or FinOps background at month 12, funded by advisory revenue. Do not PARTNER (referral-only commission model produces insufficient advocacy for a trust-based product). Do not ACQUIRE (no company to buy that solves this problem at this stage).

Constraint 2 — Advisory delivery scales through founder bandwidth. Two founders cannot scale Workshop delivery past ~8–10 new engagements per quarter without additional advisory capacity. The SME bench fills domain depth inside an engagement — it does not independently generate new client relationships or facilitate Workshops. This is the near-term ceiling on pipeline conversion.

Build/buy/partner: BUILD — the first non-founder hire should be a senior advisory delivery operator (healthcare + AI background preferred, given CPP's center of gravity) who can independently facilitate Workshops under Shea Long's process. Timeline: month 12–15, when advisory demand is confirmed but founder bandwidth is clearly constrained.

Constraint 3 — AI Dev OS is grāmatr-dependent and pre-launch. The ICP-D story (CTO, vibe-coding, AI Dev OS) requires a product that is currently in horizon status. CPP cannot sell a capability grāmatr has not delivered. The "early access — contact us" framing in the GSD brief is the correct holding position. This is a strategic constraint on ICP-D revenue until the product matures.

Build/buy/partner: PARTNER (grāmatr) — correct. CPP should not attempt to BUILD a competing internal AI Dev OS. The resource cost would dwarf the advisory revenue at this stage. The constraint is managed by honest positioning (horizon/early access) and by ensuring grāmatr has a clear Q4 2026 or H1 2027 delivery milestone that CPP's sales conversations can reference internally.

The Three Refinements Required

These are not optional enhancements. They are conditions of the ratification.

Refinement 1 — Instrument the trust-transfer mechanism from Day 1. The single most dangerous assumption (ICP-A opens product conversations for ICP-B/C/D) must be tracked as a measurable KPI from the first Workshop engagement, not assessed retrospectively at month 18. Required: a post-Workshop follow-up protocol that explicitly asks: did the CEO/COO introduce CPP to a functional buyer within 30 days? Track this with a simple CRM field. Do not wait for the pattern to be obvious before measuring it.

Refinement 2 — Add scope transparency to the AI Governance & Audit product page. Brian's decision to NOT publish product pricing is strategically sound for the advisory-first identity. The rationale holds for the Workshop ($3,500 is already visible) and for the AI Cost Optimization product (CFO buyers expect a scoped engagement conversation). It creates specific friction for the AI Governance & Audit product where ICP-C buyers are under regulatory deadline pressure and doing independent research.

Refinement required: The Governance & Audit product page should include either (a) a "governance assessment starting from" range that allows self-qualification without a formal pricing conversation, or (b) a scope description concrete enough that a CISO can estimate whether this fits their budget before requesting a call ("our standard governance assessment covers X, Y, Z and typically runs 4–6 weeks"). This preserves the advisory identity (no self-serve checkout, no price list) while reducing the friction for a motivated ICP-C buyer who is not willing to request a discovery call without any cost signal.

Refinement 3 — Internal AI Dev OS milestone, even if not external. The GSD brief correctly frames AI Dev OS as "horizon / early access" on the site. What the brief does not surface: CPP and grāmatr need an agreed internal milestone (not public-facing) for when the AI Dev OS transitions from "early access / contact us" to a productized offering with a named scope and entry point. Without an internal milestone, the ICP-D story drifts indefinitely in horizon status. Recommended: an internal Q4 2026 checkpoint where CPP and grāmatr jointly assess AI Dev OS readiness for a named early-access cohort of CTO buyers.

Strategic Implication of No-Pricing-on-Site (Advisory-Wide)

Brian's decision not to publish product pricing is correctly aligned with the advisory-first identity for three of four products/services. Summary of alignment and one tension:

The no-pricing decision is correct as a governing principle. Refinement 2 addresses the one ICP where it creates specific conversion risk.

Single Most Dangerous Assumption

ICP-A (CEO/COO) becomes the internal sponsor who transfers trust to ICP-B/C/D.

Every other load-bearing assumption has an independent recovery path. If the advisory brand takes longer to build without client proof, CPP grinds through referral pipeline. If the grāmatr product has delivery issues, CPP pauses product sales and fixes them. If the CISO wants pricing transparency, Refinement 2 addresses it.

If ICP-A does not transfer trust — if the CEO/COO exits the Workshop satisfied but does not internally sponsor product conversations — CPP is running four independent, cold sales motions to four different buyer types simultaneously, with a two-founder team, no client proof, and no product brand recognition. That is a resource allocation crisis, not a positioning problem. The trust-transfer mechanism is the architecture on which the entire commercial model rests. It must be measured from the first engagement, not assumed to be working until evidence contradicts it.

Summary Table

Overall verdict: RATIFY-WITH-REFINEMENTS.

The three refinements (instrument trust-transfer from Day 1; add scope transparency to Governance & Audit product page; establish internal AI Dev OS milestone with grāmatr) are conditions of the ratification. They do not change the identity direction. They close the three most consequential execution gaps that would otherwise remain unnamed until they became problems.

Brian Handrigan ratifies the final.

This document represents a CSO-atom strategic analysis. It does not constitute legal, compliance, or financial advice. Regulatory language throughout follows the HONEST-VERB rule: "designed to support EU AI Act / NIST-aligned" — never "certified/compliant." No retired mock facts have been introduced. Founders: Shea Long and Mike Burns.