Skip to main content

C5. Executable Whole Offer (product + terms/pricing + delivery)

Construct: the whole offer is capable of consistently producing the outcome in the ICP:

  • product/service (value mechanism),
  • terms/pricing (acceptance coherent with value),
  • delivery form (required implementation/adoption/support).

Qualifier: terms/pricing acceptance must be observable without depending on disproportionate concessions that materially alter the standard offer (scope, price, timelines, services) to make acceptance viable.

Application​

C5 asks whether you have a “whole product”: everything needed (product + terms/pricing + implementation/adoption/support) for the ICP to achieve the outcome consistently, without becoming a handcrafted project. And the key qualifier: price/terms acceptance must appear in the standard pattern, without relying on disproportionate concessions (extreme discount, custom scope, timelines/services that materially change the offer).

Examples​

Example 1 — Financial SaaS (implementation as “product,” not consulting) Unit (C1 summarized): SMEs with lean finance teams → close month-end faster → reconciliation/close SaaS vs spreadsheet+accountant.

Agent/DMU: buyer/decider=owner/CFO (accepts terms/pricing); user=finance (adoption/execution).

C5 works (executable offer):

  • Product (mechanism): integrates banks/ERP + reconciliation rules + standard reports.
  • Terms/pricing: monthly “list price” subscription (small, predictable variation).
  • Delivery: standardized onboarding (templates + checklist + 1 session) and light support; predictable time-to-value.

C5 does not work (non-executable offer):

  • It “works” only when you place one of your analysts weekly to clean data and adjust rules manually (concierge).
  • Or deals close only with “unlimited free implementation + customizations” (the offer changed in practice).

Example 2 — Compliance product (value exists, but delivery does not scale) Unit: regulated company → auditable evidence/controls → compliance platform vs spreadsheets+consulting.

Agent/DMU: buyer/decider=Security/Compliance + Procurement; user=GRC/Compliance Ops.

C5 works:

  • Product: control tracks + evidence + logs/audit (value mechanism).
  • Terms/pricing: annual pricing coherent with risk/value, without structural per-deal “exceptions.”
  • Delivery: productized implementation package (scope, timeline, done criteria) and “off-the-shelf” partners/integrators when needed (whole product “deliverable today”).

C5 does not work:

  • Every sale requires: security exception, non-standard clauses, ad-hoc data residency, custom integrations.
  • You “sell software,” but delivery becomes a project — each customer rewrites the playbook.

Example 3 — B2B with discount and “elastic” scope (acceptance is not real) Unit: support team → reduce cost per ticket while maintaining SLA → automation platform vs BPO+macros.

Agent/DMU: buyer/decider=Head of CX/COO; user=CS Ops/Support lead.

C5 works:

  • Price/terms accepted near standard (e.g., small discount with clear policy), because value is perceived and the offer closes “as is.”
  • Delivery: standard configurations + replicable playbooks; without depending on “vendor team co-operating daily.”

C5 does not work (your model’s qualifier):

  • Deals close only when you give aggressive discount and still include “dedicated service” and “promised features” (scope/timelines outside standard). This creates precedent and materially alters the offer.

Mini-checklist​

  • Does the product deliver the value mechanism without heroics?
  • Are price/terms accepted in the standard pattern, with little exception?
  • Is delivery (onboarding/support) replicable and does it ensure “whole product” in the ICP?