The engagement, week by week

How we
actually work.

You're considering paying us. You deserve to know what a Treetop engagement actually looks like — not in abstract methodology language, but in what gets built in week one, what gets shipped in week four, and what changes in your business by day 90. Here it is, in concrete terms.

The arc

From kickoff to operating system

A full Treetop engagement runs about 90 days from the day we kick off. Some clients start with just the AI Audit (one week) and stop there. Most go through the Audit, then continue into Implementation (4–8 weeks), then settle into a Monthly Retainer. The arc below covers the full Implementation engagement.

Week 1–2 · Discovery & ICP foundation
We learn your business. Then we operationalize your ICP.
Two-hour kickoff call with leadership. Async workflow interviews with 3–5 team members across functions. We read your CRM, your sales calls (if Gong/Chorus), your last quarter's marketing output, and your last 90 days of customer support tickets. By end of week one we have a written read-out of where the operational waste lives. By end of week two we've stood up your operational ICP — 15–25 structured fields, account-scoring model, buyer-persona docs loaded into shared Claude Projects.
Deliverables: Workflow audit memo · Operational ICP document · Account-scoring framework · 2 base Claude Projects configured
Week 3–4 · Outbound build
We build the research-and-outreach loop your team will actually use.
Three connected Claude Projects: account research (URL in, structured brief out), sequence personalization (account brief + persona = first message + follow-ups), and reply triage (categorize, route, suggest response). We work side-by-side with your AEs/SDRs on real accounts during this phase — not synthetic data. By end of week four, your team has shipped 20+ real outbound sequences built with the new workflow.
Deliverables: Account-research Project · Sequence-personalization Project · Reply-triage Project · Shared prompt library · 1-hour rep training session
Week 5–6 · Pipeline intelligence
We replace the pipeline-review meeting with daily intelligence.
Daily pipeline-health summary (coverage, stalled deals, risk flags) generated automatically and sent to leadership Slack. Per-rep coaching brief generator that produces a 1-page brief before every 1:1. Deal-review Claude Project that consumes call recordings + CRM data. The Monday standup transforms from a 90-minute status meeting into a 30-minute action meeting.
Deliverables: Pipeline-health automation · Coaching-brief generator · Deal-review Project · Forecasting model · Manager training session
Week 7–8 · Team velocity
We make sure the systems we built actually get used.
Multi-session training cohorts by role (AE, SDR, Manager, RevOps, Marketing). We identify and resource 1–2 internal champions. Usage dashboards stood up. Shared prompt library versioned in your team's tool of choice. Written runbook for "what to do when X stops working." A quarterly review cadence agreed on.
Deliverables: Role-based training sessions · Champion enablement docs · Usage dashboards · Operations runbook · Quarterly review template
Week 9–12 · Optimize & transition
We refine what's working, retire what isn't, and hand it off.
The last four weeks are about adjustment. Which workflows are actually being used daily? Which need rewriting? Which never landed and should be retired? We refine prompts based on a month of real usage, write the "what changed" summary, and transition into either a Monthly Retainer relationship (for ongoing optimization) or a clean handoff if you prefer to operate independently from here.
Deliverables: Usage audit · Prompt refinement pass · Final delivery memo · Transition into Retainer or handoff
How we operate

Operating principles

A few principles that shape every Treetop engagement. These aren't marketing copy — they're the actual rules we work by.

Fixed scope, fixed price

Every engagement is quoted as a flat fee against a written scope. No hourly billing. No surprise change orders. If scope changes mid-engagement, we requote in writing before doing the new work.

Written deliverables, not slides

Frameworks live in documents you can read, share, and edit. We use slides for kickoff and readouts. Everything else is written: memos, runbooks, prompts, configurations.

We build inside your tools

Claude Projects, your CRM, your knowledge base, your Slack. We don't sell you our software. The systems we build are owned and operable by you the day we leave.

Train the team, not the executive

Adoption is won at the IC level, not the CRO. Half of every engagement is training the people who do the actual work — not the leadership who hired us.

One operator, not a team

Bill Colbert runs the engagement. There's no army of associates billing your hours. The person on the kickoff is the person on the readout.

If it doesn't change the numbers, we say so

Most AI deployments produce vague "productivity gains" nobody measures. We define what success looks like in week one — and tell you in week twelve whether we got there. Honestly.

Start small

You don't have to commit to 90 days on day one

Most clients prefer to start with the $1,500 AI Audit — one week, written roadmap, no commitment to a longer engagement. About 70% choose to continue into Implementation; the rest take the roadmap and execute it themselves (which is also fine; we wrote it for that).

If you'd rather see the underlying methodology first, read The AI-Native GTM Framework — the four pillars that structure every engagement.

Ready to start the conversation?
The 3-minute Gap Assessment scores your business across the four pillars and tells you what to fix first.
Take the Gap Assessment → Or book the AI Audit