How Much to Pay Yourself From a Bootstrapped SaaS

Every article I've read about founder salary assumes you have a board, a cap table, or at least a seed round to reference against. "Pre-seed founders average $50K, Series A founders average $100K" — none of that means anything when your entire company is a Stripe account, a few hundred dollars of MRR, and you, deciding at 11pm whether it's okay to move money from the business account to your personal one.

If you're running a bootstrapped SaaS with no funding and no co-founder to argue about this with, the actual question isn't "what's the market rate." It's "how do I not either starve myself or quietly drain the business without noticing." Those are two different failure modes, and most founder-salary content only warns you about the second one.

Why Founder Salary Advice From Funded Startups Doesn't Apply to You

Almost everything written about founder compensation is really about board governance. The salary bands you see quoted — pre-seed, seed, Series A — exist because investors want to know their money isn't funding someone's lifestyle instead of the product. That's a real problem worth solving, but it's not your problem if there's no investor money in the account to misuse.

When it's just you and revenue from real customers, the constraint isn't "what will the board approve." It's "what does the business actually generate, and what happens to that business if I take too much or too little out of it." That's a cash flow question, not a governance question, and it needs a different framework than the one built for funded startups.

The Two Runways You're Actually Managing

This is the part that trips people up. When you're bootstrapped, you're not managing one runway — you're managing two, and they run on separate clocks.

Business runway is how long the company survives on its own cash if revenue stalled tomorrow — hosting, tooling, any contractors, taxes owed. Personal runway is how long you survive if the business paid you nothing this month — rent, food, the stuff that doesn't care whether your MRR chart is trending up.

The mistake I see (and made myself, watching freelance clients do this) is treating these as one pool. Founders either pull personal expenses straight from the business account without formalizing it as a salary, which makes the business's real financial health impossible to read — or they refuse to pay themselves anything "to keep runway long," while their personal savings quietly bleed out at a much faster rate than the business's. Both are the same error: solving for one runway while ignoring that the other one is running out too.

The fix is boring but it works: pay yourself something, however small, on a fixed schedule, and treat it as a real expense line in the business's books — not a withdrawal you'll "true up later." Later never comes cleanly, and by the time you try to reconstruct it, you won't trust your own numbers.

A Rough Framework by Revenue Stage

There's no universal number, but there is a reasonable way to think about the percentage of revenue you can safely draw at different stages. This isn't a rule — it's a starting point to adjust from your own costs.

$0–$1K MRR. Don't pay yourself from the business yet. At this stage the business likely isn't covering its own costs (hosting, any paid tools, transaction fees), and pulling a salary out of it just means you're funding your paycheck from your own pocket a step removed. If you need income, get it from savings, part-time client work, or a job — not from a business that can't yet support itself.

$1K–$5K MRR. This is where a token salary makes sense — enough to cover the psychological and practical cost of "should I keep doing this," not enough to strain the business. Something like 10–20% of revenue, reassessed monthly, works reasonably well here. The goal isn't to live off it; it's to make the habit of paying yourself something real before the amount matters.

$5K–$15K MRR. You can usually move toward 30–40% of revenue once your fixed costs (hosting, tools, any contractors) are a known, stable number rather than a guess. This is also the range where it's worth separating "salary" from "one-time draws" — resist pulling extra out for a good month, because a good month followed by a bad one is when people get into trouble.

$15K+ MRR. At this point you likely have enough historical data to model your actual expenses and set a salary that's closer to a real number, reviewed quarterly rather than reacted to monthly. This is also usually where it's worth a proper conversation with an accountant about entity structure, since the tax implications of drawing income change meaningfully at this size.

None of these numbers are precise, and yours should flex based on how much runway you have outside the business and how volatile your revenue actually is month to month.

The Tax Mistake That Catches Almost Everyone

Nobody warns solo SaaS founders about this clearly enough: money that hits your business account is not money you get to keep. If you're operating as a sole proprietor or through a pass-through entity, a real portion of every dollar you draw needs to be set aside for taxes before you ever think of it as spendable income.

The practical fix is mechanical, not clever: the moment revenue lands, move a fixed percentage — many freelancers and solo founders use somewhere around 25–30% depending on their tax bracket and jurisdiction — into a separate account you don't touch. A basic bookkeeping or invoicing tool that logs this automatically is worth paying for long before you think you need one; I've covered a few worth the money in 5 Tools Every Solo Developer Should Actually Pay For. Do this before you calculate what you can pay yourself, not after. I've watched this exact mistake play out in freelance client work: someone treats their whole business balance as personal spending money for months, has a great quarter, and then owes far more in taxes than they set aside for, at exactly the moment cash is tightest.

This isn't tax advice specific to your situation — talk to an accountant about your actual jurisdiction and entity type. But the habit of setting aside taxes at the moment money arrives, rather than at the moment taxes are due, is close to universal.

When "Not Yet" Is the Right Answer

Sometimes the honest answer really is that you shouldn't be paying yourself anything right now, and that's fine as long as it's a deliberate decision rather than a default. "Not yet" should mean: I've looked at my personal runway, I know how many months I have before this becomes urgent, and I've chosen to extend the business's runway with that time deliberately.

What it shouldn't mean is avoiding the conversation with yourself entirely — no number, no review date, just vague hope that revenue will eventually make the question resolve itself. Set a specific MRR or a specific date where you'll revisit the decision. Otherwise "not yet" quietly becomes "never," right up until personal financial pressure forces a rushed decision instead of a planned one.

If you want the cash-flow side of this — how long your business itself survives at current burn, separate from your own — that's a related but different calculation worth working through on its own. You can find more Finance for Builders posts on this site if that's the piece you're missing.

The Takeaway

Founder salary content built for funded startups is optimizing for a problem you don't have — investor trust in how their capital is spent. Your actual problem is running two separate clocks, personal and business runway, without letting either one quietly run out while you're focused on the other. Pick a small, real number, pay it on a schedule, set aside taxes the moment revenue lands, and revisit the number as MRR grows instead of reacting to it emotionally month to month.