agentleFS
nthnclrknthnclrk/enablement-skills/skills/onboarding-to-value-playbook/SKILL.md

onboarding-to-value-playbook

Skill14 starsChanged 8 months agoMITView on GitHub

Build customer onboarding-to-value playbooks that get customers to observable first value and reduce early churn risk. Use when asked to map implementation milestones, handoffs, adoption signals, value events, or early customer outcomes. For internal seller onboarding, use onboarding-program-builder.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If setup completion is being sold as time-to-value, rewrite it.

    line 16
  2. Distinctive:

    Ask only for the inputs that change the journey:

    line 22
  3. Very specific:

    If a baseline, SLA, or horizon is missing, leave it TBD.

    line 30
  4. Distinctive:

    Read references/ttv-playbook-framework.md before setting value events, milestones, or risk triggers.

    line 34
  5. Distinctive:

    Start event, end event, pauses, owner.

    line 41
  6. Distinctive:

    Only the enabling activation, adoption, and outcome milestones needed.

    line 45
  7. Distinctive:

    Check-ins follow dependencies and risk, not a blanket weekly calendar.

    line 53
  8. Distinctive:

    Do not write a seller ramp plan, a named-account MAP, or a QBR.

    line 72
  9. Distinctive:

    No invented TTV targets, usage metrics, SLAs, or pricing.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboarding to value playbook

Help a customer achieve an observable first result, with responsibilities and support matched to their onboarding needs.

A good playbook names the first observable value event, who confirms it, and the few milestones that make it happen. If the user wants new-hire seller ramp, use onboarding-program-builder. If they want a partner pack, use partner-enablement-package.

First value. "Mid-market assisted: the ops owner closes their first exception from the new queue without a workaround. Evidence: product event plus customer confirmation in the week-2 review."

Not value. "Users provisioned. Kickoff held. Admin logged in twice."

If setup completion is being sold as time-to-value, rewrite it.

Inputs

Reuse supplied context first. If a missing company fact would change the result, check the relevant sections of .enablement/context.md when available. Preserve source dates and approval limits.

Ask only for the inputs that change the journey:

  1. Customer segment and motion: self-serve, assisted, enterprise
  2. Desired first-value outcome, the observable event that would prove it, and any customer-agreed horizon
  3. Measurement clock: start event, end event, pauses, window, owner
  4. Implementation constraints and sales-to-CS-to-services handoffs
  5. Known early-risk patterns and commercially critical checkpoints

If a baseline, SLA, or horizon is missing, leave it TBD. Do not invent usage thresholds, TTV targets, or pricing.

Supporting material

Read references/ttv-playbook-framework.md before setting value events, milestones, or risk triggers. Skip it if the user already defined first value and only wants the operating cadence.

Procedure

  1. Define first value, not first login. Actor, observable result, evidence source, acceptance criteria, who confirms. Setup and login are activation unless the customer agreed they are the outcome. Done when you can say what "they got value" looks like in one sentence.
  2. Set the clock. Start event, end event, pauses, owner. Do not default the start to kickoff when contract activation, provisioning, or data-ready governs the work. An unagreed horizon is proposed, not promised.
  3. Segment the journey. Depth and support intensity change by self-serve, assisted, and enterprise. Done when the same playbook is not being forced on every segment.
  4. Work backward from the value event. Only the enabling activation, adoption, and outcome milestones needed. Each has owner, output, due window, and acceptance criteria.
  5. Make handoffs inspectable. Who owns the transition and what context must transfer. Sales-to-CS is not "the deal closed."
  6. Attach early-risk controls. Qualitative triggers unless a threshold comes from the customer, an SLA, historical segment data, or a measured baseline. Numeric invention stays TBD.
  7. Split the two views. Customer-visible plan: milestones, owners, due windows, success checks. Internal plan: risk, escalation, caveats. Keep dates aligned.
  8. Set cadence to the horizon. Check-ins follow dependencies and risk, not a blanket weekly calendar.
  9. Hook renewal and expansion later. Readiness checks from the contract horizon and demonstrated value. Do not bolt on an upsell track during first-value work. For reusable renewal plays, use renewal-and-expansion-enablement.

Sending a customer plan or changing a shared onboarding or CRM record requires explicit approval of the recipients and changes.

What to return

For one segment or handoff, return that portion and its dependencies. For a full playbook, include:

  • First-value definition and time-to-value clock
  • Journey map with milestones and owners
  • Customer-visible plan and internal control plan
  • Milestone acceptance criteria
  • Risk triggers with response plays
  • Leading indicators with sourced or TBD thresholds
  • Renewal or expansion handoff hooks
  • Assumptions, if you had to make any

Do not write a seller ramp plan, a named-account MAP, or a QBR.

Quality bar

  • A CSM can tell first value from activation in one sentence.
  • The journey changes by segment.
  • Customer-visible and internal views stay consistent on dates.
  • No invented TTV targets, usage metrics, SLAs, or pricing.
  • Each value event is observable, source-linked, and distinct from setup.
  • Each risk trigger has an owner and a response that can act within the customer's remaining time window.
  • The CSM can identify the next dependency preventing the customer from reaching first value.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.