B2B SaaS Go-to-Market Checklist: A Phase-by-Phase Plan

A go-to-market (GTM) plan defines how you'll reach, attract and convert the people you built the product for. Launching is not a plan. Plenty of good products stall because nobody did the selling part.

This checklist walks through each phase of taking a B2B SaaS product to market: customer discovery and positioning before you build, your offer and first sales, distribution, retention and expansion. It ends with a 90-day sprint you can work through. Treat the whole thing as a hypothesis you test and revise, not a document you write once.

Free template: Download the GTM pipeline tracker (CSV) to track your pipeline and channels.

Phase 0: Pre-Launch Foundation (Week -8 to -1)

Before you write much code, do this.

Customer Discovery

Aim for a lot of customer conversations before launch. A structure that works:

Week 1-2: Problem discovery (aim for 15 or so conversations)

An outreach script:

Subject: Quick question about [specific problem]

Hi [Name],

I noticed [specific observation about their company]. I'm researching how companies like yours handle [specific problem].

Would you have 15 minutes this week for a quick call? Happy to share what I learn from other [industry] companies.

No sales pitch - I don't even have a product yet.

[Your name]

Questions that surface real problems:

1. "Walk me through how you currently handle [process]."
2. "What's the most frustrating part of that?"
3. "What have you tried to solve this?"
4. "What does this problem cost you in time or money?"
5. "Who else would need to approve buying a solution?"
6. "Is there budget set aside for this?"

Focus on what they've actually done, not what they say they'd do. For more on running these calls, see Customer interviews that don't suck.

Week 3-4: Solution validation (another round of conversations)

Show mockups or wireframes and ask:

• "Would this solve your problem?"
• "What's missing?"
• "Would you pay $X for this?"
• "Can we start a paid pilot next month?"

Week 5-6: Pricing discovery

A pricing conversation framework:

"Based on our conversation, this would save you [specific value].
The standard price will be $[list price]/month.
For early customers, we're offering $[founding price]/month.
Can we start with a 3-month commitment?"

Only quote a list price you actually intend to charge.

A rough guide to interpreting responses:

• If almost everyone says yes immediately: you're probably underpriced
• If some say yes and some hesitate: you're in a reasonable range
• If most say no: you're overpriced, talking to the wrong people, or solving the wrong problem

Pricing discovery interviews for B2B SaaS goes deeper on this.

Define Your ICP Precisely

A vague ideal customer profile (ICP) makes every later step harder. Start by writing one paragraph describing your best-fit customer: who feels the pain most acutely, and why. Then sharpen it through five layers:

• Firmographics: industry, company size, revenue range, geography, tools they must already use
• Role: the exact titles that buy, their department, who they report to, how big their team is
• Psychographics: attitude to new tools, motivations, fears, how their success is measured
• Behaviors: where they learn (communities, publications), how they buy (committee or individual), typical sales and budget cycles
• Problem: how urgent it is, what they use today (spreadsheets or a competitor), how hard it is to switch, what solving it is worth

A hypothetical example of a sharp ICP:

VP of Sales at 50-200 person B2B SaaS companies
- Managing 5-15 reps
- Using Salesforce + spreadsheets for forecasting
- Spending hours every week assembling the forecast
- Measured on forecast accuracy
- Has discretionary budget for sales tools
- Active in sales-leadership communities
- Can buy tools without a procurement committee

Check the profile against your discovery calls. If the people who felt the problem most don't match it, change the profile, not the evidence.

Competitor Research

Identify two or three direct or indirect competitors. Skip the SWOT analysis and research the things that change how you sell:

Value Proposition and Positioning

Start with a one-sentence value proposition: the main benefit you offer your ICP. For example: "For indie hackers, BuildVoyage is a curated directory that shows the tech stack and milestones behind real products."

Then write a fuller positioning statement that names the alternative you're up against:

Unlike [competitor], we help [specific ICP] achieve [specific outcome]
in [specific timeframe] by [unique mechanism] without [common objection].

Hypothetical example:
Unlike Salesforce, we help Series A SaaS sales teams get a reliable
forecast every week by automating forecast roll-ups, without a
months-long implementation.

For a structured exercise, see Positioning statement workshop for micro-SaaS.

Messaging Matrix

From your ICP and positioning, write down the talking points you'll reuse everywhere:

• The problem, in the words customers used on discovery calls
• The solution: what the product does about it
• The outcome: what's different for the customer afterwards
• Proof: why they should believe you (demos, pilots, real customer results once you have them)
• Objections you've already heard, and your honest answers

This becomes the source material for your landing page, emails, demos and posts, so they all say the same thing.

Phase 1: Product and Offer (Week -4 to 0)

Keep the MVP Scope Small

Launch with much less than feels comfortable:

The Concierge MVP

You can deliver value before everything is automated:

1. Build the core feature
2. Do the rest by hand (imports, reports, setup)
3. Be upfront that some parts are handled by your team for now
4. Automate each manual step once you've done it enough times to know exactly what it should do

For example, a data-pipeline product could start with the founder running the sync scripts every night. Customers care that the data arrives, and you learn which parts are worth automating first.

Pricing Tiers

Choose a model (flat fee, tiered, or usage-based) that tracks the value customers get. A common tiered structure has three plans plus a custom option. The prices here are placeholders, not recommendations:

Offer a discount for paying annually (two months free is a common framing). Consider starting customers on monthly billing to reduce friction, then offering the annual plan once they've seen value.

Customers usually accept a price cut more easily than a price rise, so err on the side of not underpricing. See Pricing your SaaS: a simple guide for more on choosing numbers.

Map Your Conversion Funnel

Write down the path you want a buyer to take, step by step, so you know what to build and what to measure. For example:

Google search -> Comparison page -> Book a demo -> Trial -> Paid
LinkedIn message -> Discovery call -> Demo -> Pilot -> Annual plan

Each arrow is a conversion you'll track later. If you can't describe the path, you can't tell where people drop off.

Phase 2: Launch Week

Onboard, Don't "Launch"

For B2B, a big launch day matters less than onboarding customers one by one. Before the week starts, have the basics ready: a clear landing page built from your messaging matrix, and the emails and community posts written in advance.

A sample first week, with targets to adjust for your market:

Monday: Your warmest leads

• Email the 5 warmest leads from discovery
• Offer founding-customer pricing and regular calls with the founder
• Target: a couple of commitments

Tuesday: Your network

• Email former colleagues who fit or know people who fit
• Post in one private Slack or Discord community (within its rules)
• Message relevant LinkedIn connections
• Target: a few demos booked

Wednesday: Content

• Publish an honest comparison post: "[Your product] vs. [biggest competitor]"
• Share it in relevant communities and send it to prospects who'd care
• Target: a handful of signups

Thursday: Cold outreach

• Send personalized emails to well-researched prospects
• Focus on companies using a competitor or a spreadsheet workaround, and reference a specific pain point
• Target: a few replies

Friday: Close

• Follow up on everything from the week
• Ask for the commitment directly and get payment set up
• Target: your first paying customers

A Five-Step Sales Process

Step 1: Discovery call (30 minutes)

Agenda:

1. Current state (10 min): how they handle the problem today
2. Desired state (10 min): where they want to be
3. Gap (5 min): what's blocking them
4. Fit (5 min): whether and how you can help

Useful questions:

• "What happens if you don't solve this?"
• "How are you measured on this?"
• "Who else cares about this problem?"
• "What's your timeline for fixing it?"

Step 2: Demo (25 minutes)

1. Recap their problem (2 min)
2. Show how you solve it (10 min)
3. Walk through their specific workflow (10 min)
4. Handle objections (3 min)

Use their data, or realistic data from their world. Get to the "aha" moment early, let them drive for a couple of minutes, and end with a clear next step and a date.

Step 3: Trial (e.g. 14 days)

• Decide deliberately whether to require a card up front: it filters for serious buyers but reduces trial starts
• Send short, useful check-in emails that show progress toward a clear success milestone
• Watch for the first login and the first moment of real value; reach out if either doesn't happen

Step 4: Close

A trial-ending email:

Subject: Your [Product] trial ends in 3 days

Hi [Name],

You've [specific achievement] with [Product] - nice work!

Your trial ends Friday. Here's what happens next:

Option 1: Keep going
- Keep all your data and settings
- Lock in founding-customer pricing: $[X]/month
- Get priority support

Option 2: Export and cancel
- Download your data here: [link]
- Cancel here: [link]
- The door's always open

Questions? Just reply to this email.

[Your name]
P.S. If price is the only barrier, let me know. We can work something out.

Making it easy to leave builds trust, and the clear next steps make it easy to stay.

Step 5: Expansion (from month 2)

Help them succeed in month one, let them know as they approach plan limits, and talk about the next tier only when it genuinely fits their usage.

Phase 3: Distribution (Week 2-12)

Choose One or Two Channels

You can't be everywhere. Pick the one or two channels where your ICP already spends time: searching Google, active on LinkedIn or X, in communities like Reddit or niche Slack groups, or reachable directly by email.

Early on, direct and "unscalable" channels usually beat broad, scalable ones. A rough, qualitative comparison:

To choose between candidates on purpose, give each an ICE score:

Score = (Impact × Confidence × Ease) / 10,000

Where each is rated 1-100:
- Impact = how many potential customers it could reach
- Confidence = how sure you are it will work for your ICP
- Ease = how cheap and quick it is to try

For example, founder outbound rated 40 / 80 / 60 scores 19.2, while paid ads rated 90 / 20 / 30 scores 5.4: huge reach, but little confidence it works yet. Start with the top one or two. Add the next channel when the first stops scaling with the time you have.

Track Every Campaign

Decide how you'll know what's working before you start posting. Give every campaign, post and outbound link its own tracking URL (the UTM Link Builder makes these quickly), and log where each lead came from in your pipeline tracker.

An Outbound Sequence

Email 1 (Day 1): The problem

Subject: [Specific problem] at [Company]

Hi [Name],

Noticed [specific trigger event]. Teams in that situation often run into [specific problem].

Worth a quick chat if you're dealing with this?

[Your name]

Email 2 (Day 3): The example

Subject: Re: [Previous subject]

[Name],

[Similar company] had the same challenge. They solved it by [specific approach].

15 minutes to discuss how this might work for [Company]?

[Your name]

Only reference a real customer or a real, public example.

Email 3 (Day 7): Something useful

Subject: Quick resource for [Company]

Hi [Name],

I put together this [template/calculator/guide] on [problem].

Thought you might find it useful: [link]

If it helps, happy to show you how we automate this.

[Your name]

LinkedIn connection (Day 10):

"Sent you a resource about [problem] by email.
Connecting here in case this is the better channel."

Email 4 (Day 14): The breakup

Subject: Should I stop reaching out?

[Name],

I've sent a few emails about [problem].

Haven't heard back, which usually means one of:
1. This isn't a priority right now
2. You're happy with your current solution
3. My timing is off

Mind letting me know so I don't keep filling your inbox?

[Your name]

Check the cold-email rules for the countries you're sending to; they're stricter in parts of Europe.

Content for B2B SaaS

Not all content is equal early on. Prioritize by buying intent:

Start with bottom-of-funnel content, then broaden. The SaaS SEO playbook covers the search side.

Communities

The community approach takes about three months:

• Weeks 1-4, listen: join a handful of communities where your ICP spends time, read the last few months of posts, learn the culture and the rules on self-promotion, and don't mention your product.
• Weeks 5-8, help: answer questions regularly, share templates and resources, and write one substantial post a week. Share your expertise, not your link.
• Weeks 9-12, mention when relevant: bring up your product when it directly answers a question, offer a community-only discount, and share case studies once you have them.

From zero to ten has post templates for this.

Phase 4: Founder-Led Sales (Month 2-6)

When to Hire Salespeople

Later than you think. A reasonable progression:

1. Founder only: until you have a repeatable way to find, pitch, and close customers, and can write it down
2. Founder plus help: a VA or part-time help for research, list building, and scheduling, while you still run the calls
3. First sales hire: once the playbook is documented and demand is more than you can handle, often starting with someone who books meetings (SDR) before someone who closes

A salesperson can scale a working process. They rarely invent one, and hiring before the process exists is an expensive way to find that out.

Metrics and a Weekly Review

Pick the two or three metrics that matter most right now and review them every week or two, together with what customers are telling you. Double down on what's working and change what isn't. Your own numbers set the benchmarks; what matters is the trend and knowing what each metric points to:

Handling Common Objections

• "We don't have budget": "I understand. What does this problem cost you today? Could we start with a smaller pilot to prove the value first?"
• "We're building this internally": "Makes sense. It's worth comparing the time to build and maintain it with [price]/month. What would your team work on instead?"
• "We need to think about it": "Of course. What specifically do you need to think through? Is it price, features, or timing?"
• "We're happy with our current solution": "Good to hear. What would have to be true for you to consider switching?" Then only claim the advantages you genuinely have.
• "It's not the right time": "When would be the right time? What needs to happen between now and then?"
• "I need to talk to my team": "Makes sense. What questions will they have? I can prepare materials or join the conversation."
• "It's too expensive": "Compared to what? Let's work through the value together. If the numbers work, would price still be a blocker?"

Phase 5: Retention (Month 1 Onward)

Onboarding That Prevents Churn

Track how quickly customers reach each milestone, and keep the time as short as you can:

The SaaS customer onboarding checklist covers this in detail.

A Customer Success Cadence

• Week 1, high touch: welcome call on day 1, a setup check-in, help reaching the first success milestone, a feature walkthrough, and a short review at the end of the week
• Weeks 2-4, medium touch: a weekly check-in email, office hours, and community access
• Months 2-3, low touch: a monthly review, a roadmap preview, and an annual planning conversation for larger accounts

Use the early calls as your feedback loop. Ask every new customer "Why did you sign up?" and "What problem were you hoping to solve?" The answers tell you whether your positioning and ICP are right.

Churn Warning Signs

Watch for these and reach out when you see them:

• No login for a week or more
• Support ticket unresolved for days
• A sharp drop in usage
• No teammates invited (in a team product)
• The main contact leaves the company

Win-Back Email

Sent about 30 days after a customer cancels:

Subject: What we've fixed since you left

[Name],

You left [Product] because of [specific reason].

We fixed that. Plus:
- [New feature addressing their pain]
- [Improvement they requested]
- [Price change/offer]

Want to give us another shot? Here's [offer]: [link]

No hard feelings if not. Your feedback made us better.

[Founder name]

Only send this when you've actually fixed the reason they left. More templates: SaaS churn reduction email templates.

Phase 6: Growth (Month 6+)

Land and Expand

Start with a single team or use case, drive usage until it becomes a habit, then add teams and use cases, move customers to annual commitments, and turn the happiest ones into case studies and referrers.

Common expansion triggers:

1. Usage limits: soft limits with clear upgrade prompts
2. Team growth: each new teammate is a natural upgrade moment
3. Feature gates: advanced features in higher tiers
4. Outgrowing a plan: tell customers when their usage fits a higher tier
5. Annual reviews: proactive conversations about what's next

A Referral Program

An example structure:

• Offer: a recurring commission (for example, 20% of what the referred customer pays), or account credit
• Target: your happiest customers (e.g., those who give you a 9 or 10 on an NPS survey)
• Tracking: unique referral links
• Payouts: monthly, through a referral or affiliate tool that integrates with your billing

The ask:

"You've achieved [specific success] with [Product].
Know anyone else who struggles with [problem]?
You'll get [reward] for every customer you refer.
Here's your link: [link]"

Your 90-Day GTM Sprint

Adjust the numbers to your market; the point is to commit to specific activity.

Days 1-30: Foundation

Weeks 1-2: Customer discovery and positioning

• Hold as many customer conversations as you can book (aim for dozens, not a handful)
• Define your ICP precisely and confirm the problem is urgent
• Write your value proposition, positioning statement and messaging matrix
• Get a few pre-commitments

Weeks 3-4: Product sprint

• Build the core feature only
• Set up Stripe billing
• Create a simple onboarding flow
• Onboard your first customers

Days 31-60: Execution

Weeks 5-6: Channel testing

• Set up tracking links and your pipeline tracker
• Run a targeted cold email campaign and LinkedIn outreach
• Post in the communities you've joined
• Run demos with everyone who's interested

Weeks 7-8: Optimization

• Refine your sales process
• Fix onboarding friction
• Revisit pricing (if nobody pushes back, it's probably too low)
• Get help with outbound research

Days 61-90: Focus

Weeks 9-10: Double down

• Put most of your effort into the best channel
• Drop what isn't working
• Automate repetitive tasks
• Document your playbooks

Weeks 11-12: Plan the next stage

• Review MRR and pipeline against your goals
• Launch a referral program
• Plan your expansion strategy
• Decide what you'll hand off first

What to Expect

A good product with weak distribution often loses to a decent product that's sold well, so treat GTM as part of the product, not something to do after it's finished.

After the first few customers, growth often slows: the warm network is used up, early channels stop scaling, and you're doing support, sales and product at once. Plan how you'll find your next channel before you need it. And if months pass without real traction, don't just push harder on the same plan: go back to discovery and question the problem, the ICP or the price.

Revisit this checklist whenever your ICP, pricing or main channel changes. If you haven't launched yet, start with the SaaS pre-launch checklist.

Tracking your GTM journey? Join BuildVoyage and share your milestones with other makers. Your first customer story could help someone else find theirs.