Your portfolio's engineers are keeping the lights on.
Software companies bought between 2015 and 2022 were priced for growth. Today their engineering budgets go to bug fixes, support and upkeep, the roadmap slips, and the same question comes back every quarter: why does the team cost more and ship less?
Dev Bench gives each company a bench. It watches the app and its users, files each problem as an issue, and drafts the fixes, features and documentation as pull requests. Each company's own team approves what ships.
$12,096,000 a year
spent keeping the lights on across 20 companies with 8 developers each, at $180,000 a year per developer and 42% of their time.
The same five problems, in every company.
- the budget
Maintenance eats the engineering budget.
The team was sized for the growth plan. Now most of its week goes to bug fixes, support tickets and upgrades, and the roadmap that justified the price keeps slipping.
What the bench does: Problems are triaged and filed, and fixes arrive as pull requests, so the team spends its week on the roadmap.
- the customers
Customers leave quietly.
Users hit the same broken page for months and never file a ticket. The first sign is a renewal that doesn’t come back.
What the bench does: It notices when users don’t get what they wanted, and shows who was affected, before the renewal call.
- the people
One engineer knows how the old code works.
The founding developers are gone, the docs never got written, and the person who still understands the billing code is a resignation away.
What the bench does: Documentation is drafted from the code and kept current with what ships, as pull requests (V2).
- the exit
Diligence finds what nobody wrote down.
Open bugs nobody triaged, features with no tests, release notes that stop in 2021. The buyer’s diligence team finds them, and prices them in.
What the bench does: Issues are filed and closed in GitHub, every pull request it opens has tests, and release notes stay current (V2).
- the portfolio
Every company runs its own way.
Twenty companies, twenty stacks, twenty ways of tracking bugs. Operating partners can’t see which ones are slipping until the numbers do.
What the bench does: The same install and the same GitHub issues and pull requests in every company. No new dashboard for any team to adopt.
Start with the company that hurts most.
Install and connect GitHub
A package and one setting in the app, then the GitHub app on its repositories. Nothing to host.
See what the app is hiding
Problems filed in the company's GitHub, with who they hit, including the failures nobody reported.
Fixes arrive as pull requests
The company's team reviews and merges. Their week moves from upkeep back to the roadmap.
The same install, again
Each company keeps its own data, issues and approvals. Nothing is shared between them.
One edition per company.
V1, a support tool and support developer, is $10,000 a month billed annually. V2, a development team, is $20,000 a month billed annually. Each company picks the edition that fits it.
V1 triages every problem and files the issue; V2 also drafts the fixes and features as pull requests. Compare the editions →
Bring us the company that keeps missing its plan.
We're taking the next round of early-access customers. Tell us about the portfolio.
Request early access →