01The bar
What counts as a tool.
A product a finance team would recognize. It has org adoption. It is not a feature, not an internal library, not a research project. Paid, free, and open-source tools all count once they're in production.
- Finance-recognizable
- Adopted at the org level
- In production
02The sources
How we know.
Public filings. Vendor disclosures. Interviews the subjects agreed to be cited in. Every claim grounded in the live registry, where every piece links back to the underlying records.
- 19,000+ tools tracked
- 127,000+ deployment case studies
- 12,000+ use cases · 61,000+ persons
03The cuts
How we read it.
Each tool is read against the ones it actually competes with, in the workflows where it ships. When a team has moved off it, we name what they moved to. So the comparison names the tools you are choosing between.
- Read against the tools it competes with
- Closest replacement named when teams switch
- Workflow context, not category labels
04Why different
We read what shipped.
Most analyst desks read what was sold. Airframe sits one layer down, on the cross-company adoption graph, the record of which tools actually reached production, in which teams, with what return.
- Deployment, not slides
- Cross-company adoption graph
- What reached production