Acquiring and growing a bootstrapped SaaS in a crowded market

Executive overview

Buying an existing SaaS product bypasses the hardest part of founding — getting from zero to something. But the technical debt and market position you inherit are rarely what they appear. Cody Duvall acquired Keeping, a Gmail-based customer support tool, and had to rebuild it from scratch while competing against Zendesk and Help Scout with a fraction of their resources.

The lesson: in a crowded category, survival depends on owning a tight niche, building before hiring yourself out, and accepting outside capital when organic growth stalls at scale.

Bootstrappers in large markets need a war chest — organic growth alone won't win against publicly traded competitors.

Why enter a crowded market

• Most small businesses don't need the full power of Zendesk or Help Scout — those tools are expensive and complex.
• A gap exists between sharing a Gmail inbox and professional-grade help desk software.
• Keeping fills that gap: it turns Gmail itself into a customer support tool.
• Customers who build workflows inside the tool rarely churn — setup investment creates switching cost.
• The target customer (wholesale businesses, small B2B teams) will never grow a large support team, so "outgrowing" the tool is uncommon.

Acquiring instead of building

• Cody met FE International at Microconf 2019 while working on a developer-facing idea with a co-founder who had just had a baby.
• Keeping had a single-word domain (keeping.com) and a handful of customers — low price, validated concept.
• The code was a technical disaster: servers went down multiple times a day, customers emailed asking for reboots.
• Due diligence via GitHub revealed problems, but the full extent only became clear weeks after acquisition.
• Customers tolerated the outages without churning — a strong signal of real demand.
• Key lesson: if you're buying a software business, be ready to support it technically; that may be the hardest part.

Rebuilding the product

• Cody chose to rebuild from scratch rather than patch the existing codebase — unusual advice, but justified when the app is basically unusable.
• He hired an experienced offshore team in Poland instead of doing the rewrite himself.
• The rationale: his time was worth more than the offshore rate, and going solo would have taken nine months with the same endpoint.
• With only a handful of customers, migration was manual — account by account over a few weeks.

When to stop coding and start managing

• Technical solo founders should stop writing code as soon as they can afford to and shift to reviewing pull requests and managing a team.
• At around $2–3k MRR, that money should go toward an offshore developer rather than more founder coding time.
• The inverse applies to marketer-founders: hire developers early, but learn enough to manage them before doing so.
• Cody hired a content marketing agency before he understood content marketing — he had no way to judge quality or results.
• You need to do each function yourself long enough to know what good looks like before you can manage the people doing it.
• These are "boss battles": you have to become good enough to manage every role before hiring it out.

Growing in a market dominated by giants

• Paid search is effectively closed: Zendesk and Help Scout bid on the same keywords with far larger budgets.
• SEO and content marketing became the primary growth channel — cheaper but slower to compound.
• Natural organic growth masked the absence of a clear customer definition for the first six months.
• At sub-$5k MRR, there's not enough revenue to reinvest meaningfully into marketing in an expensive category.
• Customer interviews in a mature category backfire: customers ask for features that already exist in competitors' tools, pushing founders toward building a worse version of Zendesk.
• The winning move is to find and defend a seam in the market — not to compete feature-for-feature.
• Keeping's differentiator: everything stays inside Gmail; no extra tab, no new tool.

Recognising product-market fit

• Product-market fit is not a binary event — it's a continuum from 0 to 100, with an expanding ring of customers it applies to.
• Leading signals: low churn, improving trial-to-paid conversion, and the feeling customers communicate when they talk about the product.
• It doesn't always show up as a hockey stick in revenue charts — you still have to expose the product to new customers.
• Fit is always being iterated; expanding the product extends it to a slightly wider group each time.

Taking outside investment as a bootstrapper

• Cody applied to Tiny Seed on impulse after hearing an announcement on the podcast — the application took ten minutes.
• Two reasons to take investment: financial runway, and external validation for yourself and your family.
• Community and peer mastermind access proved as valuable as the cash.
• The investment funded two writers and a content strategist — headcount that wouldn't have been possible from profits alone.
• In a large, expensive category with well-funded competitors, a war chest isn't optional.
• Tiny Seed also brought in Demand Maven (Asia Arangio) for customer research, which was a turning point in understanding who Keeping's real customer was.

Competing as a bootstrapper against public companies

• Large competitors move slowly and absorb marketing oxygen — they dominate paid and organic search.
• Advantages of the lower end of the market: one decision-maker with a credit card, no committee, no multi-month sales cycle.
• ARPU is lower, which limits growth channels, but self-serve inbound is viable.
• Platform risk is real (Keeping depends on Gmail's API access), but three billion Gmail users is a substantial addressable market.
• You can't win by replicating a competitor's feature set. Win by owning a channel, a niche, or a unique position — not by building a slower, smaller Zendesk.