Sensitivity analysis sweeps key model inputs across ranges to identify which variable moves the outcome most and where performance cliffs appear. In tokenomics simulation, it reveals the single lever the team should prioritize and surfaces boundary conditions no single-variable view would expose.
The highest-sensitivity input becomes your primary post-launch monitoring target. Frameworks built without this analysis tend to track the wrong variables.
How it works
Sensitivity analysis varies one or more inputs across a defined range while holding the rest fixed, measuring the effect on a key output such as coverage ratio, treasury balance, or fully diluted valuation at the 10th percentile. The result is an elasticity map: for each input, how much does a 10% change move the outcome? High-elasticity inputs are load-bearing assumptions. Low-elasticity inputs are background parameters that need less rigorous calibration.
In tokenomics, the inputs swept usually include user growth rate, archetype mix, per-archetype churn, fee level, emission rate, and starting treasury. The outputs worth tracking are coverage ratio at each percentile, months spent below breakeven, and the 5th-percentile cumulative treasury balance, each recomputed across the full sweep to produce a ranked table of sensitivities.
Why it matters
The two-dimensional sweep is where the real insight lives. Sweeping fee level against user growth together often exposes a region where the model is viable across a wide range of growth rates if fees clear a threshold, and non-viable across all growth rates if fees fall below it. That performance cliff is invisible in any one-dimensional table and would be missed entirely by a single base case.
The consequence is operational. If a 15% change in archetype mix moves the coverage ratio by 40%, then archetype composition is the variable the team must measure continuously after launch and respond to when it drifts from the modeled assumption.
Common mistake
Limiting the sweep to inputs the team controls and ignoring exogenous variables. Market conditions, competitive fee pressure, and adoption rates sit outside the team's control but are frequently the highest-sensitivity inputs in the model. An analysis that reports only on internal levers gives a false sense of robustness while the real risk sits in variables the team cannot adjust.
See Tokenomics Audit for how this applies in practice.
Know the terms but not sure how they apply to your project? That is what an engagement is for. We design, document, and stress-test the whole token economy inside the Tokenomics Data Room.
80+ projects advised. Complete tokenomics in 4 to 6 weeks.