Service → Product Conversion Playbook (Runbook)

Purpose

This runbook helps you turn recurring bespoke client work into durable, sellable assets (templates, checklists, courses, automations, or digital tools) while minimizing the risk of building something customers won't buy or that still needs you to run it.

Outcome (Hunger)

Convert repeat work into products that reduce custom effort, create recurring revenue, and free your time—without losing the value clients pay for.

Overview — Five phases

1. Catalog & prioritize recurring deliverables
2. Identify and map repeatable tasks
3. Create templates, checklists, or minimum viable product (MVP)
4. Pilot with existing clients and measure
5. Package pricing, launch plan & support model

Phase 1 — Catalog & Prioritize

Goal: Find the most promising candidates for productization.

• List every deliverable you currently provide to clients.
• For each deliverable record: frequency (how often requested), time to deliver, typical customization level, margin, and which part the client values most.
• Score each item by: repeat frequency × time saved × client-perceived value.

Decision rule: prioritize items with high repeat frequency and high time-for-value ratio. Defer one-offs and highly bespoke, low-repeat tasks.

Phase 2 — Identify Repeatable Tasks

Goal: Separate the parts that can be standardized from the parts that require human judgment.

• Break the deliverable into steps and record inputs, outputs, decision points, and exceptions.
• For each step mark: Automatable, Template-able, or Human-only.
• Estimate: time for step, dependencies, and required expertise.

Use a simple decision matrix: If a step is frequent, well-defined, and not highly judgmental → Template or Automate. If it depends on deep context or tacit judgement → keep human or build a higher-touch product tier.

Phase 3 — Build MVP Templates & Tooling

Goal: Create the smallest deliverable that customers can use without heavy custom work.

• Choose a form: checklist, fillable template (doc or spreadsheet), recorded micro-course, guided wizard, or a simple SaaS/automation script.
• Create the asset focused on the core client benefit—not every feature. Aim for 70% of typical custom output with 20% of the effort.
• Include clear instructions and a short "what this does / what it doesn't" section so buyers know when they still need you.
• Prepare a quick-start guide and example deliverable that shows expected results.

Phase 4 — Pilot with Existing Clients

Goal: Validate real demand, usability, and willingness to pay before a broad launch.

1. Pick 3–8 existing clients who represent your ideal buyer profile.
2. Offer the MVP at a discounted pilot price in exchange for feedback and permission to use outcomes as case studies.
3. Run a short pilot period (2–6 weeks) with clear success metrics and support checkpoints.

Suggested pilot metrics:

• Conversion: % of invited clients who agree to pilot
• Time saved: average reduction in delivery hours
• Perceived value: Net Promoter-like question or 1–10 satisfaction
• Willingness to pay: % of pilots that would pay full price
• Support demand: # support interactions per pilot

Success thresholds (example): >25% conversion from invites; average time saved ≥ 30%; satisfaction ≥ 7/10; support demand low enough to be covered by a low-cost onboarding call.

Phase 5 — Package, Price & Launch

Goal: Make the product clear, purchasable, and scalable.

• Choose packaging tiers: Self-serve (templates + docs), Guided (templates + onboarding), Done-for-you (subscription service or premium package).
• Pricing strategies: value-based (preferred), cost-plus (fallback), or subscription. Test at least two price points in pilot scale.
• Create a simple funnel: landing page → explainer + sample → checkout or demo request.
• Define support: documentation, community, automated onboarding, or a paid coaching add-on.

Practical Tools & Checklists (copy these)

Productization Decision Checklist

• Repeat frequency: high / medium / low
• Time saved if productized: hours per engagement
• Client-perceived value: high / medium / low
• Complex exceptions: many / few
• Can a template reproduce the essential outcome? yes / no

Pilot Email Template

Hi [Client], I’m testing a new productized version of [service]. I’d like to offer you early access at [discount] in exchange for feedback and a short call. It will save you [benefit]. Are you open to trying it for [timeframe]?

Pilot Support Script (15–30 min onboarding)

1. Explain expected result and how to use the asset
2. Walk through an example step together
3. Confirm any client-specific inputs
4. Agree on check-in timing and feedback format

Human vs Automation Decision Guidance

Keep what creates trust, relationships, and high-value judgment as human. Automate or template steps that are routine, data-driven, or predictable. Consider a hybrid: automated core + human-led exceptions.

• Good for templates/automation: repetitive data formatting, report generation, routine recommendations.
• Keep human: strategic decisions, negotiations, complex exceptions, relationship management.

Common Pitfalls & How to Avoid Them

• Building too much too soon — start with the smallest useful product.
• Assuming clients want the product — validate with pilots and paid tests.
• Underpricing because you miss long-term value — test value-based pricing.
• Ignoring support burden — measure and include support costs in pricing or tiering.

Metrics to Track Post-Launch

• Revenue per product tier
• Conversion rate: visitor → trial → paid
• Average time saved per customer
• Support tickets per 100 customers
• Churn (for subscriptions)

Next Steps (Tactical)

1. Run the catalog exercise and pick 1 top candidate (this week).
2. Map tasks and mark automatable/template-able parts (next week).
3. Build a one-page MVP and recruit 3–8 pilot clients (within 2–4 weeks).
4. Run pilot, collect metrics, iterate, then package & price for launch.

Templates & Example Deliverables

Include or link: sample template files (doc, spreadsheet), onboarding script, pilot feedback form, pricing comparison table, and example landing page copy. These make pilots fast and repeatable.

Where THE capabilities can help

This runbook is suitable to pair with interactive pilot trackers, saved client submissions, and reusable domain collections so teams can copy and tailor the playbook to their context.