Make Your Small SaaS Sellable to Another Human: $250K Exit

You run a small SaaS and you are wondering whether another person would buy it. The test is whether the product can keep earning after you stop showing up.

Feather, a solo-built product, changed hands in June 2024 for $250,000, with Bhanu Teja P as the founder. The buyer was Tibo Louis-Lucas, a French serial entrepreneur, not a fund or operating company.

A buyer should be able to run it without you

Strip your name from the operating path. A buyer should be able to log in, renew infrastructure, answer a basic ticket, and release a small fix without calling you. If the codebase, billing, or onboarding depends on a private notebook, a personal email alias, or a habit only you understand, the product is not ready.

Ready means a handoff document that a cautious stranger can follow in a short sitting: identify the main revenue source, the main failure mode, and the main place to look when something breaks.

Feather stayed a one-person operation from its 2022 founding until the sale, and it charged about $40 per month on a single plan. That simplicity is part of why it could be understood quickly. A small product with a simple plan, a clear customer path, and a limited support channel is easier to value than a sprawling tool with many pricing tiers and integrations.

The usual mistake is treating documentation as a final polish. Write it while the system is still fresh, because the buyer will test the parts you assume are obvious.

A small public audience proves demand

Buyers fear a product that only exists because the founder keeps pushing it. A small public audience lowers that fear. It shows that strangers have seen the product, tried it, and paid without a sales team.

Bhanu Teja P had built a 28,000-follower X audience over eight years, and Feather gained 50 paying customers in six weeks. The audience did not need to be huge; it needed to be real, repeated, and connected to the product.

The finished state is a short public record: a launch note, a few customer replies, a changelog, or a small list of use cases that people recognize. If you have never shown the product to a public audience, the buyer will assume the demand is private and fragile.

Support should be a documented chore

Support load is the hidden cost of a small SaaS. A buyer does not want another job; they want a predictable one. If you spend most of your week answering the same questions, the fix is a written process.

Make a short support map. List the common questions, the exact answer, the place where the answer lives, and the escalation path for anything unusual. If a customer asks for a refund, the buyer should know the policy and the tone you expect.

A new owner's opening week should be orderly, with the main questions answerable without guessing your intent.

Price it as a low-maintenance asset

Do not pitch the product as the next big thing. Pitch it as a small income stream with a known ceiling and a known floor. The buyer wants a margin they can protect, not a growth story.

Feather's monthly recurring revenue rose from $843 to $4,180 during its first 9.5 months, then rose more slowly to about $6,000 by the sale, making the price about 3.5 times annualized revenue. The early jump shows the product can find customers. The slower later growth shows it can stabilize without a founder sprint.

When you set a price, anchor it to annualized revenue and the hours the product still requires. Count the hours per month, not just the revenue, because the buyer will do the same math. If the product needs more of your time, the multiple should fall. If it runs mostly by itself, the multiple can hold.

Use this scorecard before you write the final short offer:

• Founder-independence: the buyer can run it without you.
• Audience proof: a small public record shows demand.
• Support load: the recurring questions are documented.
• Documentation: a stranger can follow the handoff.
• Price: annualized revenue multiple, adjusted for hours per month.