1 min lesson
Enablement and expansion mechanics
Tell someone how to act on this idea: "Don't pitch a plan with no expansion mechanic."
Step 1 of 2
Enablement and expansion mechanicsphases two and three
Enablement is its own section later. For the plan, you commit to the form: live hands-on sessions on the team's own repo, recurring office hours, named internal champions and self-serve docs written for this org's stack. The expansion mechanic is what separates a pilot from a rollout.
Don't pitch a plan with no expansion mechanic. 'Run a great pilot' is half a plan. The thing that makes you an SA and not a trainer is the repeatable playbook that turns the pilot win into team two, team three and the org standard. Bake the expansion path into phase one, not as an afterthought.
“Phase one isn't about seats, it's about earning two things: a security sign-off I can reuse across every future team and one clean, baselined win on a metric your VP already tracks. Once I have those, expansion is a playbook, not a fresh sales cycle each time.”