SaaS software categories
A SaaS company's tool stack has the same few layers: billing, messaging, analytics, support and customer success. Each layer is priced in its own unit, so the cheapest tool at ten customers is often not the cheapest at a thousand. This page says what decides the choice in each category and points to the comparisons that work the numbers.
By Julian Pryor · Updated 7 Oct 2026
Billing & Subscription
Decide first whether you are the seller of record. Stripe leaves you as the seller on its standard rate; Paddle and Lemon Squeezy act as merchant of record; Stripe also sells a merchant-of-record option of its own.
How it is priced. Charged per payment: a percentage plus a fixed amount, with add-ons for billing logic, tax and international cards. Chargebee and Recurly add subscription operations on top of a payment gateway and price by revenue or plan.
Read first: Stripe vs Paddle · Chargebee vs Recurly · Stripe alternatives
Email Marketing
Split the job in two before you shop: product and billing email (receipts, trial reminders, failed-payment notices) and marketing email (newsletters, campaigns, nurture). Some tools do both; many do one well.
How it is priced. Marketing platforms usually price by contacts or profiles, with sends bundled in. Transactional services price by emails sent. Lifecycle tools for SaaS mix the two, so compare at your own contact count and monthly volume.
Read first: Loops vs Resend · Customer.io vs HubSpot · Resend vs SendGrid
Customer Analytics
The question is whether you need to answer 'what did people do' (event analytics) or 'who are they and where does the data go' (a customer data platform). Many teams need both, in that order.
How it is priced. Priced per event, per monthly tracked user, or per monthly active user, depending on the vendor. The same traffic can cost very different amounts under different units, which is why the comparison pages work the arithmetic at set volumes.
Read first: Mixpanel vs Amplitude · PostHog vs Amplitude · Segment vs RudderStack
Product Analytics
In-app guidance and adoption tools sit next to analytics: they show a checklist or tour to the right user at the right moment. The choice usually turns on whether non-engineers must build the experiences.
How it is priced. Mostly sized by monthly active users, with caps on the number of live experiences per plan. Several vendors sell by quote at the top end.
Read first: Pendo vs Appcues · Hotjar vs FullStory · User onboarding tools
Help Desk
Support tools differ in how much they assume a human agent at the end of every conversation. Ticket-first systems suit teams with an inbox and SLAs; messaging-first systems suit a chat widget and automation.
How it is priced. Per agent seat in most cases, with some vendors adding a usage charge for AI outcomes (Intercom lists $0.99 per Fin outcome). Seat count, not customer count, drives the bill.
Read first: Zendesk vs Intercom · Freshdesk vs Zendesk · Zendesk alternatives
Customer Success
These platforms pull usage, billing and support signals into an account health view. They pay off when a team of customer-success managers owns a book of accounts; a small team may do better with a spreadsheet and billing alerts.
How it is priced. Sold by quote: Gainsight's pricing page says 'Request Pricing' for both packages and sizes them by included users and customers per user, and Totango's says 'Request a demo'. Pages here say so rather than guess a price.
Read first: Gainsight vs Totango · Intercom vs Customer.io · Reducing churn with tools
Marketing Automation
Marketing suites bundle a CRM, forms, email and scoring. They make sense when sales and marketing share one record; they are heavy if all you need is a drip sequence.
How it is priced. Tiered by contact count, with the automation features locked to the higher tiers. HubSpot, for one, limits how many actions an automation can hold on its lower tiers.
Read first: ActiveCampaign vs HubSpot · HubSpot vs Marketo · HubSpot alternatives
User Onboarding
Tools that guide new users through the product: tours, checklists, tooltips and resource centres. They overlap with product analytics, so check which of the two your team will actually maintain.
How it is priced. Sized by monthly active or tracked users, with a ceiling on live experiences. Plans differ most in who can edit the experiences and how much custom styling is allowed.
Read first: User onboarding category · Pendo vs Appcues · User onboarding tools guide
How to choose where to start
Start with the layer that touches revenue. If money moves through the product, the billing platform decides what events you can react to: a successful payment, a failed invoice, a plan change, a cancellation. Every other layer consumes those events. A messaging tool that cannot receive them, or an analytics tool that cannot tie them to a user, leaves you doing the join by hand.
Then work outward by pain, not by completeness. A team losing trials needs messaging and in-app guidance before it needs a customer-success platform. A team with a rising ticket queue needs a help desk before it needs a better analytics dashboard. Buying one tool per category in the first year is rarely right; most small teams run billing, one email tool, one analytics tool and a shared inbox.
Check the pricing unit before the price
Billing tools take a share of each payment. Email tools charge by contacts, profiles or messages sent. Analytics tools charge by events or tracked users. Support tools charge by agent seat. Customer-success platforms quote by account count. When you compare two tools in one category, convert both to your own numbers: your payment size, your contact count, your monthly events, your agents. The comparison pages do this arithmetic at several volumes and show the sum, so you can replace our volume with yours.
Wire the layers together on purpose
Write down the events that must cross each boundary before you choose a vendor. A failed payment in the billing system should reach the messaging tool as a webhook or an integration, a plan change should reach the support tool so agents see the customer's tier, and product usage should reach the customer-success view. If a vendor's documentation does not describe the event or the integration you need, treat that as a cost of building it yourself.
Vendor pages decide these questions, not this site, so each comparison links the documentation it relied on. For the editor and method behind the prices, see About and How we evaluate.
Complete stacks by company stage
If you want a starting shortlist for a company type instead of a category, the guides for startups, bootstrapped teams, B2B SaaS and enterprise buyers each pick a stack and say why. The comparison index lists every head-to-head page.