Menu

Individual skill

onboarding-activation

0upvotes

Design customer onboarding as an activation system. Use when customers sign and stall, go-live takes months, or the gap between signed and successful is where accounts quietly die. Carries the why-they-bought evidence across the signature, drives to first realized value on a clock, detects stalls while they are cheap, and graduates accounts into steady state with a value baseline installed. Produces an activation definition, a milestone plan with a stall protocol, and the value baseline every later business review measures against. Rule: onboarding ends at first realized value, not at go-live. Trigger phrases: customer onboarding, time to value, activation, implementation drags, customers sign and stall, onboarding handoff.

skills/rutger-katz/onboarding-activation/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Onboarding to Activation: The Gap Where Accounts Quietly Die

The most dangerous period in a customer's life is the one with the least instrumentation: after the signature, before the first realized value. Sales has moved on, success has a kickoff template, and the buyer's champion is spending political capital on a promise with no proof yet. Churn recorded in month eleven is usually manufactured here, in month one; the renewal defense literature keeps rediscovering that risk is visible in behavior long before it is audible in words, and nowhere is that more true than an onboarding that never activates.

The evaluation data makes the stakes concrete: in trials, activation explains most of the conversion outcome, with activated accounts converting at multiples of un-activated ones (trial-benchmark aggregations, 2025-2026). Post-signature, the same mechanism operates on retention; treating it as transferable is a practice-based judgment this skill makes explicitly, and the first instrumentation job below is to make it a local fact: split your renewal outcomes by activated-versus-not within two quarters, and recalibrate the arc if the split is weak. Median gross revenue retention runs ~90% with top quartile above 95% (industry surveys, 2025); onboarding is the earliest controllable input to which side of that line an account lands on.

## Activation Is an Event, Not a Phase

Define activation as the smallest observable event proving the customer experienced the core value on their own data, in their own workflow. Rules:

- **Go-live is not activation.** Configured, trained, and launched are vendor milestones. Activation is a customer outcome: the report that changed a decision, the workflow that replaced the old one, the first week nobody opened the legacy tool.
- One primary activation event per segment or product line, written down, measurable from system data. If it takes a meeting to know whether an account is activated, the definition is wrong.
- Time-to-first-value (signature to activation event) is the program's headline metric, tracked as a distribution, not an average; the tail is where churn lives.
Back to top