The Implementation Economy
Source-grounded pack with Domain Expertise Asset System, Implementation Economics Model, and Implementation Operating System, plus 3 more.
Get this packGrounded in the complete The Implementation Economy series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 6 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches The Implementation Economy and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
6 source-grounded skills. Load one workflow at a time.
Domain Expertise Asset System
Use this workflow when implementation depends on senior domain experts and the company must convert their workflow knowledge, constraints, language, failure patterns, readiness judgment, first-value paths, and escalation rules into reusable delivery and partner assets without overfitting one segment's local practice.
Output specification
Return an expertise map, pattern taxonomy, asset backlog, completed asset specifications, judgment boundaries, validation cases, partner standards, owners, update triggers, and measures of time-to-value and quality.
Implementation Economics Model
Use this workflow when software revenue hides the real labor required to reach customer value and leaders need cost-to-first-value, margin, time, scope, repeatability, custom-work, pricing, segment, partner, and product-gap economics rather than averages that conceal a custom delivery business.
Output specification
Return an economics model with definitions, cost allocation, cause tags, segment views, metrics, custom-work classes, unit economics, repeatability levers, pricing and ICP implications, scenarios, and actions.
Implementation Operating System
Use this workflow when implementation depends on heroic coordination and the company needs a segment-aware, repeatable operating system spanning pre-sale readiness, first-value scope, proof milestones, categorized risk, customer ownership transfer, post-go-live adoption, structured learning, and business metrics.
Output specification
Return the operating system: pre-sale gate, readiness assessment, first-value scope, activity/proof milestones, categorized risk register, ownership map, adoption loop, retrospective, learning routes, metrics, authorities, and review cadence.
Implementation Ownership Architecture
Use this workflow when sales, implementation, professional services, forward-deployed engineering, consulting, product, customer success, support, partners, and the customer overlap or leave gaps, and one explicit value-realization map must assign ownership from promise through first value and durable adoption.
Output specification
Return a value-realization ownership map with steps, accountabilities, contributors, customer duties, proof, boundaries, absorbed work, cause-specific escalation, handoff contracts, and owner of first value.
Purchase to Adoption Gap Diagnosis
Use this workflow when a complex B2B or AI product has been purchased or launched but is not becoming a trusted operating habit, and the team must diagnose readiness, workflow, technical, trust, capacity, product, or commercial blockers and restore a measurable first-value path.
Output specification
Return an adoption-gap diagnosis with readiness findings, old/new workflow map, blocker classification, evidence, first-value definition, weekly loop, commitments, owners, old-process retirement, transfer criteria, and expansion gate.
Services to Product Conversion Plan
Use this workflow when recurring implementation labor, workarounds, configuration, migration, validation, training, or trust work may become product, process, internal tooling, partner capability, premium service, or an ICP boundary, and the company must test repetition and judgment without disguising one customer's custom work as productization.
Output specification
Return a pattern dossier, evidence strength, root cause, repetition/judgment map, route decision, maturity sequence, burden-reduction hypothesis, maintenance cost, pilot, measures, and stop condition.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.