Finance Systems Toolkit - Practical Tools That Actually Get Used

When to use it: after a weak month when you need a disciplined reset instead of a hand-wavy reforecast.

Role: You are my CFO-level FP&A partner.
Context: We are a Series B SaaS company in India with INR reporting, some USD-linked costs, and a board update in 5 days. I will give you actuals, current forecast, headcount plan, CAC by channel, and collections timing.
Task: Rebuild the next 6 months into base, downside, and stress cases. Identify the 5 drivers that explain most of the change, quantify runway impact, and highlight 3 decisions leadership should make now.
Format: Return a concise table for each scenario, then a short management note with what changed, why, and what action is required.

When to use it: when the CEO asks how much room exists before a hiring pause, fundraise, or cost reset becomes unavoidable.

Role: Act as a disciplined startup finance operator.
Context: I will share opening cash, monthly burn, collections risk, committed hires, and any debt or covenant limits.
Task: Build a scenario ladder showing runway under current plan, 10 percent revenue shortfall, 20 percent collections delay, and a combined downside case. Tell me which operating levers preserve the most runway with the least strategic damage.
Format: Output a 4-row scenario table, then a ranked list of levers with estimated runway benefit and likely business downside.

When to use it: before a board pack, when you want the model challenged for driver inconsistency and hidden optimism.

Role: You are an experienced board-facing finance reviewer.
Context: I will provide a draft forecast with assumptions for bookings, retention, headcount, gross margin, CAC, and FX.
Task: Challenge the forecast. Find assumption conflicts, unsupported optimism, and missing downside triggers. Then suggest the minimum changes needed to make the forecast board-ready.
Format: Return three sections: red flags, questions for management, and a cleaner forecast assumption set.

When to use it: after closing the month when you need crisp commentary that follows the actual bridge logic.

Role: You are an FP&A lead who writes sharp monthly commentary.
Context: I will provide plan, actual, and bridge line items for revenue, gross margin, EBITDA, and cash.
Task: Write a short monthly variance note that explains the main drivers, separates timing from structural issues, and names the immediate actions by owner.
Format: Output three paragraphs: what changed, why it changed, and what happens next. Keep the tone board-ready and direct.

When to use it: when "revenue missed" is too vague and you need segment-level explanation with clear next moves.

Role: Act as a commercial finance analyst with strong business judgment.
Context: I will share actual versus plan by segment, along with volume, price, mix, churn, and timing data.
Task: Decompose the miss into the few drivers that matter most, identify which are recoverable this quarter, and recommend 3 actions for sales, marketing, and finance.
Format: Return one driver table followed by a short action memo with named owners and expected impact.

When to use it: when costs are drifting and the team needs a sharper explanation than "higher than expected spend."

Role: You are a disciplined finance business partner.
Context: I will provide actual versus budget operating expenses by department, highlighting headcount, software, travel, and professional fees.
Task: Explain the overspend, separate one-off and recurring items, identify any approval or renewal control failures, and recommend corrective actions by owner.
Format: Return a short memo with a table for overspend drivers and a final section called "what we stop, what we keep, what we review."

When to use it: when two or more projects all sound compelling but capital is tight.

Role: You are my capital allocation partner.
Context: I will provide 3 to 5 proposed projects with expected spend, strategic rationale, payback, risks, and execution demands.
Task: Score each project on strategic fit, expected ROI, capital efficiency, risk, and execution speed. Then recommend which to fund now, phase, or stop.
Format: Output a score table, then a direct recommendation memo explaining the ranking and the most important trade-offs.

When to use it: when a project is consuming money but nobody wants to confront whether it still deserves funding.

Role: Act as a hard-nosed but fair investment reviewer.
Context: I will share the original business case for a project, money spent so far, actual outcomes, revised timeline, and strategic value today.
Task: Recommend whether we kill, continue, or reset the initiative. Explain the sunk-cost risk, what new evidence matters, and the decision rule leadership should use.
Format: Return a one-page memo with recommendation, rationale, and next action.

When to use it: when EBITDA looks acceptable but cash conversion is weak.

Role: You are a CFO advisor focused on cash conversion.
Context: I will provide DSO, DPO, inventory days, top overdue accounts, vendor terms, and any GST or billing constraints.
Task: Identify the 5 biggest working capital release levers, estimate the likely cash impact, and recommend owners plus weekly tracking metrics.
Format: Output a ranked action table and a short note on what can move in 30 days versus what needs structural negotiation.

When to use it: when you need a concise board page that surfaces only the metrics and decisions that matter.

Role: You are an experienced CFO preparing a board one-pager.
Context: I will provide the latest KPIs, actual versus plan, cash position, runway, and 3 to 4 major business developments.
Task: Turn this into a one-page board summary with headline metrics, key insights, emerging risks, and decisions required from the board or leadership.
Format: Return a tight one-page layout in bullet format with a direct, calm tone and no unnecessary jargon.

When to use it: when the CEO needs a short, action-led finance note instead of a dense report.

Role: Act as a finance chief of staff to the CEO.
Context: I will give you actuals, forecast changes, cash position, hiring updates, and any open capital decisions.
Task: Draft a short CEO update that explains what changed, what it means, and which two to three decisions need attention this week.
Format: Return a short memo with headings: headline, why it matters, decisions required.

When to use it: when finance needs one sharp memo to support a budget reset, capital request, or resource reallocation.

Role: You are preparing a finance decision memo for senior leadership.
Context: I will provide the situation, the capital requested or forecast change proposed, expected return, risks, and alternatives considered.
Task: Write a decision memo that states the ask, business rationale, financial impact, downside case, and recommendation.
Format: Use a simple structure with sections: decision required, business case, financial case, risks, recommendation.

When to use it: when month-end feels heavy but nobody has mapped where the actual delay and rework live.

Role: You are a finance operations designer.
Context: I will share the month-end close calendar, handoffs, owners, recurring delays, and manual tasks.
Task: Identify the biggest bottlenecks, which steps are candidates for automation, and where control risk means the task should stay manual.
Format: Return a process map table with columns for step, pain point, automation potential, control risk, and recommendation.

When to use it: when a use case looks promising but you need a control design before the pilot expands.

Role: You are a finance governance and controls advisor.
Context: I will describe a proposed AI workflow, the source data used, the output created, and who will consume it.
Task: Design the minimum controls required so the workflow can run safely inside finance. Cover data inputs, reviewer responsibility, version control, exception handling, and audit trail.
Format: Return a control checklist plus a simple operating policy for the team.

When to use it: when you want AI to flag weird patterns in vendor, customer, or GL data before close review.

Role: Act as a finance data quality analyst.
Context: I will provide exported transaction or master data with vendor names, GL codes, departments, dates, and amounts.
Task: Flag unusual duplicates, missing fields, coding inconsistencies, and transactions that deserve human review before close.
Format: Return a prioritized exception list with reason codes and a suggested reviewer for each exception group.