What automating this process is actually worth
Put in what the process costs you today and what you were quoted to fix it. The tool returns hours recovered, what those hours are worth, and the month the build stops being an expense.
Your process
Five numbers, all yours. Nothing is stored and nothing is sent anywhere; the arithmetic runs in your browser.
Count anyone who touches the process, including the manager who checks it.
Ask them rather than estimating. The answer is usually higher than the org chart suggests.
Salary plus employer costs, divided by hours worked. For most Israeli teams that lands well above the headline wage.
Whatever you were quoted. We do not publish prices on this page, so treat the starting figure as a placeholder to replace.
Rarely all of it. Judgement calls, exceptions and the client-facing half usually stay with a person.
What it returns
- Hours recovered per month
- 47
- Value of those hours per month
- ₪5,612
- Build pays for itself in
- 8.9 months
- Net over 12 months
- ₪17,340
Across the whole team, at the share you set.
Only real once the hours get spent on something else.
At the monthly figure above, ignoring ramp-up.
The monthly figure for a year, minus the build.
Want the real number?
A mapping call traces where the hours actually go, across every process rather than the one you had in mind. It usually reorders the list.
What this does and does not count
- A month is 4.33 weeks, so a 6-hour week reads as roughly 26 hours a month.
- Recovered hours and money are shown separately because they are different claims. The hours are arithmetic. The money arrives only if those hours go to work that earns, and stays theoretical if the team simply gets less busy.
- There is no ramp-up. A real build reaches full effect over weeks, so treat the payback month as the earliest honest one.
- There is no running cost. Hosting, model usage and maintenance are real and usually small next to the salary line, but they are not zero.
- Error and rework are left out entirely, which is the largest thing missing. In the processes we see, catching a mistake before it reaches a client is worth more than the hours, and it is the hardest number to source in a first call.
4.33 weeks per month
Why the number that matters is the second one
A calculator that multiplies hours by a rate produces a saving on paper. Whether it reaches the bank depends on what happens to the freed time. A team that redeploys it onto revenue work sees the full figure. A team that quietly absorbs it sees a calmer week and no line in the accounts, which is worth having and is a different thing to promise a CFO.
Where these projects actually pay
The processes that return the most are rarely the ones people complain about. They are the high-frequency, low-drama ones: intake, classification, chasing, reporting. Something done 40 times a week at 15 minutes a go beats the monthly ordeal everybody hates, and it is also the one a system handles with the fewest exceptions.
What to do with the answer
If the payback lands under six months on numbers you can defend, the process is worth scoping properly. Between six and twelve, it usually depends on whether the same build serves a second process. Past twelve, either the share is optimistic or the process is not the right first one, and the fix is to pick a different one rather than to negotiate the price.
Questions
What loaded hourly cost should I use?
Take the gross salary, add employer contributions, pension, and the share of overhead that person carries, then divide by hours actually worked in a year rather than hours paid. For an Israeli ops or admin role that commonly lands between 90 and 160 shekels an hour, and for a professional role considerably higher.
What share of a process can really be automated?
For structured, repetitive work with clear rules, 60 to 80 percent is normal. Where judgement, negotiation or a client relationship is involved, 20 to 40 percent is more honest, and the value shifts from removing the work to preparing it so the person spends their time on the decision rather than the gathering.
Does the calculator include what you charge?
No. The build cost field is your own figure, whether that is our quote or somebody else's. Our pricing depends on the number of processes and the integrations involved, both of which come out of a mapping call rather than a form.
Is my input stored anywhere?
No. The arithmetic runs in your browser, nothing is submitted, and there is no analytics event on the fields. Close the tab and it is gone.
The payback looks too good. What am I missing?
Usually the share. It is the one input with no source behind it, and moving it from 80 to 50 percent changes the answer more than any other field. Try the number you would defend to a sceptical CFO, then read the result again.
What if the process spans several teams?
Run it once per team and add the monthly figures. Cross-team processes tend to return more than the sum, because most of the lost time sits in the handoffs rather than inside any one team, but that part is worth measuring rather than assuming.
Tell us what's slowing your business down.
30 minutes. No pitch, no deck. Just listening to your needs and seeing how we can help.
Schedule a discovery call