Business case software holds a business case as a structured record connected to delivery work. This article lists four features to look for and says when a template or spreadsheet is enough.
Business case software holds a business case as a structured record and keeps that record connected to delivery. The record is data. Financial targets, assumptions, approved changes, and realised benefits sit in one system beside the work, so anyone can check the case against delivery at any point in the program.
The definition matters because most products sold as business case tools are templates with a logo on them. A template solves the writing problem. Business cases fail in the years after approval, when the plan has moved twice, the original sponsor has changed role, and the assumptions have aged, and a template offers nothing there.
Most business cases are written to release funding and then filed. The document does its work at the investment committee. The money is released, delivery starts in a different system, and from that day the plan moves, scope shifts, and assumptions expire without anyone recording it, so none of that ever reaches the case.
Two years later, someone asks whether the investment delivered what it promised. Take a case approved at $2.4 million NPV, resting on assumptions that nobody tracked, where delivery reported against milestones that stopped mapping to the case around month three. Reconciling the two now takes archaeology. Archaeology is expensive, so it rarely happens. Benefits realisation ends at that point, because the case and the delivery have not shared a room since approval.
Business case software keeps the case's commitments visible while delivery runs. Those commitments are NPV, IRR, the payback period, the assumptions behind them, the changes approved along the way, and eventually the benefits realised. Held as data and kept current for as long as the investment runs, all of them can be checked at every gate, by every sponsor, without a search through old folders.
The first test asks whether the case is data or a file, and the answer shows in one place. If the NPV is a number in a field, the system can track it, compare it, and report on it. If the NPV is a number on slide 14, the system can store slide 14. Many products sold as business case management are document repositories with workflow attached. They keep the file safe. Keeping the case current is a different job, and the workflow does not do it, because the numbers inside the file stay as typed until a person changes them.
Cases change. Scope gets cut. Costs shift. One assumption fails and takes a benefit with it. Good tools show the approved case and the current position together, with each approved change recorded between them, including who raised it, who approved it, and what it did to the plan. Without that record, “the business case” means whichever version the most senior person in the room remembers, and every later discussion of variance starts with an argument about which version counts.
A case system that cannot see delivery brings back the reconciliation problem it was bought to remove. If the work runs in Jira and the case lives in a standalone platform, someone has to carry status between the two by hand. That stops in the first busy month. The closer the case sits to the delivery data, the less the whole arrangement depends on one person remembering to reconcile the two on a Friday afternoon, and the sooner a drifting assumption becomes visible to the people who approved it.
The trail shows who approved the case and each change, when, and on what basis. Boards and auditors question funded programs later, and the answer is either written down or reconstructed from memory and office politics. A board can ask for the record at any time. An audit trail costs little to keep. Nobody can backfill one.
A single project with one funding decision and no ongoing governance does not need business case software, and paying for it would add cost without adding control. A template, a spreadsheet for the financials, and a well-run approval meeting will do the job, and the money saved is real. If the task in front of you is the writing, our guide to how to write a business case covers the structure and the financials.
Sometimes document management is the requirement. The organisation wants cases stored, versioned, and findable, and nobody plans to track them after approval. SharePoint already does that. Buying a case management platform to use as a document library is a common and expensive way to reach the same result.
Repetition is the signal that you have outgrown both. Multiple concurrent cases, a governance cadence that reviews them, and benefits with an accountable owner all point to the same need. At that stage the question is whether anyone can state the current position of each investment on a given day, and answering it across a dozen investments calls for software.
Tollgate is a Forge app that runs inside Jira Cloud. The business case is a structured record in it. The financial case computes NPV, IRR, and payback, both discounted and undiscounted, from the cashflows you enter. The financial case is held separately from work-package budgets and change requests, in both directions, so a change to a work package does not alter the financial figures and the financial figures do not alter a work package.
Work packages link to Jira epics, which puts the case next to the delivery data. Nobody has to feed a second system. Risks & Opportunities, Decisions, and Changes each keep an audit trail beside the financials. The approved baseline stays fixed, and changes go through change control. Investment Health shows how each investment is tracking. In Benefits Realisation the sponsor records realised benefits next to the expected ones and judges whether the case delivered.
Tollgate runs on Atlassian infrastructure. No Softwired server sits in the path. The delivery data lives in your Jira projects and stays there whatever you decide about Tollgate later. Tollgate is free for up to 10 users under standard Atlassian Marketplace terms. Beyond 10 users, pricing is per user through the Marketplace.
If your delivery already runs in Jira, install Tollgate from the Atlassian Marketplace and put your next business case in it.
Tollgate keeps the business case, the gate decisions and the payoff in one record, next to the delivery they pay for.