148. GTM Templates

Use these templates when you need to turn market understanding into customer-facing action.

GTM templates work only when they are specific. Replace every generic phrase with customer language from discovery calls, sales calls, support tickets, or actual search/community behavior.

Positioning statement

Use this structure:

For [specific customer] who struggle with [problem], [product/company] is a [category or frame] that helps them [outcome]. Unlike [alternative], we [differentiation].

Fill:

Field	Notes
Specific customer
Problem
Trigger
Category
Outcome
Alternative
Differentiation
Proof

Positioning quality check:

Question	Good sign
Can the right customer self-identify?	The sentence names a role, company type, use case, or trigger.
Is the problem concrete?	It describes a current workflow, not a vague ambition.
Is the alternative real?	It includes current tools, people, agencies, spreadsheets, WhatsApp, or doing nothing.
Is proof named?	Customer quote, pilot, result, founder credibility, usage, revenue, or workflow evidence.

Homepage copy

Section	Copy
Hero headline	Outcome for specific customer
Subheadline	Explain problem, approach, and proof in one or two sentences
Primary CTA	Book demo / join pilot / start trial / get review
Problem bullets	3 pains customers recognize
How it works	3 simple steps
Proof	Customer quote, metric, logo, pilot result, founder credibility
Objection answer	Price, trust, effort, security, migration, time
Final CTA	Repeat primary action

Homepage review:

Section	Failure mode
Hero	Too broad: “for every business.”
Problem	Founder explains instead of customer recognizing.
Proof	Claims without evidence.
CTA	Asks for trial when customer needs a conversation, or asks for conversation when product is self-serve.
Objections	Ignores trust, migration, security, pricing, or support concerns.

Launch checklist

Area	Done?	Notes
ICP defined
Message tested
Landing page ready
Analytics installed
First users/prospects listed
Founder follow-up plan ready
Support path ready
Launch channel selected
Review date set

Launch review date should be within 7 to 14 days. A launch is not a festival; it is a learning event.

Channel selection matrix

Use this before picking a GTM channel.

Channel	Best when	Weak when	First test
Founder outbound	Customer list is knowable and ACV supports sales effort.	ICP is vague or message is generic.	50 exact-fit accounts with two message variants.
Content/SEO	Buyers search, compare, or educate themselves.	Problem language is unknown or urgency is low.	5 pages based on real customer questions.
Community	Trust and peer learning shape adoption.	Founder only broadcasts and does not participate.	3 useful posts or conversations in one focused community.
Partnerships	Another party already owns distribution or trust.	Partner incentives are weak or customer value is unclear.	5 partner conversations and one pilot referral.
Paid marketing	Demand exists and conversion economics can be measured.	Funnel, ICP, or activation is not understood.	Small campaign with source, lead quality, and follow-up tracked.
Events/webinars	Buyer education and trust matter.	Audience is too broad or follow-up is weak.	One narrow event with named target accounts and next-step plan.

Pick one primary channel and one backup. Early GTM dies when every channel gets a little effort and none gets enough learning.

Message testing sheet

Use this before changing the website, running ads, or sending hundreds of outbound messages.

Message variant	Response quality	Decision
A	Strong / mixed / weak	Keep / change / stop
B	Strong / mixed / weak	Keep / change / stop
C	Strong / mixed / weak	Keep / change / stop

Judge messages by qualified replies, useful conversations, paid pilots, activation, or retention. Do not declare a message good because founders like the wording.

Message review questions:

Question	Why it matters
Does the target customer recognize themselves?	Broad messaging attracts broad noise.
Does it name a painful workflow or trigger?	Pain without situation is too abstract.
Does it explain the alternative being replaced?	Customers compare you to current behavior, not only competitors.
Does proof match the claim?	Big claims need evidence, not adjectives.
Does the CTA fit the stage?	A buyer may need a conversation, diagnostic, demo, pilot, or self-serve trial.

Outreach email

Subject options:

Quick question about [specific workflow]
How are you handling [problem]?
[Mutual context] suggested I ask you about [problem]

Email:

Hi [Name],

I noticed [specific reason they fit]. I am working on [problem] for [customer segment].

Teams I speak with are currently [current workaround], which causes [pain].

Could I ask you 20 minutes about how you handle this today? If it is relevant, I can also share what we are testing.

Thanks, [Founder]

Follow-up:

Hi [Name], quick follow-up in case this is relevant. The specific workflow I am researching is [workflow]. If this is owned by someone else on your team, could you point me to the right person?

LinkedIn message

Hi [Name], I am researching how [specific customer type] handles [specific problem]. Your work at [company/context] looked relevant. Open to a 15-minute practical conversation? Not a generic pitch; trying to understand the workflow.

Channel experiment sheet

Channel	Target audience	Message tested	Volume	Replies/signups	Qualified conversations	Learning	Decision
Founder outbound							Continue / change / stop
LinkedIn/content							Continue / change / stop
Community/event							Continue / change / stop
Partner/referral							Continue / change / stop

Judge channels by qualified conversations, activated users, paid pilots, or retained customers. Do not judge only by impressions.

Follow-up sequence

Use follow-ups to add relevance, not pressure.

Touch	Purpose	Example angle
1	Specific reason for reaching out	”Saw you are hiring operations roles, which often increases handoff pain.”
2	Sharpen the problem	”The issue we see is not reporting itself, but chasing inputs across teams.”
3	Offer value	”I can share the checklist we use to diagnose this workflow.”
4	Route or close loop	”If this sits with someone else, who owns it? Otherwise I will close the loop.”

Do not use fake urgency. Relevance beats persistence.

Sales call notes

Field	Notes
Account
Contact and role
Segment
Pain
Trigger
Current workaround
Decision process
Budget signal
Objections
Next step
Owner/date

Pilot proposal

Section	Proposal
Customer problem
Pilot goal
Scope
Timeline
Customer responsibilities
Startup responsibilities
Success metric
Price or commercial terms
Post-pilot decision

Add a paid option where possible. Even a small paid diagnostic can reveal more than a free pilot with vague enthusiasm.

Pilot success criteria

Write success criteria before the pilot starts.

Area	Criteria
Business outcome	What customer result must improve?
User behavior	What repeated action proves adoption?
Time to value	How fast should the customer see value?
Support load	What level of manual support is acceptable?
Commercial step	What happens if the pilot works?
Customer responsibility	What data, access, or time must the customer provide?

A pilot without success criteria becomes unpaid consulting with a hopeful ending.

Objection map

Track objections by type, not as random comments.

Objection	What it may really mean	Evidence needed	Response or product/GTM action
Too expensive	Value unclear, wrong buyer, weak urgency, budget timing, or price truly too high.	ROI, comparison, buyer role, budget cycle.	Reframe value, adjust segment, change pricing, or stop pursuing.
Not a priority	Pain is weak, timing is wrong, or champion lacks influence.	Trigger, consequence of inaction, decision date.	Find urgent segment or better trigger.
Need more features	Core workflow incomplete, buyer wants custom work, or product promise is too broad.	Feature frequency, willingness to pay, segment pattern.	Narrow scope or convert into paid pilot.
Need approval	Economic buyer not involved, procurement path unclear, or internal risk is high.	Decision process, stakeholders, approval criteria.	Map buying process and arm champion.
Send details	Prospect is polite, not engaged, or needs internal forwarding material.	Specific next step and recipient.	Send concise proof and ask for decision path.
Trust/security concern	Risk is higher than proof.	Security, data, compliance, references.	Prepare trust pack or avoid segment until ready.

If the same objection appears five times, it is not an objection anymore. It is product, positioning, pricing, segment, or proof feedback.

Case study

Section	Notes
Customer
Before	What was broken or costly?
Why they chose us
What changed
Measurable result
Quote
What others can learn

India GTM notes

Add these fields to GTM experiments when relevant:

Field	Why
Trust path	Warm intro, founder credibility, customer logo, local partner, community, advisor.
Buying process	Owner approval, procurement, finance, department head, family, principal, doctor, shopkeeper.
Payment friction	Invoice, GST, TDS, PO, UPI/card, delayed collections.
Support channel	Product, email, phone, WhatsApp, field visit, training.
Language/geography	English/Hindi/regional language, metro/tier 2/3, India/global.

For many Indian segments, distribution and trust are the product’s first interface. Capture them deliberately.

Launch retrospective

Run this 7 to 14 days after a launch, campaign, webinar, content push, or outbound sprint.

Question	Answer
What did we launch?
Which segment was targeted?
Which channel was used?
What was the message?
What happened: traffic, replies, conversations, demos, pilots, paid customers?
Which leads were actually qualified?
What did customers repeat back in their own words?
Which objections repeated?
What should we keep?
What should we change?
What should we stop?
What is the next experiment?

A launch that does not produce learning was not reviewed properly.

GTM experiment packet

Every GTM attempt should be written as an experiment packet before money or founder time is spent. The packet keeps the team from confusing activity with learning.

Field	Prompt
Segment	Which exact customer group are we trying to reach?
Problem	What painful situation are we naming?
Promise	What outcome are we offering in plain language?
Proof	What evidence, demo, case, founder credibility, or customer result supports the promise?
Channel	Where will we reach this segment?
Offer	What is the immediate ask: call, demo, pilot, audit, waitlist, purchase, referral?
Owner	Who will run the experiment daily?
Volume	How many messages, posts, calls, demos, ads, or events?
Success metric	What specific signal makes this worth continuing?
Stop rule	What result means we stop or change?
Follow-up	What happens within 24 hours of a reply or lead?

Example stop rules:

Experiment	Stop or change when
Cold founder-led outbound	Fewer than 3 meaningful replies after 50 well-targeted messages.
LinkedIn content	Good likes but no buyer conversations after repeated posts.
Webinar	Registrations happen but target buyers do not attend or ask questions.
Paid ads	Leads arrive, but qualification and conversion are poor.
Partner channel	Partner likes the idea but will not introduce real prospects.

The packet should fit in one page. If the team cannot state the segment, promise, and proof clearly, the campaign is not ready.

Message-to-market review

After a GTM experiment, review the market’s response without defensiveness.

Question	What to inspect
Did the right people notice?	Segment match of replies, leads, attendees, demos, or inbound messages.
Did they understand the promise?	Their words in replies and calls.
Did they believe the proof?	Objections about credibility, risk, case studies, data, or references.
Did they take the next step?	Calls booked, pilots discussed, data shared, budget owner introduced.
Did the channel fit the buyer?	Speed, cost, trust, reach, and conversion quality.
What changed in our understanding?	New objections, better phrasing, narrower segment, stronger trigger.

Decide one of four actions:

Decision	Meaning
Keep	Same segment, message, and channel are producing useful signal. Increase consistency.
Narrow	A smaller segment or sharper trigger is responding better. Focus there.
Change	Pain may be real, but message, proof, offer, or channel is wrong.
Stop	The market is not responding with enough quality to justify more effort now.

For Indian founders, the review must separate visibility from trust. A post can get attention, an event can create conversations, and a large community can produce encouragement. Revenue usually needs trust, timing, decision authority, and follow-up discipline.

Copy-paste GTM experiment brief

Use this before launching any channel experiment, campaign, outreach push, webinar, partnership, or founder-led content series.

Experiment name:

Customer segment:

Problem / trigger:

Promise:

Channel:

Why this channel should reach this customer:

Message being tested:

Offer / CTA:

Qualification rule:

Success metric:

Minimum sample:

Budget / time box:

Owner:

Stop rule:

Scale rule:

Track results:

Date	Channel	Message	Prospects reached	Replies / actions	Qualified leads	Calls	Pilots / sales	Learning

After the experiment, decide:

Result	Decision
Right people, weak action	Improve promise or CTA.
Wrong people, high action	Narrow targeting and copy.
Right people, strong calls, weak payment	Run pricing or buyer-path test.
Low reach, strong quality	Increase distribution inside same channel.
High reach, low quality	Stop or reposition.

The founder should be able to say what the experiment taught even if it failed. If the only learning is “we need more traffic,” the experiment was not designed sharply enough.

Copy-paste sales call notes

Use this after discovery, demo, pricing, and pilot calls. The goal is to make pipeline quality visible, not to create a beautiful CRM note.

Account:
Contact:
Role:
Segment:
Source:
Call type: Discovery / demo / pricing / pilot / renewal

Problem they described:
Recent incident:
Current workaround:
Business impact:
Buyer / approver:
Budget path:
Trust requirement:
Objections:
Exact words used:

Next step:
Owner:
Date:
Deal confidence: Low / medium / high
Reason:

Qualification table:

Signal	Evidence	Score 0-2
Pain
Buyer
Urgency
Budget
Trust
Next step

Decision rule:

Total	Action
10-12	Advance with a dated next step.
7-9	Clarify missing buyer, budget, urgency, or proof.
4-6	Treat as learning, not pipeline.
0-3	Disqualify or nurture.

Copy-paste pilot proposal

Use this when a prospect wants to “try it.” A pilot should have commercial shape.

Pilot title:
Customer:
Customer owner:
Startup owner:

Problem:
Current workflow:
Pilot scope:
Out of scope:
Data/access needed:
Customer responsibilities:
Startup responsibilities:

Duration:
Kickoff date:
Review date:
Success criteria:
Decision after pilot:
Pilot fee:
Post-pilot commercial option:
Risks/open questions:

Pilot success criteria should be observable:

Weak success criteria	Stronger success criteria
”Customer likes it.”	3 operators use it weekly for 4 weeks.
”Saves time.”	Reduces reconciliation effort from 6 hours to under 2 hours per week.
”Improves visibility.”	Manager reviews a weekly dashboard and makes one decision from it.
”Ready for rollout.”	Buyer confirms budget, owner, users, and rollout date.

Copy-paste first case study

Early case studies do not need to sound like enterprise marketing. They need to prove one specific change.

Customer type:
Context:
Problem before:
Why it mattered:
What changed:
Implementation effort:
Measured result:
Customer quote:
What we learned:
Who this is relevant for:

Case study quality bar:

Section	Good standard
Customer type	Specific segment without exposing confidential details.
Problem	Concrete workflow or business pain.
Result	Measured outcome or honest qualitative improvement.
Relevance	Makes the next buyer think, “This looks like us.”
Proof	Quote, metric, before/after, screenshot, or process artifact where allowed.

Do not exaggerate early case studies. Credibility compounds faster than hype.

Copy-paste GTM weekly review

Use this every week while testing a GTM motion.

Week:
Primary segment:
Primary channel:
Primary message:
Offer / CTA:

Activity:
- Prospects reached:
- Replies / signups:
- Qualified conversations:
- Demos / pilots / trials:
- Paid commitments:

What worked:

What did not work:

Best customer language:

Repeated objections:

Channel quality:

Decision: keep / narrow / change / stop

Next week's experiment:

Review quality bar:

Area	Good evidence
Segment	Leads match the intended customer, not just anyone interested.
Message	Customers repeat the problem and outcome in their own language.
Channel	The channel produces conversations or conversions with the right people.
Offer	Prospects understand the next step and some take it.
Follow-up	Every qualified lead has owner, date, and next action.

If a GTM review only reports impressions, likes, traffic, or number of messages sent, it is not yet a business review.

Channel quality scorecard

Use this before scaling a channel.

Channel	Lead fit	Trust level	Conversion quality	Decision
Founder outbound	High / medium / low	High / medium / low	High / medium / low	Scale / continue / change / stop
Content/SEO
Community
Partners
Paid ads
Events/webinars

Notes:

Lead fit beats lead volume.
Trust path matters more in high-stakes B2B.
A channel is repeatable only when someone can run it again with similar quality.
A channel that produces learning but no customers may still be useful temporarily, but do not confuse it with scale.

Copy-paste channel decision memo

Use this after two to four weeks of testing a channel. The memo prevents the founder from continuing a channel because it feels busy, visible, or emotionally rewarding.

Channel:
Time period:
Owner:
Segment tested:
Message tested:
Offer / CTA:

Activity:
- Prospects reached:
- Qualified replies / leads:
- Conversations:
- Demos / trials / pilots:
- Paid commitments:
- Revenue or pipeline created:

Lead quality:
[Who responded? Were they the intended buyer, user, influencer, student, founder, CFO, HR head, operator, parent, doctor, developer, etc.?]

Trust path:
[What made people believe or not believe us? Founder credibility, proof, referral, case study, demo, community, brand, price, risk, compliance, local context.]

Conversion friction:
[Where did people drop: message, CTA, scheduling, demo, budget, procurement, payment, legal, timing, internal approval?]

Best customer language:
[Exact words from replies/calls that should shape positioning.]

Repeated objections:
[Objections with count or pattern.]

Cost and founder time:
[Money spent, founder hours, team hours, agency/tool cost.]

Decision:
Keep / narrow / change / stop

Why:
[Evidence, not optimism.]

Next experiment:
[One concrete change for the next cycle.]

Channel decision rules

Pattern	Decision
Right segment, low volume, strong conversations	Keep and increase consistency before judging too early.
Wrong segment, high volume	Change targeting or channel; volume is misleading.
Good engagement, no qualified next steps	Change offer, proof, or CTA.
Good conversations, no payment or pilot commitment	Inspect urgency, budget owner, and commercial terms.
Strong replies only from founder network	Useful for learning, but not yet a scalable channel.
Agency or paid spend creates leads the team cannot qualify	Stop scaling; fix qualification and follow-up first.
Channel works only when founder personally drives it	Keep as founder-led motion or design handoff before hiring.

Do not scale a channel until the company understands why it works. A channel that cannot be explained usually cannot be delegated.

Sales asset checklist

Before pushing GTM harder, prepare the minimum sales assets needed for the chosen motion.

Asset	Use it when	Minimum standard
One-line positioning	Any outreach, website, or pitch.	Specific customer, problem, outcome, and proof.
Discovery call notes	Founder-led sales or pilots.	Captures pain, buyer, budget, objections, and next step.
Short demo script	Product needs explanation.	Shows the exact workflow, not every feature.
Pilot proposal	Buyer wants to try before buying.	Scope, timeline, success metric, price, post-pilot decision.
Trust pack	Buyer worries about risk.	Security, data, compliance, references, founder credibility where relevant.
Case note	One customer has seen value.	Before, after, measured or credible result, quote if allowed.
Objection responses	Same objections repeat.	Plain answers tied to evidence, not defensive copy.

The asset should support a conversation. Do not spend weeks polishing collateral if the founder has not yet earned enough buyer conversations.