What does it cost to run a SaaS with 100 paying customers?

Most SaaS cost guides — including our $1K MRR teardown and our $10K MRR teardown — index off MRR. That’s great for benchmarking the tooling stack, but it hides something important: what your business actually feels like depends on customer count, not revenue. 100 customers paying $9/month and 10 customers paying $90/month are both $900 MRR, but they’re completely different companies with completely different costs. This guide does the math from the customer-count perspective.

Why 100 customers is the right unit (not MRR)

MRR is a derived metric. Customer count is structural. The reason: pricing varies wildly across SaaS categories, but most operational reality — support load, billing edge cases, onboarding work, refunds — scales with the count of humans you’re serving, not the dollar size of their plan.

Two solo founders both at $5K MRR can have radically different lives:

• Founder A: 500 consumers paying $10/month. They handle 30 support tickets a week. Refunds happen weekly. Email volume is high. Stripe disputes occasionally appear.
• Founder B: 25 mid-market companies paying $200/month. They handle 5 support emails a week. Disputes are nonexistent. Email volume is low. But each customer expects a quarterly check-in.

Same MRR. Different cost profiles. Different scaling traps. Different next steps. That’s why customer count matters as its own lens.

Scenario 1: Low-touch consumer SaaS at $9/month ARPU

100 customers × $9/month = $900 MRR. Think a productivity utility, a hobby tool, a niche consumer app. Customers self-serve, churn is high, support is high-volume but low-touch.

The monthly P&L

The Stripe line item is the headline cost driver in low-ARPU SaaS. At $9/mo, the 30¢ per-transaction fee is over 3% of the customer’s payment, on top of the 2.9% rate. So your effective Stripe rate is closer to 6.2% — double the rate a $99 product pays. We covered this dynamic in Stripe pricing explained.

What the numbers don’t show

The line item missing from this P&L is your time. 100 consumer customers at $9/month typically generate 20–40 support touches per week. If each takes ten minutes, that’s 3–7 hours/week of unpaid founder support work. At $50/hour notional, that’s $600–$1,400/month of invisible cost. Most low-ARPU SaaS founders quietly run a negative real margin until they automate or raise prices.

Scenario 2: Standard SMB B2B SaaS at $29/month ARPU

100 customers × $29/month = $2,900 MRR. This is the meat of the indie SaaS market. Tools used by small businesses, freelancers, agencies. Customers are professional, churn is moderate, support is mixed self-serve and email.

The monthly P&L

The economics here are dramatically better than the consumer scenario, even though tooling costs are nearly double. The reason is simple: your Stripe effective rate dropped from 6.2% to 4.0% because the 30¢ flat fee is a smaller share of $29 than $9. Higher-ARPU SaaS scales more profitably per customer, and that’s before any productivity gains from fewer support tickets.

For a sense of how this evolves, our $1K MRR teardown covers a similar profile from a different angle, and $10K MRR shows what changes once volume hits.

Scenario 3: High-touch B2B SaaS at $99/month ARPU

100 customers × $99/month = $9,900 MRR. Think tools for mid-sized teams, vertical SaaS for specific industries, products with real workflow depth. Customers are evaluating you against bigger vendors, and they expect more.

The monthly P&L

The high-touch scenario is where the support-tooling, CRM, and security line items become real. SOC 2 readiness alone often costs $200–$500/month in tooling once you’re selling to customers who ask about it. That single line item is invisible at $9 ARPU and unavoidable at $99 ARPU.

Where the support cost shows up at 100 customers

Across all three scenarios, the line that doesn’t appear on the P&L is the most important one: your time. Even if you’re not on payroll, hours you spend answering tickets are hours you’re not building, marketing, or selling.

Realistic founder-time-on-support estimates at 100 customers:

• Consumer at $9/mo: 5–10 hours/week. Volume is high, individual issues are simple, but the cumulative load is brutal.
• SMB B2B at $29/mo: 3–5 hours/week. Lower volume, occasionally meatier issues. Most can be batched into a couple of focused sessions.
• High-touch B2B at $99/mo: 5–10 hours/week. Lower volume than consumer, but each issue takes longer and customers expect faster response. Often includes monthly check-in calls.

Notice that consumer and high-touch B2B are roughly equivalent in support load — via completely different mechanisms. That’s why “100 customers” is the unit, not MRR.

What 100 customers tells you about the next 100

The math at 100 customers is genuinely encouraging. The gross margins are healthy. The tooling costs are manageable. The product clearly works for someone. But here’s the warning: the things that worked manually at 100 customers usually break at 1,000.

Your funnel can scale; your support load probably can’t

If you went from 0 to 100 customers via direct outreach, content marketing, or a hot launch — great, those channels can keep working at the next 100 with more polish. But if support is taking 5 hours/week at 100 customers, it’ll take 50 hours/week at 1,000 customers without intervention. That’s a full-time job, plus a part-time one. Most solo founders hit this wall at 200–400 customers, and it’s usually the moment to either automate aggressively or hire help — we covered the decision in when to hire your first contractor.

Onboarding breaks before billing breaks

At 100 customers, you can probably remember most of them by name. You can DM them when something breaks. You can write personalized welcome emails. None of this scales. The first thing you’ll need to systematize is onboarding — an automated welcome sequence, a self-serve setup flow, in-app tutorials. Customers who self-onboard well churn less, and the math compounds.

Billing edge cases multiply

At 100 customers, a refund per month is normal. At 1,000 customers, you’ll see disputes, chargebacks, prorations, mid-cycle plan changes, failed-card retry flows, dunning emails. None of this matters until volume forces it. Stripe’s built-in tools handle most of it — if you’ve set them up.

What changes between 100 and 1,000 customers

The cost structure shifts in ways that aren’t linear:

• Stripe fees scale linearly, so 10× customers means roughly 10× the processing line item.
• Hosting and database costs grow sub-linearly — you might pay 3× what you paid at 100 customers, not 10×. Most SaaS workloads are bursty enough that capacity gets re-used efficiently.
• Email costs scale closer to linearly if your transactional volume is per-customer (welcome flows, alerts, receipts).
• Support tooling costs scale by tier, not volume — you’ll likely move to a higher Plain or Help Scout tier, but it’s a step function, not a multiplier.
• Your time scales linearly with support load unless you intervene with self-service, automation, or hiring.

Net-net: gross margin tends to improve from 100 to 1,000 customers because most fixed-tier tooling is already paid for. The bigger risk isn’t cost; it’s execution — whether your funnel and your support model can both scale 10× without you burning out.

What 100 customers is wrong about

This is the section most cost guides skip. At 100 customers, you don’t actually have a sales motion. You have a launch. The customers who arrived in your first cohort responded to whatever signal you put out — a launch tweet, a Product Hunt post, a YC batch, an existing audience, a viral TikTok. Those are not repeatable channels in the same way that an SDR-driven outbound motion or a content-marketing engine is.

The trap: you assume the next 100 customers will arrive the same way. Sometimes they will. Often they won’t. The launch surge fades within 60–90 days, and the second 100 customers usually require building something resembling a real channel — SEO content, paid ads with measured CAC, partnerships, referrals. We laid out the path in our zero-to-$1K MRR playbook.

So the honest framing of 100 customers is: you’ve proven the product works, you’ve proven a launch can move people, and you’ve generated enough revenue to fund the next experiment. What you have not proven is a repeatable, scalable acquisition channel. Treat the next 100 customers as a separate research problem, not a continuation of the first 100.

Bottom line on 100-customer economics

Across all three scenarios, the operational reality at 100 customers is similar:

• Tooling costs land between $150 and $1,000 per month
• Gross margin sits in the 80–90% range before founder time
• Stripe processing is the largest variable cost
• Founder time on support is the largest invisible cost
• The next 100 customers requires different machinery than the first 100

If you’re at 100 customers right now, the questions to ask yourself are about the second 100, not the first 100’s costs. Where do new customers come from this month, next month, three months from now? That’s the planning problem, and the cost-side answer takes care of itself if the acquisition side does.

Related reading

• SaaS cost at $1K MRR — the same math from the revenue side
• SaaS cost at $10K MRR — what changes when you cross five figures
• Zero to $1K MRR playbook — how to actually get to 100 customers
• When to hire your first contractor — the moment support load tips over