Four ICPs. Each one is a story.
Who they are, what broke, the first line we send, and the filters that build the list. An ICP counts only if the list is buildable from public filters. Test: 100-200 accounts, 2-3 weeks, meeting rate decides kill or scale.
Seed or Series A closed within the last 90 days, 5-40 people, no SDR, BDR, or RevOps titles. The board now expects pipeline. Prospecting is manual and depends on the founder. They know they need a system before they commit a hire to it: a wrong first sales hire costs six months of runway.
Hey {name}, skipping the congrats, you have plenty this week. We install signal-based outbound inside early B2B teams: built in your accounts, your team runs it. Curious: sales hire first, or system first?
You raised for growth and outbound is still manual. We install the system before you hire around the gap.
- List build
- Crunchbase or Dealroom funding feed into Clay. Title scan excludes anyone who already has sales ops.
- Filter spec
- Round = Seed or A · announced <= 90 days · raised $1M-15M · HQ US/UK/EU/IL. LinkedIn enrich: headcount 5-40. Clay arithmetic: BDR_SET = 0, OPS_SET = 0, AE_SET <= 1. PLG check on the pricing page. Boosts: first sales vacancy on careers page, second-time founder. Drop when funding is older than 120 days.
- Buyer
- Founder / CEO
- Disqualify
- PLG-only motion, B2C, pre-revenue with no sales motion planned.
| Sub | Trigger | Why different | Angle |
|---|---|---|---|
| A1 · Fresh raise | Announced <= 90 days | Every agency and recruiter congratulates them this month. High attention, higher noise. | Anti-congrats. System before the first sales hire. |
| A2 · Quiet runway | Announced 3-12 months ago · still zero BDR / ops titles, AE <= 1 | The congrats wave passed, nobody writes them now. Money not burned, board pressure grows monthly. | "{n} months since the round and outbound is still manual." |
| A3 · Burned once | Raised <= 12 months · post-raise sales hire left within 6 months, or vacancy reposted | Already paid for a wrong hire. Afraid of the second bet. | The system instead of the second gamble. Needs job-change tracking, runs after A1/A2. |
11-50 people, revenue exists, 1-3 AEs all hired within the last 6 months, no SDRs, no RevOps. The founder handed over quota but not a process. AEs source their own leads and close less than the founder did. The fix is not another hire; it is the system the AEs were assumed to have.
Hey {name}, saw {Company} brought on its first AEs. We install the signal-based sourcing system that feeds new AEs, so they close instead of prospecting. Curious how yours get pipeline right now.
Your first AEs are sourcing their own leads without a system. We install the one that feeds them.
- List build
- Sales Navigator / Clay: AE title count 1-3 plus start dates under 6 months, zero ops titles.
- Filter spec
- Sales Nav: headcount 11-50 · company age 2-10 yrs (revenue proxy) · headcount flat or growing. Clay arithmetic: AE_SET = 1-3 with every start date <= 6 months · BDR_SET = 0 · OPS_SET = 0. Alt trigger, same ICP: live AE posting at a company with zero existing sales titles. Boost: AEs hired out of bigger companies (they expect a system and notice it is missing).
- Buyer
- Founder, sometimes the new Head of Sales
- Disqualify
- AEs hired for inbound only; founder not in the decision.
| Sub | Trigger | Why different | Angle |
|---|---|---|---|
| B1 · About to hand off | Live first-AE posting · zero existing sales titles | The system can land before the AE does; the founder designs the sales workflow right now. | Day-one system for the hire they are making. |
| B2 · Handoff running | 1-3 AEs, all started <= 6 months | The core case. Quota handed over, process was not. | The system the AEs were assumed to have. |
| B3 · Handoff stalling | First AEs started 6-12 months ago · no second AE, no BDR, no ops since | AE numbers sit visibly below the founder's own; the founder starts blaming the hires. | "Before you conclude the AEs are the problem." Fixing the system beats rehiring. |
20-200 people with a live posting for GTM Engineer, RevOps, Growth Ops, or Outbound Ops. Stronger when open 45+ days or reposted. The role costs $13-18k per month fully loaded in the US, senior candidates are scarce, ramp takes about four months. The budget and the pain are already written into the posting.
Hey {name}, saw the {role} req at {Company}. We install what that hire would build: a signal-based GTM system in your accounts, about six weeks, your team owns it. Worth connecting either way.
Your GTM req has been open for weeks. We install what that hire was supposed to build: six weeks, in your accounts, your team runs it.
- List build
- LinkedIn Jobs, Indeed, Ashby, Greenhouse, Lever: weekly scrape, dedupe by domain, enrich the hiring manager and posting age.
- Filter spec
- Title query: "GTM Engineer", "Go-to-Market Engineer", "Revenue Operations", "RevOps", "Sales Operations Manager", "Growth Operations", "Outbound Manager" · posting age >= 30 days (priority: >= 45 or reposted) · company 20-200 · US/UK/EU/IL or remote. JD boost words: Clay, Apollo, Outreach, Salesloft, Instantly, enrichment, sequences, signals. JD kill words: Salesforce Administrator, CPQ, commission, Deal Desk. Context check: current OPS_SET employees 0-1. Boost: salary range >= $120k (that number is our anchor).
- Buyer
- The req owner: VP Sales, COO, or founder
- Disqualify
- Pure CRM-admin or reporting reqs; enterprise procurement.
| Sub | Trigger | Why different | Angle |
|---|---|---|---|
| C1 · Fresh req | Posting 30-45 days | Still optimistic, interviewing, drowning in recruiter mail. A non-candidate message stands out. | Plant the alternative before the salary is committed. |
| C2 · Stuck req | 45+ days or reposted | The core case. Budget approved months ago, pain compounds weekly, the market is thin. | Install what the hire was supposed to build, in six weeks. |
| C3 · Gave up | Posting delisted · no new ops title within 60 days | Budget exists, problem unsolved. Nobody else sees this signal: everyone scrapes live postings only. | "The req closed, the pipeline problem didn't." Needs posting-history tracking. |
30-300 people, 2-10 AEs, BDR count at half the AE count or less, including zero. AE:BDR at 2:1 or worse is the qualifying line. Closers spend paid closing time on prospecting, pipeline coverage sits below target, and each new BDR quits before a system exists around them.
Hey {name}, straight up: I found {Company} by counting AE vs BDR titles ({x} to {y}). Usually that ratio means closers prospect for themselves. We install the signal engine that fixes it. If I misread, ignore me.
Ten AEs on one BDR means your closers do their own prospecting. Instead of hiring five BDRs, install the engine; the one you have operates it.
- List build
- Pure LinkedIn title arithmetic in Clay: count AE titles vs BDR titles, compute the ratio, sort by AE count descending. The 10-and-1 cases first.
- Filter spec
- Sales Nav: headcount 30-300. Clay arithmetic: AE_SET = 2-10 · BDR_SET <= AE_SET / 2 (incl. zero) · sort AE desc, then ratio desc. Always-on pool, refresh monthly. Boosts: recurring BDR postings over the last 12 months (hire-and-churn loop) · Outreach/Salesloft in postings but never Clay · AE postings saying "self-sourcing expected".
- Buyer
- VP Sales / Head of Sales, founder at the smaller end
- Disqualify
- Full-cycle-by-design orgs (verify on the call); channel-led revenue.
| Sub | Trigger | Why different | Angle |
|---|---|---|---|
| D1 · Zero BDR | 2-10 AEs · zero BDRs | The purest version. Closers do all prospecting, the math is undeniable. | Straight title arithmetic: "{x} AEs, zero BDRs." |
| D2 · Churn loop | Ratio 2:1+ · recurring BDR postings over 12 months | They keep refilling the seat; each BDR quits before a system exists around them. | Stop refilling the seat. Install the engine the next BDR plugs into. |
| D3 · Tools, no system | Ratio 2:1+ · Outreach / Salesloft in postings, never Clay, no ops titles | Tooling budget spent and idle. Buying was easier than building. | "Your stack is paid for and idle. We wire it into a system." |
Wave plan
| Wave | ICP | Why this order | Status |
|---|---|---|---|
| 1 | C, then A | Cleanest triggers, lists buildable today. C carries budgeted pain: the unfilled req. | Awaiting Sofia |
| 2 | D | One Clay title-arithmetic run. Big always-on pool. | Planned |
| 3 | B | Biggest volume, softest trigger. Needs the job-change enrichment layer. | Planned |
ICP E. Never built GTM in-house.
A fifth ICP, distinct from the locked A-D set on the Story ICP page. A-D all target a visible crack in an outbound motion that already exists (missing BDR, stale req, unfed AEs). ICP E is different in kind: there is no motion and no attempt to build one internally, because leadership cannot evaluate GTM/RevOps talent well enough to hire it.
Sitting on a small but high-margin, defensible niche (Sofia's live example on the call: an Enterprise DataSaaS client billing $10-50k/yr off a scraped-data product, unchanged for a decade). Founder/decision-maker skews older (40+), never had to compete hard so never built real GTM, and is now visibly falling behind AI-native peers. Wants "a GTM engineer" out loud but cannot write the job description, let alone interview for one.
You've run this margin for ten years without a GTM hire, because you never needed one. The market just stopped waiting.
- List build
- Not built yet. Needs company-age plus all-time OPS_SET history (harder than A-D's current-state title count) plus an ACV/pricing-page pass.
- Additive filters on the shared base
- Company age boost at >= 8-10 years (5-year floor still applies) · niche, high-margin, small-TAM vertical (data- or API-driven B2B product, or a narrow B2B service) · ACV/pricing proxy $10-50k/yr off a small number of accounts, not volume · decision-maker age proxy: LinkedIn start date of the founder's first professional role implies 40+.
- Buyer
- Founder / CEO, older, non-sales background
Pays, or has recently paid, a lead-gen/outbound agency instead of hiring internally, because leadership cannot evaluate the work well enough to hire around it directly. Engagements run short, roughly a 3-month cycle per Sofia's own Sally-client base, because the buyer cannot distinguish real progress from agency theater, so they churn and re-buy instead of building.
You've rented this from an agency before and it never stuck. We install it instead, so it's yours for good.
- List build
- Not built yet. Needs agency case-study/client-logo scraping plus short-tenure contractor-engagement detection on LinkedIn.
- Additive filters on the shared base
- Agency signal: company appears in a lead-gen/outbound agency's public case studies or client-logo wall · churn-pattern signal: LinkedIn shows a pattern of short (~3 month) growth/outbound contractor engagements with no permanent GTM/RevOps hire ever in between · repeat-churn boost: 2+ distinct agency engagements over 24 months via contractor/consultant tags.
- Buyer
- Founder / COO, non-technical, non-sales background
| Sub | Trigger | Why different | Angle |
|---|---|---|---|
| E1 · Aging niche incumbent | Company >= 5 yrs (boost 8-10+) · AE 1-5, BDR <= 2 · small high-margin niche · founder 40+ · OPS_SET = 0 all-time | Never had to compete hard, so never built real GTM. Now visibly falling behind AI-native peers. | "You never needed a GTM hire before; you do now." |
| E2 · Habitual agency outsourcer | Company >= 5 yrs · AE 1-5, BDR <= 2 · OPS_SET = 0 all-time · pays or churns agencies on ~3-month cycles | Can't evaluate the work, so buys and re-buys the same rented competence instead of building it. | Install once, stop the rental cycle. |
Where this leaves off
Clients.
Every deal in play, one row each. Open a row for the full dossier: company, buyer, call plan, pricing, objection map.
Alhena.
Ashu Dubey (CEO, alhena.ai) wanted to hire Sofia full-time by Jul 15. We sell the install instead. Call: Fri Jul 10, 19:30 Tbilisi / 08:30 PT. Goal: verbal yes, kickoff Monday Jul 13.
One-screen prep.
- The play
- Sofia opens with the reveal (off the market, co-founded Spice GTM), brings Pavel in as co-founder and architect. Discovery before pitch: his point B, ACV of a big customer, SQLs/month and cost per SQL. Then the offer: his own loop, installed on his existing stack (HubSpot, Clay, Smartlead, his 20 domains) in ~1 month, team of three, everything registered to Alhena, his team trained.
- The price
- Anchor first: our standard engagement is $20k install + $10k/mo retainer. For him: $8k install + $5k/mo from month 2, first-in-queue exclusive, holds this week. The $5k also matches the number he already budgeted for Sofia. Optional per-SQL bonus above an agreed plan. Floor 8+5. The anchor IS the concession: less than half of standard, nothing more to give. If pushed, trade scope or start date, never price. No numbers in writing before the call.
- The proof
- Pavel: the same engine built inside Nebius (NASDAQ: NBIS) as an operator, the team runs it daily. Sofia: reply 6.8>14.2%, SDR team 5>25, $1M+ closed. Meta-proof: he spent three weeks trying to hire exactly this skillset.
- The close
- Use his own deadline (role closed by Jul 15): decision this week, engine live before any hire would even sign. Propose kickoff Monday.
- Watch out
- Counter-offer to Sofia directly: agreed line = not hireable at any number, said warmly, once. His candidate "exercise": do it as a Spice GTM mini-audit on our template. Yaroslav is "our engineer" on this call, nothing more (partnership unconfirmed).
Ashu, before we talk about my package: since our call my situation changed. I stopped collecting offers. I co-founded Spice GTM with two partners, and one of them is on this call. Instead of you hiring me and waiting three months while I build alone, we install a working GTM engine into Alhena in about a month, and I stay as your lead operator. You end up with more than you were hiring for, faster and cheaper than the hire. Let me introduce Pavel.
Our standard engagement is a $20k install plus a $10k monthly retainer: that is what this system costs when we walk into a company. With you we can do $8k and $5k, for one reason: you were first, and we want this case in e-commerce AI. Same full build: engine live, campaigns running, team trained, every license in Alhena's name. The $5k a month is the number you already budgeted for the role, and for it you get the three of us: hypotheses, new plays, and Sofia running your outbound. At your close rate one big customer pays this back many times over. If we start Monday, the engine is live before a hire would have signed an offer.
Objections, one line each.
| He says | We answer |
|---|---|
| "I wanted core team, not a vendor. People here work for a mission." | Agencies rent meetings and keep the machine; we install it in YOUR accounts and Sofia works inside your team as your named operator. In-house outcome, minus the 4-month ramp and the single point of failure. |
| "For $5k I hire someone full-time who is 100% mine." | His own words: A-players are hard to find. One hire = 4 months ramp + a system in one head. Same monthly money buys a live engine plus three seniors; when he hires, we onboard that person, it is documented and his. |
| "We already have Smartlead, Warmy, 20 domains, playbooks." | Agree, it shortens our setup. What is missing is the agentic layer: signals, scoring, personalization at scale, feedback from replies and calls into targeting. His own verdict: "the way we do things is not really agentic". |
| "Too expensive / discount?" | He is already below half of standard (20+10 vs his 8+5): that concession is the whole negotiation. Shift to ROI: at ~20% close, 5 SQLs = 1 big customer; ask his ACV and do the math live. No second cut. |
| "What am I paying for after month 3?" | Two paths: keep the team for the compounding layer (new segments, plays, call insights), or documented handover to his hire. "Want to save, take the keys. Want the result, keep the team." |
| "You are a brand-new company." | The engine is not new: Nebius runs it daily. Sofia's numbers are public. And he is the reference: he found her and chased for three weeks. |
Ask before pitching.
- What must the next two quarters produce: a raise, profitability, or the category before incumbents ship good-enough AI?
- ACV and margin of a "big customer"? (Prices the whole deal.)
- SQLs/month from the BD pair now, and all-in cost per SQL?
- If meetings 5x next month, what breaks first: onboarding, solution engineering, your calendar (he closes everything)?
- Which wedge closes fastest: shopping conversion, support deflection, AI visibility? Who do you lose deals to?
Company in 30 seconds.
- What
- Agentic commerce platform, ex-Gleen (rebrand Feb 2025): shopping assistant, support concierge, AI visibility, voice, analytics. Hallucination-free wedge. Premium-priced while competitors dump.
- Scale
- ~35 people, 300+ brands, 50-60 paid, ~1 big customer onboarded/week, goal 1/day in 1-2 quarters. Revenue grew 20x in 2024 (his post); ~$4M/yr per third-party estimate.
- Proof he sells
- Tatcha 3x conversion +38% AOV; Victoria Beckham +10% revenue; also Paula's Choice, Huckberry, K18, Murad, Living Proof.
- GTM today
- Inbound biggest; 2-person BD (head: Mahesh, no engineering) with manual Clay lists; events playbook; ~20 domains, Smartlead + Warmy; close rate ~18-20%; Ashu closes every deal himself.
- Funding, verified
- One raise on record: $4.9M seed, announced Sep 2023 (as Gleen), Slow Ventures lead. Checked Crunchbase, PitchBook ($4.9M total), Tracxn ("no rounds"), GetLatka ("bootstrapped"), SEC Form D (no filings): nothing newer anywhere. Sofia's "raised a year ago" and her colleagues' "just raised" match no source; most likely the Feb 2025 rebrand or the strong Q2 read as funding news. Working assumption: he runs on revenue, counts every dollar, ROI language wins. On the call ask neutrally: "are you building on revenue or is there fresh capital behind the push?"
- The buyer
- IIT > UCLA > startup backed by Marc Benioff (1M users, died monetizing too late) > 4-5 yrs LinkedIn growth. Builder, "generational company" talk, works hard. Warm and personal until price, then negotiates hard and expects a concession: give it once, framed as loyalty, time-boxed. Sets deadlines, gives homework, asked Sofia to "take herself off market".
Personal.
- Path
- Grew up in India, IIT grad; worked in India, Israel and Melbourne before moving to the US in 2012, as a UCLA student, specifically to start companies. Immigrant-founder chip on the shoulder, his words: "why are you here, away from where you grew up... you still have not made a generational company". source: podcast
- The scar
- First startup (AI, backed by Marc Benioff): 1M+ active users, he was CTO and coded it himself, and it died because they started charging too late, "out of gas". That is why Alhena is deliberately premium-priced and revenue-obsessed ("create value AND capture value"). Sales angle: he respects premium pricing and paid engagements; do not offer free work. source: podcast
- Drive
- Hero: Steve Jobs. "Builder by heart... I hero people who build things." Goal: an institution that outlasts him. Named the company after Alhena, a bright star in the Gemini constellation: wants to be the bright star in noisy AI (and enjoys the accidental Google Gemini pun). source: podcast
- Work style
- "Blending, not balancing": works Sunday nights because customers are in Europe and Asia, naps on Wednesday afternoons when the body asks; family and health first, then company, everything else cut. Says "we work very hard, I don't know if I give that vibe on LinkedIn". Takes calls at 7:30-8:30 AM Pacific. source: podcast + call
- People
- Co-founder Nagendra = school friend and weekend hacking partner before the company; they still sync a few times a day. Keeps talent warm for months: found Sofia, waited three weeks, wished her happy birthday twice on one call. Warm and personal in style, testing in substance. source: podcast + call
- AI-native
- Used Fable to analyze his own sales calls and changed how he sells based on it. His 5-year vision: solopreneurs running billion-dollar online stores on agents (cites the NYT two-brothers $1.9B story); Alhena exists to create that leverage. Our "engine your one seller runs" story plugs straight into this. source: podcast + call
- His own words to use
- "By the time a funding round is announced, it is probably already too late. Build your own map of where the puck is going." That IS signal-based GTM: quote it back when explaining why we source on signals, not announcements. source: podcast
Full dossier.
How this deal came to be
~Jun 15: Ashu finds Sofia on LinkedIn ("kickass GTM engineer"), keeps her warm 3 weeks. Jul 8: 60-min hiring call: role scope (agentic BD: "100 numbers, leads and notes each morning", buying-window signals, 5-10x productivity), comp $3-4.5k discussed, homework = her ideal package + artifacts, his calibration exercise pending, close by Jul 15, start August, he interviews others in parallel. Sofia sends the Alhena GTM Pack + a $5k/mo "dream offer" branded Spice GTM. Jul 8 evening, Pavel <> Sofia strategy call: sell the install, not the hire; $8k setup decided; Pavel joins the Friday call.
His numbers, from his own mouth
- Sources: organic/inbound biggest + referrals; BD outbound "not agentic"; events with pre-event dialing.
- Email volume ~5k, he was unsure per week or month ("I'll get that number"): ask for the real funnel: delivered, reply, meetings.
- Close rate 18-20% in HubSpot, "real number higher, we are not disciplined".
- Market window: customers matured, 2 vendors per eval, ~9 months to take share before Gorgias/Zendesk/Intercom ship good-enough AI.
- Pain: "we come across as more expensive, competitors reduce price like crazy". If he had a free month he would build the engine himself.
Deal rules and logistics
- Paperwork: contract from Pavel's Georgia IE, invoice + wire; NDA fine; all data stays in Alhena's accounts. US buyers bring legal friction, have the boring answers ready.
- Pacific-hours question resurfaces as "who covers US mornings": his own 7:30 AM PT slot already overlaps both; plus async in his Slack.
- He is testing constantly: every question doubles as an evaluation of how we sell, because that is the skill he is buying.
- Internal partnership track (Yaroslav terms, splits) never appears in front of the client.
Assets.
- Alhena GTM Pack (Sofia, sent to Ashu): 95.181.174.35 · login alhena. Tabs: GTM Loop, Action Plan, Market Brief, Job Offer.
- Ashu on YouTube: founder-story interview (Tech Startup Stories, "Creating a Legacy") · voice-first shopping demo by Ashu.
- Company: alhena.ai · Ashu Dubey LinkedIn.
- Transcripts: Sofia <> Ashu Jul 8 (EN, from Sofia) · Pavel <> Sofia Jul 8 (Fireflies, RU, 107 min).
- Our side: spicegtm.com (he will check it; audit CTA is still a mailto, known TODO).
Content strategy.
How the three of us post, how often, and what actually goes viral in this niche mapped into our own voice.
Three voices, one system
One brand cannot be one voice here. Each founder owns a lane that never overlaps with the other two, all three pointed at the same install-not-rent thesis from a different altitude: Sofia argues it through the buyer's pain, Yaroslav proves it through the build, Pavel owns it as a category and closes on it live.
| Voice | Title | Owns | Never touches |
|---|---|---|---|
| Pavel | GTM Architect | Category thesis, enterprise proof, founder authority, closing philosophy | SDR-level how-to, unproven client numbers, buyer-pain framing |
| Sofia | GTM Strategist | Buyer pain, founder-led handoff, ICP recognition, sales leadership | Build detail, architecture diagrams, personal milestones |
| Yaroslav | CTO / builder | Real build logs, failures, decisions, technical depth | Buyer-pain framing, category definition, closing philosophy |
Runs call two, draws the engine on top of what Sofia surfaced, prices it, gets the yes. Sits at the altitude Sofia and Yaroslav cannot: why the agency model is structurally broken, not just annoying.
- Proof
- Nebius Academy: $0 to $2M as the engine's own CCO, told as a strategy and closing story, not a build log.
- Register
- Mechanism first, economics second, one sharp closing line: "An agency's results stop when the invoice stops. A system you own keeps compounding."
- Guardrail
- If any agency founder could have said it, kill it. If it cannot be defended live on a call two, cut it.
Runs call one: warm discovery, CHAMP, gets the prospect talking about their own mess. Trust in this category is built through someone who has actually run a sales team. Full system already locked: style-passport.md + voice-fingerprint.md, do not touch the mechanics, only the vocabulary fix above.
- Proof
- $1M+ closed B2B, ex-Head of Sales, scaled an SDR team 5 to 25.
- Register
- Recognizable sales moment first, hidden system gap underneath it, diagnostic close. Never engagement bait.
- Guardrail
- One claim per post. If it reads like a meeting-booking agency's post, rewrite it.
The technical profile on call two, the one who wired the engine. Source-driven, not calendar-driven: a post exists because something real happened, not because a slot needs filling. Most mature pipeline of the three (12 causal archetypes + writer + ledger); the newest public track record, so volume ramps behind reps.
- Proof
- Working engine (Apollo → segmentation → depersonalization → SmartLead), built and run in public, failures left in.
- Register
- Scene before lesson, one turn of thought ("I thought X, it was Y"), a real stake, no tidy moral.
- Guardrail
- No archetype without its required beats. Thin source gets angles back, not an invented story.
Cadence
A skipped slot beats a forced post, for all three of us. Numbers are capacity-based, not aspirational: raise a voice's cadence only once it is visibly running out of real material before its slot comes around.
| Voice | Cadence | Why this number |
|---|---|---|
| Sofia | 3/week | Primary buyer-facing voice, system already locked, sets the pace. |
| Yaroslav | 2/week | Newest public track record. Capped by real build events, not effort; close to Sofia's pace on purpose, not trailing far behind. |
| Pavel | 1–2/week | Scarce on purpose: most of his weekly presence is comments on the other two's posts, not a fourth post. |
| Combined | 6–7/week |
What actually goes viral here
Pulled real hook text out of the 86-link pool's own URLs (LinkedIn encodes the first line into the slug), 40 of 86 had one. No engagement numbers yet, that part is still blocked (below), but the hook patterns themselves are real, not invented.
| Pattern | From the pool |
|---|---|
| Contrarian claim, names the sacred cow | "RIP McKinsey, you don't need a $300k..." · "Don't bet your house on ABM, here's what..." |
| News-jacking a real event in the space | "The CEO of Cognism just stepped down..." · "Salesforce laid off 4,000 people last year..." |
| System reveal, offer to share how it works | "I built Claude skills that create full GTM..." · "Let me show you how to use Claude Code for..." |
| Numbered framework, proof of depth | "These are the top 13 GTM motions we're implementing" · "52 GTM signals, signal-based outreach is..." |
| Curiosity-gap open loop | "Two years ago Varun and I came up with the..." · "To top up the 20VC podcast with Harry, this..." |
| High-stakes personal narrative | "This week ChatGPT helped save a baby's life" · "Bootstrapped founders working 80 hours..." |
Content mix, mapped to those patterns
| Pavel | % | Borrows |
|---|---|---|
| Category thesis | 35% | Contrarian claim |
| Enterprise proof (Nebius case) | 25% | Numbered framework / proof of depth |
| Founder pattern-recognition | 25% | News-jacking a real event |
| Closing philosophy | 15% | Curiosity-gap open loop |
| Sofia | % | Borrows |
|---|---|---|
| Founder-led handoff | 25% | Already her own locked rhythm, no change |
| ICP trigger story | 20% | Contrarian claim, reframed as a buyer symptom |
| Category / agency positioning | 20% | News-jacking a GTM/agency-world event |
| Buyer fear / risk reversal | 15% | High-stakes narrative, told secondhand as the buyer's story |
| Workflow notes + proof/build-in-public | 20% | Numbered framework / proof of depth |
| Yaroslav (priority order, not %) | Borrows |
|---|---|
| 1. Inside the build (default) | System reveal, offer to share how it works |
| 2. Decisions & constraints | Curiosity-gap open loop |
| 3. Failure under load (only if real) | No strong pool analog, own archetype covers it |
| 4. AI changes work | System reveal, same family as #1 |
| 5. Ownership & handover | No strong pool analog, own archetype covers it |
| 6. Conversation changed the build | No strong pool analog, own archetype covers it |
| 7. Human milestone, no moral (rare, never forced) | High-stakes personal narrative |
Weekly ops rhythm
| When | What |
|---|---|
| Monday | 5-minute async ping: what got built, what call happened, what pattern repeated. Raw material, not drafts. |
| Draft | Each voice drafts against its own gate: Sofia's (style-passport.md + voice-fingerprint.md), Yaroslav's anti-AI lint (voice-fingerprint.md), Pavel's: could an agency founder have said this, could I defend it live on a call two. |
| Publish | Whoever posts first that day, the other two comment within a few hours, real comments, not emoji. |
| Yaroslav only | Approved posts get logged in content-ledger.csv so the writer never repeats a hook or beat. |
Content research.
Who to watch, what already worked, who to sound like, in support of the strategy. Niche: AI-native GTM engineering, signal-based outbound, GTM engineering as a role, AI agents in sales, the Clay/n8n-style stack. Not classic sales leadership, not generic RevOps.
Leaders (28)
Cut down from 47 per Pavel's review: dropped rank-and-file tool-vendor employees (Clay, HeyReach, Unify, Apollo.io, La Growth Machine) with no founder standing, and generic "Independent GTM Engineer" entries with no follower count and no distinguishing signal, i.e. thin matches from the original job-title search. Kept: founders of the matching agencies, plus the handful of individually major voices (Adam Robinson, Nate Nasralla, Todd Busler, Umer Ishaq) and real Head-of/Founding GTM-engineering roles at non-tool-vendor companies. Sorted by follower count.
| Name | Company | Followers | Why relevant | Connected |
|---|---|---|---|---|
| Adam Robinson | RB2B / Retention.com | 155,679 | Founder of RB2B, the category-defining anonymous-visitor-ID tool at the center of signal-based outbound; builds GTM/data infra in public. | |
| Nate Nasralla | Fluint | 86,188 | Coined "DevOps for RevOps"; weekly frameworks on revenue ops as engineering + AI-agent-assisted selling. | |
| Alex Vacca Pavel add | Frontal AI (ex-ColdIQ) | 69,060 | Founder/CEO, 1 of 4 Clay Elite Studio Partners worldwide, 275+ clients; posts real pipeline numbers (e.g. $7.83M for AirOps), not theory. | |
| Dan Rosenthal Pavel add | Workflows.io | 46,482 | Co-Founder of Workflows.io, ex-ColdIQ Partner & Head of GTM, Clay Enterprise Partner + Instantly Certified Expert; AI growth-playbook content, 20M+ organic LinkedIn impressions claimed for himself + clients. | |
| Todd Busler | Clay | 40,019 | Ex-founder Champify, now enterprise sales @ Clay; prolific on modern GTM playbooks and signal-based selling. | |
| Ivan Falco Pavel add | Frontal AI (ex-ColdIQ) | 23,231 | Partner at Frontal Ads, ex-Head of Demand Gen at ColdIQ; ABM + paid media angle on the same GTM-engineering niche. | |
| Dima Bilous | Anfloy | 11,329 | Runs a forward-deployed AI/GTM engineering agency, Apify + Trigify brand partner; posts on agentic GTM systems. | |
| Umer Ishaq | HeyReach | 9,878 | One of the first Clay experts globally; leads GTM engineering at HeyReach, detailed Clay/Supabase/n8n/HubSpot build-outs. | |
| Luca Carrese Pavel add | Frontal AI (ex-ColdIQ) | 5,361 | Partner at Frontal AI, ex-Chief of Staff ColdIQ; GTM/revenue-scaling angle. | |
| Mark Lim Pavel add | Quali Conversion | 4,595 | Founder of Quali Conversion, a Hamburg Clay agency; building an agentic GTM operating system for B2B professional services. | |
| Jovan Kocev | tabbo | 4,457 | Certified Clay Creator + Warmly partner, built outbound engines for 60+ B2B companies; case-study-driven posts. | |
| Hamed Tavalla Pavel add | TAM Acceleration | 2,282 | GTM/growth/AI automation at TAM Acceleration, a Miami Clay agency building AI-enhanced outbound for B2B companies. | |
| Daniel Scott | Solve Intelligence | 1,564 | Founding RevOps Engineer building GTM infra from scratch at an AI startup; RevOps-as-engineering pattern. | |
| Ben Miller | Continuum AI | 1,100 | Heads RevOps & GTM Engineering at an AI startup; the RevOps-to-GTM-engineer title merge in practice. | |
| Adam G. | Wayflyer | 744 | AI GTM Engineer building LLM-powered agentic workflows (n8n, RAG, MCP) for revenue teams. | |
| Stephen Brown | Engrain | 629 | Head of GTM Engineering, "technical infrastructure behind how we sell, onboard, and grow." | |
| Anton Nemyrovskyi | Suxeed | 313 | Head of GTM Engineering at a RevOps consultancy serving EY, SAP, Ericsson, Celonis; GTM engineering as outsourced discipline. | |
| Nicolas Schell Pavel add | Scalantec | — | Co-Founder/CEO of Scalantec (Berlin GTM engineering studio) and Clay's own Community Lead. | |
| Moritz Heininger Pavel add | Scalantec | — | Co-founder of Scalantec, ex-Bain/Rocket/Softbank-Venture; builder/operator angle on AI-enabled revenue systems. | |
| Manav Makhija Pavel add | Rendition | — | Runs Rendition, which installs GTM engineering systems inside client businesses; claims 3,000+ enterprise conversations generated. | |
| Sebastian Vinther Pavel add | The Growth DNA | — | Co-founder of The Growth DNA (Clay experts + GTM engineers + data scientists building inbound/outbound/RevOps systems for clients). | |
| Emil Jørgensen Pavel add | The Growth DNA | — | Co-founder of The Growth DNA; "engineering pipeline aha moments." | |
| Alexander Ivanov Pavel add | Hypergen | — | Founder of Hypergen, a larger (41-person) cold-email/RevOps agency publishing Clay enrichment tutorials. | |
| Justin Ross Pavel add | The Sales Detective | — | Founder of The Sales Detective, a sales/GTM engineering/Clay consultancy that clones a client's best-seller process into automated outbound. | |
| Alex Scholz Pavel add | Agentic.it | — | Runs Agentic.it, a Sydney "GTM engineering as a service" boutique; B2B revenue automation, global professional services for GTM. | |
| Miska Kaskinen Pavel add | SwiftDial.ai | — | Co-founder of SwiftDial.ai, "the Nordic Clay Agency" (Finland); AI workflows for revenue teams. | |
| Ville Forsell Pavel add | SwiftDial.ai | — | Co-founder of SwiftDial.ai. | |
| Vidhi Gulati Pavel add | Effi Flo | — | Runs Effi Flo, a Clay agency specialized for recruitment/staffing firms; solving talent acquisition with AI, automation and Clay. |
Top posts
LinkedIn: 86-link candidate pool (author, date, URL only, not yet scored) that Pavel pulled directly: hq.spicegtm.com/viral-posts. Next step is pulling real engagement numbers per post and picking the genuinely high-reaction ones, once the AnySite LinkedIn quota resets.
X / Twitter, genuinely viral (500+ likes, since Jan 2026)
X has its own AnySite quota, separate from LinkedIn's, so this one is scored. Swept 10 keyword angles (GTM, GTM engineer, signal-based outbound, AI SDR, AI-native GTM, Clay/enrichment/workflow, outbound/revenue engine, cold outbound, RevOps/lead scoring, n8n) at both min_likes: 1000 and, per Pavel's ask to push wider, min_likes: 500. The filter isn't perfectly enforced by the API, so most hits came back well under the threshold and got dropped; the Shiv Sakhuja "Goose Ads" post from the first pass got cut too, per Pavel's call: ad-creative generation isn't the GTM/Clay/signal-based-outbound story. Near-duplicate comment-bait posts from one account (Alfie Carter, same template 5 times this window) got reduced to the single best one. Result: 7 posts genuinely clear both bars (real topical fit + 500+ real likes), 5 above 1,000 and 2 in the 500-999 band — the honest count from 53 unique posts reviewed, not a sample of a bigger set. Full raw pool (all 53, unfiltered, with real like/reply/view counts and post text): hq.spicegtm.com/x-posts.
| # | Author | Likes | Replies | Views | What it says |
|---|---|---|---|---|---|
| 1 | Todd Saunders | 4,475 | 498 | 878,588 | A seed-stage company's VC-endorsed board-deck strategy: clone an incumbent's product via a customer's licensed access, using Claude Code, and undercut by 90%. Real industry-ethics debate, not a growth-hack template. |
| 2 | Finn Mallery | 2,999 | 77 | 355,639 | What the $1M+ ARR founders in the current YC batch are actually doing: build lead lists in Clay/Origami, 200 LinkedIn connects/week, 2-sentence warm-thread DMs, post 5x/week, AEO. A real, named-tool playbook, not theory. |
| 3 | Alfie Carter | 3,472 | 3,156 | 267,410 | "Rebuilding your GTM stack from scratch every session" pitch for a 130+-skill Claude skill library replacing a $15k/mo agency retainer. Comment-bait format, but genuinely the highest-liked GTM-skills post in the window. |
| 4 | Sam Blond | 2,097 | 41 | 865,473 | One-line thesis: "the company you're buying GTM technology from should be exceptional at GTM. If they're not, don't buy their product." High view-to-like ratio, sharp aphorism format. |
| 5 | Matthew Berman | 1,906 | 1,088 | 188,782 | "Replaced a $200K GTM hire" with an AI agent chain: LinkedIn engagement mining, enrichment, ICP scoring, personalized outreach, automated sends, pre-call briefings. The closest single post to Spice GTM's own pitch. |
| 6 | Samuel Spitz | 770 | 46 | 278,624 | Real product launch: "Introducing Replit AI SDR, find your next 100 customers with AI." Short, on-topic, no comment-bait CTA. |
| 7 | Alex Vacca | 507 | 8 | 176,988 | "Cold outbound has been definitively solved. The study cost 23,000,000 sends, the findings fit in 5 bullet points." Frontal AI's own founder, same voice as his Leaders-list entry above. |
GTM agencies with great content (12)
Cut down twice per Pavel's review. First pass removed tool vendors (Clay, Warmly, Unify, Koala, Common Room, RB2B, Trigify, La Growth Machine, Surfe, HeyReach, Smartlead, Instantly, Apollo.io, Amplemarket): software products, not agencies. Second pass removed the media/community brands (GTMfund, RevGenius, Exit Five) and the two larger, differently-shaped consultancies (Refine Labs, Winning by Design): real agencies, but not the same species as our profile. What's left is only small, founder-led, Clay-partner, AI-native GTM-engineering-as-a-service shops, i.e. direct analogs of Frontal AI and Workflows.io. The 10 marked "Pavel add" were found by searching Clay-partner listings and ex-ColdIQ alumni, then verified one by one; 6 other candidates were checked and rejected as tool vendors, unrelated studios, or unverifiable (Palmstone AI, Green Hive Systems, CRM Refinery, TheClaygency, Clay Consultancy Vancouver, Clay Bootcamp).
| Name | Category | Why the content is good |
|---|---|---|
| Frontal AI Pavel add | Agency | Ex-ColdIQ, 1 of 4 Clay Elite Studio Partners worldwide, 275+ clients. Content leads with real pipeline numbers ($7.83M for AirOps) instead of claims; three named operators post individually (Vacca, Carrese, Falco). |
| Workflows.io Pavel add | Agency | Another ex-ColdIQ spinout (founder Dan Rosenthal). AI-native GTM services across 4 lines (LinkedIn Content, Outbound, RevOps, ABM); positions explicitly against both "another software" and "another traditional agency." |
| TAM Acceleration Pavel add | Agency | Miami Clay agency (8 people) building AI-enhanced, personalized outbound for B2B companies ($1M+ revenue) with Clay plus other tech-sales tools. Installed system, not a tool. |
| Quali Conversion Pavel add | Agency | Hamburg Clay agency, founder Mark Lim. Unlocks an automated go-to-market system using Clay for clients (research, CRM enrichment, personalized outreach), 20+ B2B clients claimed. |
| Scalantec Pavel add | Agency | Berlin GTM engineering studio (4 people) building revenue systems (Clay, sales automation, AI agents) for clients instead of adding headcount. Co-founder/CEO Nicolas Schell is also Clay's Community Lead. |
| Rendition Pavel add | Agency | Builds and installs GTM engineering systems inside SaaS, consulting, and M&A client businesses using in-house LLMs, AI agents and web scraping for 6-7 figure campaigns. The install-the-system model that defines this category. |
| The Growth DNA Pavel add | Agency | GTM engineers, data scientists and Clay experts (2 people) building inbound, outbound and RevOps systems for B2B clients. Two confirmed co-founders running it as a service shop, not a product. |
| Hypergen Pavel add | Agency | Larger, more established cold-email/RevOps agency (41 people, Sofia/Delaware) building data-enriched outbound systems for clients, publishes Clay enrichment tutorials. Closest in scale to Frontal AI. |
| The Sales Detective Pavel add | Agency | Self-described sales, GTM engineering, and Clay consultancy that clones a client's best-seller process into automated, signal-based outbound. |
| Agentic.it Pavel add | Agency | Sydney boutique (5 people) offering "GTM engineering as a service": GTM strategy, process automation, an intelligent GTM layer for B2B orgs. Team from Accenture, Akamai, Freshworks. |
| SwiftDial.ai Pavel add | Agency | Billed as "the Nordic Clay Agency" (Finland, 3 people): custom data enrichment synced to CRM, automated prospecting, buying-intent signal tracking. Two confirmed co-founders plus two co-owners. |
| Effi Flo Pavel add | Agency | A specialized Clay agency for recruitment and staffing firms (7 people), builds Clay-based client-acquisition and talent-sourcing workflows. A vertical-specific version of the Frontal AI/Workflows.io model. |
Sales script.
How we run a deal from first message to close: the two-call structure, what to ask, how to position, and how to answer the objections. Copy blocks are ready to say on a call or paste into a message.
Discovery flow: two calls
Split discovery from the close. One person opens warm and gets the problems out; the architect comes in second to show the engine. Nobody pitches on call one, nobody sells cold on call two.
| Call | Who runs it | What it is for |
|---|---|---|
| 1 · Warm discovery | Sofia (GTM Strategist) | Place them in an ICP pattern or rule them out in the first few minutes, then run CHAMP to get the prospect talking about their problems, not a pitch. Output: which ICP they are (or that they're not one), their point B, who owns outbound, current numbers, why now, and where solving this ranks against their own plan to do it in-house. No engine, no price on this call. |
| 2 · Technical close | Pavel (GTM Architect) + Sofia | Show the engine. Draw the architecture on top of the problems Sofia surfaced, confirm Money and Prioritization with their own numbers, map it to their existing stack, then price and next step. This is where the install gets made concrete. |
ICP fit: qualify in, qualify out
Before CHAMP, place them in one of four patterns or rule them out. Two minutes of pattern-matching on call one saves an hour of pitching to someone we will never close. Full research and filter specs: Story ICP.
| ICP | What you'll hear | Confirm with |
|---|---|---|
| A · Just funded, no engine | Raised seed or Series A in the last few months, 5-40 people, still no BDR or ops hire, pipeline is one person's job. | When did you raise, and who runs outbound day to day right now? |
| B · Founder-led handoff | 1-3 AEs hired in the last 6 months, founder still closes the biggest deals, AEs source their own pipeline. | Are your AEs building their own pipeline, or is someone feeding them? |
| C · Open GTM/RevOps req | A GTM Engineer or RevOps role has been open 30+ days, nobody's landed it. | Are you actively trying to fill a GTM or RevOps hire right now? |
| D · AE-heavy, BDR-starved | Several closers, one BDR or zero, AE:BDR at 2:1 or worse. | How many closers do you have versus people feeding them pipeline? |
Qualification framework: CHAMP
Challenges → Authority → Money → Prioritization, asked in that order, on call one. Not BANT, not MEDDIC, on purpose. Open each card below on the call, in order; Challenges carries most of the weight, that's why it's the long one.
1 · Challenges: their pain, in their numbers
Opens the call without asking for anything yet. Six areas, in order, each one written to double as proof we already know this space better than a first call usually implies. Read it close to word for word until it's memorized.
Org & ownership
"Before we get into numbers, help me place where you are today. Who runs outbound day to day right now, is that you, someone on the team, or an outside agency? And if it's split between people, who owns the strategy versus who's actually sending the messages?"
Listen for: whether you're replacing a person, displacing a vendor, or filling a gap nobody's covering, before you've committed to a pitch.
Agency check
"Are you working with an agency or freelancer on outbound right now? What exactly do they own for you, the lists, the sending, the strategy, and what are you paying them? And honestly, what's working, what isn't?"
Listen for: a yes turns this into a displacement deal, not a greenfield one. Run the "already have an agency" objection response directly instead of waiting for it to surface, and treat any unhappiness they admit to as free urgency.
Funnel, end to end
"Walk me through the funnel end to end: how do you find the accounts you go after, how do you actually reach them, and what happens the moment someone replies? And let's put real numbers on it: how many accounts a month, what's the reply rate, how many meetings come out of that, how many turn into a real SQL, how many close?"
Listen for: stage-by-stage numbers are the whole ROI model. Asking for every stage instead of just "how many meetings" is the question that signals you've actually built this before, not just sold it.
Signal vs static list
"How do you decide who to reach out to in a given week, is it a list you built once and keep working, or are you reacting to signals, someone raising funding, hiring a certain role, shipping a new product?"
Listen for: a static list points straight at the ICP A or D gap, the problem is targeting, not execution. This is the question that introduces "signal-based" before you've said the word.
Tooling
"What's already sitting in your stack, Clay, Apollo, Outreach, Smartlead, HubSpot, Salesforce, anything else? And who actually runs it day to day?"
Listen for: this defuses "we already have tools" before it becomes an objection, and tells you whether the gap is the tools or the system wired around them.
Call intelligence
"Last one, and it's usually the one that lands hardest: when a call happens, what happens to what you learn on it? Does anything from a call ever change who you target next, or what you say to them?"
Listen for: almost nobody has a real answer. It demonstrates the feedback loop we install better than any pitch line, and the pause before they answer is most of the sale, right there.
2 · Authority: one-person yes, or does someone else sign off
"Who owns outbound, you or someone on the team? Is bringing in outside help your call, or does someone else weigh in first?"
Listen for: whether this is a one-person yes or someone else signs off. Find the decision-maker, not just the operator, before you pitch to the wrong person.
3 · Money: priced against their own economics
"What's the ACV on a big customer? If meetings 5x next month, what breaks first? How does that compare to $13-18k a month for a full-time hire?"
Listen for: price the deal against the real cost of what they're comparing us to, a GTM engineer runs $13-18k/mo fully loaded, verified market rate. Do not ask for a budget number, a founder won't give you an honest one on call one.
4 · Prioritization: where we rank against their own plan to fix it
"Why now, what do the next two quarters need to produce? Is hiring in-house already on the table? What would have to be true for you to do this yourselves instead of with us?"
Listen for: the step that would have saved our one lost pitch. The real objection there was never price or the model, it was that in-house already outranked us in the founder's head before the call started, and we found that out mid-pitch instead of in the first ten minutes. Ask this before you pitch, not after, it surfaces the objection map below while it's still cheap to answer.
Positioning script
The "why hire when you can install" story, and the analogy that answers "I'll just hire someone." Say it plainly. The whole point is that it is simple enough not to argue with.
You can absolutely hire someone, that is a real option. Here is the choice underneath it. Think about a car. Some people can drive a car, and some people can build one. The ones who build them are engineers. They are expensive, and they are hard to find. If you hire one, their job is to build your car from scratch, and that takes a few months and a lot of money. Then once it is built, driving it every day bores them, so they leave, and now you are hiring again, this time for someone to drive it. We are the single point of entry: you agree with us once, we build the car, we drive it well and bring you the results, and if you ever decide you want to drive it yourself, we hand you the keys and help you take the wheel. That is the difference from an agency. We do not need to sit in your car forever.
Hiring a GTM engineer means paying six figures for someone to spend two or three months building one system, alone, in one person's head. Ninety percent of that value is the build. Instead of hiring the build, you install it: we bring the finished engine into your own accounts, wire it into your stack, and train your team to run it. You own the machine. When you do want a person on it, you hire a cheaper operator for a system that already works, or we keep running it for you.
You already drive a car, you do not build it yourself. Saying you will hire in-house to build your GTM is like saying you will assemble your own car from the blueprints. The blueprints exist, sure, but the engine has to be built right, and that is the hard part, not the driving. We are the people who build the car for you, tuned for your business. You just drive it, and yes, you need to know where the pedals are, but that is nothing like building the engine.
Let's put a number on it instead of arguing feelings. A GTM engineer runs $13-18k a month fully loaded, verified market rate, plus two to three months before they ship anything, plus the risk they leave once the system runs itself. We install the finished engine in your accounts inside weeks, priced against your own cost per SQL, not a headcount line. If the math doesn't beat hiring, don't do this. But run the math first, don't decide on the org chart before you've seen the number.
Results & timeline
What to say when they ask "what do we actually get, and when." Two different things: proof of what we've built before, and the timeline for what happens after they sign.
| Stage | Timeline | What happens |
|---|---|---|
| Free audit | Now, one call plus a written teardown | We diagnose the gap using CHAMP and the ICP fit above, and hand over a short written teardown, useful even if you never hire us. |
| Setup | Fixed price, 1-2 months | We build the engine in your own accounts, wired into your stack. Campaigns go live during setup, not after, so you see activity before the build is even finished. |
| Growth | Monthly, ongoing | Hypothesis testing, new plays, and a rising reply and win rate as the system learns your market. Billed month to month, no multi-year lock-in. |
We haven't run this as Spice GTM yet with a signed client, so I won't invent a number for you. What I can tell you is what this exact system did running inside other companies, as operators, not as a vendor: reply rate went from 6.8% to 14.2% at one, an SDR team scaled 5 to 25 at another and now books 150 to 200 meetings a month, one org went from 0 to 15 meetings a month in about four months. That's the track record behind the build. What you get with us starts with the free audit, then a fixed one to two month setup with campaigns already live, then a month-to-month growth phase where we keep tuning it.
Pricing
How we talk about price, how we justify it, and how we handle pushback on it specifically. Working hypothesis from the Y1 financial model, not final until the dedicated pricing session.
| Tier | Setup, one-time, billed upfront | Retainer, from month 3 |
|---|---|---|
| S | $10k | $5k/mo |
| M | $16k | $8k/mo |
| L | $20k | $10k/mo |
Price objections
| Objection | Don't do this | Say instead |
|---|---|---|
| Too expensive. "That's more than we budgeted for." | Do not drop price first, that trains them to always ask again and undercuts the anchor. Do not apologize for the number. | Go back to their own numbers from Money: ACV, cost per SQL, what a hire would cost instead. Price against the GTM-engineer alternative, not against a discount. If the tier genuinely doesn't fit, cut scope first, a narrower ICP wave, fewer channels, before you touch price. |
| Can we start smaller. "Can we do a smaller pilot before committing to the full setup?" | Do not invent a discount pilot tier on the spot, that undermines the fixed-price model and trains every future prospect to ask for one too. | The free audit is the pilot, and it's already free. Everything after that is us building real infrastructure in your live accounts, not a sandbox test, that's the entire point of installing instead of renting a trial. |
| Pay only for results. "Can we just pay per meeting or per SQL instead of a retainer?" | Do not agree to a pure success fee. That turns us into the meetings-as-a-service agency we position against, and makes our revenue depend entirely on their close rate, which we don't control. | We'll add a per-SQL kicker on top of the retainer once a baseline is proven, not instead of it. The retainer pays for building and running the system; the kicker rewards it working even better. |
Expectations
What to say when they ask how many SQL they will actually get. A range tied to the tier they pick, not a single number pulled from nowhere.
| Tier | Infrastructure | Month 1 | Month 2 | Month 3+ |
|---|---|---|---|---|
| S | 5 domains (15 mailboxes), 3 LinkedIn accounts | 5-6 SQL | 8-9 SQL | 10-12 SQL |
| M | 10 domains (30 mailboxes), 5 LinkedIn accounts | 7-8 SQL | 11-12 SQL | 13-17 SQL |
| L | 15 domains (45 mailboxes), 8 LinkedIn accounts | 8-9 SQL | 13-14 SQL | 15-20 SQL |
Based on our own run-rate across email and LinkedIn, the S tier lands around 5-6 SQL the first month and grows to 10-12 a month by month three, once the infrastructure is fully seasoned. M lands 13-17, L lands 15-20, both tiers taper below straight-line scaling because more infrastructure chasing the same ICP runs into the same finite pool of accounts, not an unlimited one. The exact number moves with your niche and list quality, this is the range we build the plan around, and we adjust it with real numbers once your campaigns are live.
Objection map
Each row: what they say, what not to do, and what to say instead. Ordered by how often we'll actually hear it: agency-in-place and "I'll hire in-house" come up on almost every call, the rest are real but rarer. Re-order once we've run enough calls to know for sure.
| Objection | Don't do this | Say instead |
|---|---|---|
| Already have an agency. "We already work with an agency on this, and it's working fine." The most common live objection: most of our targets run some outbound today. | Do not trash the incumbent's performance, you have no data on it yet and it reads as cheap. Do not compete on being cheaper or faster than an agency, that is not the real gap. | Ask ownership, not performance: when that contract ends, what do you keep, the lists, the sequences, the messaging that works, the learnings from replies and calls? Most agencies hand back nothing, you restart at zero if you switch or leave. We install the same caliber of system in your own accounts, so you own it whether we stay involved or not. If their agency genuinely delivers, the question isn't who's better, it's who owns what's working. |
| Prove it, you're new. "Spice GTM barely exists, why should I trust you with this?" Comes up on almost every first call, before pricing, often before discovery even finishes. | Do not get defensive or claim a Spice GTM track record we do not have yet. Do not dodge the question or rush past it. | Be direct: the company is new, the operators are not. This exact system ran inside other companies under Sofia and Pavel, not as a vendor, as the people who built and ran it. See Results & timeline above for the real numbers. And the model itself lowers the trust bar: fixed setup, month to month after, you are not betting years on us. |
| What if it doesn't work. "How do we know this pays off before we're locked in?" Usually surfaces right before they'd otherwise say yes. | Do not oversell a guarantee we cannot actually make, and do not get cornered into a discount instead of answering the real fear. | You are not locked in. Setup is a fixed, one-time build, after that it is month to month, not a multi-year contract. If it stops producing, you leave with the system already installed in your own accounts, that is the entire point of installing instead of renting. |
| What if you get busy or leave. "It's two or three of you, what happens if you're stretched thin or move on?" A fair question for any small team, expect it from careful buyers. | Do not dismiss it as unlikely. A small team is a real, legitimate concern, treating it as paranoia loses trust fast. | That is exactly why we train your team and document everything as we build, unlike an agency's black box. If we ever became unavailable, you keep a working system and a team that knows how to run it, not a subscription that stops the day we do. |
| I'll just hire someone. The single most common reflex objection, on almost every call before anything else is said. | Do not say "you'll never hire anyone as good as us, there's no one like us." It is arrogant and unprovable, and it puts you above the buyer. | Run the car-and-the-engineer script above. Yes, you can hire, but you need a builder, not a driver. Builders are expensive, slow, and get bored once the car is built. We build it once and hand you the keys. |
| Already decided to hire. "We're already planning to bring someone in-house for this, it's not really a decision anymore." One layer past the generic version above: Prioritization lost before the call started. | This is the one we missed entirely on our one real pitch so far; it never got named out loud until the call was already lost. Do not treat it as a scheduling detail and keep pitching the engine over it. | Name it directly: sounds like the in-house hire already outranks this conversation, worth checking before we go further. Run the math copy above: a hire costs a quarter before it ships anything, we ship in weeks, priced against your cost per SQL. If the math doesn't beat the hire, this isn't a fit, say so and end the call well instead of pitching past a decision that's already made. |
| Core competency. "GTM is the core of what we do. I don't want an engine built by someone else." | Do not blur the word: "agency doesn't really mean anything because I'll be leading it." To a founder who is against outsourcing, that reads as apologizing and selling rented hands under a new label. | We don't work as an agency either. An agency sells you hours and leaves you with nothing when the contract ends. We build an IT asset that you own, installed in your own accounts. The core stays in-house, because the machine lives in your house and your team runs it. |
| No long commitment. "I want people with me for three, four years, not a contractor for three months." | Do not drift to "since we are friends now" and concede the model does not fit. Do not leave the four-year hire unchallenged. | The bored-engineer math. A senior GTM engineer earns their salary in the two-month build. After that the engine runs itself and they are overqualified and bored, so they leave anyway. Paying a senior for four years to babysit a finished engine is the expensive option. We build it, then you run it cheap: a junior operator, or ours. |
| Timezone / co-location. "The team has to be in one timezone, work closely, or they don't gel." | Do not let the call slide entirely into relocation and Pacific-time logistics and drop the engine pitch, the way the technical advantages got swallowed last time. | An engine doesn't need a timezone. It runs in your accounts around the clock. Your named operator covers your mornings, and the build is async and fully documented. This isn't a hire who has to gel with the team; it's infrastructure that is there on day one. |
| Already paying for tools. "We already have Clay, Apollo, Outreach, tools aren't the problem." Most common from ICP D, AE-heavy shops with a paid stack and no system around it. | Do not concede that a paid stack means the problem is solved. Do not let "we have the tools" end the conversation. | A tool is not a system. Clay finds records, Apollo sends messages, neither scores signals, personalizes at scale, or feeds call outcomes back into targeting. Your stack is paid for and idle; we wire it into a system instead of replacing it. |
| Already 80% done. "We're advanced AI users, our system is basically there." | Do not accept it and retreat because they call themselves advanced. Do not swallow the technical pitch and go quiet. | Hit the inefficiency with their own numbers. 35,000 emails for 35 meetings is 0.1% conversion, at that volume it is unpersonalized static-list sending, not a system. Agree the plumbing exists, then show what is missing: the agentic layer, signals, scoring, personalization at scale, and feedback from replies and calls back into targeting, the layer that turns volume into qualified conversations instead of noise. |
| Just send us meetings. "Can't you run this like an agency and send us qualified meetings?" | Do not say yes to keep the deal alive. Do not quietly become the agency we position against. | That's the one thing we won't do, on purpose. An agency that sends meetings owns the machine and the relationship; you rent results and lose them the day you stop paying. We build the machine in your accounts so you own it whether we stay involved or not. If meetings-as-a-service is genuinely what you want, we're not a fit, better to say so now than three months in. |
Outbound sequence
Three steps, personalized, not a classic cold funnel. How outstanding the first touch is decides the whole downstream conversion. Lead with value, never ask before you give.
| Step | What it is | Why |
|---|---|---|
| 1 · Opener with value baked in | A specific insight already done for them: their ICP, a competitor teardown, a signal you found. A short paragraph, not one line. TL;DR up front, "the rest is in the report." One small ask so they invest a reply. | A generic "do you handle outbound?" gets ignored. Value first earns the reply. The small ask keeps it from being over-giving. |
| 2 · Value exchange | Send the GTM / market analysis (Yaroslav's skill: GTM strategy, signals, channels, market size) plus a short personalized Loom walking them through how to read it. | The Loom stops the report from being ignored or read as "I could do this myself with Claude." It is made by hand, for them. |
| 3 · Meeting ask | Framed as a free GTM / sales audit, not a sales pitch: "we can run a free audit on a call, you tell us your problems, we show what it would cost and how we'd help, plus recommendations even if you do it yourself." | We are not closing them on a sales call. We are offering an audit with a clear takeaway, which is easier to say yes to and shows the work. |
Hey {name}, not pitching, I did a bit of homework first. {Company} sells into {segment}, and your closest comps {A} and {B} are winning on {angle}. I mapped a way to differentiate your outbound from them. TL;DR: {one concrete finding}. The rest is in a short teardown I put together for you, want me to send it over?
Outbound.
Pavel's queue: who to reach out to, and what to say. Prospect list is the ranked real leads; Sequences is the canonical A2/C2 template library plus two fully worked examples.
Prospect list · Pavel's queue
100 leads assigned to Pavel, the finalized operational_v2 queue Yaroslav sent 14 Jul (balanced 100 Sofia / 100 Pavel, Sofia has her own sheet). Ranked by score. Open each profile, send the connect note that matches the tag (see Story ICP for the exact wording), check it off.
| Rank | Contact | Company | Play | Connected | |
|---|---|---|---|---|---|
| 1 | Jillian C. Liu Head of Revenue Operations | Hebbia | C2 Stuck req | Open profile ↗ | |
| 2 | George Clemenceau Head of Revenue Operations | LiveFlow | C2 Stuck req | Open profile ↗ | |
| 3 | Akylai Kasymkulova Co-Founder | Human Delta | C2 Stuck req | Open profile ↗ | |
| 4 | Ratmir Timashev Founder | OH.io | C2 Stuck req | Open profile ↗ | |
| 5 | Adam Olien CTO/Co-Founder | ApartmentIQ | C2 Stuck req | Open profile ↗ | |
| 6 | Jeremy Ben-Meir Co-Founder & CTO | PointOne | C2 Stuck req | Open profile ↗ | |
| 7 | Cliff Weitzman Founder CEO | Speechify | C2 Stuck req | Open profile ↗ | |
| 8 | Alex Marshall Head of Sales, UK & IE | Eye-Able | C2 Stuck req | Open profile ↗ | |
| 9 | Jantzen Vargas, MBA Vice President of Revenue Operations | Stonegrove Roofing Partners | C2 Stuck req | Open profile ↗ | |
| 10 | Neal Lathia Co-Founder & CTPO | Gradient Labs | C2 Stuck req | Open profile ↗ | |
| 11 | Wayne L. Co-founder, Chief Innovation Officer | HeyGen | C2 Stuck req | Open profile ↗ | |
| 12 | Gil McVean Co Founder and Director | Genomics | C2 Stuck req | Open profile ↗ | |
| 13 | Danny Martinelli Co-Founder, Product & Partnerships | Zyphra | C2 Stuck req | Open profile ↗ | |
| 14 | Tatiana Krupenya CEO | DBeaver | C2 Stuck req | Open profile ↗ | |
| 15 | Phillip J. Henke Head of Sales | Acto | C1 Fresh req | Open profile ↗ | |
| 16 | Jeff Huisman Chief Revenue Officer (CRO) | Ambient.ai | C1 Fresh req | Open profile ↗ | |
| 17 | Luciana Juarez Head of Sales Development | Xelix | C1 Fresh req | Open profile ↗ | |
| 18 | Hemanth Meenakshisundaram Co-Founder & Chief Scientist | Canopy | C2 Stuck req | Open profile ↗ | |
| 19 | Mike Madsen Global Head of Revenue Operations | LeanData | C1 Fresh req | Open profile ↗ | |
| 20 | Nate Carr Senior Vice President of Revenue Operations | GOARC | C1 Fresh req | Open profile ↗ | |
| 21 | David Duckworth Co-founder & COO (We're hiring!) | Ben | C1 Fresh req | Open profile ↗ | |
| 22 | Lauren McCully Executive Assistant to Chief Executive Officer | DISCO | C1 Fresh req | Open profile ↗ | |
| 23 | Jed Putterman Co-Founder and Head of Engineering | Kana | C1 Fresh req | Open profile ↗ | |
| 24 | Ron Nachum Co-Founder & CEO | Sapien | C1 Fresh req | Open profile ↗ | |
| 25 | Yiannis Kiachopoulos Co-founder, CEO | Causaly | C1 Fresh req | Open profile ↗ | |
| 26 | Fabian Hedin Co-Founder | Lovable | C1 Fresh req | Open profile ↗ | |
| 27 | Quinn Litherland Founder & CEO | Revin | C1 Fresh req | Open profile ↗ | |
| 28 | Zack Sicotte Head of Sales | Albi | C1 Fresh req | Open profile ↗ | |
| 29 | Maximilian Glos Head of Sales | Roger | C1 Fresh req | Open profile ↗ | |
| 30 | Bennett Mayrock Head of Sales | Basis | C1 Fresh req | Open profile ↗ | |
| 31 | Neil Tewari Co-Founder & CEO | Conversion | C1 Fresh req | Open profile ↗ | |
| 32 | Rik Chomko Founder and Advisor | InRule | C1 Fresh req | Open profile ↗ | |
| 33 | Randy Neilson Chief Executive Officer | Cubiscan | C1 Fresh req | Open profile ↗ | |
| 34 | Jaleh Rezaei CEO & Co-founder (YC S18) | Mutiny | C1 Fresh req | Open profile ↗ | |
| 35 | Sean Murray Founder & Co-CEO | QuadSci | A2 Quiet runway | Open profile ↗ | |
| 36 | Robert Tran Co-Founder, CTO | Inkeep | A2 Quiet runway | Open profile ↗ | |
| 37 | Qasim Mithani Co-Founder and CEO | depthfirst | A2 Quiet runway | Open profile ↗ | |
| 38 | Andrew Van Noy Co-Founder | Glīd | A2 Quiet runway | Open profile ↗ | |
| 39 | Peter Albert Co-Founder | Viktor | A2 Quiet runway | Open profile ↗ | |
| 40 | Tushar Nair Co-Founder & CTO | Harper | A2 Quiet runway | Open profile ↗ | |
| 41 | David Mytton CEO | Arcjet | A2 Quiet runway | Open profile ↗ | |
| 42 | Justin Hunter Founder | Confido | A2 Quiet runway | Open profile ↗ | |
| 43 | Matan Bar-Efrat Co-Founder & CEO | Rein Security | A2 Quiet runway | Open profile ↗ | |
| 44 | Adi Singh Co-Founder | AgentMail | A2 Quiet runway | Open profile ↗ | |
| 45 | Ajay Singh CTO / Co-Founder | Airrived | A2 Quiet runway | Open profile ↗ | |
| 46 | Dhruv Amin Co-Founder / CEO | Anything | A2 Quiet runway | Open profile ↗ | |
| 47 | Windsor Nguyen Co-Founder & CTO | Dedalus Labs | A2 Quiet runway | Open profile ↗ | |
| 48 | Itai Gafni Co-Founder & CEO | Huskeys | A2 Quiet runway | Open profile ↗ | |
| 49 | Eyal Bukchin CTO & Co-Founder | MetalBear | A2 Quiet runway | Open profile ↗ | |
| 50 | Paul Gambrell Co-Founder | Bourn | A2 Quiet runway | Open profile ↗ | |
| 51 | Charley Lee Co-Founder | Datacurve | A2 Quiet runway | Open profile ↗ | |
| 52 | Varun Sivaram Founder and CEO | Emerald AI | A2 Quiet runway | Open profile ↗ | |
| 53 | Victoria Toli Co-Founder & President | FINNY | A2 Quiet runway | Open profile ↗ | |
| 54 | Sriharsha Guduguntla Co-Founder & CEO | Hyperbound | A2 Quiet runway | Open profile ↗ | |
| 55 | Sid Malladi Co-Founder/CEO | Nuvo | A2 Quiet runway | Open profile ↗ | |
| 56 | Matthias Nagel Founder & COO | Pyck | A2 Quiet runway | Open profile ↗ | |
| 57 | Dr. Camillo Werdich CEO | Founder | Sinpex | A2 Quiet runway | Open profile ↗ | |
| 58 | Carlos Rubal Co-Founder, New Venture | AAZZUR | A2 Quiet runway | Open profile ↗ | |
| 59 | Doni Hoti CEO & Co-Founder | Adclear | A2 Quiet runway | Open profile ↗ | |
| 60 | Christina Qi Chief Executive Officer | Databento | A2 Quiet runway | Open profile ↗ | |
| 61 | Prof Iain H Woodhouse Knowledge & Outreach Lead - Co-founder | Earth Blox | A2 Quiet runway | Open profile ↗ | |
| 62 | Ben Warner Co-Founder | Electric Twin | A2 Quiet runway | Open profile ↗ | |
| 63 | Grace Hanson Co-Founder & CEO | Elysian | A2 Quiet runway | Open profile ↗ | |
| 64 | Eric Ciarla Co-Founder & Chief Growth Officer | Firecrawl | A2 Quiet runway | Open profile ↗ | |
| 65 | Mustafa Girgin Co-Founder | Lucida AI | A2 Quiet runway | Open profile ↗ | |
| 66 | Dr. Najam Kidwai Co-Founder and Board Director | TransFi | A2 Quiet runway | Open profile ↗ | |
| 67 | David Yue Co-Founder & CEO | Accordance | A2 Quiet runway | Open profile ↗ | |
| 68 | Imanuel H. Kaiser Co-Founder & President | Bloxley | A2 Quiet runway | Open profile ↗ | |
| 69 | Pierre Anderson Co-Founder | Bracket | A2 Quiet runway | Open profile ↗ | |
| 70 | Chris Paver Co-Founder + Chief Operating Officer | Dataro | A2 Quiet runway | Open profile ↗ | |
| 71 | Alena Tuttle Co-Founder | Hardline | A2 Quiet runway | Open profile ↗ | |
| 72 | Eric Stecker Co-Founder | Insight Health | A2 Quiet runway | Open profile ↗ | |
| 73 | Jansen Derr Founder | Loman AI | A2 Quiet runway | Open profile ↗ | |
| 74 | Niklas Weidmann Co-Founder & Managing Director | Tilla Technologies | A2 Quiet runway | Open profile ↗ | |
| 75 | Zach Kamran Co-Founder & CTO | Simple AI | A2 Quiet runway | Open profile ↗ | |
| 76 | Konstantinos Faliagkas Co-Founder & CTO | Wealthyhood | A2 Quiet runway | Open profile ↗ | |
| 77 | Nate Barbettini Founder, Member of Technical Staff | Arcade.dev | A2 Quiet runway | Open profile ↗ | |
| 78 | Josh Benaron Founder & CEO | Irys | A2 Quiet runway | Open profile ↗ | |
| 79 | Sriharsha Chintalapani Co-Founder & CTO | Collate | A2 Quiet runway | Open profile ↗ | |
| 80 | Ramiro Iglesias Concepción CEO & Co-Founder | Crescenta | A2 Quiet runway | Open profile ↗ | |
| 81 | Sherry Chiramattel Kunjachan Co-Founder and CTO | eternal.ag | A2 Quiet runway | Open profile ↗ | |
| 82 | Raphael Karger Co-Founder & CTO | ZeroPath | A2 Quiet runway | Open profile ↗ | |
| 83 | Sara Egetemeyr COO & Co-Founder | PENEMUE | A2 Quiet runway | Open profile ↗ | |
| 84 | Animesh Koratana Founder & CEO | PlayerZero | A2 Quiet runway | Open profile ↗ | |
| 85 | Steven Schmatz Co-Founder / CTO | Taxwire | A2 Quiet runway | Open profile ↗ | |
| 86 | Daniel León Co-Founder & CRO | Akave Cloud | A2 Quiet runway | Open profile ↗ | |
| 87 | Sergio Prada Co-Founder and CTO | Metal | A2 Quiet runway | Open profile ↗ | |
| 88 | Zhenwen Dai Co-Founder and CTO | Trent AI | A2 Quiet runway | Open profile ↗ | |
| 89 | Jash Minocha Founder and COO | BQP | A2 Quiet runway | Open profile ↗ | |
| 90 | Lidan Hazout Co-Founder and CTO | Capsule Security | A2 Quiet runway | Open profile ↗ | |
| 91 | César Rodríguez Rosario CEO / Founder | Commutator Studios | A2 Quiet runway | Open profile ↗ | |
| 92 | Arjun S Khanna Co-Founder & COO | Mozart AI | A2 Quiet runway | Open profile ↗ | |
| 93 | Austin DeAngelis Co-Founder and COO | furl | A2 Quiet runway | Open profile ↗ | |
| 94 | Nathan Allman Founder & CEO | Ondo Finance | A2 Quiet runway | Open profile ↗ | |
| 95 | Ryan Howard Co-Founder, Chief Operating Officer, and Head of Finance | Coral Care | A2 Quiet runway | Open profile ↗ | |
| 96 | Aescobar Mike Chief Operating Officer | Rhea Finance | A2 Quiet runway | Open profile ↗ | |
| 97 | Andrew Schwartz COO/CPO & Co-Founder | Rebar | A2 Quiet runway | Open profile ↗ | |
| 98 | Ben H. Co-founder/CTO | Antiverse | A2 Quiet runway | Open profile ↗ | |
| 99 | Léonard Strouk Co-Founder & CTO | Living Models | A2 Quiet runway | Open profile ↗ | |
| 100 | Tolga Osman Bozkurt Co-founder/Director | Resurrect Bio | A2 Quiet runway | Open profile ↗ |
Event · LinkedIn "GTM in LATAM"
The finalized 66-person connection list from the LinkedIn event "GTM in LATAM: where to find your first B2B clients" (484 attendees screened down to 66 by AnySite signal scoring). Same format as the prospect list above: ranked by score, check the box once you have sent the connect.
| Rank | Contact | Company | Band | Connected | |
|---|---|---|---|---|---|
| 1 | Vasily Petrovskiy Head of Analytics and AI Operations | Voiso | A Priority | Open profile ↗ | |
| 2 | Val Serezhkin Marketing Lead | Ænix | A Priority | Open profile ↗ | |
| 3 | Margarita Tikhonova Head of Marketing | Эйч | B Design partner | Open profile ↗ | |
| 4 | Ekaterina Yaremenko International Marketing Director | Positive Technologies | C Network | Open profile ↗ | |
| 5 | Данил Ращупкин CEO | ТОО Teleport 3D | C Design partner | Open profile ↗ | |
| 6 | Pavel Taranov Founder CTO Fractional CTO Independent Director | TarCom | C Design partner | Open profile ↗ | |
| 7 | Dmitry Savichev CPO | Rightech LLC | C Design partner | Open profile ↗ | |
| 8 | Semyon Berezovskiy Cofounder | Istok AI | C Design partner | Open profile ↗ | |
| 9 | Дилфуза Самандарова General Director and Managing Partner | Business Media Central Asia Uzbekistan | C Network | Open profile ↗ | |
| 10 | Артём Гизерский Учредитель | TASKONFF | C Design partner | Open profile ↗ | |
| 11 | Valentina Jelvacova Старший менеджер проекта | Feloom | C Design partner | Open profile ↗ | |
| 12 | Alena Ryabova Product Marketing Manager | Mellow | C Priority | Open profile ↗ | |
| 13 | Ali Dashdamirov Marketing Director | Profex Group | C Network | Open profile ↗ | |
| 14 | Proshinsky Vladislav Учредитель | Proshinsky.com | D Design partner | Open profile ↗ | |
| 15 | Marat Bruk Партнёр | Latenode.com | D Priority | Open profile ↗ | |
| 16 | Yahor Abdulin Head of Trading House - OMZ | Пинский опытно-механический завод | D Network | Open profile ↗ | |
| 17 | Nik Pavlov Chief Marketing Officer | Centida Consulting | D Signal rescue | Open profile ↗ | |
| 18 | Andrei Karpach co-founder | TeamTeam | D Network | Open profile ↗ | |
| 19 | Jamila Manafova Founder and CEO | CharterBay Shipping | D Design partner | Open profile ↗ | |
| 20 | Dmitry Shirokov Co-founder | AgentFi | D Design partner | Open profile ↗ | |
| 21 | Sayat Kakzhanov Founder &CEO | Regent Protocol | D Design partner | Open profile ↗ | |
| 22 | Andrew Baturin CMO | Tumodo | D Priority | Open profile ↗ | |
| 23 | Viktoria Vostrikov | Garna.io | D Priority | Open profile ↗ | |
| 24 | Vadim Chepel Product & Strategy Lead | IntrovertAI.co | D Design partner | Open profile ↗ | |
| 25 | David Merkulov CEO & Founder | hao | D Design partner | Open profile ↗ | |
| 26 | Laziz Iskandarov Founder CEO | TDK | D Design partner | Open profile ↗ | |
| 27 | Madina Nurmatova Cofounder & CEO | WorkFindMe | D Design partner | Open profile ↗ | |
| 28 | Alisher Abdulloh Замиститель гендиректора по продажам и маркетингу | ООО "ХУМО" | D Network | Open profile ↗ | |
| 29 | Andrey Balaev Chief Product Officer | IBLS | D Network | Open profile ↗ | |
| 30 | Mirsəid Hüsülü Founder & CEO | MR Technology | D Design partner | Open profile ↗ | |
| 31 | Fidan Azimova Co-Founder and CPO | AeroVolve | D Network | Open profile ↗ | |
| 32 | Artem Poltoratskiy Founder | AI Infrastructure for Clinical Research | D Priority | Open profile ↗ | |
| 33 | Olga Andreeva Director of Strategic Marketing | Brand Analytics | D Priority | Open profile ↗ | |
| 34 | Pavel Magaril | Algodocs | D Priority | Open profile ↗ | |
| 35 | Gennady Sedykh Founder & CEO | Maritime AI Platform | D Design partner | Open profile ↗ | |
| 36 | Natia Goletiani Founder and CEO | Matilda Events | D Design partner | Open profile ↗ | |
| 37 | Timur Kurmangozhin CEO & Founder at ERFIX COMPANY Software Architect LegalTech | Erfix Company | D Design partner | Open profile ↗ | |
| 38 | Андрей Васильев Technical Co-Founder | Accord AI | D Design partner | Open profile ↗ | |
| 39 | Alexander Kovalenko CPO | TELENORMA Gruppe | D Network | Open profile ↗ | |
| 40 | Aliaksandr Sabolka Co-founder | Smart Nasal Ring | D Network | Open profile ↗ | |
| 41 | Atabek Shamshetovich Chief Executive Officer | AT Group Inter Power | D Network | Open profile ↗ | |
| 42 | Gregory Karfo | ChargeMeCar | D Network | Open profile ↗ | |
| 43 | Joshgun Adilov Founder | CA Group LLC | D Network | Open profile ↗ | |
| 44 | Katerina Gudym Co-Founder & Chief Wellness Officer (CWO) At Tailor Fit AI Dubai, UAE | Tailor Fit AI | D Network | Open profile ↗ | |
| 45 | Luna Seol Founder & Visual Identity Designer | Luna Space | D Network | Open profile ↗ | |
| 46 | Oleg Polushin Founder & Fractional Customer Success Director | StopOttok | D Network | Open profile ↗ | |
| 47 | Tabriz Ismayilov Business Professional | Предприниматель | D Network | Open profile ↗ | |
| 48 | Yerzhan Beisembayev Founder LVK | Lifevkaif | D Network | Open profile ↗ | |
| 49 | Zura Gorgodze Chief Executive Officer | Stickerstellar | D Network | Open profile ↗ | |
| 50 | Nini Tvaltvadze Head of Growth and Business Development | KiwiPost | D Network | Open profile ↗ | |
| 51 | Suren Arutinyan | BIZON Business Club | D Network | Open profile ↗ | |
| 52 | Сардор Икромов Коммерческий директор | Birinchi Business Club | D Network | Open profile ↗ | |
| 53 | Rashid Guliyev Regional Sales Director | KORA | D Network | Open profile ↗ | |
| 54 | Yermek Aibulatov Product Marketing Manager | reKassa | D Design partner | Open profile ↗ | |
| 55 | Elizaveta Petrova Head of Busniness Development | ANIX | D Design partner | Open profile ↗ | |
| 56 | Maria Poleshchuk Head of Marketing & GTM | AHUB:AI | D Priority | Open profile ↗ | |
| 57 | Daria Demeshina | — | D Network | Open profile ↗ | |
| 58 | Maria Kulesho | — | D Network | Open profile ↗ | |
| 59 | Alexey Momot | — | D Network | Open profile ↗ | |
| 60 | Konstantin Ismagilov Product Monetization & Revenue Lead | FinalPrice Travel LTD | D Network | Open profile ↗ | |
| 61 | Петр Медведев Product Marketing Manager | MKSKOM | D Network | Open profile ↗ | |
| 62 | Arianna Barbesino Marketing Manager | Movylo, Inc | D Network | Open profile ↗ | |
| 63 | Yan Chizhevskiy Head of International Growth | SBDA Group | D Priority | Open profile ↗ | |
| 64 | Jale M. Aliyeva | All in One Technologies | D Network | Open profile ↗ | |
| 65 | Michael Kozhevnikov | — | D Network | Open profile ↗ | |
| 66 | Aline P. | Garna | D Priority | Open profile ↗ |
Sequences
The finalized 3-touch canon for both hypotheses (PR #1 in spice-gtm-hq: 9 plays, QA 97/100), plus two sequences actually written on real leads from the prospect list above. Fold a play open, copy what you need.
needs_detail for most A2 funding facts, so bulk rendering waits on that research pass. The two worked sequences at the bottom are hand-filled from verified data as a proof of the system.Rules that do not move
| Rule | What it means |
|---|---|
| 3 touches | Step 1 earns trust, offers the artifact, asks "Reply yes". Step 2 adds one new idea, never a repeat. Step 3 is the break-up: recap, then forward / Calendly / no. |
| Calendly placement | Only in Step 3 and after a positive reply. Never in Steps 1-2. |
| One contact per company | First pass: one person, one channel, one angle. |
| Artifact must be READY | If the one-pager is not built, the sequence does not send. "I built / I mapped" only if the file exists. |
| Fact vs hypothesis | A2/C2 picks the angle; it never appears in copy as a claimed fact. No number without a public source. |
| Positioning | Install-not-rent: we put GTM engineering in your stack, you own it. Not a lead-gen agency. |
A2 · after the round
Trigger: seed or Series A closed 3-12 months ago, a GTM/growth priority is public, repeatable motion still unproven. 4 plays.
1. Founder / CEO A2 Sofia · Email
Angle: post-round priority → active market choice. · Artifact: one-page market signal map for {{company}}.
Subject: the post-round GTM question
Hi {{first_name}},
Your round put {{funding_priority}} on the agenda. {{months_since_round}} months later, the useful GTM question is which accounts have changed enough to act on now - not how large the database is.
Instead of renting meetings from an agency, we install a signal-based GTM engine directly in your stack. I mapped that into a one-page signal map for {{company}}: the target-account definition, two observable triggers, and the route from signal to outreach.
Reply yes and I'll send it.
Sofia Altman
Spice GTM - in-house GTM engines · spicegtm.com
Вставляется после первого абзаца и только если цифры входят в готовую карту:
Of {{sam_accounts}} accounts that fit the reachable ICP, {{monthly_signal_accounts}} showed one of the signals we screened for in the last 30 days, including {{signal_example_1}}.
Hi {{first_name}},
One useful distinction in the map: fit says who could buy; a signal says why an account is worth action now. We wire this logic directly inside your CRM, so your team owns the infrastructure and doesn't depend on rented channels.
Is that market-to-outreach loop owned by you, Sales, or Ops today?
Hi {{first_name}},
Quick recap: we install GTM engines in your stack; you own them.
The signal map for {{company}} is ready. Forward it to the owner, compare notes: {{calendly_url}}, or reply no and I'll stop here.
Sofia Altman
Spice GTM - in-house GTM engines · spicegtm.com
2. CRO / VP Sales / Head of Sales A2 Sofia · LinkedIn
Angle: signal context for AEs, not a larger list. · Artifact: one-page signal play for {{company}}.
Пустой инвайт - canonical default. Не использовать funding pitch в connection note.
{{first_name}} - {{months_since_round}} months after the round, with {{funding_priority}} on the agenda, which accounts should {{company}}'s AEs act on now?
We install signal-based engines in your stack so reps prospect with reasons, not templates. I have a one-page play for {{company}}: the account change, why it matters, and the outreach path.
Reply YES and I'll send it.
- Sofia, Spice GTM
The sample contains {{monthly_signal_accounts}} accounts showing {{specific_trigger}} in the last 30 days.
{{first_name}} - one design choice in the play: every account arrives with a reason-now, not just a score. We build this in your CRM, keeping data and routing rules inside your stack rather than a parallel black box.
Is this owned by Sales, Ops, or still founder-led?
{{first_name}} - quick recap: we install GTM engines in your stack; you own them.
The signal play for {{company}} is ready. Forward it, compare notes: {{calendly_url}}, or reply NO.
3. COO A2 Pavel · Email
Angle: stated growth priority → explicit operating model. · Artifact: one-page GTM operating map for {{company}}.
Subject: the GTM operating model
Hi {{first_name}},
Your round announcement put {{funding_priority}} on the agenda. {{months_since_round}} months later, the operating question is which GTM work needs a permanent owner - and which infrastructure should be built once, documented, and handed over.
We install GTM engines inside our clients' own accounts, handing over the keys so they own the machine. For {{company}}, that split runs across signal inputs, routing, ownership, and the feedback loop. I have it in a one-page blueprint for {{company}}.
Reply yes and I'll send it.
Pavel Papin
Spice GTM - in-house GTM engines · spicegtm.com
Hi {{first_name}},
The useful split is not "people versus automation." It is recurring judgment versus repeatable infrastructure. We wire the infrastructure directly into your stack, ensuring that workflows do not depend on one person's memory or a vendor's tool.
Does that ownership sit with you, Revenue, or an Ops lead today?
Hi {{first_name}},
Quick recap: we install GTM systems in your stack and hand over the keys.
The operating blueprint for {{company}} is ready. Forward it, book time: {{calendly_url}}, or reply no and I'll close the loop.
Pavel Papin
Spice GTM - in-house GTM engines · spicegtm.com
4. Technical Founder A2 Pavel · Telegram
Angle: GTM as observable instrumentation. · Artifact: one-page technical signal architecture for {{company}}.
Use only: devtools / AI infrastructure + подтверждённый публичный рабочий Telegram.
{{first_name}}, привет. Это Павел из Spice GTM. После раунда {{company}} обозначила {{funding_priority}}.
Мы ставим GTM-пайплайны в ваш стек - они остаются у вас, не арендуются как лиды. Для devtools схема такая: {{tech_dependency}} → сигнал аккаунта → outreach → outcome обратно в модель.
Есть одностраничная схема под {{company}}. Ответь да - скину.
Только при подтверждённой migration hypothesis:
Отдельно отметил переходы с {{competitor_tech}} как один из проверяемых сигналов.
{{first_name}} - один принцип из схемы: raw activity не равна intent. Сигнал становится полезным только после account match и feedback от sales. Мы настраиваем эту петлю в ваших аккаунтах, без внешнего вендор-лока.
Кто у вас сейчас владеет этой петлёй - founder, sales или ops?
{{first_name}} - мы ставим GTM-системы в ваш стек; вы ими владеете.
Схема для {{company}} готова. Перешли owner'у, выбери время: {{calendly_url}} - или ответь «нет».
C2 · stuck req
Trigger: a relevant GTM/RevOps role has been open 45+ days (stale_45d) or was reposted (repost). 5 plays.
1. Founder / CEO C2 Sofia · Email
Angle: build before hire without undermining the hire. · Artifact: one-page build-before-hire map for {{company}}.
Subject: the open {{role}} role
Hi {{first_name}},
[STALE] Your {{role}} role has been open for {{days_open}} days.
[REPOST] I noticed {{company}} reposted the {{role}} role.
The JD combines {{job_component_1}} with {{job_component_2}}. That leaves a system to define while the search runs.
We install GTM engines in your accounts. The one-page map for {{company}} splits this into build now, operate weekly, and future-owner judgment.
Reply yes and I'll send it.
Sofia Altman
Spice GTM - in-house GTM engines · spicegtm.com
Вставляется только если accounts и signal logic входят в готовый артефакт:
Separately, {{monthly_signal_accounts}} target accounts showed one of the approved signals in the last 30 days, including {{signal_example_1}}.
Hi {{first_name}},
The map separates install-once integrations from judgment the internal owner should retain. We build it in your stack, so the new hire inherits working infrastructure, not a rented agency pipeline.
Who covers that loop while the role is open?
Hi {{first_name}},
Quick recap: we install GTM engines in your stack; you own them.
The build-before-hire map for {{company}} is ready. Forward it, compare notes: {{calendly_url}}, or reply no and I'll stop here.
Sofia Altman
Spice GTM - in-house GTM engines · spicegtm.com
2. CRO / VP Sales / Head of Sales C2 Sofia · LinkedIn
Angle: protect AE attention while the role is open. · Artifact: one-page interim signal play for {{company}}.
Пустой инвайт - canonical default. Не использовать vacancy pitch в connection note.
{{first_name}} - [STALE] The {{role}} seat has been open {{days_open}} days.
{{first_name}} - [REPOST] I noticed {{company}} reposted the {{role}} role.
While the seat is open, which account changes should reach AEs? We install the signal engine in your stack; you own it. The play for {{company}} covers {{signal_example_1}} and {{signal_example_2}} with context.
Reply YES and I'll send it.
- Sofia, Spice GTM
{{first_name}} - useful distinction in the play: reps see the account change and why it matters, not another static list. We build this routing directly in your CRM so you own the intelligence, not rent it from an external vendor.
Is that feed currently owned by Sales, Ops, or nobody formally?
{{first_name}} - quick recap: we build GTM infrastructure in your stack, not a rented pipeline.
The signal play for {{company}} is ready. Send this to the owner, book time: {{calendly_url}}, or reply NO.
3. COO C2 Pavel · Email
Angle: one job post contains several operating layers. · Artifact: JD-to-system blueprint for {{company}}.
Subject: breaking down the {{role}} req
Hi {{first_name}},
[STALE] Your {{role}} req has been open for {{days_open}} days.
[REPOST] I noticed {{company}} reposted the {{role}} req.
The JD combines {{job_component_1}} with {{job_component_2}}, but those need different ownership: some work is built once; some requires ongoing judgment.
We install GTM infrastructure in your stack so you own the machine rather than renting it. I broke the req into three layers - build now, operate weekly, hand over to the future hire - in a one-page blueprint for {{company}}.
Reply yes and I'll send it.
Pavel Papin
Spice GTM - in-house GTM engines · spicegtm.com
Hi {{first_name}},
The blueprint makes each handoff explicit: source, logic, destination, owner, and failure state. We document and wire this inside your systems, preventing GTM knowledge from living only in the eventual hire's head or walking out with them.
Does the interim owner sit with Ops or Revenue today?
Hi {{first_name}},
Quick recap: we install GTM infrastructure in your stack; {{company}} owns every tool and workflow.
The blueprint is ready. Forward this to the owner, book time: {{calendly_url}}, or reply no and I'll close the loop.
Pavel Papin
Spice GTM - in-house GTM engines · spicegtm.com
4. RevOps Lead / Head of RevOps C2 Pavel · LinkedIn
Angle: specialist build capacity without taking ownership away from RevOps. · Artifact: build-vs-own technical schema for {{company}}.
Пустой инвайт - canonical default. Не использовать vacancy pitch в connection note.
{{first_name}} - [STALE] {{days_open}} days open for a role mixing {{job_component_1}} and {{job_component_2}}.
{{first_name}} - [REPOST] Reposted {{role}} role, still mixing {{job_component_1}} and {{job_component_2}}.
Two different ownership models in one seat. We install GTM engines inside your stack so you retain full control. I have a build-vs-own schema for {{company}} - separating build-now tasks from what internal RevOps should retain.
Reply YES and I'll send it.
- Pavel, Spice GTM
{{first_name}} - one constraint in the schema: data model, routing rules, and documentation stay in the client stack - no parallel black box. We act as a build studio, keeping the keys entirely on your side.
Is the current bottleneck build capacity, or unclear ownership between teams?
{{first_name}} - quick recap: we build GTM systems in your stack and leave you the keys.
The schema for {{company}} is ready. Route this to the owner, compare notes: {{calendly_url}}, or reply NO.
5. Technical Founder C2 Pavel · Telegram
Angle: the vacancy describes an event/data pipeline. · Artifact: one-page technical architecture for {{company}}.
Use only: devtools / AI infrastructure + подтверждённый публичный рабочий Telegram.
{{first_name}}, привет. Это Павел из Spice GTM. [STALE] Увидел, что роль {{role}} у {{company}} открыта {{days_open}} дней.
{{first_name}}, привет. Это Павел из Spice GTM. [REPOST] Увидел, что команда {{company}} переопубликовала роль {{role}}.
Мы ставим GTM-пайплайн в ваш стек; он остаётся вашим. В JD {{job_component_1}} и {{job_component_2}} - это source → scoring → routing → feedback. Одностраничная схема для {{company}} готова.
Ответь да - скину.
Только если dependency подтверждён:
В signal layer отдельно учёл аккаунты, использующие {{tech_dependency}}.
{{first_name}} - один принцип из схемы: событие становится GTM-сигналом только после account match и feedback от sales - иначе это просто шум. Мы разворачиваем эту петлю данных в ваших аккаунтах, вы ею полностью владеете.
Кто сейчас владеет этой петлёй у вас?
{{first_name}} - мы ставим GTM-инфраструктуру в ваш стек без вендор-лока.
Схема для {{company}} готова. Перешли ответственному, забронируй время: {{calendly_url}} - или ответь «нет».
Written from real leads
Not hypothetical: one A2 and one C2 sequence, fully rendered on real contacts already sitting in the Outbound queue, with sources for every substituted fact.
Real row from the Outbound queue (#70, Chris Paver, Co-Founder + COO). Written on play 3, COO, Pavel, Email. Funding facts verified against the public Series A announcement, not the routing CSV: that row still carries needs_detail for funding date and priority, so this is hand-researched, not pulled straight from the pipeline.
- Contact
- Chris Paver, Co-Founder + Chief Operating Officer
- Round
- $14.28M Series A, led by Blueprint Equity, announced 17 Feb 2026
- Months since round
- 4, as of 15 Jul 2026
- Funding priority
- expanding go-to-market across sales, customer success, and marketing
- Source
- PR Newswire, 17 Feb 2026 ↗
Subject: the GTM operating model
Hi Chris,
Your round announcement put expanding go-to-market across sales, customer success, and marketing on the agenda. 4 months later, the operating question is which GTM work needs a permanent owner, and which infrastructure should be built once, documented, and handed over.
We install GTM engines inside our clients' own accounts, handing over the keys so they own the machine. For Dataro, that split runs across signal inputs, routing, ownership, and the feedback loop. I have it in a one-page blueprint for Dataro.
Reply yes and I'll send it.
Pavel Papin
Spice GTM, in-house GTM engines, spicegtm.com
Hi Chris,
The useful split is not "people versus automation." It is recurring judgment versus repeatable infrastructure. We wire the infrastructure directly into your stack, ensuring that workflows do not depend on one person's memory or a vendor's tool.
Does that ownership sit with you, Revenue, or an Ops lead today?
Hi Chris,
Quick recap: we install GTM systems in your stack and hand over the keys.
The operating blueprint for Dataro is ready. Forward it, book time: {{calendly_url}}, or reply no and I'll close the loop.
Pavel Papin
Spice GTM, in-house GTM engines, spicegtm.com
Real row from the Outbound queue (#1, Jillian C. Liu, Head of Revenue Operations). Written on play 4, RevOps Lead / Head of RevOps, Pavel, LinkedIn. Both JD components below are quoted from the live posting's raw_job_description field, not summarized.
- Contact
- Jillian C. Liu, Head of Revenue Operations
- Open req
- GTM Engineer, open 56 days (stale_45d)
- Job component 1
- AI-powered workflow development across Claude, Clay, and prompt libraries for GTM teams
- Job component 2
- owning and administering the GTM stack (Salesforce, Outreach, Gong, Apollo, Clay)
- Source
touch_pending.csv, run scale-01, scoring_v3, row for Hebbia
Empty invite, no vacancy pitch, per canon.
Jillian, 56 days open for a role mixing AI-powered workflow development across your GTM stack with owning and administering that same stack (Salesforce, Outreach, Gong, Apollo, Clay).
Two different ownership models in one seat. We install GTM engines inside your stack so you retain full control. I have a build-vs-own schema for Hebbia: separating build-now tasks from what internal RevOps should retain.
Reply YES and I'll send it.
Pavel, Spice GTM
Jillian, one constraint in the schema: data model, routing rules, and documentation stay in the client stack, no parallel black box. We act as a build studio, keeping the keys entirely on your side.
Is the current bottleneck build capacity, or unclear ownership between teams?
Jillian, quick recap: we build GTM systems in your stack and leave you the keys.
The schema for Hebbia is ready. Route this to the owner, compare notes: {{calendly_url}}, or reply NO.
{{calendly_url}}, no real Calendly link was substituted, and the actual artifact (the one-page blueprint for Dataro, the build-vs-own schema for Hebbia), neither is built yet. Per the framework's own send gate, a missing artifact blocks sending regardless of how good the copy is.