GTM OS

A cold prospecting core: change language, filters, and angle — not the nucleus. Demand by system, not referrals.

What it is

A B2B outbound system that stays installed in the client’s team — not a rented SDR that shuts off when the contract ends.

Is	Is not
Manual of criteria, milestones, and reply protocol	Ads or social agency
Same reusable machine per vertical: change ICP and message, not the architecture	Wiki for someone else’s SaaS
Pipeline the client can operate	Dump of lists, CRM, or APIs

Field	KEEP
Buyer	Founder / CEO or B2B ops lead
Signal +	Already sells; the bottleneck is a repeatable pipeline
Motion	ICP-filtered cold email; first run always cold
No-ICP	Pure ecom/B2C · ads only · enterprise RFP with no outbound owner

M	Step
M0	Sector research
M1	ICP and validation
M2	Messaging framework
M3	Sales playbook + gate
M4	Campaign activation
M5	Crawl / analysis
M6	Weekly KPIs (recurring)
M7	Close and scale to the next vertical

No milestone is skipped. Each phase produces the raw material of the next. Validate per vertical before scaling.

Role	Does	Does not
Commercial Architect	Designs the system and approves gates	Run the playbook below the criteria
Outbound Specialist	Researches, runs sequences, classifies replies, documents	Change the playbook. Approve advancement.
HoD	Validates technical fit	Skip gates

Classify before answering.

Type	Signal	Action
Open	Open to talk	Reply promptly. Three time windows. Short call.
Question	Wants to know what this is	Research framing. No pitch. Confirm the call.
Referral	Talk to someone else	Thank + contact the referral with a mention.
OOO	Auto-reply	Mark. Follow up on the return date.
Not interested	Does not apply	Thank. Discard. No follow-up.
Silence	Nothing in 5–7 days	One bump on the same thread. If no reply: discard. A single follow-up.

Discovery call: the lead describes the process in their own words. No feature pitch.

Is not
Ads or social agency
Wiki for someone else’s SaaS
Dump of lead lists / CRM / APIs
Promise of N guaranteed meetings