Annual PR volume
—
Engineers × PRs/week × 52
What does your team actually spend reviewing pull requests for security?
Most engineering organisations don't have a line item for "PR security review". The hours go into senior engineers' calendars, escalations to a security team, back-and-forth on regulated-data changes — and never roll up. Move the sliders to see your number.
Annualised cost
52-week run rate · before any Osynax discountAnnual saving
£—
Payback period
— weeks
Engineer-weeks reclaimed
—
How the number is built
Annualised from your weekly inputs above. Every cell updates live.
Hours / yr · standard review
—
Volume × review minutes
Hours / yr · escalations
—
Volume × escalation rate × extra mins
Total annual hours
—
The number nobody reports on.
Cost · standard review
£—
Standard hours × engineer rate
Cost · escalations
£—
Escalation hours × senior rate
Cost per PR (effective)
£—
Total review cost ÷ PR volume
Equivalent headcount
—
Total hours ÷ 1,750 working hours / yr
In plain English
—
Talk to us about a pilot
3-month pilot · £30k + VAT · credit-back on annual conversion
Methodology · assumptions you can change
- Working year: 46 weeks of PR-shipping activity (52 weeks minus holiday, training, on-call rotation).
- Standard review time is reviewer minutes only — author rework time is excluded so we don't double-count.
- Escalations layer on top of the standard review; they don't replace it.
- Engineer-weeks reclaimed assumes a 35-hour working week.
- Osynax annual contract is modelled at £90k as a published mid-market estimate. Pilot engagements run at £30k for 3 months with credit-back against the annual on conversion. Real pricing depends on repo count, frameworks in scope, and seat count.
- Every figure rounds to the nearest hundred pounds for display. Internal calculation is to the penny.