A tool, not a quote
What the manual work costs you a year.
Put in what you know about one repetitive task. You get what it costs today and what handing part of it to software would free up. Conservative defaults, every assumption on the page, nothing sent anywhere.
The estimateEstimate, not a quote
- This task costs you, a year
- USD 18,000
- 720 hours, from 15 a week
- Hours handed back, a year
- 432 h
- about 9 hours a week across the team
- Labour value of those hours
- USD 10,800
- Time back for the people, not money off payroll.
Bring these numbers to the call and we’ll tell you whether a build is worth it. If it isn’t, we’ll say so.
How it is worked out
Four lines of arithmetic, and what they leave out.
The arithmetic
- Hours a year = people × hours each per week × 48 working weeks. Not 52: people take leave.
- Cost a year = hours a year × cost per hour.
- Freed = cost a year × the share you chose, capped at 90%.
- Payback = build cost ÷ freed value, in months. Only shown when you give a build cost.
Not counted
- Fewer mistakes, and the time spent fixing them. Real, but not something to put a number on from here.
- Faster turnaround for customers. Worth something; worth what depends on your business.
- Running costs after launch: hosting, API usage, the occasional fix. Small for most builds, never zero.
- The time your team spends on the project while it is being built.
This is an estimate from your own inputs, not a forecast and not a quote. It counts the same hours once: the hours freed are a share of the hours you entered, nothing is added on top. The page keeps nothing and sends nothing.
Next step
Now get the real number. A free call, then a written scope and a fixed price within one business day.
The call is free and takes 30 minutes. You talk to the engineers who would do the work, not a sales team. If we’re not the right fit for the job, we’ll say so.
