Free Tools
Make the decision with numbers
Six free calculators. No sign-up, no email; the maths runs in your browser.
These tools do not promise you a savings rate. Each one either performs open arithmetic on the numbers you enter or maps your scope to KodDelta’s published budget bands. Every formula, multiplier and points table is written out on the tool’s own page, and fields that require a judgement call are labelled “your estimate” right where you type them.
Prices the annual labour and rework burden of a process running on spreadsheets and email, plus a rough payback on a pilot budget.
- Input
- People, weekly hours, hourly cost, error count
- Output
- Annual hours and cost + payback months
Compares accumulated subscription plus workaround labour against a one-off build fee and optional maintenance.
- Input
- Users, monthly subscription, workaround hours, build fee
- Output
- Both column totals + break-even year
Adds up the scope weight of the modules you select and names which of three published budget bands your scope falls into.
- Input
- Selection from 13 modules
- Output
- Published band + delivery window
Turns source readability, data quality and structural size into a rough engineer-day range with a phase breakdown.
- Input
- Records, entities, fields, source type, quality
- Output
- Day range + phase split
Prices the annual cost of internal information search and estimates how fast a RAG assistant covers its setup cost.
- Input
- Questions per month, lookup time, coverage share
- Output
- Hours recovered + net value + payback months
Scores system count, data direction, frequency and access method, then maps the total to a published band.
- Input
- Systems, direction, frequency, API status, fields
- Output
- Score + risk level + band
Why we publish calculators
The hardest part of an enterprise software decision is not the price — it is the absence of a common basis for comparison. You are holding a quote for an off-the-shelf package and a quote for a custom build; they measure different things, contain different line items and cannot be placed side by side. The same applies to timelines: the answer to “how long will it take” depends entirely on how the scope was defined.
These tools exist to build that basis. None of them produces a magic result; what they do is gather the items that drive the decision onto one screen and make the arithmetic visible. You could run the same calculation on paper — the tools only make it faster and stop you from omitting a line.
What we do not do
- We do not invent savings rates. A sentence like “automation cuts costs by 40%” is advertising copy unless that figure has been measured in your company. No such coefficient exists in these tools.
- We do not present industry averages. Default values exist only so the form is not empty and are meant to be replaced; none of them is offered as a research finding.
- We do not collect your numbers. The calculations run in your browser. What you type is never sent to a server, never stored and never shared.
- We do not tilt the outcome. The TCO tool will show setups where off-the-shelf wins; the budget tool will recommend shrinking your scope. Our job is not to sell you something but to get the right build at the right price.
What order to use them in
- Put a number on the problem. Run the manual work cost calculator on the single process that consumes the most hours. If the result is far below your pilot budget, that process is not the one to start with.
- Compare the alternatives. If you are holding a quote for an off-the-shelf package, go to the 5-year TCO comparison. Double the user count and look again; that is where the real difference shows.
- Fix the scope. In the budget and timeline estimator, tick only the modules you genuinely need in the first release.
- Measure the risks separately. If data is coming from an old system, use the data migration estimator; if another program has to be connected, use the integration complexity score. Those two are usually what stretch a delivery date.
- Assess the AI side on its own. If your document search burden is large, the assistant payback calculator supports a separate decision — usually a smaller investment, independent of the main system.
What happens afterwards
You do not have to bring the number to us; the tools are useful on their own. If you do want to talk, the sequence is straightforward: in a 30-minute discovery call you describe the process, and we tell you which module should come first and which published band your scope falls into. Once the scope is written down, a fixed-price proposal follows. Every package includes a perpetual licence, unlimited users and source-code handover; the details are on the pricing page.
To read the same subjects in prose, our guides, the off-the-shelf versus custom comparison and the process automation page cover the same ground in narrative form.
Frequently Asked Questions
Are these tools free, and do they require sign-up?
All of them are free and none of them ask for a name, an email address or a phone number. The calculation runs entirely in your browser; the numbers you type are never sent to a server and never stored.
Do the tools give me a quote?
No. Each tool either performs arithmetic on the numbers you enter or maps your scope to one of KodDelta’s published budget bands. An exact figure is only given after process discovery, once the scope has been written down.
Are there hidden assumptions inside them?
Every formula, multiplier and points table used is written out in full on the tool’s own page. We do not set defaults for rates we have not measured; fields that require a judgement call — the automatable share, the coverage share — are labelled “your estimate” right on the field.
Which tool should I start with?
If you have not yet put a number on the problem, start with the manual work cost calculator. If you are holding a quote for an off-the-shelf package, the 5-year TCO comparison is the right entry point. If your scope is already clear, go straight to the budget and timeline estimator.
You have the number; now let us fix the scope
Thirty minutes settles which module should come first.