Chapter 2: Market

Core Idea

Much of a SaaS company’s success depends on understanding its market and ideal customer. You strengthen product-market fit by talking to customers and by being strict about which features to build. In a crowded market, compete on price, sales model, or product. Watch competitors only for what matters, build moats that last, and avoid common distractions.

Frameworks Introduced

• Customer conversations: the most reliable way to understand your market. They shape your road map, positioning, marketing copy, and pricing.
  • Talk to four groups: prospects, customers, people who decided not to buy, and people who bought and then cancelled.
  • Typical questions: “Can you walk me through a sample flow?”, “What problem are you trying to solve?”, “What do you currently use to solve this problem?”, “What did you use in the past?”, “What are some of your biggest frustrations about this solution?”
  • Ask open-ended questions, not leading ones. Showing a mock-up and asking for a reaction makes honest answers hard.
  • Put your “consultant hat” on: the conversation is about the customer’s needs, not your product. Jim Kalbach (The Jobs To Be Done Playbook) says that looking at people through your own solution clouds your judgment.
  • Example: SignWell’s founder, Ruben Gamez, kept hearing that customers wanted to send their own link for signing instead of an email from a third-party service. Building that helped SignWell stand out in a very competitive market.
• Three buckets for feature requests:
  • The Crackpots (about 10–15%): requests that need a whole new product, would turn you into a clone of a competitor, or go against your product’s strengths. Decline them.
  • No-Brainers (about 20%): requests already on your road map or so good you want them now. Drip’s examples were adding tags to subscribers retroactively based on past link clicks, and a button to prune inactive subscribers.
  • In-Betweens (the rest): not bad and not obviously good. These need judgment.
• Three questions for In-Betweens:
  1. What’s the use case? Ask what leads them to want it, what problem it solves, and what they use now. Sometimes the product already solves it; then explain how and make it easier to find in the UI.
  2. What percentage of customers will use it? Guess. If it’s 5–10%, check who they are. If they are power users, consider building it hidden from the standard UI and turning it on by request. At 20% or more, consider building it.
  3. Does it fit my vision of the product? Every feature has an opportunity cost. If it doesn’t fit, don’t build it.
  • For large requests, an integration with a product that already solves the problem can take days instead of months.
  • The founder makes these calls until a product manager is hired, usually above $1M ARR.
• Three ways to compete in a mature market (the author advises against a first startup in a very competitive market without experience, funding, or both):
  • Price: offer more than 80% of the product for half the cost. Incumbents’ pricing power leaves room under them. Raise prices as the product matures; don’t stay the low-cost option forever.
  • Sales model: if incumbents require demos before showing prices or charge setup fees, enter with low- or no-touch sales and public pricing. Infusionsoft required a setup fee of a couple of thousand dollars and training; Drip offered a free trial with a credit card.
  • Product: modern UX and fast shipping against old code bases (Xero against QuickBooks; Pipedrive and Close against Salesforce). This advantage fades as your own code ages.
• Marketing against large competitors (judo): use their size against them. Find users who are frustrated with the incumbent, help them migrate, and they tell others. Position as the underdog: Avis ran “We’re #2, we try harder”; Drip’s home page said “Lightweight Marketing Automation That Doesn’t Suck” and positioned it as not Infusionsoft, Marketo, or Pardot.
• How much to watch competitors:
  • Care about high-level updates (news big enough for industry sites: funding, major features, positioning changes). Study what they tell you about the market.
  • Care about deals you’re losing. Find out why (features, price, certifications such as SOC 2) and respond by repositioning, repricing, or closing the gap.
  • Ignore low-level details. From outside, every competitor looks polished, and many funded companies make basic mistakes.
  • Ignore their funding. Most blow through it in about 18 months. The exception: a raise of $5M or more may fund a free or low-price push to take over the market.
  • Ignore being copied. It will happen if you succeed. Use a cease and desist only for blatant copying.
• Four moats (the idea of an economic moat comes from Warren Buffett):
  • Integrations (network effect): in bootstrapped SaaS, network effects come from integrations rather than users. Zapier has over 3,000 integrations, some through private APIs that competitors can’t easily get. Each integration a customer turns on, especially one that puts more of their data in your database, is another reason not to switch.
  • A strong brand: your reputation, “what people say about your company when you’re not around.” Strong brands are in the conversation when buyers compare options. Positioning is part of brand: focusing a general tool on museums can build a moat around that segment. (See April Dunford’s Obviously Awesome.)
  • Owned traffic channels: ranking for high-volume terms on Google, Amazon, or the WordPress plugin store lets even a commodity product compete. One friend’s company gets 500,000 visitors a month from SEO. Algorithm changes are the risk.
  • High switching costs: APIs (Stripe, Twilio, SendGrid) need developer time to replace. Slack needs buy-in from every manager and has many integrations. Social media schedulers and one-click analytics tools are easy to leave.
  • False moat: unique features. Competitors copy them within months. Relying on a stream of new features is “a hamster wheel of features,” not a moat.
• Siren songs (distractions founders pursue when growth is slow; usually the real fix is product-market fit or marketing and sales):
  • Translating the product: you also have to translate marketing, support, docs, social, and email. The one success the author saw translated only the app, for Spanish-speaking end users whose English-speaking managers were the customers.
  • White labeling: most requests come from people with no audience or distribution. Talk only to large players, and charge $30,000–50,000 up front at minimum. You also give up brand, which is a moat.
  • Adding verticals too early: wedding photographers to wedding videographers can work; adding wedding coordinators brings different needs and product complexity. Do it only if you already dominate a niche or are pivoting fully.
  • Underpricing: the most common mistake, and usually psychological (fear of rejection, undervaluing what you built, comparing with cheap competitors). At $10 instead of $100 a month you need 10× the customers and can afford fewer marketing channels. It can be the difference between a $250,000-a-year business and a multimillion-dollar one.

Key Concepts

• Ideal customer: the customer whose problems you build for. Deep knowledge of them can itself become a moat.
• Economic moat: a lasting advantage that protects market share and profit, and grows stronger as the business grows.
• Network effect: value rises with the number of participants (one telephone is useless; a hundred are valuable).
• Switching cost: the work a customer must do to move to a competitor.

Mental Models

• Customers don’t know how to build your product. Solve the problem behind the request, not the requested button.
• Saying no is the job. The author quotes Steve Jobs: focus means saying no to the hundred other good ideas.
• Your vision is your scarcest resource, more than time or money.
• A competitive market is a proven market. People already pay to solve the problem, and incumbents leave frustrated, underserved niches.

Anti-patterns

• Building every feature request: the product turns into “a mass of buttons, boxes, toggles, and settings.”
• Checking competitors every morning: it hurts your mental health and distracts from customers. Unless you lose deals to them regularly, “keep your eyes on your own paper.”
• Assuming a competitor’s move is smart just because they made it.
• Counting on unique features as a moat.
• Fixing slow growth with translation, white labeling, new verticals, or low prices.

Rules of Thumb (author’s wording)

• Offer more than 80% of the product for half the cost.
• Your brand “is what people say about your company when you’re not around.”
• If you rely on new features to stand out, “You have a hamster wheel of features.”
• For white labeling, “$30,000 to $50,000 at a minimum” up front.
• Keeping the price low is not the key to kickstarting growth.

Worked Example

Triaging five feature requests for a hypothetical invoicing SaaS with 400 customers.

Request	Bucket	Three questions	Decision
“Can you add a full CRM?”	Crackpot (new product, competitor clone)	—	Decline politely.
“Auto-remind clients 3 days before an invoice is due”	No-Brainer	Clear use case, most customers send invoices	Put it on the road map now.
“Multi-currency with live FX rates”	In-Between	Use case: international clients. About 8% of customers, and they are the highest-paying accounts. Fits the vision.	Build it, hidden from the standard UI and turned on by request.
“Export to our accounting tool”	In-Between	About 30% would use it. Fits the vision.	Build it as an integration with that tool’s API, in days rather than a native feature.
“Add 12 layout options to invoices”	In-Between, against your strength (simple UI)	3% would use it. Hurts the simple UI.	Decline and explain the existing template option.

Key Takeaways

1. Talk regularly to prospects, customers, people who didn’t buy, and people who cancelled. Ask open-ended questions.
2. Sort feature requests into Crackpots, No-Brainers, and In-Betweens. Judge In-Betweens by use case, share of users, and fit with your vision.
3. In a mature market, compete on price, sales model, or product, and turn the incumbent’s frustrated users into word of mouth.
4. Watch only competitors’ high-level moves and the deals you lose.
5. Build lasting moats (integrations, brand, owned traffic, switching costs). Unique features are not a moat.
6. When growth is slow, fix product-market fit or marketing instead of translating, white labeling, adding verticals, or cutting prices.

Connects To

• Ch 3: underpricing and how to fix it.
• Ch 4: integration marketing, positioning, and how the sales model affects marketing.
• Ch 6: churn interviews, which feed product decisions.
• Michele Hansen, Deploy Empathy and Rob Fitzpatrick, The Mom Test (both in the book’s resource list): customer interviews. See The Mom Test.
• April Dunford, Obviously Awesome: positioning.