Chapter 13 · Part 4: Customers

Go-to-Market and Launch

“Marketing is not the art of finding clever ways to dispose of what you make. It is the art of creating genuine customer value.”

— Philip Kotler

The launch nobody noticed

Brindlepath’s first big release after the new strategy was the outcome report: a view that showed a health system’s chief nursing officer and chief financial officer how many high-risk patients had been owned within 24 hours, how many follow-ups had been kept, and what that was likely worth in avoided readmissions. The product team was proud of it. It shipped on time, worked well, and was announced in a release note and a customer newsletter.

Three months later, four customers had opened it. The sales team had not mentioned it in a single deal. Customer success managers had not shown it in a single business review.

The report was not the problem. The launch was. Nobody outside the product team understood who the report was for, what it let them do, or how to use it in a conversation with a customer. Maya relaunched it properly: a one-page story for each audience, training for sales and customer success, a short demo built around a real (anonymized) customer’s numbers, and a target to show it in every quarterly review. Within a quarter, it was the most-requested part of every sales demo, and three customers used it to justify expanding to new hospitals.

The lesson is old, and every product team relearns it: building the product is half the job. Getting it into the hands and heads of the people it is for is the other half.

What go-to-market means

A go-to-market (GTM) strategy is the plan for how a product reaches its customers and wins their business: who you sell to, what you say, through which channels, at what price, and how you support them after the sale. It connects the strategy and positioning from Chapter 4, the pricing from Chapter 6 and the customer success work in Chapter 14.

A complete GTM plan answers six questions:

  1. Who exactly is the target? The best-fit customer profile and the buying group from Chapter 2.
  2. What is the message? The positioning, translated into language for each role in the buying group.
  3. How will they find and buy it? The motion and channels: direct sales, self-service, partners, marketplaces.
  4. What will it cost them, and how will they buy? Pricing, packaging, contract terms, procurement path.
  5. How will they succeed with it? Onboarding, implementation, training, support.
  6. How will we know it is working? Pipeline, win rates, sales cycle length, time to value, early adoption.

Choosing a motion

Software reaches customers in a few broad ways, and the choice shapes the product itself.

  • Sales-led. A sales team finds, qualifies and closes deals, often with long cycles and many stakeholders. Typical for large, complex, regulated purchases such as Brindlepath’s.
  • Product-led. Users discover, try and adopt the product themselves, often through a free tier or trial, and expand over time. Typical for tools that individuals or small teams can adopt without procurement.
  • Partner-led. Resellers, system integrators, platforms or marketplaces carry the product to customers. Common when a partner already owns the relationship or the channel, as Chapter 15 discusses.

Most companies end up with a blend. Brindlepath was firmly sales-led, but it learned from product-led companies: it made the pilot experience as self-explanatory as possible, so navigators adopted the product with little training, and their enthusiasm helped the sales team expand to other hospitals in the same health system.

Messaging for each audience

Positioning, from Chapter 4, is the shared understanding of what you are and why you matter. Messaging is how you express it to each audience, in their words, about their concerns.

For each role in the buying group, write three things: the problem they feel, the outcome they want, and the proof they need. For Brindlepath’s outcome report:

Audience Problem they feel Outcome they want Proof they need
Chief nursing officer Can’t show the board that care transitions are improving A clear, credible view of progress Their own data, trended over time
Chief financial officer Readmission penalties with no clear plan to reduce them A return on the investment Avoided readmissions, valued conservatively
Navigator manager Staff overloaded, no way to see where help is needed Balanced workload, fewer missed patients Patients per navigator, missed follow-ups by team

Test messages with real buyers before launch. Read them aloud in a customer’s voice. If a sentence sounds like a brochure, rewrite it until it sounds like something a customer would say to a colleague.

Building the launch plan

Not every release deserves the same launch. A useful practice is to tier launches by their importance to customers and the business, and match the effort to the tier.

A Tier 1 launch, a new product, a major capability or a change that shifts the company’s positioning, gets the full treatment: messaging for each audience, sales and customer success enablement, external announcement, customer events, and measures of success. A Tier 2 launch, a significant feature, gets targeted communication to affected customers and enablement for the teams that will discuss it. A Tier 3 launch, an improvement or fix, gets a release note and an update to help content.

Decide the tier when the work is planned, not the week before release, so marketing, sales and customer success have time to prepare.

Enabling sales and customer success

The sales and customer success teams are the product’s voice with customers. If they cannot explain a capability confidently, it effectively does not exist. Good enablement includes:

  • The story: a short narrative of the problem, the solution and the outcome, with a customer example.
  • The demo: a script built around a realistic scenario, not a tour of every button.
  • The objections: the hard questions customers will ask, with honest answers.
  • The boundaries: what the capability does not do, so nobody over-promises.
  • Practice: time for people to rehearse and ask questions, not just a slide deck in their inbox.

Pilots that become purchases

In business software, and particularly in healthcare, the path to a sale often runs through a pilot. Chapter 3 described pilots designed to end in a decision: agreed measures, a baseline, a success threshold, a fixed duration and a named decision-maker. From a go-to-market perspective, three more practices matter.

Price the pilot. Even a modest fee changes behavior. Customers who pay for a pilot assign people to it and take the decision seriously.

Design the pilot for expansion. Choose a scope that, if it succeeds, naturally leads to a larger rollout: one hospital in a system of five, one service line in a hospital.

Write the expansion terms in advance. Agree what happens if the success threshold is met: the price, scope and timeline of the full deployment. Then the decision at the end of the pilot is about results, not a fresh negotiation.

In the Brindlepath story, the share of pilots that became contracts rose from under half to about three in four once the company adopted these practices, and the time from pilot start to signed contract fell by several months. Your own results will depend on your market, but the direction is one I have seen repeatedly.

Launching in regulated markets

Launching in healthcare and other regulated markets adds steps a product leader must plan for:

  • Customer approvals. Health systems may require clinical, security, legal or IT review before a new capability can be turned on, sometimes for each hospital.
  • Training and change management. A change to a clinical workflow may need formal training and updated procedures at the customer. Feature flags, from Chapter 9, let you enable capabilities customer by customer when they are ready.
  • Claims and evidence. Be careful what you claim. Statements about clinical outcomes or cost savings should be supported by evidence and reviewed by legal and compliance. Use customers’ own results, with permission, rather than broad promises.
  • Contract and procurement timelines. Budget cycles, procurement committees and contract reviews can add months. Know your customers’ fiscal calendars and plan launches and pilots around them.

After the launch

A launch is a hypothesis about adoption. Check it.

Set measures before launch: how many customers will adopt the capability within 30, 60 and 90 days; how often it will appear in sales conversations; what share of eligible users will use it. Review them on schedule, and talk to customers who did not adopt to find out why. Sometimes the product needs work. Often, as with Brindlepath’s outcome report, the launch did.

Brindlepath in practice: relaunching the outcome report

The relaunch of the outcome report, described at the start of this chapter, followed the Tier 1 playbook.

The product marketing lead and Maya wrote a one-page story for each audience. For chief nursing officers: “Show your board that care transitions are improving, with your own data.” For CFOs: “See the value of avoided readmissions, calculated conservatively, with the assumptions shown.” For navigator managers: “See where your team needs help before patients are missed.”

The demo was rebuilt around a realistic scenario. A health system with five hospitals, one of them lagging, and a chief nursing officer preparing for a board meeting. The demo took eight minutes, and it ended with the question every buyer was actually asking: what is this worth to us?

The enablement session ran for two hours rather than the usual thirty minutes. Salespeople and customer success managers each demoed the report to a colleague playing a skeptical CFO, and the hardest questions were collected into an objections guide. The most common question, “How do you calculate avoided readmissions?”, got a careful, honest answer: a conservative method, the assumptions behind it, and a reminder that the customer’s own finance team should validate the figure.

Customer success set a goal to show the report in every quarterly review for the next two quarters, and tracked it. Three measures were reviewed at 30, 60 and 90 days: customers who opened the report, appearances in sales opportunities, and expansions where the report was cited.

At 90 days, the report had been opened by most customers, appeared in most active sales opportunities, and had been cited by three customers as part of the case for expanding to new hospitals. The product had not changed at all between the first launch and the relaunch. Only the launch had.

Pricing the pilot, in practice

Brindlepath’s early pilots were free, on the theory that removing cost would remove friction. It did. It also removed commitment. Customers assigned whoever was available, missed weekly reviews and let pilots drift.

The company began charging a modest fee for every pilot, credited against the first year’s contract if the customer went ahead. The effect on behavior was immediate. Customers assigned a named manager, protected navigators’ time for training, and came to decision meetings prepared. The fee was small enough that it rarely slowed a deal, and the few prospects who would not pay anything turned out to be the ones least likely to buy.

Common mistakes

Launching to the product team. A release note and a newsletter mention reach the people who already know about the feature. Customers and sellers need a story, a demo and a reason to care.

One message for everyone. The navigator, the chief nursing officer and the CFO care about different things. A single message usually speaks to none of them.

Enabling sales with slides. Sellers learn by practicing, not by reading. Give them a demo script, the hard questions and time to rehearse.

Free pilots with no exit. Unpriced pilots without expansion terms invite casual commitment and end in renegotiation rather than a decision.

Forgetting the customer’s calendar. Health systems and other large buyers have budget cycles, approval committees and training windows. Launches that ignore them stall.

Overpromising AI. Claims an AI feature cannot consistently meet damage trust far more than the feature builds it.

Try this

Pick your next significant release and write the messaging table from this chapter for it: each role in the buying group, the problem they feel, the outcome they want and the proof they need. Then give a salesperson ten minutes to demo the capability to you, cold, using only the materials you have prepared. Note every question they cannot answer and every claim they make that the product does not support. That list is your enablement plan.

How AI changes this

AI accelerates launch work. Assistants can draft messaging variants for each audience, release notes, help articles, sales talk tracks and training quizzes from the product brief. They can analyze win and loss notes and call transcripts to find which messages resonate. Review everything for accuracy, especially claims.

Launching AI features needs extra care. Customers, especially in healthcare, want to know how an AI feature works, what data it uses, how accurate it is, and what happens when it is wrong. Prepare clear answers, documentation of evaluation results, and guidance on appropriate use. Over-promising on an AI feature damages trust faster than almost anything else.

Buyers will ask about your AI posture. Even for non-AI features, many security and procurement reviews now include questions about how a vendor uses AI, where customer data goes, and whether it is used to train models. Add these answers to the trust package from Chapter 11.

AI changes how buyers research. Buyers increasingly ask AI assistants to compare vendors and summarize options before they talk to sales. Clear, specific, well-structured public information about what your product does and for whom helps you show up accurately in those answers.

Chapter checklist