How many tools does your startup need?

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.

Tool counts can grow unnoticed as subscriptions are added separately. Start with an inventory of your own accounts and required workflows; this article provides no published survey of startup stacks.

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

The ranges below are editorial prompts for reviewing responsibilities, not measured norms or limits. A team’s needs depend on its product, operational duties and access requirements.

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)

Count the additional tools only when they serve a required role. A pre-launch tool count does not establish fear of missing out or waste.

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.

A company’s tool count depends on its size, business and operational requirements. No sourced company-app survey is published in this article; use your own account inventory.

The signs you have too many

• For two tools serving a similar role, check the owners and the work each actually performs. Separate teams or requirements may justify both; category overlap is not proof of waste.
• 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"

Unused subscriptions and overlapping tools can waste money, but this page does not establish a representative savings percentage. Inventory your actual bill and usage before deciding what can be cut.

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.

Further reading

• The Tool Stack Problem - the thesis behind why the number matters.
• How to Audit Your SaaS Stack in 90 Minutes - the practical audit.
• How to choose a tech stack without wasting weeks - getting to the right number from day one.
• The Stack Calculator - concrete cost math.