Every audit software purchase eventually reaches the same room: a CFO or a controller protecting a budget, sometimes an audit committee with fifteen minutes on a crowded agenda, being asked to approve a five- or six-figure recurring cost for a tool most of them will never personally open. A chief audit executive who walks in with a features list usually loses that conversation. One who walks in with a cost line built from real public numbers, a benefit case that says plainly what it can and cannot prove, and a straight answer to “what if we just kept using Excel” tends to walk out with a budget. Gartner’s press release of 16 September 2026 puts audit management software adoption at 84 percent of the 259 audit functions it surveyed, which means the person across the table has probably approved one before, for this organization or a prior one. That does not make the ask automatic. It makes the bar for a credible case higher, not lower, because a CFO who has seen one of these requests before also knows what a padded one looks like.
This guide builds that case end to end: the questions a CFO and an audit committee actually ask before a technology purchase, the cost side with public evidence behind every figure, the benefit side stated honestly rather than inflated, the “do nothing” and “Excel plus an analytics tool” alternatives every credible case has to address, a one-page template to fill in directly, and a worked five-year model for Lakeshore Bancorp, the $9 billion regional bank used across this site, built only from public price evidence with every assumption labeled. It follows the same evidence-based method used throughout the independent buyer’s guide to internal audit software, and it assumes the field is already narrowed to a shortlist; the RFP method and the pricing guide cover getting to a quote in the first place.
What this guide is for. Building the internal business case for an audit or SOX platform: the questions a CFO and audit committee ask, a cost model built from public price evidence, a benefit case with honest ranges, the alternatives a credible case has to address, a one-page template, and a worked five-year model for a fictional $9 billion bank.
Evidence. Research-based: vendor documentation and release notes, public procurement records, third-party pricing data, verified user reviews on Gartner Peer Insights and G2, and analyst coverage. We have not used any of these products hands-on for this guide. The worked model uses only public price evidence, with every assumption stated plainly rather than estimated.
Last verified. 27 September 2026.
In this guide
- What CFOs and audit committees actually ask
- The cost side: what a platform actually costs over five years
- The benefit side: what you can honestly claim
- The alternatives you have to address: doing nothing, and Excel plus analytics
- Building your own model: assumptions, ranges and how to defend them
- Timing the ask: the audit plan and the budget cycle
- A one-page business case template
- Presenting it: the committee packet, and what happens if you are turned down
- Worked example: Lakeshore Bancorp’s five-year business case
- Questions about building the business case
- Sources and verification
- Related guides
What CFOs and audit committees actually ask
Strip away the specifics of any one vendor and the questions repeat across nearly every budget conversation reflected in public board materials, procurement records and practitioner accounts. They rarely start with features.
- Why now, and what is actually broken? A CFO wants the trigger, not the wish list: a missed control, a spreadsheet that failed during an examination, a QAIP finding, an audit plan that headcount cannot keep pace with. “It would be nicer” does not clear this bar; “here is what happened last quarter, and here is why it happens again without this” does.
- What does this actually cost, all in? Not the license quote. The license, the implementation fee, training, admin time, and what happens at renewal. A case that shows only the subscription price gets challenged on the number the vendor left off the slide, and the challenge sticks.
- What do we get for it, and how will we know? A committee wants a short list of claims stated with the right amount of confidence, not a long list that all sound equally certain. The rule worth adopting, covered in full below, is to quantify what can be proven and state plainly what cannot.
- What happens if we do nothing, or do the cheap version instead? A credible case addresses the alternative directly rather than assuming the platform is the only option; see the alternatives section below.
- Who else has done this, and did it work? Gartner’s 16 September 2026 release puts audit management software adoption at 84 percent of the 259 functions it surveyed, useful as a peer signal. The same release adds a caution worth repeating to a committee directly: in Gartner’s own words, “it’s not a question of whether audit teams need” the software, but whether they capture the value they expected from buying it. Cite the adoption figure to show this is a normal purchase category; do not cite it as proof the specific tool will work here.
- Is this vendor going to exist in five years? Ownership changes are common in this market: Hg bought AuditBoard, since renamed Optro, in 2024; Cinven bought Archer in 2023; Wolters Kluwer folded StandardFusion into TeamMate in January 2026. A short vendor-viability note, covering ownership and how long the product has existed under its current name, answers this before it is asked; the due diligence guide covers vendor stability in full.
Audit committees, when they see a technology request at all rather than delegating it to management, tend to ask a narrower version of the same questions through a governance lens: does this strengthen the third line’s independence and its evidence trail, and does the spend fit inside what the committee already approved for the function. How to raise that inside a normal quarterly reporting cycle, rather than as a special appeal, is covered in the presenting section below.
The cost side: what a platform actually costs over five years
Every figure in this section comes from a public source: Vendr’s aggregated buyer data, a state or local government procurement record, a UK government rate card, or a vendor’s own published price. None of it is a quote for any specific organization, and none of it is this guide’s own estimate; where no public figure exists for a cost that matters, the table says so instead of inventing one.
The table below spans four kinds of public evidence, from a mid-market Vendr median to a large public-sector bid, to show how far license cost actually moves with scale and geography.
| Evidence type | Vendor | Annual figure | What it covers |
|---|---|---|---|
| Vendr median (Feb 2026) | Onspring | $33,808 a year, range $9,972 to $55,810 | No-code platform; dedicated internal audit product |
| Vendr median (Feb 2026) | Optro (formerly AuditBoard) | $45,947 a year, range $21,220 to $111,208, 86 purchases | Audit-native SaaS; internal audit and SOX modules |
| Vendr median (Feb 2026) | LogicGate Risk Cloud | $53,784 a year, range $12,294 to $136,130 | No-code GRC platform; internal audit app |
| Vendr median (Feb 2026) | Workiva | $49,420 a year, range $12,736 to $153,365, 164 purchases | Whole platform, unlimited seats; audit is one solution |
| Public bid (Nov 2023, not a confirmed award) | Optro (formerly AuditBoard) | $164,000 a year, 25 core users | Bid to the West Virginia DOT; unlimited stakeholder seats, 1,500 audits a year |
| AWS Marketplace listing | IBM OpenPages | $7,740 to $8,400 a year before add-ons | Real 12-month base SaaS contracts for the Internal Audit Management module |
| UK G-Cloud 14 (14 Oct 2025) | Ideagen Internal Audit | £6,375 a year per instance (new edition) to £13,870 (legacy Pentana Audit MK edition) | Both headline, before named-user licensing, support and services |
Three patterns are worth noting before the total gets built. First, the four Vendr medians cluster in a fairly narrow $34,000 to $54,000 a year band despite covering four different products, which suggests that band is a reasonable planning range for a mid-size function evaluating any of them. Second, the West Virginia bid shows what happens once headcount climbs into the dozens: at 25 core users, the same vendor’s own figure runs more than three times its Vendr median. Third, IBM and Ideagen are unusual in this category for publishing anything at all; most vendors in the internal audit and SOX space gate every number behind a quote, which is itself a fact worth stating in a business case rather than apologizing for.
The license line is rarely the whole number. The table below covers the components that show up after the subscription quote, again using public evidence where it exists and saying plainly where it does not.
| Component | Public evidence | What to budget |
|---|---|---|
| Implementation | $15,630 (TeamMate, City of Norman, OK, 2 users, after a $6,000 discount) to $50,000 (Optro, West Virginia DOT bid, 25 users); Workiva’s Audit Management onboarding ran $21,000 as a fixed fee per the Kentucky Teachers’ Retirement System’s 2025 statement of work | Ask for a fixed implementation fee at your own core-user count, not a time-and-materials estimate |
| Training | $535.60 a person, TeamMate Analytics’ eLearning add-on, itemized in the same Norman, OK quote | Multiply by however many people need certified training; most vendors fold basic onboarding into implementation and sell deeper courses separately |
| Ad hoc configuration or services | $250 an hour, Optro’s West Virginia DOT bid rate | A contingency line for work beyond the base implementation scope |
| Ongoing support and maintenance | $988,160 over five years, New York State Comptroller’s TeamMate support and maintenance contract (2023) | A state agency’s scale, not a bank’s, but evidence that multi-year support commitments run into seven figures once a deployment is large enough |
| Renewal escalator | 5 to 9 percent a year on uncapped renewals, per a licensing advisory for ServiceNow, a different vendor; the only public escalator commentary found in this category | Negotiate a capped escalator or a multi-year flat rate at signature, not at renewal |
| Admin FTE | No vendor publishes this | Budget a fraction of a senior auditor’s or a system administrator’s time; treat it as a practitioner estimate in the case, not a sourced figure |
The admin FTE line deserves a sentence of its own, since it is the one component in this table with no public figure behind it: no vendor publishes what administering its own system costs a customer. Budget it anyway, and say in the business case that the number is a practitioner estimate rather than a sourced figure, the same honesty standard the rest of this table holds to. The site’s guide to implementing audit management software covers what that time actually goes toward in the first 120 days.
The benefit side: what you can honestly claim
The rule for this section is the one a good CFO applies whether it is stated or not: quantify what can be proven, and state plainly what cannot, rather than forcing a number onto a benefit that has none attached to it in the public record. A business case with one honest “we cannot quantify this precisely, but here is why it matters” line usually reads as more credible than five padded ones, because it signals the rest of the numbers were not padded either.
Two vendor-published case studies in this category do put a number on a specific customer’s result. Both are single-customer claims, not market averages, and the table below treats them that way.
| Benefit | What the evidence actually shows | How to state it honestly |
|---|---|---|
| Auditor time on documentation and testing admin | Alteryx’s own published case study for one customer, Papa Johns, claims 300 to 400 hours a year saved on SOX-related close workflows (published 3 Aug 2026) | A single vendor case, not a market average; ask any vendor for its own methodology before repeating a figure like this |
| Evidence-gathering and testing efficiency | DataSnipper’s 14 Jan 2026 release cites the UK National Audit Office reporting £400,000 in efficiency savings, with routine audit work completed “up to three times faster” | Again a single, vendor-selected customer; an illustration of what evidence-linking tools claim, not a benchmark for a platform purchase |
| Follow-up and issue closure | No vendor publishes a market-wide closure-rate figure | State the mechanism honestly: automatic aging and escalation replace email chains, a real change with no percentage attached to it |
| Coverage of the audit universe | No public figure | The honest claim is that a platform makes the gap between the risk-based plan and what actually got covered visible, not that coverage itself increases by a stated amount |
| Audit committee reporting time | No public figure | A consolidated reporting layer replaces slides rebuilt by hand each quarter; state this as a process change, not a number of hours, unless your own function tracks the before and after |
| Evidence retention and audit trail for examiners | No public figure | Often the actual trigger behind “why now” rather than a benefit to project forward; state what was specifically missing last time, not a hypothetical future finding |
None of this makes the benefit case weak. It means the strongest version of it is built from mechanism and honest attribution, not from a percentage nobody can trace back to a source, and a CFO who has read a few vendor ROI calculators will notice the difference immediately.
The alternatives you have to address: doing nothing, and Excel plus analytics
A business case that does not name its alternatives invites the committee to name one for it, usually the cheapest one. Two come up in nearly every conversation reflected in public materials and practitioner accounts: keeping the status quo, and pairing spreadsheets with a standalone analytics tool instead of a full platform. The site’s audit software versus Excel guide covers this decision in full; this section covers what belongs in the business case specifically.
Doing nothing is rarely free, even when no line item says so. The clearest public illustration of that is not from this category’s leading vendors but from a small, easy-to-miss procurement record: a UK public body paid £30,322 to maintain just 10 legacy TeamMate AM licenses over three years, a system already superseded by a newer product, only to keep an old deployment running. Spreadsheet-based audit functions carry an equivalent cost that rarely appears on any invoice: staff hours spent formatting and version-controlling workpapers by hand, the risk that comes with end-user-computing tools nobody has inventoried, and the rebuild time every time a committee wants a cross-engagement view. The site’s guide to auditing end-user computing covers the spreadsheet-risk side of that cost in more detail than belongs in a budget request.
The middle option, pairing spreadsheets and email with a standalone analytics tool, is genuinely cheaper than a platform, but it is not free, and a business case should say what it actually costs rather than implying the alternative to spending money is spending none. Alteryx’s own published pricing, for example, starts its entry tier at $250 a person a month, billed annually, and explicitly excludes several features sold in higher tiers. That is real money for a handful of licenses, and it buys data preparation and testing, not workflow, sign-off, issue tracking or committee reporting, which is the actual gap this alternative leaves open.
| Dimension | Doing nothing | Excel plus an analytics tool | A platform |
|---|---|---|---|
| Upfront cost | None on paper; the hidden cost of maintaining what already exists | An analytics tool license, commonly a few hundred dollars a person a month at entry tier | License plus implementation, commonly tens of thousands of dollars a year at this guide’s evidenced range |
| What it actually replaces | Nothing | Manual data pulls and testing | Data pulls, testing, workflow, sign-off, issue tracking and reporting together |
| Audit trail | Whatever discipline the team enforces manually | Improves for the testing it covers; workpapers and sign-off stay manual | Built into the workflow, with a version history the vendor maintains |
| What breaks first as the plan grows | Coverage, since headcount cannot scale with the plan | Reporting and issue tracking, since the tool was never built for them | Rarely breaks structurally; cost becomes the constraint instead |
| The honest case for keeping it | Only when volume is genuinely low and stable | When budget is the binding constraint and the workflow and reporting gap is tolerable | When coverage, evidence and committee reporting are the binding constraint instead |
Every row above should appear somewhere in the business case, even the ones that argue against buying anything at all. A committee trusts the sections that argue for spending more when the same document is also willing to say when spending less is the right call; teams of one to five auditors are frequently in that position, and the site’s small-team guide covers real prices at that scale specifically.
Building your own model: assumptions, ranges and how to defend them
The worked example later in this guide uses Optro’s figures more than any other vendor’s, and that deserves a direct explanation rather than a silent pattern: Optro (formerly AuditBoard) is the most heavily evidenced product in this category, with 86 Vendr purchases behind its median and a fully itemized public procurement bid behind its larger-scale figure, not a preference this guide is expressing. Build your own model from whichever vendor’s figures are actually the most complete for your shortlist; the point of this section is the method, not the specific vendor.
Start from a headcount, not a budget. The number of core, named licenses your function actually needs, plus a stated assumption about how many unlimited free seats the vendor offers auditees and control owners, drives the license line more than anything else does. Confirm in writing what counts as a core user versus a free stakeholder seat before you build a single row of the model; the definition varies by vendor and materially changes the total.
Treat every vendor-supplied ROI calculator as a marketing input, not a model output. Ask for the same three things this guide asked for: a not-to-exceed price in writing, the renewal escalator in writing rather than left to the vendor’s discretion at renewal, and a reference customer of comparable size willing to confirm what they actually pay. The pricing guide has the negotiation levers for each pricing model in detail, and the demo script has the questions that surface a true total before a contract is signed.
Timing the ask: the audit plan and the budget cycle
A business case submitted at the wrong point in the calendar competes with every other unbudgeted request the CFO’s office sees that quarter, and loses more often than the case itself deserves. The annual risk assessment that produces the coming year’s audit plan is the natural point to raise a platform request, since the plan itself is the evidence for why current capacity, tooling included, cannot deliver it. A request framed as “the plan the committee is about to approve requires this” is a fundamentally different conversation from the same request raised in isolation six months later.
Most organizations run an annual budget cycle with a defined submission window, typically several months before the fiscal year it funds; find that window and work backward from it rather than forward from when the business case happens to be finished. A request that misses the window usually waits a full year, not a few months, which is itself worth stating plainly in the “risk of not acting” line of the template below. Where a genuine trigger exists, an examination finding, a control failure, a QAIP gap, most budget processes have an exception path for an unbudgeted, risk-driven request; use it, but only when the trigger is real, since a false urgency claim spends credibility a function may need again.
Once approved, the clock keeps running. Implementation realistically takes the better part of the first year, evidenced by public quotes and case studies throughout this program rather than any single figure this guide will assert; the implementation guide covers the first 120 days and what tends to slip. Build that timeline into the business case itself, since a committee that approves a purchase in March and expects results by the next quarter’s meeting is set up to be disappointed regardless of which vendor was chosen.
A one-page business case template
The template below is deliberately one page. A committee is more likely to read one page closely than skim ten, and every section maps directly to a question covered earlier in this guide.
The one-page audit software business case
The ask. Name the product category, or the specific vendor if the field is already narrowed, the annual license figure, the one-time implementation fee, and the total first-year cost.
The trigger. One or two sentences on what specifically changed: a finding, a near-miss during an examination, a QAIP self-assessment gap, a plan the current process cannot deliver. Not a wish.
The status quo and its real cost. What the function spends today, in hours, rework and risk, to run on spreadsheets or its current tool, stated as honestly as the platform case below it, including where the number is genuinely not known.
The alternatives considered. Doing nothing, and a lighter option such as Excel paired with an analytics tool, each with one sentence on why it was rejected or deferred.
The five-year cost. License, implementation, training, admin time and a stated escalator assumption, in one table, built the way the worked example below builds it.
The benefit case. A short list, each line marked either “quantified” with its source, or “expected but not quantified” with the reasoning. No line gets a number it cannot support.
What we will measure. Two or three metrics the function will actually track after go-live, and when the committee will see the first read on them.
Risk of not acting. What continues to happen, at the current pace, if the request is deferred another year.
The decision needed, and by when. The specific approval requested, the budget cycle it needs to clear, and the date after which the assumptions in this case start to go stale.
Fill in every line, including the ones with an honest “not quantified” in them. A template with every box confidently filled in numbers is one nobody will fully believe; one that draws an honest line between what is proven and what is expected is the one that survives the first hard question in the room.
Presenting it: the committee packet, and what happens if you are turned down
Where the audit committee needs to see the request at all, rather than management approving it directly, the audit committee deck template has the slide structure for folding a technology ask into a normal quarterly reporting cycle: one slide stating the trigger and the ask, one showing the five-year cost table, one stating the benefit case with its honest and quantified lines kept visibly separate, and one naming the decision needed and by when. Resist the urge to add a features comparison slide; a committee is evaluating a spending decision and a risk argument, not shopping for software, and a features slide reads as the CAE outsourcing the judgment the committee is actually there to exercise.
A CAE presenting this kind of request benefits from the same governance grounding covered in the site’s audit committee playbook: know which decision belongs to management and which belongs to the committee before the meeting starts, and frame the ask accordingly rather than asking the committee to approve a decision that was actually management’s to make.
If the request is turned down, the honest options are narrower than they feel in the room. Resubmit at the next budget window with a tighter trigger and the same evidence standard, rather than a louder version of the same case. Run the “Excel plus an analytics tool” alternative for real, for a defined period, and track the hours and gaps it actually produces, since that data becomes the strongest possible input to the next submission. Or accept that the case genuinely was not there yet, which is a legitimate outcome a business case built honestly should be able to produce, not a failure of the process.
Worked example: Lakeshore Bancorp’s five-year business case
Lakeshore Bancorp, the $9 billion regional bank used across this site, carries 212 key controls across 60 branches. This guide assumes, for the purpose of this model only, that Lakeshore’s internal audit function runs 12 auditors, SOX testers and system administrators who need named licenses, plus an unlimited number of free auditee and control-owner seats reaching the branch network, a mid-size function by this guide’s own fit-by-situation categories, and the size assumption drives every dollar figure below.
The trigger, in Lakeshore’s case: a regulatory examination six months earlier found that two of the bank’s key controls had been reassigned during a reorganization without the control register being updated, a gap the audit team caught only because a reviewer happened to notice a mismatched name, not because any system flagged it. That is a genuine “why now,” in the terms set out earlier in this guide, and it is the kind of trigger the site’s guide to control ownership covers directly.
The table below builds Lakeshore’s five-year cost from two real public data points, scaled by assumptions stated plainly rather than a blended figure this guide invented. It is an illustration of the arithmetic, not a quote for any specific bank.
| Line item | Amount | Basis |
|---|---|---|
| What the model assumes | — | 12 core licensed users; unlimited free auditee and stakeholder seats; one platform covering internal audit and SOX, no separate analytics tool priced in this line |
| Year 1 license | $45,947 | Vendr’s February 2026 median across 86 Optro purchases, used as the base-case license figure; a bank licensing well above 12 core users should budget toward Vendr’s $111,208 upper range instead |
| Year 1 implementation | $50,000 | The flat implementation fee in Optro’s own November 2023 bid to the West Virginia DOT, for a similarly structured 25-core-user, unlimited-stakeholder deployment; the only public implementation figure at this scale found |
| Year 1 training | $5,356 | 10 people at $535.60 each, the TeamMate Analytics eLearning fee itemized in the City of Norman, OK quote; the only granular per-person training figure in the public record, for a different vendor’s course, used here for order of magnitude |
| Year 1 total | $101,303 | Sum of the three lines above |
| Years 2 to 5, flat scenario | $45,947 a year | No escalator applied; the license held at the Year 1 figure |
| Years 2 to 5, escalated scenario | 7 percent a year, compounding | The midpoint of the 5 to 9 percent uncapped-renewal range a licensing advisory reports for ServiceNow, a different vendor; the only public escalator commentary found in this category |
| Five-year total, flat | $285,091 | Year 1’s $101,303 plus four further years at $45,947 |
| Five-year total, escalated | $319,585 | Same Year 1 cost, with the license line compounding at 7 percent for years two through five |
The gap between the two five-year totals, $285,091 flat against $319,585 with a 7 percent annual escalator, is $34,494, about 12 percent of the entire five-year cost, and it comes from a single negotiated term rather than from anything about the software itself. That is the highest-leverage line in this whole model: a capped or flat multi-year rate, negotiated at signature, is worth more to Lakeshore’s five-year total than any feature on a platform’s roadmap. West Virginia’s own contract shows this is achievable in this category, since Optro’s bid to that state held its price flat for the full five years rather than escalating it.
On the benefit side, Lakeshore’s business case states one quantified claim and several honest, unquantified ones, following the rule set out earlier in this guide. The quantified claim, attributed plainly to a single vendor’s published case study rather than presented as Lakeshore’s own result, is that a platform of this kind can save meaningful auditor hours on close-adjacent documentation, per Alteryx’s Papa Johns example above. The unquantified claims, stated as mechanism rather than forced into a percentage, are that reorganization-driven control gaps like the one that triggered this request become visible automatically rather than by chance, and that the audit committee’s quarterly reporting stops being rebuilt by hand each cycle. Neither is assigned a dollar figure, because no public source supports one, and Lakeshore’s business case says so directly rather than estimating one to fill the slide.
Questions about building the business case
How much should we actually budget, all in?
This guide’s own worked example lands Year 1 at just over $101,000 once implementation and training are added to the license, and a run rate in the $34,000 to $54,000 Vendr band for every year after. Treat that as one scenario’s arithmetic, not a universal number; build the same table from your own headcount and shortlist before naming a figure to your CFO.
What if we cannot get exact numbers before the meeting?
State the range and its source instead of guessing a point figure. Vendr’s published ranges, shown throughout this guide, exist precisely because real deals vary; a business case that says “$34,000 to $54,000 a year, per Vendr’s February 2026 data across four comparable products” is more credible than one that states a single number with false precision and gets challenged on it.
Should internal audit’s own budget pay for this, or IT’s?
Most of the public procurement records behind this guide show the buying function itself, not IT, as the named party on the contract, which fits the standards’ expectation that the third line control its own tools and evidence. Where IT holds the enterprise vendor relationship or the security review, involve them early as a stakeholder in due diligence, covered in the due diligence guide, without necessarily ceding budget ownership.
What if the CFO tells us to just use Excel and Power BI instead?
Take the instruction seriously rather than treating it as an objection to argue past. Run the comparison honestly, using the alternatives section above and the site’s audit software versus Excel guide, and if the honest answer is that Excel plus an analytics tool genuinely covers the function’s needs at its current size, say so. If it does not, the specific gap, evidence retention, workflow, committee reporting, is the strongest part of the case, stated as a gap rather than a list of features Excel lacks.
How long does approval realistically take?
Long enough that the budget-cycle timing covered above matters more than the quality of any single slide. A request that lands inside the normal annual cycle, tied to the risk assessment and the plan it produces, moves in months; one raised outside that cycle, without a genuine trigger, often waits for the next cycle entirely regardless of how well it is built.
What happens if the request is turned down?
See the presenting section above: resubmit with a tighter trigger at the next window, run the cheaper alternative for real and bring back what it actually produced, or accept that the case was not there yet. All three are legitimate outcomes of an honestly built business case, not failures of it.
internalauditguide.com has no commercial relationship with any vendor named on this page. We take no vendor money, run no affiliate links and accept no sponsored placements, and no vendor saw this page before publication. Product and company names are the trademarks of their owners. Corrections: desk@internalauditguide.com.
Sources and verification
- Vendr: AuditBoard (Optro) pricing — median, range and purchase count, February 2026 (accessed 26 September 2026).
- Vendr: Workiva pricing — median, range and purchase count, February 2026 (accessed 26 September 2026).
- Vendr: LogicGate pricing — median and range, February 2026 (accessed 26 September 2026).
- Vendr: Onspring pricing — median and range, February 2026 (accessed 26 September 2026).
- AuditBoard (Optro) bid response to the West Virginia DOT, CRFQ 0803 DOT2400000036 (November 2023) — subscription, unit prices, implementation, services rate and the five-year total (accessed 26 September 2026).
- City of Norman, OK: TeamMate+ quote, 28 February 2025 — subscription, implementation after discount, and the itemized eLearning training fee (accessed 26 September 2026).
- New York State Comptroller: TeamMate sole-source procurement justification — the five-year support and maintenance figure (accessed 26 September 2026).
- UK Contracts Finder: legacy TeamMate AM maintenance notice — the three-year maintenance figure for 10 licenses (accessed 26 September 2026).
- Teachers’ Retirement System of Kentucky: statement of work for Workiva Audit Management onboarding, 19 September 2025 — the fixed onboarding fee (accessed 26 September 2026).
- IBM OpenPages: AWS Marketplace listing — real 12-month base SaaS contract pricing (accessed 26 September 2026).
- UK G-Cloud 14: Ideagen Internal Audit listing — headline per-instance pricing, dated 14 October 2025 (accessed 26 September 2026).
- Redress Compliance: ServiceNow Audit Management licensing advisory — the uncapped-renewal escalator range (accessed 26 September 2026).
- Gartner press release, 16 September 2026 — the adoption figure and the caution on what adoption does and does not prove (accessed 26 September 2026).
- Alteryx: Papa Johns customer story — the hours-saved claim used in the benefit-case example (accessed 27 September 2026).
- DataSnipper: 2025 productivity savings release — the UK National Audit Office case cited in the benefit-case example (accessed 27 September 2026).
Related guides
- Internal audit software: the independent buyer’s guide — every review, comparison and buying guide in one place.
- How we review audit software — the evidence levels, the scorecard and the fit-by-situation method.
- The audit software shortlist finder — eight questions, a shortlist with the reasons from each review.
- The requirements matrix — 156 weighted requirements and vendor scoring in a free Excel workbook.
- Best internal audit software — 25 platforms and tools compared by use case.
- Internal audit software pricing — every vendor’s real numbers and how to negotiate.
- Types of internal audit software — audit management, GRC, SOX, compliance and analytics explained.
- GRC suite vs standalone audit management software — how to make the platform call in 2026.
- Internal audit software vs compliance automation — why Vanta and Drata are a different purchase.
- Evaluating AI in audit software — what is real and what is agent-washing.
- The audit software demo script — 25 scenarios that make vendors show, not tell.
- Audit software due diligence — security, data residency, AI data use and vendor stability.
- Audit software vs Excel and SharePoint — when to switch, and how big you need to be.
- Implementing audit management software — the first 120 days and migrating off Excel.
- 15 mistakes internal audit teams make when buying software — and how to avoid each.
- Selecting an audit management system — the vendor-neutral RFP method.
- Audit software for small internal audit teams — options and real prices for one to five auditors.

Leave a Reply