Calculate · Assess & Decide · Analysis & Finance
Integration adoption rate with a build-next ranking
Per-integration adoption rate over the overlapping base it can actually serve, health-flagged, plus a build-next ranking by addressable market.
You receive: A reviewed adoption-rate calculator + the passing test report, run on your integrations.
Part of Grow Partnerships
Example
A sample of what this play produces. Your result is generated for your inputs.
Table
| Name | Adoption rate | Flag |
|---|---|---|
| github | 43.75 | healthy |
| slack | 21.43 | healthy |
| stripe | 12 | at_risk |
| notion | 4.55 | below |
| linear | undefined |
Ranking
| Rank | Name | Addressable market |
|---|---|---|
| 1 | vercel | 12000 |
| 2 | hubspot | 9000 |
| 3 | jira | 9000 |
Inputs
- Existing
Name Numerator Denominator Install base github 14 32 100000000 slack 6 28 750000 stripe 3 25 4000000 notion 1 22 30000000 linear 0 0 15000 - Benchmark
- 0.15
- Flag band
- 0.2
- Prospective
Name Addressable market Overlap base vercel 12000 4000 jira 9000 3000 hubspot 9000 3500 - Tiebreak
- overlap_base
Arithmetic recomputed against the tasks.py compute_integration_adoption reference oracle, 2026-08-13: each rate is active adopters over the overlapping base that could actually use the integration (the partner's install base is context only and never enters a rate). With a 15 percent benchmark and a 0.2 flag band the at-risk floor is 12.0 percent: github 14/32 = 43.75 (healthy), slack 6/28 = 21.43 (healthy), stripe 3/25 = 12.0 sits exactly on the floor (at_risk), notion 1/22 = 4.55 (below), and linear has no overlapping base yet so its rate comes back undefined rather than zero. The build-next ranking orders prospective integrations by addressable market with the overlap_base tie-break: vercel (12000) first, then hubspot before jira (both 9000, hubspot's 3500 overlap beats jira's 3000). The snapshot is STUD's illustrative month-one launch scenario, a cohort of 40 activated buyers in the pre-seed soft launch; adopter counts, overlap bases, install bases, and addressable markets are illustrative.
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the arithmetic of this calculator: each adoption rate is the active adopters divided by the overlapping base that could actually use the integration (never the partner's total install base), reported to two decimals, the healthy/at-risk/below flag is applied against your benchmark and band on that reported rate, an integration with no overlapping base comes back undefined rather than zero, and the build-next ranking orders prospective integrations by addressable market with your chosen tie-break. STUD does NOT verify that your adopter counts, overlap bases, or addressable-market estimates are accurate, or that the benchmark you chose is right for your category. The partner install base you provide is context only and never enters the rate.
Get early access to STUD the day it goes live.