Which invoice would actually go away?
Pull the last three invoices for your tools and check their renewal dates. For each line, record who owns the process, how many people use it and which feature still requires a paid account. A service business might use a separate reporting tool even though every field in the report already lives in its job system. Reporting is a plausible replacement project. Email and accounting can stay where they are.
Read the minimum seat commitment. If eight people stop using a product today but the contract requires twenty seats through December, the first saving comes when the company can change plans. Compare the build with the best option already available, including cancelling dormant seats or downgrading a tier.
What does it take to recover PLN 52,000 over 36 months?
Consider an illustrative Polish service business. After migration it can retire three monthly fees for job tracking, reporting and keeping the two in sync. The charges are PLN 1,800, PLN 1,200 and PLN 600. Unaffected tools cost the same in both scenarios. The figures exclude VAT and assume flat prices with no discounting.
- Current subscriptions total PLN 3,600 a month, or PLN 129,600 over 36 months.
- One-off investment totals PLN 52,000. The example allocates PLN 40,000 to development, PLN 8,000 to migration and PLN 4,000 to training and the overlap period.
- Running costs are PLN 1,000 a month for hosting, backups, updates and support. Spending on the new option comes to PLN 52,000 + 36 × PLN 1,000 = PLN 88,000.
- The three-year cash difference is PLN 41,600. Once the legacy fees stop, the company retains PLN 2,600 each month. Dividing PLN 52,000 by PLN 2,600 gives 20 months to payback from cancellation.
One overlooked licence can change the decision. Suppose the company can actually cancel only PLN 2,200 a month. After running costs it retains PLN 1,200. It recovers the investment in month 44, leaving a shortfall of PLN 8,800 at the three-year mark. Under those conditions a smaller integration deserves a closer look.
Where do recovered hours belong?
Give them their own column. Recovering 16 hours a month at a labour cost of PLN 85 per hour frees capacity worth PLN 1,360. It becomes a cash saving when a real expense disappears, such as paid overtime. If the team uses the time to take extra orders, measure the additional margin on completed work. Each recovered hour should enter the business case once.

How can KTB take a company from the numbers to cancellation?
We start by following one real, anonymised job. Who enters the information? Who can correct it? What file or report must come out at the end? With that in hand we can compare reconfiguring the current tool, connecting two systems or building the missing module. A first release needs to cover the entire chosen task, including exceptions that would otherwise stop the team doing its work.
Before giving notice, export the agreed data and restore a backup in a test environment. During a parallel run, have a team member check the final document, its total and the revision history against the old system. After acceptance, schedule cancellation against the contractual notice period. Give the process owner a support contact and a working data export for any future handover.
For an initial conversation, bring one anonymised report, the relevant invoice amounts and the notice deadlines. That gives us a specific budget line to test the project against. Discuss a custom application with KTB

