SaaS growth percentile calculator for your sample

Use this tool with the saas market guide. The useful result is a transparent working calculation or statement whose assumptions can be inspected.

Your inputs stay in this browser. Example values are constructed, not market data.

Comparable observations, separated by commas or new lines -5, 8, 12, 18, 22, 25, 30, 40, 55, 70 Value to compare Calculate from this sample

Prepare the inputs

Enter growth percentages from the same period and revenue definition. Keep company size, funding context and customer motion comparable. Negative growth values are permitted.

Keep the source and scope beside the inputs. If you are practicing without real evidence, label the case as illustrative. Do not add private customer or employee identifiers; the calculation does not need them.

Method and interpretation

The percentile is 100 times the count below your value plus half the count equal to it, divided by the sample size. Quartiles use linear interpolation between ordered observations.

The output cannot repair an unrepresentative sample, an unclear offer or inconsistent definitions. Before sharing a conclusion, explain where the inputs came from and what population or customer situation they describe.

Validate the next decision

Use the related worksheet or research guide to record the evidence. Identify the assumption most likely to change the result and test it before making a larger commitment. A useful planning tool makes uncertainty visible instead of replacing it with a precise-looking number.

Related reading

• Global SaaS Market Size
• SaaS Market Growth Rate
• SaaS Industry Growth
• B2B SaaS Market Size
• The B2B SaaS Industry

Browse all calculators and working resources for related tasks.

Apply saas growth percentile calculator for your sample in a working review

Record the source and unit of every input before using the result. Change one assumption at a time to understand which inputs matter most. Keep outputs that describe money, time and percentages distinct, and preserve undefined cases rather than converting them into plausible-looking zeroes.

For this topic, involve the research owner and the person using the estimate for a decision and work from source method, market boundary and assumption table. The relevant unit is a clearly defined population, period and value measure. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

Read the original definition before combining figures. Publication date, collection period and forecast horizon answer different questions. A market estimate can be useful without being directly comparable to another publisher’s number.

Two situations that can change the interpretation

When a forecast is presented as measured growth

A category growth projection can provide context but does not establish the acquisition rate a new entrant will achieve.

Use this check: Check the source’s methodology and identify which periods are observed and which are modeled. Do not convert a third-party forecast into a guaranteed outcome for an individual product.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When competitor count is treated as demand

A crowded category may contain many small tools serving different jobs rather than one homogeneous market.

Use this check: Separate evidence of supply from evidence of customer problems, spending and switching behavior. Few competitors can indicate opportunity or lack of demand; the count alone does not decide.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

A software-revenue estimate and a broader customer-spending estimate may both be credible within their own definitions. Averaging them does not create a better answer. Explain the boundary and choose the measure that matches the decision being made.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.