Free tools for software-delivery teams
No signup. No tracking. Pure client-side calculators that teach the framework instead of selling you on it. Each one is calibrated against real team data.
Story-point estimator
Maps 5 dimensions of a story (complexity, scope, unknowns, dependencies, testing effort) to a Fibonacci estimate (1, 2, 3, 5, 8, or 13). Or flags it for splitting.
Framework: Teaches the 5-dimension framework: estimating effort directly collapses risk into a fake-precise number; estimating across independent axes produces calibrated results.
Calibrated against ~3,000 stories from Stride beta customers.
Open the estimatorSprint capacity calculator
Takes 6 inputs (team size, sprint length, PTO, meetings, on-call, velocity) and outputs realistic sprint capacity in points, with a breakdown of where time goes.
Framework: Naive capacity (team × days) overestimates by 40-50%. PTO + meetings + on-call rotation are the three biggest gaps; this calculator surfaces each so teams stop systematically over-committing.
Calibrated against ~400 sprint plans from Stride beta customers.
Open the calculatorPR review-time estimator
Estimates code-review wall-clock time + quality risk from a PR's size, files changed, tests, and cross-module scope. Outputs an easy / medium / hard / split tier.
Framework: PR size predicts review quality. Cohen 2006 + Bosu et al. 2017 + GitHub 2023 data converge: review quality drops sharply past 400 LOC, becomes essentially impossible past 800. The calculator quantifies it so teams can self-regulate.
Grounded in published research (Cohen 2006, Bosu 2017, GitHub 2023).
Open the estimatorAI delivery ROI calculator
Takes 4 inputs (team size, hourly cost, hours saved per week, monthly seat fee) and outputs annual savings, cost, ROI multiple, and payback days. Conservative defaults.
Framework: Hours saved × hourly cost minus seat fees. Marketing-leaning, we say so on the page, but every input is yours to control. Defaults reflect mid-market US engineering economics with conservative hours-saved (5/week, the low end of Stride beta telemetry).
Hours-saved range from telemetry across 5,200 stories on Stride beta customers.
Open the calculatorDORA metrics calculator
Enter the four DORA inputs (deploys/month, lead time, MTTR, change failure rate) and get composite Elite / High / Medium / Low tier with per-dimension explanation.
Framework: DORA's honest framing: your composite tier is bounded by your weakest dimension, not the average. Calibrated against Google's 2024 State of DevOps thresholds; each tier comes with a one-sentence explanation citing the underlying threshold.
Thresholds from Google's 2024 State of DevOps report.
Open the calculatorADR generator
Fill in context, decision, alternatives considered, and consequences. Get a Michael-Nygard-style ADR in markdown that you can copy or download.
Framework: The 4-section ADR (context / decision / alternatives / consequences) is the canonical format for capturing architecture decisions. The generator enforces the structure so the rationale survives team changes.
Format from Michael Nygard, 2011. Used by thousands of engineering teams.
Open the generator
Coming next
We're building more free tools (velocity tracker, defect- prediction calculator, AC-quality scorer) all calibrated against real Stride beta-customer data. They'll surface here as they ship.
About these tools
- Are these tools really free?
- Yes, no signup, no tracking, no email capture. Each tool runs entirely client-side; nothing leaves your browser. The tools exist to teach the underlying framework (capacity, estimation, DORA tiers, ADRs) more than to act as a marketing funnel.
- What data are the tools calibrated against?
- Where calibration matters (sprint capacity, story-point estimation, PR review time), the defaults are calibrated against Stride beta-customer telemetry, typically 400-5,000 real artefacts depending on the tool. The DORA calculator uses Google's 2024 State of DevOps thresholds. The ADR generator follows Michael Nygard's 4-section format.
- Can I embed these tools in my own site?
- Not as embeds, but you're welcome to link to them and the canonical URLs will stay stable. We maintain backwards-compatible URLs across all framework changes.
- What's the relationship between the tools and the Stride platform?
- The tools are standalone. They don't require a Stride account and don't connect to the Stride platform. They're the framework distilled to its essence. The Stride platform takes the same framework and applies it continuously against your team's real data (PTO from HRIS, velocity from sprint history, deploys from CI/CD, etc.).
- How often are the tools updated?
- When the underlying framework changes (e.g. DORA thresholds drift year-over-year), we update annually. When the tool surfaces UX issues, we fix as we notice. The tool definitions and calibration constants are version-controlled with comments pointing at the source year for each constant.