Scale Pod onboarding

Start your Scale Pod. We need 10 minutes of context.

Scale Pod is our flagship offer: one primary ICP plus one experimental lane, a GTM engineer owning the operating system, dedicated SDR capacity, email, LinkedIn, and calling in one cadence, data, sending infrastructure, deliverability, and human reply handling, CRM integration, and a weekly pipeline review, on a 90-day initial engagement. The detail you share here drives ICP scoring, signal lanes, sending capacity planning, and the 90-day roadmap.

About you
Scale Pod kickoff details

We respond within 1 business day. Your details go straight to our sales operators, never a drip campaign.

Timeline at a glance

Your first 90 days on Scale Pod.

Week 1 is the Foundation build, charged once. From there the pod runs the motion and reports every week.

  1. Week 101/04
    Foundation 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.

  2. Weeks 2 to 402/04
    Warmup, first sends, first meetings
    • Mailbox warmup completes and sending ramps on a safe schedule
    • Signal pipelines go live and the first lists deploy
    • Cold calling, email, and LinkedIn run together with reply handling
    • First meetings typically land in weeks 3 to 6

    Handoff checkpoint: weekly pipeline reporting starts in your Slack and every booked meeting lands on your calendar with context notes.

  3. Months 2 to 303/04
    Target volume
    • 1 GTM engineer plus 2 dedicated SDRs run parallel plays across up to 2 ICPs
    • Forecast range of 25 to 40 accepted meetings per month
    • Weekly list refresh and sequence iteration based on reply data
    • Objection handling and booking owned end to end by the pod
  4. Weeks 9 to 1204/04
    Scale what works
    • Add a second motion, layer intent data, and tighten routing to AEs
    • Deliverability and domain health reviewed and rotated as needed
    • 90-day review with the full funnel from list to closed pipeline
    • Month-to-month after the 90-day initial engagement
ROI estimator

What the Scale Pod could return.

Set your own average contract value and conversion rates to estimate meetings, pipeline, closed-won revenue, and the month you break even.

$35,000

Annual value of a closed-won deal.

60%

Share of accepted meetings that become real opportunities.

22%

Your historical win rate on qualified opportunities.

60 days

Days from first meeting to closed-won. Delays when revenue lands.

12 months

90-day initial engagement, then month to month.

Forecast over 12 months
Forecast accepted meetings
273-436
First meetings in weeks 3 to 6, target volume in months 2 and 3
Pipeline created
$5.7M-$9.2M
Opportunities x ACV
Closed-won revenue
$1.3M-$2.0M
Sourced in period, closing ~60 days later
Total investment
$178,500
$4,500 build + $14,500/mo
Return on investment9.2x

Midpoint net gain of $1.5M on $178,500 invested. Cash breakeven around month 4, once the first cohort closes.

Cost per meeting
$504
Cost per opportunity
$839
Get my pipeline model for Scale Pod

Your estimate carries over and pre-fills the onboarding form.

Forecasts only, not guarantees. The Scale Pod model assumes 25 to 40 accepted meetings per month at full volume: Foundation is delivered in seven days, first accepted meetings typically land in weeks 3 to 6, and target volume is reached during months two and three. We guarantee the operating work instead - infrastructure live by an agreed date, a defined research volume, a one-business-day reply SLA, weekly documented experiments, agreed accepted-meeting criteria, and replacement of meetings that miss them.

Methodology and assumptions

This is a planning model, not a forecast of your results. It multiplies a ramped monthly meeting range by your own conversion rates, then compares the output to the price of the offer. Every input is yours to change.

Accepted meetings
A meeting that meets the accepted-meeting criteria agreed with you before launch: right account, right role, real intent, and held. The Scale Pod model assumes 25 to 40 per month at full volume.
Ramp
Foundation is delivered in seven days, then output builds as domains warm and messaging iterates: 25 percent of full volume in month 1, 70 percent in month 2, 95 percent in month 3, full volume after that.
Average contract value
First-year contract value of a closed-won deal, before expansion or renewal.
Meeting to opportunity rate
Share of accepted meetings your team converts into a qualified opportunity in the CRM. Your own historical rate is the best input here.
Opportunity to closed-won rate
Your win rate on qualified opportunities. Outbound-sourced deals often close a little below inbound, so trim it if you are unsure.
Sales cycle
Days from first meeting to closed-won, applied as a 2-month revenue lag. It does not change how much closes, only when the cash lands and when breakeven appears.
Engagement length
12 months of managed execution after the Foundation build.

What the price includes

  • GTM engineer, SDR capacity, and reply handling for the selected offer
  • The one-time Foundation build, charged in month 1
  • Data, sending infrastructure, deliverability, and CRM integration
  • Weekly experiments and weekly pipeline review

What the model excludes

  • Your own AE time to run the meetings and work the pipeline
  • Paid media budget, billed to you directly by the platforms
  • Seat costs for CRM or sales tools you already own
  • Expansion, renewal, and referral revenue from closed deals
  • Any assumption that a meeting held is a meeting won
FAQ

Scale Pod questions, answered.