SpiceGTM system overview · 08.2026
qualified pipeline. pay on delivery.

Performance-based outbound.

AI-native, signal-led outbound built for complex B2B markets.

spicegtm.com
SpiceGTMthe core
01 · the whole thing in three ideas

Three questions decide whether outbound works.

pillar 1 · the boundary
Who.
The market, counted before anyone is sourced.

We draw the edge of who can be sold to and count it against real databases: segments, thresholds, geography, the buying roles inside each account. The count is frozen before the first list is built, so nobody argues about the size of the market in month two.

pillar 2 · the trigger
Why now.
A public, dated event on the account.

An account joins the queue when something happened to it: a raise, a hiring pattern, a change of platform, a person moving into the seat. No signal, no message. That single rule is what keeps the volume low and the reply rate where it is.

pillar 3 · the claim
Evidence.
Every line points at a fact.

Each touch has to name the fact it stands on, and each fact carries a link and a date. A sentence that stands on nothing is blocked before a human sees it, which is the difference between personalization and a merge field with a first name in it.

The hard part was never the sending. It is knowing who, why this week, and on what evidence.

02 / 08
SpiceGTMhow a launch runs
02 · six steps, four of them decided by a person

One launch, start to finish.

step 01 · a person decides
Frame
The market is measured once and frozen. The brief names the segment, the roles, the reason to write and the spend ceiling.
segmentsrolesceiling
step 02 · the machine
Collect
Our own records first, then the public reasons to write. Anyone on the exclusion list is dropped before anything else happens.
own datapublic signalsexclusions
step 03 · a person approves
Enrich
Checkable facts are attached to every target, each with a link and a date. Missing addresses are bought only against a counted shortfall.
factssourcesaddresses
step 04 · the machine
Write
One pass per person writes that person's whole sequence, seeing only their facts, and has to say which fact each touch leans on.
per personper channelchecked
step 05 · a person approves
Load
The launch is read whole and approved as a whole. It is then loaded into the sending tools as a draft, and the contents are read back to confirm.
reviewapproveverify
step 06 · a person closes it
Outcome
What the channels observed comes back and is counted. An unsubscribe becomes a block that outlives this launch and every one after it.
repliesblocksverdict

A second attempt is a new launch, not an edit of the old one. Nobody in it can receive a second first touch.

03 / 08
SpiceGTMthe line
03 · what the machine is not allowed to do

It prepares the whole launch and stops.

sending

A person presses Start.

There is no send, no start and no activate anywhere in the code, in any tool client. The machine can read that Start was pressed and nothing else, which is the only path from a prepared launch to a live one.

the input

Approval freezes the brief.

Approving a launch records a fingerprint of the whole brief. Editing the request afterwards stops the run rather than quietly producing something the approver never read.

the money

Spend is capped, then recorded.

Every paid call is written down before it goes out and corrected to the real price when it returns. A ceiling is set per launch, and a shortfall of zero means zero calls regardless of what was approved.

the copy

Five checks before a human reads it.

A touch is blocked if it references nothing, borrows someone else's fact, runs long, asks a question without asking one, or repeats another person's opening. Approval covers the package as one: move a target and it breaks.

0send commands anywhere in the code
1person, pressing Start by hand

Each of these closed a mistake that had already happened. None of them is a policy in a document.

04 / 08
SpiceGTMon your side
04 · what any of this buys you

What arrives, and where it lands.

every sql

Arrives with its evidence.

The account, the buyer, the signal we opened on and the correspondence that produced it. You can check any one of them against the definition agreed before launch, and reject one that fails it.

your crm

Records land on your side.

Threads, objections and outcomes are written into your CRM as they happen, not summarised into our slides at month end. Your closers walk into a conversation that already has a history.

your domains

Sending runs off our estate.

Domains and mailboxes are registered in your name, warmed and paid for by us during the term, and handed over on exit. Your main corporate domain is never used for cold outreach.

your list

Exclusions apply before the first touch.

You hand over the companies and people nobody may approach, in any form you like including hashes or domains. An unsubscribe becomes permanent across every launch that follows.

Three channels: LinkedIn, email and Telegram. One sequence per person, never two.

05 / 08
SpiceGTMtrack record
05 · proof

Proof across three B2B markets.

refty.ai · real estate intelligence · Dubai · named with permission
200
meetings a month
Outbound that feels like a concierge for 60,000 brokers. The SDR team scaled 5 → 25 and reply rates reached 55-65%, on a fifteen-minute signal-to-contact SLA.
international data SaaS · under NDA · name on the call
50
meetings in four months
A niche burned by years of template outreach, re-entered with a reason to write per account: 8,024 companies mapped and warm reply to meeting up from 23% to 40%.
academy.nebius.com · Nebius Group · NASDAQ: NBIS · built by our co-founder as CCO
$2M
qualified pipeline over the year
Outbound synced with the sales calls, so call evidence became the targeting filters. Three converting segments and product-market fit in under six months.

$2M is pipeline, not revenue. Full write-ups at spicegtm.com/cases; the NDA name is verifiable on the call.

06 / 08
SpiceGTMcommercial model
06 · how we are paid

Performance fee per SQL.

agencyfixed retainer

Invoiced anyway.

  • The price is agreed before the market has answered anything
  • It pays for volume of work: lists built, messages sent, hours logged
  • The monthly report is activity: sequences live, invites accepted, open rates
  • A quarter with no pipeline movement is invoiced in full
Spice GTMper SQL

Earned after delivery.

  • Paid only when the written criteria are met
  • Each SQL recorded in your CRM with its account, buyer and signal
  • Qualification checked against the definition agreed before launch
  • No SQL means no invoice

One small setup instalment covers infrastructure, data and operator time, and it is capped before launch. Everything after it moves with the result.

07 / 08
SpiceGTMhow we start
07 · from agreed outcome to live outreach in 1-2 weeks

How we start.

stage 01 · define

Agree the outcome.

The segment, the buying roles, the definition of an SQL and how each one is evidenced. Attribution, the exclusion list, the monthly cap and both figures, in writing.

free · one call
stage 02 · build

Build the motion.

The first cohort sourced and screened, domains and mailboxes warmed in your name, signals wired, sequences written per micro-segment, your CRM connected.

setup instalment · 1-2 weeks
stage 03 · run

Deliver and improve.

We work the replies, log the objections and deliver each SQL with its evidence. Lists and copy are revised weekly against what actually came back.

per SQL · the cap is yours
Qualified pipeline.
Pay on delivery.
Book the 30-minute call
08 / 08