The SaaS Podcast: How B2B SaaS & AI Founders Get Customers

By Omer KhanBusiness Entrepreneurship Technology

The SaaS Podcast: How B2B SaaS & AI Founders Get Customers episodes

January 18, 2015Startup Traction: DuckDuckGo's Bullseye Framework
Gabriel Weinberg built DuckDuckGo into a search engine with over a billion searches in 2013. But early on, he was stuck at just 10,000 searches a month - and the startup traction strategy he was using was never going to scale.
So he studied dozens of successful founders, from Jimmy Wales at Wikipedia to Alexis Ohanian at Reddit, and unpacked exactly what made their startup traction breakthroughs happen. The result was the Bullseye framework - a repeatable process for testing 19 traction channels to find the one that actually works.
When Gabriel first launched DuckDuckGo, he defaulted to SEO because it had worked at his previous company. It drove about 10,000 searches a month, but for a search engine that needed millions, it was never enough. That familiarity bias cost him valuable time and led to the startup traction testing methodology he now teaches.
🔑 Key Lessons
🎯 Startup traction requires testing all 19 channels: Weinberg found that every breakout startup had one dominant acquisition channel, but founders could never predict which one. The Bullseye framework forces structured testing across all 19.

📉 Familiarity bias kills startup traction efforts: Weinberg defaulted to SEO at DuckDuckGo because his previous company used it. It capped at 10,000 searches per month while the search engine needed millions to survive.

🔄 Rerun your startup traction process when channels plateau: DuckDuckGo cycled through the Bullseye framework six or seven times, switching from SEO to content marketing to social ads to PR as each channel hit its ceiling.

🚀 Content marketing takes six months before it pays off: OkCupid struggled early with their blog but once it hit critical mass with data-driven posts, growth skyrocketed. Even big companies write to no one at first.

🤝 PR is about building relationships, not pitching cold: DuckDuckGo landed a Time magazine Top 50 mention by building Twitter relationships with the 10-20 reporters covering their industry, not mass press releases.

📉 TechCrunch coverage rarely converts to paying customers: Most startups see a traffic spike from major press but zero conversions. Start with niche blogs and Hacker News first - bigger outlets feed on smaller ones.

🛠️ Quantify viral marketing before building it in: The biggest mistake with viral loops is not measuring the viral coefficient first. Without quantifying natural spread, you cannot know whether a referral system will drive startup traction.
Chapters
Introduction

Overview of Traction book

Why founders treat marketing as an afterthought

How the Traction book was written over five years

The Bullseye framework for startup traction explained

DuckDuckGo's Bullseye process in practice

Deep dive into 19 traction channels

Viral marketing explained

Common mistakes with viral marketing

DuckDuckGo's viral marketing experiments

PR as a traction channel

Why pitching TechCrunch is the wrong approach

TechCrunch traffic rarely converts

How DuckDuckGo landed Time magazine coverage

Content marketing beyond blogging

OkCupid's content marketing breakthrough

Getting traction for the Traction book

Where to buy the book and closing
Resources
Full show notes: https://saasclub.io/34
Join 5,000+ SaaS founders: https://saasclub.io/email
30 min
January 14, 2015Startup Competitive Differentiation: DuckDuckGo vs. Google
Gabriel Weinberg spent $10,000 to launch a search engine against Google. Every previous competitor had failed by trying to match Google's technology. But competitive differentiation on privacy, not technology, is what made DuckDuckGo work - reaching 250 million monthly searches with just 30 people.
In this episode, Gabriel reveals how competitive differentiation shaped DuckDuckGo's entire strategy: leveraging 300+ open data sources instead of crawling the entire internet, focusing on privacy and instant answers that Google could not easily match, and building a lean team with zero paid distribution deals.
Gabriel self-funded DuckDuckGo for three and a half years before raising venture capital. His competitive differentiation strategy avoided the head-on approach that had killed every previous search startup. Instead of spending billions to crawl the internet like Bing, he treated links as a commodity and focused on SaaS positioning around privacy, instant answers, and cleaner design.
🔑 Key Lessons
🎯 Competitive differentiation beats technology parity: Gabriel Weinberg proved that matching Google's crawling technology was the wrong approach. DuckDuckGo differentiated on privacy, instant answers, and design - areas where a 30-person team could outperform a thousand-engineer competitor.

🛠️ Leverage open data for competitive differentiation at low cost: DuckDuckGo used 300+ external data sources like Wikipedia, IMDb, and Yelp instead of crawling the internet. This let Weinberg launch for roughly $10,000.

🧠 Solve the switching problem, not the technology problem: Previous search startups failed because they copied Google's infrastructure instead of giving users a reason to switch. The psychological barrier to changing search engines was harder than the engineering challenge.

📉 Being a decade early can kill a good idea: Weinberg's first startup, an educational software company, targeted a real problem but launched in 2000 when structural conditions for adoption did not exist.

🚀 Constraints force market differentiation into unexpected directions: DuckDuckGo could not afford billion-dollar distribution deals like Bing, so every user switched by choice - building a product people genuinely wanted rather than one they defaulted into.
Chapters
Introduction

Gabriel Weinberg's background and family life

Favorite quote from Charlie Munger

What DuckDuckGo does and its target audience

Career before DuckDuckGo and selling a social networking startup

First startup failure - educational software a decade too early

How side projects in data led to building a search engine

Overcoming barriers to entry in search without massive capital

Launching DuckDuckGo for roughly $10,000

Validating the idea on Hacker News and Reddit

Biggest mistakes in the early days

Reaching product-market fit and Time magazine recognition

Running a search engine with 30 people and 300+ data sources

The hardest problem in search is competitive differentiation

DuckDuckGo's scale: 250 million searches per month

Open-source instant answer platform and community contributions

Lightning round

Ideation process for the next business opportunity
Resources
Full show notes: https://saasclub.io/33
Join 5,000+ SaaS founders: https://saasclub.io/email
31 min
January 11, 2015SaaS Product-Led Growth: Trello's Path to Millions of Users
Michael Pryor and Joel Spolsky spent 15 years building developer tools at Fog Creek Software. Then they created Trello - a product-led growth experiment that millions of people would use, including Google, Adobe, and the New York Times.
In this episode, Michael shares how product-led growth shaped every decision at Trello, from targeting 100 million free users with just 1% paying $100 a year, to designing a product so simple that users wrote their own blog posts promoting it for marketing, recruiting, and editorial workflows.
The freemium SaaS model was central to Trello's product-led growth strategy. Michael wanted 100 million people getting value from Trello, which required radical simplicity. Users started writing blog posts about how they used Trello for everything from applicant tracking to kitchen renovations. Trello never asked them to do it - the product spread through organic self-serve adoption.
🔑 Key Lessons
🚀 Product-led growth requires radical simplicity to reach mass adoption: Trello targeted 100 million users at 1% paid conversion, so the product had to be simple enough for anyone to use immediately, which meant resisting developer-specific feature requests from day one.

🎯 Product-led growth accelerates when users market for you: Trello's biggest growth driver was users writing blog posts about their own use cases - marketing, recruiting, editorial - each speaking to a specific audience without any prompting from the company.

🛠️ Side projects can outperform your main product: Fog Creek poured effort into City Desk, their first CMS product, but the bug tracker they built internally became FogBugz - the company's cash cow for 15 years.

📉 Most product experiments will fail, so run many: Fog Creek launched 13 products over 15 years. A job board for Indian programmers made 25 rupees. A $2,500 documentary series found no buyers. Only three products became significant.

🔄 Horizontal positioning is a freemium SaaS marketing problem: Trello could be used as a project manager, CRM, or applicant tracker, but having no category name made it hard to market. User-generated content solved this by showing specific use cases.

🏢 Self-fund before raising to retain control and validate traction: Fog Creek self-funded Trello for several years using product revenue before raising $10M+ in outside investment, which meant investors came inbound after traction was already proven.
Chapters
Introduction

Meet Michael Pryor

Success quote: Keep it simple

Trello overview and target customers

Before Fog Creek: Working at Juno

First product: City Desk CMS

FogBugz becomes the cash cow

Fog Creek's product philosophy

Why Trello spun off from Fog Creek

Where the idea for Trello came from

Creek weeks and innovation culture

Validating ideas at Fog Creek

Product-led growth: marketing Trello beyond developers

Positioning a horizontal product

The branding and naming challenge

How Omer uses Trello for podcasting

Trello as a flexible process tool

Fog Creek culture and values

Revenue and team size today

Why Michael became CEO of Trello

What excites Michael most right now

Lightning round
Resources
Full show notes: https://saasclub.io/32
Join 5,000+ SaaS founders: https://saasclub.io/email
44 min
January 07, 2015SaaS Content Marketing: Hiten Shah on KISSmetrics Blog
Hiten Shah and Neil Patel lost $2-3 million of their own money on failed businesses before Crazy Egg took off. Then they turned SaaS content marketing into the growth engine behind KISSmetrics, building one of the top marketing blogs on the web.
In this episode, Hiten explains how SaaS content marketing started as a Twitter account around the #measure hashtag before becoming KISSmetrics' primary lead generation channel. He also shares how he collected 23,000 email signups before Crazy Egg even launched and why a non-technical founder can build analytics companies by focusing on audience before product.
The KISSmetrics SaaS content marketing engine began with curation, not creation. Hiten shared analytics links where marketers already gathered, built a Twitter following, and then expanded into blogging about 18 months into the business. That content-led growth strategy outperformed every other channel and became the foundation for a $10M-funded analytics company.
🔑 Key Lessons
🎯 Start SaaS content marketing with curation, not creation: KISSmetrics' content engine began as a Twitter account sharing analytics links around the #measure hashtag, proving audience demand before investing in original blog content.

💰 Validate with a landing page before building the product: Hiten Shah collected 23,000 email signups for Crazy Egg by buying cheap ads on CSS gallery sites, spending just a few hundred dollars per month to prove market demand.

📉 Expensive failures teach the cheapest lessons about validation: Hiten and Neil Patel lost $2-3 million on failed businesses including a web hosting company that never launched, learning that customer willingness to pay matters more than founder conviction.

🚀 SaaS content marketing can become your primary growth channel: The KISSmetrics blog started 18 months into the business and grew into one of the top marketing blogs online, generating more leads than any other channel.

🧠 Break complex decisions into binary choices to maintain speed: Hiten first decides whether to pursue a direction before evaluating tactics, arguing that debating execution details without commitment wastes time and slows startups down.

🛠️ Non-technical founders can build SaaS by asking the right questions: Hiten contacted about 100 Ruby on Rails developers to find the right engineer for Crazy Egg, evaluating them by whether they could explain problems in non-technical terms.
Chapters
Introduction

Who is Hiten Shah outside of work

Success quote from Zig Ziglar

Why helping others pays dividends

Managing time across multiple businesses

Crazy Egg and KISSmetrics explained

Failed businesses before Crazy Egg

How the Crazy Egg idea evolved from broken analytics

Building the product as a non-technical founder

Advice for non-technical founders

Validating Crazy Egg with 23,000 email signups

From Crazy Egg to KISSmetrics

Why KISSmetrics raised $10M in funding

SaaS content marketing and the KISSmetrics blog

Marketing advice for founders without money

KISSmetrics growth trajectory

Biggest business challenges

Binary decision-making framework

Stepping down as CEO of KISSmetrics

Lightning round

Where to find Hiten
Resources
Full show notes: https://saasclub.io/31
Join 5,000+ SaaS founders: https://saasclub.io/email
55 min
January 04, 2015SaaS Product-Led Growth: 70K Downloads in 30 Days
Baydin launched Boomerang for Gmail with a two-month prototype and got 70,000 downloads in 30 days while still in private beta. Users were so desperate for the product they hacked around invite codes and hosted Chrome extension files on their own servers. That is what product-led growth looks like when you nail product-market fit.
In this episode, Aye Moah reveals how a team of just eight people turned a simple Gmail plugin into a profitable mid-7-figure business on under $400K in total funding. She explains how product-led growth powered Boomerang's expansion through viral loops, a porous paywall, and voluntary subscriptions that revealed their ideal pricing.
Baydin discovered their freemium SaaS pricing by letting users pay whatever they wanted. People started paying in multiples of 12, thinking in monthly terms, which revealed the price ceiling the team needed. That insight shaped their transition from free to a structured model that drove product-led growth at scale.
🔑 Key Lessons
🛠️ Build your MVP in weeks, not months, to test product-led growth fast: Baydin built Boomerang's first version in two months and launched into private beta immediately. The scrappy approach let them validate demand before investing in infrastructure.

💰 Use voluntary subscriptions to discover pricing: Instead of guessing a price, Baydin let users pay whatever they wanted. Payment patterns in multiples of $12 revealed users were thinking monthly, which shaped the eventual tiered pricing structure.

🚀 Build viral loops at moments of delight for product-led growth: Baydin prompted users to share at the exact moments they were happiest with the product. This low-cost tactic created sustained organic growth without any marketing budget.

🔄 Design a porous paywall that turns free users into promoters: Instead of a hard cutoff, Boomerang let free users extend access by referring friends or sharing on social media. The paywall itself became a customer acquisition channel.

📉 Keep referral programs simple or users will not engage: Baydin built a gamified referral wheel with variable prizes including Kindle Fires, but users found it confusing. The engineering effort far exceeded the growth impact.
Chapters
Introduction

Aye Moah's background and journey to entrepreneurship

Success quote: Focus on the process, not results

What Boomerang does and the pain points it solves

Where the idea for Boomerang came from

Meeting co-founder Alex and building the prototype

Launching into private beta and contacting press

70,000 downloads in 30 days during beta

Scrappy waitlist management with Google Docs forms

Building the first version in two months

Raising a seed round on $400K

Voluntary subscriptions and pricing discovery

Transition from voluntary subscription to freemium

Biggest early mistakes and MVP philosophy

Product-led growth through viral loops and zero-budget marketing

Organic press coverage from passionate users

Expanding to Boomerang Calendar and Outlook

What worked: porous paywall and viral moments

What didn't work: gamified referral wheel

Mid-7-figure revenue with 8 people

Excitement about the Boomerang mobile app
Resources
Full show notes: https://saasclub.io/30
Join 5,000+ SaaS founders: https://saasclub.io/email
41 min
December 18, 2014SaaS Co-Founder Clash: Why He Stepped Down
Martin Novak and his SaaS co-founder built Visidom with high school friends, bootstrapped it to paying customers, and flew to San Francisco chasing Y Combinator. Then Martin made the hardest call of his startup career - he stepped down.
In this episode, Martin reveals how two "CEO types" running one company created confusion for employees, slowed development to a crawl, and forced a painful SaaS co-founder breakup. He shares hard-won lessons on choosing a co-founder, the real limits of bootstrapping with equity-only teammates, and what the Y Combinator application process taught him even though Visidom did not get in.
The SaaS co-founder conflict at Visidom ran deep. Both Martin and Michael gave employees conflicting directions. The nine-person team was entirely part-time and paid mostly in equity, making accountability nearly impossible. A $70K EU government grant funded their San Francisco expansion but did not solve the internal leadership problem that was stalling the company.
🔑 Key Lessons
🤝 Two CEO-type SaaS co-founders create paralysis: Martin and Michael both tried to lead Visidom, giving employees conflicting directions that created confusion and accountability gaps. Martin stepped down to restore a single clear chain of command.

🧠 Test your SaaS co-founder relationship before committing full-time: Martin recommends doing a smaller project together first to see how you actually collaborate under pressure. Y Combinator reports that co-founder disputes are the number one reason their startups fail.

📉 Over-bootstrapping with equity-only teams kills your shipping speed: Visidom's nine-person team was entirely part-time and paid mostly in equity rather than salary. Chronic underfunding made it impossible to demand accountability or ship product fast enough.

🎯 Your co-founder agreement needs written terms from day one: Martin and Michael skipped important discussions about vesting schedules, cliff periods, and exit scenarios before incorporating. The lack of documentation made the breakup harder.
Chapters
Introduction

Meet Martin Novak

Personal motto and mindset

What Visidom does and who it serves

Martin's background before Visidom

How the idea for Visidom was born

Being naive enough to enter a competitive market

Validating the idea with existing contacts

Working 60-hour weeks while studying

Recruiting high school friends as the team

Bootstrapping costs and limits

Building the first beta version

Why the product still felt unfinished

Underestimating the scope of a SaaS product

Competing against established players

Charging from day one

Getting the first paying customers

Early marketing and conference outreach

Performance issues that blocked the launch

Applying to Y Combinator

Funding through EU government grants

Startup challenges in post-communist Czech Republic

Current business status and product pivot

Revenue, pricing, and raising a seed round

Managing a nine-person part-time team

When bootstrapping stops working

The SaaS co-founder breakup decision

Lessons on choosing co-founders carefully
Resources
Full show notes: https://saasclub.io/29
Join 5,000+ SaaS founders: https://saasclub.io/email
46 min
December 14, 2014SaaS Competitive Differentiation That Beat Microsoft Project
LiquidPlanner entered the project management market in 2006 when everyone already had Microsoft Project on their desktops. People told them they were crazy. But a single competitive differentiation bet on predictive scheduling - capturing uncertainty with best-case, worst-case estimates - gave them a foothold that incumbents could not replicate.
In this episode, CEO Liz Pearce shares how competitive differentiation on one feature let a small team challenge Microsoft, why interviewing 100+ users forced a painful 9-month product re-architecture, and how the company grew from a coffee shop sketch to 55 people and $11 million in funding.
Early growth came from a "Three for Free" model that gave away the first three users at no cost. But the real turning point came when LiquidPlanner interviewed over 100 customers and discovered a fundamental usability problem. The product required a full re-architecture - a 9-month sprint that tested the team but ultimately proved their SaaS positioning around uncertainty-based planning could work at scale.
🔑 Key Lessons
🎯 Win with competitive differentiation, not feature parity: LiquidPlanner entered a market owned by Microsoft Project by betting on one differentiator - predictive scheduling with uncertainty estimates - rather than trying to match incumbents feature-for-feature.

📉 Interview 100+ customers to find your real product problem: LiquidPlanner's team spent a summer interviewing over 100 customers and discovered a fundamental usability issue that required a 9-month re-architecture, not a quick feature fix.

💰 Use freemium to jumpstart early adoption: LiquidPlanner's "Three for Free" model gave away the first three user licenses, driving significant trial volume, though the team learned users will share licenses to avoid paying.

🤝 Treat customer communication as equal priority to development: During a 9-month product rebuild, LiquidPlanner retained customers by proactively sharing monthly updates about what was changing, why, and what the impact would be.

🏢 Go upmarket when competitive differentiation shows enterprise pull: After raising an $8 million Series B, LiquidPlanner shifted toward enterprise because larger teams got more value from the collaborative platform, creating stronger retention and expansion.
Chapters
Introduction

Liz Pearce's background and career path

Success quote: Feed the eagles, starve the turkeys

What is LiquidPlanner and the predictive scheduling engine

Joining the founders before any code was written

Validating the market against Microsoft Project

How competitive differentiation on one feature beat the incumbents

Free beta and the path to the first paying customer

Customer acquisition and the "Three for Free" freemium model

Biggest mistake: discovering the usability problem

The 9-month product re-architecture sprint

Marketing channels: blogging, events, and free trials

Why some marketing activities are worth doing without direct attribution

Retaining customers during the 9-month development freeze

Growth trajectory and raising angel funding

Moving upmarket from SMB to enterprise

Scaling the team from 12 to 55 people

Growing pains: process, management layers, and tech debt

Revenue and current business stage

Lightning round
Resources
Full show notes: https://saasclub.io/28
Join 5,000+ SaaS founders: https://saasclub.io/email
34 min
December 10, 2014Selling a SaaS Business: Why He Left a 7-Figure Company
Stu McLaren built Wishlist Member into a 7-figure business powering 54,000 membership sites. Then he did something most founders would never consider - selling a SaaS business while it was still thriving.
In this episode, Stu reveals the 2 AM moment at a family camp that changed everything, how two books rewired his thinking about focus and essentialism, and why selling a SaaS business that ranked an 8 out of 10 was the hardest but most important decision of his career.
What makes this SaaS exit story compelling is the context. Wishlist Member was not failing. The business was profitable, growing, and Stu loved his partners and customers. But after reading Essentialism by Greg McKeown, he applied the 90% rule - anything below a 9 had to go. He validated his next move by partnering with Michael Hyatt to launch a membership site that hit 1,100 members at $20/month in the first week.
🔑 Key Lessons
🎯 Use the 90% rule before selling a SaaS business: Rank every project on a 1-to-10 scale against one criterion. Anything below a 9 must go, even an 8, because near-great drains energy from truly great work.

📉 Leaving a successful business is harder than leaving a failing one: Stu ranked Wishlist Member an 8. That score was harder to act on than a 5 because it felt close enough to justify staying.

🚀 Validate your next move before finalizing the sale: Stu partnered with Michael Hyatt and launched a membership site that hit 1,100 members in week one, proving demand before fully walking away.

🧠 Cure "idea diarrhea" by channeling creativity into one focus: Stu chased new ideas daily and made no meaningful progress. Wishlist Member only took off when he committed all creative energy to one product.

🔄 Separate your identity from your SaaS exit: Stu had to confront that Wishlist Member was how he answered "what do you do?" for years. Detaching self-worth from the company was essential to selling a SaaS business.

💰 Go all-in on Plan A instead of hedging across B, C, and D: Splitting effort across ventures means none reach potential. Full commitment and failing fast beats half-hearted attempts that drag on for years.
Chapters
Introduction

Recap of Wishlist Member and Rhino Support

Stu announces selling a SaaS business

Why sell when both businesses are thriving

The 2 AM moment at family camp

How Essentialism and The One Thing changed everything

The 90% rule for making decisions

Ranking projects on a scale of 1 to 10

Wishlist Member scores an 8 out of 10

Fear, doubt, and identity crisis

Partnering with Michael Hyatt on a membership site

1,100 members in the first week at $20/month

Growing the membership to seven figures

Helping entrepreneurs redesign their businesses

Advice for founders juggling multiple projects

The disease of "idea diarrhea"

Doubling down on one idea vs. scattered effort

What if you pick the wrong idea

Lightning round

Building schools in Kenya
Resources
Full show notes: https://saasclub.io/27
Join 5,000+ SaaS founders: https://saasclub.io/email
28 min
December 07, 2014Bootstrapped Software Startup: $47 Plugin to 7 Figures
Stu McLaren had no coding skills and no funding, but he managed to bootstrap to profitability within months. He sketched mockups in Photoshop, sold a $47 beta to 21 friends in a mastermind group, and watched Wishlist Member grow into a 7-figure business powering over 54,000 membership sites.
But the bootstrap to profitability journey nearly ended when his lead developer quit, WordPress released a breaking update, and six replacement hires still could not keep up. What happened next changed the trajectory of the company forever.
Stu's path to profitability started with a $47 beta sold to 21 mastermind members. All of them bought. The public launch at $97/$297 generated $6,000 in month one, $10,000 in month two, and $21,000 by month three. The first year totaled roughly $450,000, and year two crossed seven figures - all self-funded SaaS growth with zero outside investment.
🔑 Key Lessons
🎯 Bootstrap to profitability by scratching your own itch: Stu built Wishlist Member to solve his own membership site frustration, which meant he deeply understood customer pain and could communicate it authentically without expensive market research.

💰 Charge from day one to validate real demand: Stu sold the beta at $47 to mastermind members instead of giving it away free. All 21 paid, confirming willingness to buy before he invested in a public launch.

🚀 Bootstrap to profitability through word of mouth, not paid marketing: Wishlist Member grew from $6,000 to $21,000 monthly revenue in three months with minimal marketing spend, driven almost entirely by email lists and organic referrals.

📉 Single-point-of-failure on a key hire can nearly kill a business: When Wishlist Member's sole developer left, six replacements still could not keep up. A breaking WordPress update during the transition created a four-month support crisis.

🤝 Offer equity to retain irreplaceable team members: Stu convinced developer Mike to return by offering a partnership stake, not just a job. Mike came back, fixed everything, and built a team that eliminated future dependency risk.

🛠️ Build virality into your product's daily usage: Rhino Support added "Powered by" branding to every help desk email, turning each customer interaction into a marketing impression for thousands of end users.
Chapters
Introduction

Who is Stu McLaren

Favorite success quotes

Wishlist Member overview and target customers

How the product idea started from personal frustration

Turning the idea into a real product

Why the product took off without much marketing

Handling customer feedback and feature requests

Why scratching your own itch drove early success

Selling the beta to 21 mastermind members

Early pricing strategy from $47 to $97

Revenue growth from $6K to $21K per month

Launch date and first year revenue milestones

Biggest mistake: losing the lead developer

Developer Mike returns as a business partner

Current revenue and bootstrap to profitability results

Rhino Support origin story

Marketing Rhino Support with built-in virality

Why Rhino Support grew slower than expected

Splitting Rhino Support between both teams
Resources
Full show notes: https://saasclub.io/26
Join 5,000+ SaaS founders: https://saasclub.io/email
39 min
December 03, 2014SaaS Pricing Fix: How Charging More Doubled Revenue
Rick Perreault thought cheaper SaaS pricing would attract more customers. Instead, Unbounce's $10 and $25 plans were costing $150 per acquisition while those customers churned after just four months. The SaaS pricing model was bleeding money.
Rick reveals how Unbounce went from zero to $7.2 million in annual revenue by killing its cheapest pricing strategy tiers, raising average revenue per customer from $30 to $80, and using content marketing instead of a sales team to grow to 7,500 paying customers.
🔑 Key Lessons
💰 Fix SaaS pricing by measuring cohort economics, not volume: Unbounce saw dozens of $25 plan trials daily, but cohort analysis revealed those customers churned after four months, paying $100 total against $150 in acquisition costs.

📉 Cheap plans create hidden support costs: Low-tier customers demanded six support calls before onboarding. Eliminating those subscription pricing tiers freed the team for proactive customer success.

🎯 Validate before building: Rick spent under $200 on Facebook ads targeting marketers by job title and collected 42 survey responses from strangers, proving universal pain before writing any code.

🚀 Use content marketing to build a category: Unbounce published 100 blog posts on landing pages and A/B testing before launch, creating an audience for a product category no one was searching for.

💰 Higher SaaS pricing attracts better customers: When Unbounce dropped sub-$50 plans, average revenue per customer rose from $30 to $80 and churn fell because professional marketers valued the tool more.

📉 Avoid enterprise distractions when built for self-serve: Unbounce wasted cycles on custom feature requests from big brands. Nine times out of ten, those companies signed up for the standard pricing model anyway.
Chapters
Introduction

Who is Rick Perreault outside of work

What Unbounce does and the pain it solves

Rick's career before starting Unbounce

Deciding to quit consulting and build a product

Using Facebook ads for customer development

What Rick asked potential customers in surveys

Why being non-technical forced better validation

Pitching the idea to future co-founders

Building the first version with six co-founders

Bootstrapping with credit cards and lines of credit

First four paying customers in 2010

Biggest mistake: trying to be everything to everybody

The $25 plan SaaS pricing disaster and cohort analysis

How charging more doubled revenue

Content marketing as primary growth channel

Why paid advertising never worked for Unbounce

Managing decisions with six co-founders

Unbounce today: $620K MRR and 7,500 customers

Lightning round
Resources
Full show notes: https://saasclub.io/25
Join 5,000+ SaaS founders: https://saasclub.io/email
48 min

About The SaaS Podcast: How B2B SaaS & AI Founders Get Customers

From the publisher's feed

Building software got easier. Getting customers didn't. Every week, a founder building B2B SaaS or an AI product tells you how they got their first customers, and how they kept them: what worked, what didn't, and what they'd do differently.