Product teams are running some of the most bloated SaaS stacks in the company — and nobody's watching. Between roadmapping tools, design platforms, product analytics, user research software, and project tracking systems, a 30-person PM team routinely carries $120K–$280K in annual SaaS spend. A significant chunk of that is redundant.
The pattern: product managers buy tools to solve immediate pain. Three years later, the team has Jira and Linear for project tracking, Figma and Sketch and InVision for design, Productboard and Aha! for roadmapping, Amplitude and Mixpanel for analytics, and UserTesting and Dovetail for research. Each tool was bought by someone with real intent. Most of them do 70% the same things.
This guide breaks down the true cost of the PM stack, where the overlaps hide, and how a real 30-person product team cut $52K/year without losing any capability that mattered.
Based on 30-person Product team (PMs + Designers + Researchers) at a 200–500 employee B2B SaaS company
| Category | Common Tools | Typical Spend (30-person team) | % of Budget |
|---|---|---|---|
| Roadmapping / Product Strategy | Productboard, Aha!, Roadmunk, Craft.io, ProdPad | $18K–$50K | 15–18% |
| Design / Prototyping | Figma, Sketch, InVision, Zeplin, Marvel | $20K–$60K | 17–21% |
| Product Analytics | Amplitude, Mixpanel, Heap, FullStory, Contentsquare | $25K–$65K | 21–23% |
| User Research | UserTesting, Dovetail, Lookback, Maze, Hotjar, Sprig | $15K–$40K | 13–14% |
| Project / Sprint Tracking | Jira, Linear, Notion, Asana, Monday.com | $12K–$35K | 10–13% |
| Customer Feedback / NPS | Pendo, Delighted, Canny, Productboard Feedback | $8K–$25K | 7–9% |
| Documentation / Wiki | Notion, Confluence, Slite | $5K–$15K | 4–5% |
PM teams have particularly high redundancy because every discipline (PM, Design, Engineering, Research) buys their own tools, and nobody reconciles overlaps at the team level. Figma handles prototyping and design handoff — yet Zeplin and InVision are still active. Productboard captures feedback and builds roadmaps — yet Aha! runs in parallel for leadership presentations.
The most common PM stack waste: two roadmapping tools running in parallel. One was bought by the CPO for executive presentations (Aha!). The other was bought by the PM team for day-to-day prioritization (Productboard). Nobody merged them. Both renew automatically.
| Tool | Best For | Pricing (30 PMs) | Feature Strengths |
|---|---|---|---|
| Productboard | Customer feedback → roadmap | $24K–$42K/year | Insight capture, customer feedback synthesis, prioritization frameworks |
| Aha! | Strategy → roadmap → execution | $18K–$38K/year | Goals/initiatives hierarchy, roadmap presentations, capacity planning |
| Linear | Engineering-first project tracking + roadmap | $6K–$18K/year | Fast, developer-loved, excellent sprint management, good roadmap views |
| Notion | Wiki + lightweight roadmapping | $6K–$12K/year | Flexible, team-wide, good for small PM teams not needing dedicated roadmap tools |
Productboard and Aha! are both roadmapping platforms. Both handle: idea capture, prioritization, roadmap views, stakeholder presentations, and integrations with Jira/Linear. The overlap is ~80%. The main functional distinction: Productboard focuses on customer feedback synthesis; Aha! focuses on strategy-to-execution hierarchy. Most teams only need one or the other.
This one is more clear-cut than any other PM category: Figma has won the design tool market. Sketch lost its web/cloud advantage. InVision stopped developing its core product. Zeplin is redundant since Figma added Dev Mode. If you're paying for multiple design tools, you're paying for Figma's competitors to stay on life support.
| Tool | Original Purpose | Annual Cost (30 designers/PMs) | Status in 2026 |
|---|---|---|---|
| Figma | UI design, prototyping, handoff | $15K–$36K | ✅ Keep — clear winner, team actively uses it |
| Sketch | Mac-only UI design | $4K–$10K | ❌ Eliminate — designers already using Figma; Sketch is vestigial |
| InVision | Interactive prototypes, design review | $6K–$18K | ❌ Eliminate — Figma Prototype + Figma Comments replaces this entirely |
| Zeplin | Design-to-dev handoff | $4K–$12K | ❌ Eliminate — Figma Dev Mode (included in Figma Professional) is direct replacement |
| Marvel | Quick prototypes | $2K–$8K | ❌ Eliminate — Figma does this and more |
If your team is on Figma Professional/Organization (which nearly every product team is), you are already paying for features that replace InVision, Zeplin, and Marvel. The savings are immediate: cancel non-Figma tools at their next renewal. No migration required — your designers are already using Figma for everything that matters.
Figma raised prices significantly after the Adobe acquisition deal collapsed. Figma Professional went from $12/seat/month to $15/seat/month (+25%). Figma Organization jumped from $45/seat/month to $55/seat/month (+22%). For a 30-designer team on Organization plan: $16,500/year → $19,800/year.
Figma negotiation levers:
Product analytics is the category where PM stack bloat gets expensive fast. The tools are individually priced on data volume (monthly tracked users), which means costs compound as the product scales. Running two analytics tools on a growing product can easily hit $60K–$100K/year for data you're only analyzing once.
A common rationalization for running two analytics tools: "We need to validate data between platforms." In practice, analytics data is never perfectly consistent between tools due to sampling, attribution windows, and tracking differences. The gap is a feature, not a bug — you're supposed to choose one source of truth, not compare them forever. If you're validating analytics in two platforms, you've deferred the decision to use one platform. Make the decision instead.
| Situation | Recommended Tool | Annual Cost (30-person PM team) |
|---|---|---|
| B2B SaaS, <10M events/month | Amplitude Growth | $22K–$40K |
| Consumer app, high volume | Mixpanel Growth | $18K–$35K |
| Session replay + heatmaps (UX focus) | FullStory or Hotjar (one) | $15K–$30K |
| Early stage / limited budget | PostHog (open-source, self-hosted) | $0–$5K (infrastructure) |
User research tooling has exploded in the last three years, and PM teams often accumulate 3–4 tools that each address a slightly different use case — while overlapping on 50–70% of their core features.
| Tool | Core Use Case | Annual Cost | Overlap |
|---|---|---|---|
| UserTesting | Moderated + unmoderated usability tests | $18K–$40K | Overlaps with Maze for unmoderated tests |
| Dovetail | Research repository + synthesis | $8K–$20K | Unique: repository/synthesis is differentiated |
| Hotjar | Heatmaps + session replay + surveys | $6K–$16K | Overlaps with FullStory; surveys overlap with Delighted |
| Maze | Unmoderated usability testing | $6K–$20K | Overlaps with UserTesting unmoderated |
| Sprig | In-product surveys + microsurveys | $12K–$25K | Overlaps with Hotjar surveys; Pendo surveys |
The research stack principle: You need exactly two research tools — one for qualitative research synthesis (Dovetail or Notion-based repository) and one for usability testing (UserTesting or Maze). Everything else is redundant with existing tools in your stack.
Engineering and product teams have different preferences for project tracking. Engineering prefers Linear (fast, developer-first) or Jira (enterprise, deep customization). PMs prefer Notion (flexible docs + database) or Asana (visual, cross-functional). When neither team wins the argument, both tools get bought and both run in parallel.
Engineering should own one sprint/ticket tracking tool. Product should own one documentation/roadmapping tool. These can be different tools if they integrate (Jira ↔ Notion, Linear ↔ Notion, etc.). What doesn't work: Engineering running both Jira AND Linear simultaneously, or PM running both Productboard AND Notion for roadmaps. The team will always gravitate to one — let them choose and eliminate the other.
Situation: 200-person B2B SaaS company, 30-person product team (15 PMs, 12 designers, 3 researchers). Product VP inherited a stack bought piecemeal over 4 years. Annual PM SaaS spend was $186K — nobody had ever added it up before.
Before Audit (Bloated Stack):
| Tool | Annual Cost | Issue Found |
|---|---|---|
| Productboard (roadmapping) | $28,000 | Only 8 of 15 PMs use it regularly; feedback feature barely used |
| Aha! (roadmapping) | $22,000 | Bought by VP for exec presentations; PMs use Productboard for everything else |
| Figma (design) | $19,200 | Keep — used daily by all designers |
| InVision (prototypes) | $12,000 | Nobody had touched it in 8 months; Figma Prototype replaced it |
| Zeplin (design handoff) | $8,400 | Figma Dev Mode replaced this; Zeplin on auto-renew for 2 years |
| Amplitude (analytics) | $32,000 | Keep — primary analytics platform, well-instrumented |
| Mixpanel (analytics) | $18,000 | Bought before Amplitude; nobody actively uses it; data is stale |
| Hotjar (heatmaps) | $9,600 | FullStory covers heatmaps; Hotjar on auto-renew |
| FullStory (session replay) | $24,000 | Keep — actively used by PM + Design for UX debugging |
| Dovetail (research repo) | $9,600 | Keep — researchers use it for every study |
| UserTesting | $18,000 | 6 tests run in last year; Maze would cover same use cases at 40% cost |
| Jira (engineering tracking) | $15,600 | Engineering uses it but has migrated 70% to Linear |
| Linear (sprint tracking) | $7,200 | Engineering team's preferred tool; growing adoption |
| Notion (docs + specs) | $5,400 | Keep — universal PM docs platform |
| Total | $228,000 |
Consolidation Actions:
After Consolidation (Lean Stack):
| Tool | Annual Cost | Function |
|---|---|---|
| Productboard | $28,000 | Roadmapping + feedback synthesis + exec presentations |
| Figma (Professional) | $19,200 | Design + prototyping + dev handoff |
| Amplitude | $32,000 | Product analytics — single source of truth |
| FullStory | $24,000 | Session replay + heatmaps |
| Dovetail | $9,600 | Research repository + synthesis |
| Maze | $7,200 | Unmoderated usability testing (replaced UserTesting) |
| Linear | $7,200 | Sprint tracking (replaced Jira) |
| Notion | $5,400 | Product documentation + specs |
| Total | $132,600 |
Actually achieved $95K in savings (not the $52K originally projected). Three "keep" decisions became eliminations after deeper usage review.
📊 Free Benchmark Tool
See if your SaaS budget is above or below the industry benchmark — 2,100+ companies benchmarked across 12 industries.
Benchmark my spend →The PricePulse free audit tool scans your PM tools for price increases, over-licensed seats, and tool overlaps. Takes 5 minutes.
Run Free PM Stack Audit →A 30-person product team spending $120K–$280K/year on SaaS typically has $40K–$120K in recoverable overspend. The culprits are always the same: two roadmapping tools, a design tool the team abandoned when Figma improved, two analytics platforms for historical reasons, and a mix of user research tools that overlap significantly.
The fix is systematic, not surgical. One afternoon of usage audits, one quarterly renewal calendar, and clear ownership rules (one roadmapping tool, one analytics tool, one sprint tracker) eliminates the bloat. The savings fund new tools or headcount that actually matter.
The lean PM stack — Figma + one analytics tool + one roadmapping tool + Linear + Notion + one research tool — covers everything a modern product team needs for $75K–$150K/year, often half of what's currently being spent.
Related guides:
Customer Success SaaS Stack Guide 2026 ·
Sales Team SaaS Stack Guide 2026 ·
HR & People Ops SaaS Stack Guide 2026 ·
DevOps & IT Ops SaaS Stack Guide 2026 ·
Free SaaS Cost Audit Tool