# AI Opportunity Audit for finance teams and CA firms in India. > AI opportunity audit by a chartered accountant: a fixed-fee two-week sprint that maps finance and CA-firm workflows, scores AI use cases and leaves a 90-day roadmap. Canonical: https://pratikbajoria.com/audit Last updated: 2026-10-26 Productised engagement · 2 weeks An AI opportunity audit, run by a chartered accountant: a fixed-fee, two-week sprint that finds where AI moves your P&L — and where it does not. Mapping, scoring, build/buy/wait calls, and a prioritised 90-day roadmap. No vanity pilots. **Direct answer.** An AI opportunity audit is a structured review of where AI can save time or reduce errors in your workflows, and where it should not be used. Mine is a fixed-fee, two-week sprint that maps workflows, scores use cases, and delivers a prioritised 90-day roadmap — so leaders know where AI moves the P&L before they fund a build. For a CA-firm-specific explanation of the audit, read the [AI Opportunity Audit for CA firms guide](https://pratikbajoria.com/ai-opportunity-audit-for-ca-firms). **2 weeks** Fixed sprint **Fixed-fee** Quote on discovery call **90-day** Prioritised roadmap **CA-led** Ex-Big 4 · 9+ years Fit check 01 ## Who this is *for — and not.* ### For - CFOs, COOs and operators who need a ranked list of AI bets, not a tool tour - Finance and ops leaders under pressure to cut cycle time or error without adding headcount - Founders who have tried “AI pilots” and want a P&L-grounded next step - Teams ready to assign an owner and measure outcomes in 90 days ### Not for - Shopping for a generic chatbot demo or slide deck - Teams unwilling to share real workflows, volumes or constraints - Engagements that need a multi-month strategy study before any decision - Buyers looking for the cheapest tool recommendation without process ownership Deliverables 02 ## What’s *included.* Everything you need to decide where to invest — and where to wait — without inventing a second programme of work. 01 / MAPPING ### Process & workflow mapping Walk through the high-friction processes that actually burn time and margin. Document owners, systems, volumes and control points. 02 / SCORING ### Use-case scoring Score candidates on business impact, implementation effort and risk — so “interesting” does not outrank “measurable”. 03 / DECISIONS ### Build / buy / wait Clear recommendations per use case: build in-house, buy a tool, or wait until data, ownership or process maturity catches up. 04 / ROADMAP ### Prioritised 90-day roadmap A sequenced plan for the first quarter: what ships first, who owns it, what “done” looks like in numbers. How it works A — D ## Diagnose in *two weeks.* The Audit is the Diagnose stage of the wider engagement model — compressed into a fixed sprint so you leave with decisions, not homework. WEEK 1 ### Map Kick-off, stakeholder interviews and workflow walkthroughs. Surfaces where time and margin leak under real constraints. WEEK 1–2 ### Score Candidate use cases scored on impact, effort and risk. Weak ideas are cut early — before they consume budget. WEEK 2 ### Decide Build vs buy vs wait for each priority. Tooling only enters the conversation after the process decision is clear. DAY 10–14 ### Roadmap Read-out with a prioritised 90-day plan, owners and measurement. Ready for implementation or a pause with eyes open. Why a diagnostic first Why ## Fund the first win, *not the fifth pilot.* Most leaders I speak to are not short of AI ideas. They are short of a defensible answer to a simpler question: which one should we fund first, and how will we know it worked? Without that answer, the default is a pilot chosen by whoever saw the best demo. The numbers say that default is expensive. Gartner predicted that [at least 30% of generative AI projects would be abandoned after proof of concept by the end of 2025](https://www.gartner.com/en/newsroom/press-releases/2024-07-29-gartner-predicts-30-percent-of-generative-ai-projects-will-be-abandoned-after-proof-of-concept-by-end-of-2025), citing poor data quality, inadequate risk controls, escalating costs or unclear business value. McKinsey’s 2026 global survey found that [only 37% of respondents attribute any EBIT impact to AI, a share unchanged from 2025](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai), even though nearly nine in ten use it regularly. Finance is no exception: Gartner’s 2025 survey found [59% of finance leaders using AI, but 91% reporting only low or moderate impact at first](https://www.gartner.com/en/newsroom/press-releases/2025-11-18-gartner-survey-shows-finance-ai-adoption-remains-steady-in-2025). The Audit exists to close that gap before money is committed. As a Chartered Accountant, I treat it the way I would treat any investment decision: baseline first, controls designed in, and a written reason to build, buy or wait. ## By the numbers Why I insist on a baseline and a written business case before any build. Each figure links to its source and date. 37% of respondents attribute at least some EBIT impact to AI, essentially unchanged from 2025. Source: [McKinsey, The state of AI in 2026, 25 August 2026](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) About 6% of respondents are AI “high performers” (5%+ of EBIT from AI); nearly three-quarters of them have fundamentally redesigned workflows, against one-quarter of others. Source: [McKinsey, The state of AI in 2026, 25 August 2026](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) 91% of finance AI adopters reported low or moderate impact at first; bigger gains came once projects reached production. Source: [Gartner, 18 November 2025](https://www.gartner.com/en/newsroom/press-releases/2025-11-18-gartner-survey-shows-finance-ai-adoption-remains-steady-in-2025) 30%+ of generative AI projects predicted to be abandoned after proof of concept by the end of 2025. Source: [Gartner, 29 July 2024](https://www.gartner.com/en/newsroom/press-releases/2024-07-29-gartner-predicts-30-percent-of-generative-ai-projects-will-be-abandoned-after-proof-of-concept-by-end-of-2025) 59% of finance leaders report using AI in their finance function (183 CFOs and senior finance leaders surveyed, May–June 2025), against 37% in 2023. Source: [Gartner, 18 November 2025](https://www.gartner.com/en/newsroom/press-releases/2025-11-18-gartner-survey-shows-finance-ai-adoption-remains-steady-in-2025) **Sources** - [Gartner — 30% of generative AI projects predicted to be abandoned after proof of concept by end of 2025 (29 July 2024)](https://www.gartner.com/en/newsroom/press-releases/2024-07-29-gartner-predicts-30-percent-of-generative-ai-projects-will-be-abandoned-after-proof-of-concept-by-end-of-2025) - [McKinsey — The state of AI in 2026: On the road to ROI (25 August 2026)](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) - [Gartner — Finance AI adoption remains steady in 2025 (18 November 2025)](https://www.gartner.com/en/newsroom/press-releases/2025-11-18-gartner-survey-shows-finance-ai-adoption-remains-steady-in-2025) Updated 22 Oct 2026 Investment 03 ## Fixed-fee. *Confirmed on the call.* Pricing ### Fixed-fee two-week sprint — quote confirmed on the discovery call Scope, access and sector complexity determine the fee. No invented day rates on this page. Book a short discovery call and you leave with a clear quote — or a polite no-fit. Method ## How the AI opportunity audit *actually runs.* This is the method in full, so you can judge it before we speak — or run a version yourself. The two-week sprint covers mapping and scoring; the roadmap it leaves takes you to a working release by day 90. ### From two-week audit to a 90-day roadmap **Days 1–20: map the work.** Pick the five to eight recurring workflows that consume the most skilled time or create the most rework. For each, write five lines: input, decision, output, owner, and what “good” looks like today. In a CA practice this is usually research and first drafts, document extraction, reconciliations, reporting packs and routine client communication. In a finance team it is close, payables, collections and management reporting. **Days 21–45: score and cut.** Score each workflow on value (hours, cycle time, error cost, cash timing), feasibility (data availability, system access, process stability) and control risk (confidentiality, regulatory exposure, whether an error reaches a client or a filing). Be ruthless. Anything that needs clean data you do not have goes to the “later” column. Anything that would put an unreviewed answer in front of a client goes to “redesign”. **Days 46–70: design one release.** Take the top one — occasionally two — and design the thin version: which team, which data classes the tool may see, where the human approval gate sits, what is logged, and the metric you will review weekly. Write the stop conditions now, while nobody is emotionally invested. **Days 71–90: run it beside the old process.** Two to four weeks with one team, reviewed weekly. The output of the audit is not the deck. It is a working release with evidence, or a clean “no” with reasons. ### The plan on one page 90-day AI opportunity audit: phases, outputs and decision gates | Days | Work | Output | Decision gate | | --- | --- | --- | --- | | 1–20 | Map five to eight recurring workflows: input, decision, output, owner, today’s “good” | Workflow maps and a rough baseline | Do we have owners and data for at least three workflows? | | 21–45 | Score value, feasibility and control risk; cut weekly | Ranked shortlist, with a “later” and a “redesign” column | Which one workflow (occasionally two) goes forward? | | 46–70 | Design the thin release: team, data classes, human gate, logging, metric, stop conditions | Release design and pilot charter | Is the control design acceptable to the partner, CFO or risk owner? | | 71–90 | Run beside the old process with one team; weekly review of the exception log | Evidence against the baseline | Keep, change or stop, in writing | ### The scoring rubric Score each workflow from 1 to 5 on each line. This is a framework for your own data, not benchmark data. AI opportunity scoring rubric (score your own workflows) | Dimension | What a 5 looks like | What a 1 looks like | | --- | --- | --- | | Value: hours | Many skilled hours every week across the team | A few hours a quarter | | Value: error and cash | Errors are costly, or cash timing improves | Little cost to an error; no cash effect | | Feasibility: data | Structured data you already hold and can access | Data is on paper, scattered or owned by a third party | | Feasibility: process | Stable, written-down steps | Changes every month or lives in one person’s head | | Control risk (reverse-scored) | Errors are caught inside the business before anyone relies on them | An unreviewed error could reach a client, a filing or a regulator | | Ownership | A named manager wants it fixed and will run the release | Nobody’s job | ### How to spot audit theatre early Three signals tell me an audit is drifting. First, the idea list keeps growing after week three; a healthy audit shrinks its list every week. Second, nobody has asked for a baseline — not a perfect cost model, just rough volume, hours by role and the errors people already complain about. Third, the recommendations name tools before they name owners. If a recommendation cannot say who will be accountable for the metric, it is a brochure, not a plan. Audit theatre versus a useful audit | | Theatre | Useful | | --- | --- | --- | | Starting point | Workshops and a long idea list | Five to eight recurring workflows with owners | | Baseline | None, or a vendor’s benchmark | Rough volume, hours by role and known error patterns from your own data | | Idea list over time | Grows every week | Shrinks every week | | Recommendations | Name tools and platforms | Name owners, metrics and controls first | | Output | A closing deck | One working release with evidence, or a clean “no” with reasons | ### Governance anchors to use in India You do not need a heavy framework, but you should be able to show that the audit considered risk in a recognised way. These are the ones I use, depending on the organisation: - **Any organisation:** the [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) (govern, map, measure, manage) as a neutral checklist. - **Indian policy direction:** MeitY’s [India AI Governance Guidelines](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2186639) (November 2025), which take a principles-based approach built on existing laws. - **Personal data:** the [DPDP Rules, 2025](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2190014), notified in November 2025 with an 18-month phased compliance timeline. - **Regulated financial entities:** the RBI’s [FREE-AI committee report](https://rbi.org.in/scripts/BS_PressReleaseDisplay.aspx?prid=61018) (August 2025), with 7 sutras and 26 recommendations across six pillars. - **Audit firms:** NFRA’s [General Principles for Technology Adoption in Audit](https://nfra.gov.in/staff-series-on-technology-in-audit/) (July 2026), including validation of tools before live use. Treat all of them as prompts. Your chart of accounts, staffing and auditor’s expectations are the real constraints. ### Deliverables checklist - Workflow maps (five lines each) for every workflow reviewed. - Baseline sheet: volume, hours by role, error patterns, with how each was measured. - Scored and ranked list, including what was cut and why. - One release design: team, data classes, human approval gate, logging, metric, stop conditions. - Cost of the next 90 days, including review time and change management, not just licences. - Control notes: data protection, who reviews what, and for CA firms, which outputs a signing professional must see. - Evidence from the parallel run and a written keep, change or stop decision. ### Monday-morning checklist - List no more than eight recurring workflows and write the five-line map for each. - Collect a rough baseline: volume, hours by role, known error patterns. - Score value, feasibility and control risk; cut the list every week. - Design one thin release with owner, data classes, human gate and stop conditions. - Judge the audit by the release it ships, not by the length of the deck. ### Frequently asked questions ### What is an AI opportunity audit? A time-boxed review that maps an organisation’s recurring workflows, scores each on value, feasibility and control risk, and ends with one designed release run beside the existing process, rather than a list of ideas. ### How long does an AI opportunity audit take? About 90 days if it includes a real parallel run: roughly 20 days to map workflows, 25 to score and cut, 25 to design one release and 20 to run it beside the old process. ### What should an AI audit report contain? Workflow maps, a baseline, the scored and ranked list with what was cut, one release design with owner, metric and controls, the cost of the next 90 days and, after the parallel run, a written keep, change or stop decision. ### Which frameworks should an AI audit in India refer to? The NIST AI Risk Management Framework as a neutral checklist, MeitY’s India AI Governance Guidelines, the DPDP Rules, 2025 for personal data, the RBI’s FREE-AI report for regulated financial entities and NFRA’s 2026 principles for audit firms. ### Is an AI audit worth it for a CA firm? It is worth it when partners want a defensible answer about where AI pays back. For CA firms the audit should also record which outputs a signing professional must review, because AI does not change who is accountable. ## Keep reading in this topic This guide is part of [AI automation in India: a practical hub for business owners](https://pratikbajoria.com/ai-automation-in-india). [Why Most Corporate AI Pilots Never Reach Production](https://pratikbajoria.com/blog/corporate-ai-pilots) [The Monday Morning Test for Any AI Workflow](https://pratikbajoria.com/blog/2026-09-29-the-monday-morning-test-for-any-ai-workflow) [Build vs Buy: A Decision Framework for AI Tooling](https://pratikbajoria.com/blog/build-vs-buy-ai-tooling) Also useful: [AI implementation for finance teams: the CFO and controller guide](https://pratikbajoria.com/ai-implementation-for-finance-teams). This section replaces my earlier article “The AI Opportunity Audit: A 90-Day Roadmap Without the Theatre”. Sources: [NIST AI RMF](https://www.nist.gov/itl/ai-risk-management-framework); [PIB on India AI Governance Guidelines](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2186639); [PIB on DPDP Rules, 2025](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2190014); [RBI FREE-AI report](https://rbi.org.in/scripts/BS_PressReleaseDisplay.aspx?prid=61018); [NFRA Staff Series](https://nfra.gov.in/staff-series-on-technology-in-audit/). FAQ 04 ## Questions before *you book.* ### What is an AI Opportunity Audit? An AI Opportunity Audit is a fixed-fee, two-week diagnostic that maps workflows, scores AI use cases on impact, effort and risk, and delivers a prioritised 90-day roadmap before a build is funded. ### What do you need from us? Access to process owners, a shortlist of workflows under pressure, and honest volume/cycle-time context. You do not need a polished data lake — you need clarity on how work actually runs. ### Is this a tool selection exercise? No. Tools come after process and ownership. The Audit decides whether to build, buy or wait — then names the next step. ### What happens after the two weeks? You leave with a scored roadmap. Many clients continue into implementation or team enablement; some execute internally. Either path is fine if the prioritisation is clear. ### Can this stay remote? Yes. Remote interviews and screen-shares work well. On-site days can be scoped when the process is heavily paper- or floor-based. ### How do I start? Book a discovery call, or message on WhatsApp mentioning the Audit. Expect a reply within one business day. ## Related - [AI Opportunity Audit for CA firms guide](https://pratikbajoria.com/ai-opportunity-audit-for-ca-firms) - [AI automation in India: a practical hub for business owners](https://pratikbajoria.com/ai-automation-in-india) - [Why Most Corporate AI Pilots Never Reach Production](https://pratikbajoria.com/blog/corporate-ai-pilots) - [The Monday Morning Test for Any AI Workflow](https://pratikbajoria.com/blog/2026-09-29-the-monday-morning-test-for-any-ai-workflow) - [Build vs Buy: A Decision Framework for AI Tooling](https://pratikbajoria.com/blog/build-vs-buy-ai-tooling) - [AI implementation for finance teams: the CFO and controller guide](https://pratikbajoria.com/ai-implementation-for-finance-teams)