> For the complete documentation index, see [llms.txt](https://the-gtm-hq.gitbook.io/go-to-market-course/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-gtm-hq.gitbook.io/go-to-market-course/course/go-to-market-pmf-course/2.-why-marketing-should-own-pmf.md). # 2. Why Marketing Should Own PMF ### Learning Objectives By the end of this chapter you will be able to: * Understand why PMF is fundamentally a demand-side problem and why that makes it a marketing responsibility * Identify the 3 things only marketers and GTM teams can do that product teams structurally cannot * Recognise the specific signals marketing sees first before any product iteration can capture them * Build a marketing-led PMF hypothesis grounded in demand signals, not feature roadmaps * Redesign how your team assigns ownership of PMF discovery from this week forward ### Introduction There is a default assumption baked into most early-stage companies: PMF is something the product team discovers through iteration. Build, ship, measure, repeat. Get the product right and the market will follow. This assumption is not just incomplete — it actively slows you down. PMF has two sides. There is the supply side which is your product, its features, its quality, its reliability. And there is the demand side, who wants it, why they want it, how urgently they need it, what they are currently using instead, and what language they use to describe their problem. The supply side is a product function. The demand side is a marketing function. And here is the uncomfortable truth: most of the signals that tell you whether you have PMF, live on the demand side. This chapter makes the case that marketing should own PMF discovery not execute a launch once product has declared it ready. If you are a solo founder, this means you need to put on your marketing hat before your product hat. If you have a team, this chapter will redefine how you assign accountability for the most important question in your business. ### The Myth: PMF Is a Product Team Problem The myth goes like this: if you build the right product with the right features, the right UX, the right performance, customers will come. Iterate your way to PMF. Ship fast, learn fast, and eventually the product will be good enough that the market snaps into place. This is not entirely wrong. Product quality matters. But it tells you what to build, not who wants it, how badly, or why. Those are demand-side questions. And demand-side questions require market contact not build cycles. Consider what product iteration alone cannot tell you: * Whether the problem you are solving is urgent enough that people will change their behaviour to fix it * Whether your target segment has budget and authority to buy * Whether your positioning is landing or whether the market is hearing something completely different from what you are saying * Whether the channel you are using to reach people is the one they actually use when looking for solutions like yours * Whether the friction in your sales process is a product issue or a messaging issue Every one of those questions requires market contact. Customer interviews. Outreach experiments. Messaging tests. Conversion data. That is marketing work. Product iteration can improve what you build. Marketing discovery tells you whether what you are building is wanted and by whom. The most expensive mistake in early-stage businesses is confusing product improvement with PMF progress. Today, with AI you can build and launch a better product, that the market does not want. You need marketing from day 1 to give you the confidence to build what the market wants and is willing to pay for it. ### Why Marketing Owns the Demand Side of PMF Marketing's core function, in its most fundamental form, is to create and measure demand. Not to write copy. Not to run ads. Not to manage social media. To understand what a specific group of people want, surface that want clearly, and connect it to a solution that delivers it. That definition makes marketing the natural owner of PMF discovery. Let me break down this more for you, First, marketing is the function that has direct, ongoing contact with the market before a sale happens. Customer discovery interviews, positioning tests, messaging experiments, cold outreach, all of these generate demand-side data that product teams do not have access to in their build cycles. Second, marketing is responsible for the language gap. One of the most underrated PMF problems is when a product solves the right problem but uses the wrong words to describe it. Customers do not recognise their own problem in your messaging. This is not a product failure it is a positioning failure. And it is entirely a marketing problem to diagnose and fix. Third, marketing owns channel intelligence. Whether your ICP discovers solutions through Google search, LinkedIn, word of mouth, communities, or direct outreach is not something you learn from a product dashboard. It is something you learn by being in the market, running experiments, and watching where pull actually comes from. Product teams do not do this. Marketing does. As solo founders, this reframe has a practical implication: before you build the next feature, before you redesign the onboarding flow, ask whether you have done the marketing work first. Have you talked to 20 prospects this month? Have you tested three different positioning angles? Do you know which channel generates the highest-quality inbound, and why? If not, you are optimising the supply side without understanding the demand side. ### What GTM Teams See That Product Teams Miss Product teams have deep visibility into what happens inside the product. They see usage data, feature adoption, session length, error rates, and support tickets. That data is valuable. But it only covers the people who have already found you, already signed up, and already started using what you built. GTM and marketing teams have visibility into everything that happens before that and that is where PMF signals are most concentrated. Here is the comparison:
What product teams seeWhat marketing teams see
Feature adoption ratesWhy prospects chose not to sign up at all
In-app behaviour of existing usersWhich segments respond to which messaging angles
Support ticket themesObjections raised before a purchase decision is made
Churn after onboardingWhy the wrong customers signed up in the first place
NPS from current customersWhat competitors are saying and how the market is positioned against you
Session depth and retention curvesWhich channels bring high-intent visitors vs low-intent browsers
The signals in the right column are PMF signals. They tell you whether the right people are finding you, whether your positioning is working, whether the market understands what you do and wants it. Product data is a lagging indicator of PMF. Marketing data is a leading indicator. This does not mean product is unimportant. It means that the diagnostic work of figuring out whether you will have PMF and where the gaps exist require market contact that only GTM teams generate. ### The 3 Marketing Inputs That Unlock PMF Faster There are three specific marketing inputs that consistently accelerate PMF discovery. Each one generates demand-side data that cannot be replicated by product iteration alone. 1. **Prospect interviews.** Interviews are the highest-leverage tool in your PMF toolkit. Not surveys. Not analytics. Direct conversations with real prospects, people who have the problem you are solving, whether or not they have found you yet. Each interview surfaces language, urgency, context, and decision-making logic that no product metric can show you. The goal is not to validate your idea. It is to understand the demand landscape accurately enough that your product, positioning, and channel decisions are grounded in reality. Twenty interviews minimum before drawing conclusions. Forty before making significant investment decisions.
2. **Messaging experiments.** Before you know whether your product has PMF, you can test whether your messaging has it. Write three versions of your core value proposition different angles, different emphasis, different language. Run them in outreach sequences, LinkedIn posts, or ad copy. Measure response rates, not click rates. Response is a proxy for resonance. The version that generates the most replies from your target segment is the message that reflects what the market actually cares about. This is market data. It should inform your product roadmap, not just your copy deck.
3. **Channel experimentation.** Channel intelligence is knowing exactly where your ideal customers go when they have a problem like yours. Not where you assume they go. Not where the startup playbook says they go. Where they actually go. This requires deliberate experimentation, running outreach across two or three channels, measuring quality of response (not just volume), and tracking which channel produces customers who stay, pay, and refer. Channel fit is a component of PMF. You can have a great product and strong demand but still stall if you are fishing in the wrong pond. As a solo founder, you cannot do all three simultaneously at depth. Sequence them. Start with interviews, they inform everything else. Use what you learn to build your first messaging experiment. Then use what converts to identify which channel to go deeper on. ### Building a Marketing-Led PMF Hypothesis A marketing-led PMF hypothesis is a single, testable statement that captures your current best understanding of who wants your product, why, and how you will reach them. It is not a mission statement. It is not a vision. It is a falsifiable claim about demand that you can go and test this week. Here is an example: | **THE PMF HYPOTHESIS FORMULA** | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | We believe that \[specific segment] experiences \[specific problem] urgently enough that they will \[specific behaviour — pay, switch, refer] when we offer \[specific solution] through \[specific channel]. | | Example: We believe that solo B2B founders with fewer than 5 customers, experience the problem of not knowing which GTM channel to prioritise urgently enough that they will pay for a structured framework when we offer it through a LinkedIn content + direct outreach motion. | Every word in that hypothesis is testable. The segment, are you actually reaching solo B2B founders? The problem, do they describe it this way when you talk to them? The urgency, will they pay, or just say they will? The solution, does the framework actually work? The channel, is LinkedIn the right place? A hypothesis is not a plan. It is a starting point for structured experimentation. Write yours now, before you have all the answers. The act of writing it will immediately reveal which parts you have evidence for and which parts are assumptions dressed as facts. Those gaps are your research agenda. Revisit and rewrite your hypothesis after every five customer conversations. When you stop needing to rewrite it when the words stop changing because the market keeps confirming them that is a signal you are getting close to PMF on the demand side. ### Case Example | **SUPERHUMAN - MARKETING-LED PMF DISCOVERY** | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Superhuman is one of the most cited PMF case studies in the startup world — and it is almost always framed as a product story. It should be framed as a marketing story. | | In 2018, Rahul Vohra wrote a now-famous piece on how Superhuman found PMF. The method he used was not a product sprint. It was a survey — a marketing research tool. He asked every user one question: how would you feel if you could no longer use Superhuman? The options were: very disappointed, somewhat disappointed, not disappointed. The benchmark: if 40% or more answer 'very disappointed,' you have PMF. | | When Vohra ran the survey, the overall score was below 40%. But the marketing insight came from segmenting the responses. Among a specific type of user founders and executives who managed a high volume of email the score was well above 40%. The PMF was there. It was just hidden inside a broader, less well-defined audience. | | Superhuman's response was not to improve the product for everyone. It was to reposition to focus their entire GTM motion on the segment that already had PMF. That is a marketing decision. Messaging, ICP definition, channel focus, referral mechanics all of it was realigned around a demand-side insight. | | The lesson: PMF discovery happened through a marketing tool, led to a marketing decision, and was executed through a GTM motion. Product followed. Marketing led. | ### **Do This Before Moving To Chapter 03** | **Step 1.** List every PMF-related decision made in your business in the last 30 days. Who made each decision, was it product, marketing, or founder gut? Write it down honestly. | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Step 2.** Write your first marketing-led PMF hypothesis using the structure above. Do not refine it endlessly. Write a rough version in 10 minutes and move on. | | **Step 3.** Identify one demand-side signal you do not currently have but you need. Is it interview data? Channel response rates? Messaging test results? Write down exactly what you would need to observe to confirm or deny your hypothesis. | | **Step 4.** Book at least 3 prospect conversations this week. Not customer calls. Prospect calls, people who have the problem but have not yet bought from you. Go in with your hypothesis. Come out with data. | ### Key Takeaways * PMF has two sides: supply (product) and demand (marketing). Most founders only optimise the supply side. * Marketing owns the demand side of PMF, customer language, channel fit, positioning resonance, and urgency signals. * GTM teams see leading PMF indicators. Product teams see lagging ones. Both matter, but discovery requires market contact. * The three marketing inputs that accelerate PMF fastest are: prospect interviews, messaging experiments, and channel experimentation. * A marketing-led PMF hypothesis is a falsifiable, testable statement about who wants your product, why, and how you will reach them. Write one before you do anything else. ### What is Next In Chapter 03, we go deep on one of the most consequential decisions in any early-stage business: picking the right niche. Most founders choose a niche that is too broad, too vague, or picked for the wrong reasons, market size, personal interest, or proximity. Chapter 03 gives you a practical filter for evaluating niche candidates based on pain, purchasing power, and growth signal, the three variables that actually predict whether a niche will convert. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://the-gtm-hq.gitbook.io/go-to-market-course/course/go-to-market-pmf-course/2.-why-marketing-should-own-pmf.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.