01Flagship Micro-ProjectFinance Knowledge Assistant Pilot
A scoped, source-grounded assistant with access controls and an evaluation set.
Finance problem
Policies, process knowledge and KPI definitions are spread across documents and individuals. Finding a current, authoritative answer takes time.
Delivered outcome
An assistant retrieves and explains approved information in one defined knowledge domain, with document and version references.
In scope
One Finance knowledge domain, agreed user groups, document ingestion, retrieval and answer drafts. No autonomous decisions or enterprise-wide knowledge programme.
Inputs & data
Approved policies, Finance manuals, KPI definitions and process documents; content owners; version and access rules.
Controls & review
Mandatory source references, role-based access, stale-document checks, access-boundary tests and an explicit no-answer path when evidence is insufficient.
Definition of Done
An agreed evaluation set checks retrieval, citation accuracy, access boundaries and missing-answer handling. Finance owners accept the workflow through UAT.
Potential expansion → Finance Knowledge & Decision Platform
Add knowledge domains and documented decision support after the pilot demonstrates reliable behaviour.
Also required for every project: the shared delivery and acceptance standard.
02Flagship Micro-ProjectManagement Reporting & Variance Copilot
A controlled reporting workflow through to approved commentary.
Finance problem
Monthly management packs are assembled from Excel, BI and email. Calculations and business explanations are difficult to trace together.
Delivered outcome
A repeatable workflow combines checked Actual/Budget/Forecast figures, approved business rules and evidenced context with reviewable commentary drafts.
In scope
One reporting pack, agreed KPIs and periods, data import, deterministic calculations, context retrieval, commentary drafting and Finance approval.
Inputs & data
Excel/CSV/BI exports, KPI definitions, budget and forecast versions, organisational hierarchies, materiality thresholds and sourced business notes.
Controls & review
Calculations remain deterministic. Periods and versions are validated. Observed variance, evidenced context and open causal questions stay distinct; the model does not invent root causes.
Definition of Done
Figures reconcile to approved sources. Drafts contain no unsupported causal claims. Exceptions, review, approval and a repeat reporting cycle pass the agreed UAT.
Potential expansion → Management Reporting & FP&A Workbench
Extend to reporting packs, review stages and integrated planning commentary after pilot acceptance.
Also required for every project: the shared delivery and acceptance standard.
04Focused Micro-ProjectFinance Document Intelligence Pilot
A bounded document workflow with a traceable exception queue.
Finance problem
Recurring Finance documents are read, rekeyed and checked manually. Exceptions can disappear into routine processing.
Delivered outcome
Convert one document type into agreed structured fields, validate them with rules and hand over with an explicit review status.
In scope
One document class, one field schema, agreed input formats, extraction, classification, validation and one defined handover.
Inputs & data
Synthetic or approved samples, field definitions, validation rules, exception examples and an agreed target workflow or approved interface.
Controls & review
Field-level provenance, format and plausibility checks, materiality and review rules, traceable exceptions and human approval before consequential downstream use.
Definition of Done
The agreed test set covers normal cases, unreadable content, missing fields and conflicts. Handover and exception handling pass UAT, without silent failures.
Potential expansion → Finance Document Intelligence Platform
Extend to document classes and controlled API connections after validating extraction and review.
Also required for every project: the shared delivery and acceptance standard.
05Focused Micro-ProjectMonth-End Close Coordination Assistant
Transparent close status with tasks, evidence and open issues.
Finance problem
Close tasks, evidence and follow-ups are tracked in separate lists and messages. Review status and escalations are difficult to oversee.
Delivered outcome
A coordinated view of tasks, owners, evidence, issues and review status supports Finance-led close management.
In scope
One close team and a defined reporting cycle; task coordination, evidence links, reminders, follow-ups and status drafts.
Inputs & data
An approved close calendar, task list, owners, review stages, evidence references and agreed escalation rules.
Controls & review
Trace status changes. Keep evidence separate from approval. Journal entries, accounting controls and Finance sign-off remain in the responsible systems and roles.
Definition of Done
Tasks and evidence are correctly assigned. Missing evidence and overdue reviews are flagged. Escalation and handover pass UAT for an agreed close cycle.
Potential expansion → Controlled Finance Workflow / Agent Automation
Controlled workflow automation with explicit approvals; no autonomous postings or accounting responsibility.
Also required for every project: the shared delivery and acceptance standard.
06Focused Micro-ProjectFinance Workflow Automation Sprint
A working workflow with explicit handovers and a fallback path.
Finance problem
A recurring Finance process involves manual transfers, follow-ups or approvals. An existing pilot is not yet a reliably repeatable workflow.
Delivered outcome
Implement exactly one recurring workflow using deterministic rules, appropriate AI steps and explicit approval points.
In scope
One defined start and end point, bounded integrations, rules, AI-assisted tasks, approvals and traceable handovers.
Inputs & data
A process description, system/API access within the agreed permission model, field definitions, sample data, roles and approval rules.
Controls & review
Scoped write permissions, secrets in approved stores, retry and duplicate protection, error logs, escalation and a manual fallback path.
Definition of Done
Test normal cases, failure, retries, timeout and cancellation. Approvals and handovers pass UAT; operating responsibilities and documentation are handed over.
Potential expansion → Controlled Finance Workflow / Agent Automation
Coordinate multiple AI, rule-based and human steps after the first workflow demonstrates value.
Also required for every project: the shared delivery and acceptance standard.