Product-channel fit: why the channel decides what you prompt
Product-channel fit is Brian Balfour's name for a rule most first apps break: “Products are built to fit with channels. Channels do not mold to products.” The channel sets the rules (search rewards pages that answer queries, a product-led loop rewards products that get better with more people), so the channel decides features, and features belong in the first prompt. Every one of the 114 library prompts with a channel carries the features that channel needs.
By Marco Kohns · Essay re-read 23 October 2026
4fits
Market-product, product-channel, channel-model and model-market, per Balfour.
8channels
Across the library, from organic search to paid search.
1channel
To start with; the second waits until the first brings users.
The framework
What is product-channel fit, in Brian Balfour's terms?
One of four fits that have to hold together for growth. It is the one a prompt can act on.
Fit 1
Market and product
Fit 2
Product and channel
Fit 3
Channel and model
Fit 4
Model and market
Brian Balfour, Product Channel Fit Will Make or Break Your Growth Strategy, re-read 23 October 2026.
In a prompt
How does the channel change what the prompt asks for?
The same app, without a channel and shaped for search.
Without a channel
Build a habit tracking app with daily check-ins, streaks, and reminders.
Shaped for organic search (excerpt)
# Context A habit tracker for remote team leads, found through search: people type "[habit] tracker template" and arrive on a template page. ## Core Features (Priority Order) 1. A public template page per habit, each with its own URL, title, H1 and HowTo structured data 2. Use a template without an account; sign up only to save progress 3. Daily check-ins with streaks computed in the user's time zone ## Growth Features Server-render every template page, list them in sitemap.xml, link related templates to each other. ## Done When - A template page fetched without JavaScript contains its H1 and steps - /sitemap.xml lists every template
| Channel | What the product needs |
|---|---|
| Organic SEO / AI Search | Design your product so it naturally attracts traffic by creating pages that directly answer what users are already searching for and get picked up by Google and AI search engines. |
| Paid Search | Get a prompt that optimizes your product for fast perceived value and clear conversion paths so ad clicks have a fighting chance to pay back. |
| Organic Socials | Shape your product around outputs people actually want to share, not because you ask them to, but because it makes them look smart or helpful. |
| Paid Socials | Structure your product so its value is instantly understandable in a scroll, making it viable to acquire users even when attention is expensive. |
| Short-Form Video | Build your product around moments that can be shown, not explained, so it works naturally in short, visual formats like TikTok or Reels. |
| Product-led Growth | Create a product experience where users reach a meaningful 'aha moment' before they ever have to sign up, pay, or talk to sales. |
| Community-led Growth | Design your product so users benefit from contributing, sharing, or improving it together, causing value to compound over time. |
| B2B Sales / Outreach / LinkedIn | Get a product structure that can be explained in one message and clearly ties features to business outcomes decision-makers care about. |
| X (Twitter) | Give the product a visible artifact worth posting, so building in public produces something to show, with nothing left to announce. |
| Email Marketing | Build a reason for the product to send something a user actually wants to open, so the list works as a retention channel and stops being a broadcast list. |
In the library
How does the prompt library encode a channel into every prompt?
Each prompt names its target channel; its Pro variant adds the growth features for it.
| Channel | Prompts |
|---|---|
| Product-led Growth | 60 |
| Organic SEO | 16 |
| B2B Sales | 16 |
| Email Marketing | 8 |
| No single channel | 8 |
| Organic Socials | 7 |
| Community-led Growth | 6 |
| Paid Search | 1 |
Product-led growth leads because most first apps spread through use, and an invite, a share or a public page is code a prompt can ask for. Filter the library by category to find the prompt for your step.
Choosing
How do you choose the right channel?
Three questions, answered before the first prompt.
- 01
Where do users look today?
Search, a community, a colleague's recommendation, an ad. Go where they already are. - 02
What can you sustain for a month?
Writing and waiting point to search; being useful in two or three places points to community; a budget and a measurable page point to paid. - 03
What does the product produce?
A result worth sharing points to social; something better with more people points to product-led growth.

Turning the chosen channel into a launch is in the first 100 users guide.
Time to work
How long does each channel take before it brings users?
A rough order, from the playbooks on the first 100 users page. The channel you can wait for is part of the fit.
| Channel | First users | What it asks of you |
|---|---|---|
| Paid search | Days | A budget and a page that converts the click |
| Launch platforms | A day, then it fades | A product a stranger can judge in thirty seconds |
| Organic socials | Days to weeks | A result people want to post |
| Community | Weeks | Being useful where your users already talk |
| Product-led | Weeks, after the first users | An invite or share inside the product |
| Weeks | A list, and a reason to write to it again | |
| B2B sales | Weeks to months | Conversations, and a summary a champion can show |
| Organic search | Months | Pages that answer what people type, and patience |
Prompts with the channel written in
Frequently asked
What is product-channel fit?
Brian Balfour's term for building the product to fit the channel it will grow through, because the channel sets the rules. In his words: products are built to fit with channels; channels do not mold to products.
What are Balfour's four fits?
Market-product fit, product-channel fit, channel-model fit and model-market fit. All four have to hold together; product-channel fit is the one that turns into features in a prompt.
Why does the channel belong in a Lovable prompt?
Because the channel decides features. A search-first app needs server-rendered pages with their own URLs, a product-led app needs an invite flow, a social app needs a result worth posting. Lovable builds what the prompt names, so a prompt without a channel builds an app with no way to be found.
Should I pick more than one channel?
One to start. Each channel needs its own features, and the first weeks spread over three leave each too thin to learn from. Add the second when the first brings users steadily.
Can product-channel fit change later?
Yes, channels change their rules and products outgrow channels; Balfour describes the fits as something to revisit. For a first app, pick one channel, build for it, and change only when the numbers say the channel has stopped working.
Is product-channel fit more important than product-market fit?
Balfour treats them as two of four fits that must hold together. Without market-product fit nobody wants the product; without product-channel fit the people who would want it never find it.
How does a library prompt show its channel?
Each prompt names a target channel, and its Pro variant opens with a Growth Features section for that channel: the pages, invites, share results or capture forms the app needs before that channel can bring anyone. The free base prompt builds the product; the Pro variant adds the channel mechanics.
What we did not publish
- A test of the same app built for two channels; the comparison above is two prompts, not two runs.
- Channel-model and model-market analysis; pricing and market size need numbers this page does not have.
Sources
- Brian Balfour: Product Channel Fit, read 23 October 2026
- The prompt library's channel data, counted at build time
Written by

Marco Kohns
Founder of ProtoBites - Venture Growth Studio
Growth PM at a Silicon Valley scale-up (a16z and General Catalyst backed), ex-Techstars where he consulted 13 early-stage startups, Reforge-trained. Every prompt on this site comes out of shipping ProtoBites' own portfolio products.
Related reading
- the first 100 users · Turning the channel into a playbook.
- landing page prompts · Built for one traffic source.
- SaaS prompts · Product-led loops in the prompt.
- app builder prompts · Thirty apps, each mapped to a channel.
- UI prompts with share moments · Organic social in the interface.
- integration prompts · Community and product-led mechanics.
- how to write the prompt · The section that carries the channel.
- the landing page kit · A capture page shaped for one source.
- vibe coding prompts by channel · Ten first prompts, one channel each.
- best AI app builder · Which builder ships which surface.
- app ideas · Fifty ideas sorted by the channel that gets them users.
- SaaS landing page prompt · One page for one source: the prompt and its run.
- how to build an MVP · A finished MVP with no users yet: the case for this page.