The honest answer almost nobody gives straight: less than you think, and a lot less than what you probably use. The gap between what your startup actually needs and what it's subscribed to is where your runway goes.

I've audited dozens of early-stage stacks. The pattern is consistent: founders think they have 10 tools, count more carefully and find 25, and look at the credit-card statement to discover 40. The number keeps going up and nobody notices.

This post gives the actual target by stage, explains the gap between "subscribed to" and "actually using," and shows you how to land at the right number for where you are now.

How to count your tools honestly

Before we talk targets, a definition problem. People count tools three different ways:

  • Subscribed to - you pay for it, or you're on a free tier.
  • Logged in the last 30 days - anyone on the team actually opened it.
  • Load-bearing - if it disappeared tomorrow, something breaks.

When people say "we use X tools," they usually mean Subscribed. The number that actually matters is Load-bearing. A typical 10-person startup might be subscribed to 40, log into 25 in a month, and genuinely load-bear on 12-15.

If a tool isn't load-bearing, you don't use it. You pay for it.

The honest targets by stage

6-10
Pre-launch solo founder
10-15
Early-stage (under 1k users)
15-25
Scaling (1k-10k users)
25-40
Post-PMF (10k+ users, 10+ team)

These are load-bearing tools, not total subscriptions. If your pre-launch solo stack has 25 tools, something is wrong. If your 30-person post-PMF company uses 80, something is wrong.

Pre-launch solo founder: 6-10 tools

At this stage, you're testing the idea, writing the first code or the first copy, and talking to a handful of potential users. You need:

  • Editor (Cursor, VS Code, Framer, or Notion - depending on what you're building)
  • Hosting (Vercel or Netlify)
  • Backend / database (Supabase or similar, if you're coding)
  • Email (Gmail for personal, Beehiiv for newsletter)
  • Payments (Stripe)
  • Docs / notes (Notion or Apple Notes)
  • Design (Figma)
  • Analytics (Plausible or PostHog)

That's 8. If you genuinely need 3-4 more (e.g. dev tooling like GitHub, a Claude subscription, a design asset library), fine - still under 12. Above 12 at pre-launch is almost always FOMO.

Early-stage (under 1k users): 10-15 tools

Once you're in-market with real users, you add a few specific tools:

  • Customer support (Crisp or similar - see our support tools post)
  • Transactional email (Resend)
  • Basic automation (Zapier or Make, only if you need it)
  • Team comms (Slack - only once you have a co-founder or first hire)
  • Project tracking (Linear or Notion tasks)

Now you're at 12-13. If you're over 18, you started adding "nice-to-have" before "must-have" earned its keep.

Scaling (1k-10k users): 15-25 tools

At this stage you're hiring, reporting, and specializing. Additions:

  • CRM (Attio or HubSpot Free)
  • Accounting (Xero or QuickBooks)
  • HR / payroll (Deel, Gusto, etc.)
  • Error tracking (Sentry)
  • Auth (Clerk or Supabase Auth if not native)
  • A few specialist tools based on what you actually sell

You're now at 18-22. Still tight. The next red flag: adding a second CRM, a second project tool, or a third analytics dashboard.

Post-PMF (10k+ users, 10+ team): 25-40 tools

Real scale needs real tooling. But 40 is a ceiling, not a target. Once you pass 40, assume you have bloat unless proven otherwise.

The BetterCloud SaaSOps report showed the average mid-size company runs 130+ SaaS apps. That's not a target; it's a warning. Most of those are duplicates, silos, and shadow IT.

The signs you have too many

  • Same job, two tools. Two CRMs. Two docs platforms. Two analytics. Almost always means two teams bought without talking.
  • Nobody on the team knows what a subscription is for. If someone on your finance team sees a line item and no owner claims it, it's probably dead.
  • Onboarding takes a week just to set up access. Too many logins means too many tools.
  • Integration glue is a job. If you have a "tools person" whose role is keeping Zapier running, your stack is too fragmented.
  • You're paying for Starter plans you haven't used in 90+ days. Common. Easy to fix with a 90-minute audit (framework here).

The gap between "we use" and "we pay for"

BetterCloud's research suggests 44% of SaaS licenses go unused in a typical 30-day period. The cost of tools you don't use is pure waste. Every audit I run reclaims 20-35% of spend by canceling things nobody remembered buying.

The simplest hygiene practice in 2026: quarterly stack audit, 90 minutes, one pass. Count every tool. Kill anything you haven't opened this quarter. See the audit framework.

Over the number for your stage?

Run our 3-minute Stack Grade to see how your count compares to other founders, and get a personalized list of tools to cut.

Grade my stack →

Further reading