This is the playbook we run across small and mid-sized B2B companies — refined across many engagements, week-by-week, with the deliverables, the patterns that work, and the patterns that fail. If you only read one piece on Treetop, read this. It\'s the operational core of everything we do.
Walk into ten B2B companies that "rolled out AI" in the last 18 months. In eight of them you\'ll find the same pattern: they bought subscriptions, hosted a kickoff, did a single training session, and then waited for the productivity gains to show up. They didn\'t. The team mostly ignored the tools. The few who used them produced incremental improvements but nothing transformative.
The failure pattern isn\'t about the tools. Claude, ChatGPT, Copilot — they all work. The failure pattern is treating AI rollouts as a procurement event rather than as an operating-model change. The companies that capture the real value treat it as the latter.
"Buying AI is a procurement decision. Becoming AI-native is an operating-model decision. The companies confusing the two are the ones whose AI spend produces nothing."
What follows is the playbook for the second category — the operating-model rebuild. It runs about 90 days for a typical 10–50 person B2B company. The longer version (with more functions, larger teams, deeper integration) runs 6 months. The arc is the same.
The 90 days split into four phases. The phases aren\'t equal length — discovery is short, build is long, deploy is medium, optimize is the rest. The sequence matters: skipping discovery to "just start building" is the most common way rollouts collapse.
Phase 1 — Discovery (Weeks 1–2): What to deploy, in what order. Operational ICP. Workflow audit.
Phase 2 — Build (Weeks 3–6): Claude Projects, system prompts, knowledge bases. The technical work.
Phase 3 — Deploy (Weeks 7–9): Training cohorts, runbooks, governance. Where adoption is won or lost.
Phase 4 — Optimize (Weeks 10–12): What\'s working, what isn\'t, what to refine.
A successful 90-day AI rollout for a B2B company looks like this at day 90:
Quantitative: Content output up 2–3x on the same headcount. Sales rep prep time down 60–70%. Pipeline review time down 50%. Time-to-proposal cut from days to hours. Daily AI usage rate >60% across the deployed team.
Qualitative: The team uses AI as part of normal workflow language. New hires onboard into AI-native processes from day one. Leadership decisions about scaling don\'t default to "let\'s hire" — they start with "can AI do this."
Cultural: The company starts to feel like it operates at a different speed than competitors who haven\'t made this transition. This is the moment the bet starts paying back.
This playbook is the default. Three variants we run depending on company stage:
If you\'re under 10 employees: compress to 45 days. Skip the multi-cohort training (you\'re too small for cohorts) — do one comprehensive working session with the whole team. Focus on 2 workflows instead of 5.
If you\'re 50–150 employees: extend to 180 days. The phases are the same but each gets more time. Multiple training cohorts. More champion development. Deeper integration work.
If you have regulated industry constraints (healthcare, legal, finance): add a 2-week governance phase at the start. Written AI policy, compliance review, vendor selection have to happen before Phase 1 of the standard playbook.
You can run this playbook yourself if you have senior internal capability. Most companies don\'t — which is why we exist. Treetop\'s Implementation engagement is exactly this playbook, executed by us, at $3,500–$25,000 fixed depending on scope.
If you want the structural understanding before committing, read The AI-Native GTM Framework — the operating model this playbook is built on top of. For the week-by-week breakdown of a Treetop engagement specifically (which extends this playbook with our specific tooling), see How We Work.
— Bill Colbert, Treetop Growth Strategy