From kickoff to predictable pipeline in 90 days.
Every managed engagement opens with the same Foundation build in week 1 at the attached one-time rate of $4,500, and $9,500 buys it standalone. From day 8 you either run the system with your own reps or a managed pod operates it for you. Most vendors keep onboarding vague. Here is exactly what we ship, week by week.
GTM Diagnostic
$3,500, one weekBefore anything gets built: ICP definition and segment ranking, reachable account universe sizing with the real count, a buying committee map, a sample verified contact set, a deliverability and CRM readiness audit, and a written go or no-go recommendation. The fee credits toward whatever you buy within 60 days.
See the GTM DiagnosticFoundation
$9,500 standalone / $4,500 attachedWe build the whole outbound system in 7 days - ICP, target accounts, verified buyers, messaging, sequences, sending infrastructure, CRM, and AI workflows - then hand it to your reps with a playbook and live training. You run it from day 8.
See what Foundation includesManaged pod
From $14,500/monthWeek 1 is the exact same Foundation build, charged once. From day 8 our GTM engineer and SDRs run the system for you: lists, cold calling, email, LinkedIn, replies, objections, booking, and weekly pipeline reporting.
See the flagship Scale Pod and pricingThe 90 days, in four moves.
Milestones and handoff checkpoints, from the Foundation build through the 90-day review.
- Week 101/04Foundation build - $4,500 one-time
- Days 1 to 2: ICP definition, account list, verified buyer contacts
- Days 3 to 4: messaging, offers, multi-channel sequences
- Days 5 to 6: sending domains, DNS, warmup, CRM and AI workflows
- Day 7: operating playbook plus live training handoff
Handoff checkpoint: the system is built, documented, and warming. You either run it yourself from day 8 or a pod picks it up with no rebuild.
- Weeks 2 to 402/04Warmup and first meetings
- Warmup completes, signal pipelines go live, first lists deploy
- SDRs run cold calling, email, and LinkedIn in one cadence
- First meetings typically land in weeks 3 to 6
Handoff checkpoint: pod takes over daily execution and weekly reporting starts.
- Months 2 to 303/04Target volume
- Pod runs the play at target cadence
- Weekly list refresh and sequence iteration
- Meeting volume reaches the tier target range during months two and three
- Weeks 9 to 1204/04Predictable pipeline
- Scale signal sources and expand to a second ICP
- Full funnel review from list to pipeline
- Month-to-month after the 90-day initial engagement
Only need the system built because your own reps will run it? Foundation delivers it in 7 days
Exactly what ships, and when.
Week 1 is Foundation and is identical on both paths. Weeks 2 to 12 describe the managed pod path.
Foundation build (one-time, $4,500 attached rate)
This week is the Foundation offer. It can be bought on its own at $9,500 if your team runs the system, and it is $4,500 when it runs as week 1 of a managed engagement.
- ICP workshop with founders or CRO; align on 1 to 2 primary segments
- CRM audit (HubSpot or Salesforce)
- Domain procurement (3 to 4 secondary domains)
- DNS configuration: SPF, DKIM, DMARC for all sending infra
- Initial ICP list build and validation against your ICP criteria
- Messaging, offers, and multi-channel sequences written and loaded
- Operating playbook, KPI dashboard, and live training handoff
- Slack channel and reporting cadence set
Your team takes the playbook and runs the system you now own, or a managed pod picks it up with no rebuild and no second setup fee. Everything below is the pod path. See Foundation on its own.
Warmup, signals, and first lists live
- Mailbox warmup begins (2 to 4 weeks at safe ramp)
- Signal stack built in Clay (job changes, funding, intent, installs)
- Weekly list validation and enrichment cadence established
- Sequences drafted across cold email, LinkedIn, and calling
- First list deployed and approved by you
- First accepted meetings typically land in weeks 3 to 6
- AE handoff and objection-handling playbook documented in your CRM
Pod runs the play
- Sequences live across email, LinkedIn, and calling
- SDRs handle replies, objections, and warm meeting booking
- Meeting volume reaches the tier target range
- Weekly reporting in your Slack: meetings, replies, deliverability
- Sequence iterations every 2 weeks based on data
Refine and scale
- Cost per meeting normalizes to vertical benchmark
- Second ICP or signal lane launched if ready
- Pipeline coverage projection delivered to CRO
- 90-day initial engagement review: continue, expand, or part ways cleanly
We guarantee the operating work, not a meeting count.
Meeting volume depends on your ICP density, offer, and market timing, so promising a number is a promise nobody can keep honestly. What we can commit to in writing is the work that produces meetings, the speed we learn at, and the quality bar every meeting has to clear.
Infrastructure live by an agreed date
Sending domains, mailboxes, warmup, data enrichment, and CRM wiring are live by a date written into the engagement, not a vague first month.
A defined number of accounts researched
Each month we research and enrich an agreed account volume with verified buying-committee contacts. The number is stated per tier and reported against every week.
Reply-handling SLA
Every prospect reply is worked by a human within one business day, including objections, referrals, and out-of-office reroutes.
Weekly experiments
A minimum number of documented experiments run every week across list, offer, message, and channel, with results logged so you can see what we learned.
Transparent accepted-meeting criteria
We agree the definition of an accepted meeting before launch and publish it in the weekly report. No moving goalposts on either side.
Replacement for meetings that miss the bar
Any meeting that fails the mutually agreed qualification rules is replaced at no additional cost.
What counts as an accepted meeting
- The contact matches an agreed title, function, and seniority in the target ICP
- The account matches agreed firmographic and technographic fit rules
- The prospect stated a relevant problem, initiative, or evaluation timeline
- A real calendar hold exists with your AE, with context notes attached
- No existing open opportunity or active inbound conversation for that account
We report accepted meetings rather than bookings. Anything that fails these rules is replaced at no cost.
Scale Pod operating terms
- Infrastructure: Infrastructure live by the end of week 1
- Research volume: 1,500 to 2,500 new accounts researched and enriched per month
- Learning velocity: At least 3 documented experiments per week
- Reply handling: every reply worked within one business day
What we do not guarantee
- A guaranteed monthly meeting count
- Guaranteed closed revenue, which depends on your AEs, product, and pricing
Published meeting ranges are forecasts based on observed conversion, not commitments.
Frequently asked questions
See the 90-day timeline applied to your ICP.
See your reachable market, realistic meeting range, expected cost per meeting, and recommended outbound motion.