Month-end commentary
Move from source figures to checked variances, a bounded narrative and an explicit review step.
COPILOT STUDIO FOR FINANCE TEAMS
Make Copilot
work for
your team.
One useful workflow. A team equipped to run it.
Turn recurring finance work into a connected, tested Copilot Studio workflow. We implement it with your team, teach the method and hand over the tools to operate it.
Six weeks · 4–8 participants · From $12,500 USD
A CONNECTED MICROSOFT WORKFLOW01—04
THE AGENT
Copilot Studio
Understand the request. Call approved tools.
THE WORKFLOW
Route the work.
Power Automate / agent flows
THE MANAGED RUNTIME
Execute checked logic.
Azure Functions / Fabric notebooks
04 / Review & approve
Evidence and an accountable owner.
LEARN IT. BUILD IT. RUN IT.
Work directly with the founder.
Build in your Microsoft environment.
Inspect the published method ↗START WITH WORK YOU RECOGNISE
Where does the
same work pile up?
Choose a recurring task with a clear owner, usable data and a result someone can review. These are examples of the work we can scope together.
Discuss this workflow ↗
Management reporting
Bring the reporting instructions, approved inputs and review checklist into one repeatable workflow.
Forecast review
Surface changes and missing explanations, then route questions to the people responsible.
01 / THE APPROACH
Learn by doing.
Leave with ownership.
The people who do the work help build the system. Working sessions connect practical teaching to the actual task, its decisions and its operating requirements.
Learn the method.
Define the task, give useful instructions and recognise where calculations, model judgment and human review belong.
Build it together.
Configure the agent in Copilot Studio. Connect its tools, define the workflow and implement calculation logic in an agreed managed runtime.
Make it yours to run.
Test outputs and failure paths. Document access, releases and recovery. Your team demonstrates the handover by operating and reviewing the workflow.
A CLOSER LOOK
The figures reconcile.
The story gets reviewed.
A monthly variance note is a useful place to start. The figures come from a defined calculation. The narrative stays within the evidence. A person reviews the conclusion.
Explore a simplified example below. These are prepared examples, not a live AI system or client results.
START WITH DEFINED INPUTSSAMPLE
A figure you can trace.
| Measure | Amount |
|---|---|
| Actual revenue | $1,240,000 |
| Budget revenue | $1,200,000 |
| Variance | +$40,000 |
| Variance ÷ budget | +3.3% |
Calculation: actual − budget. Percentage rounded to one decimal place.
BOUND THE NARRATIVESAMPLE
Say what the data supports.
Revenue was $40,000, or 3.3%, above budget for the month.
The input establishes the movement. It does not establish whether pricing, volume or timing caused it.
Question for the owner: what explains the movement, and what evidence supports that explanation?
KEEP JUDGMENT VISIBLESAMPLE
A correct number is a start.
- Amount and percentage reconcile.
- Figures refer to the same period.
- Commercial cause still needs evidence.
Hold unsupported explanations for review. Passing a numerical check does not establish that the story is complete.
02 / LEARN & IMPLEMENT
A defined engagement.
A tangible handover.
A focused Copilot Studio engagement for a small finance team. Build one connected workflow in your Microsoft environment, with practical teaching, evaluation and an operating handover.
- 01
Define
Map the task, baseline the effort and agree what success means.
- 02
Learn
Practise the method with clear inputs and review criteria.
- 03
Implement
Connect the Copilot Studio agent, workflow and execution layer.
- 04
Test
Check outputs, permissions, failed actions and review gates.
- 05
Operate
Have your team run and review the workflow.
- 06
Transfer
Hand over the solution, release notes and operating runbook.
- A configured workflowThe agent, agreed integrations and calculation logic in your environment.
- An evaluation recordTest cases, observed results, known limits and a release recommendation.
- An operating packSource/configuration, review instructions, access notes and release steps for the agreed scope.
- A practical team handoverYour team demonstrates that it can run the workflow and recognise when to intervene.
Release follows the evidence. If acceptance criteria are unmet, you receive the current implementation, findings and remaining work; further remediation is scoped before it begins.
START WITH A SESSION
Copilot Workflow Workshop
A three-hour working session to map a real task, practise the method and leave with a workflow outline and readiness gaps.
$3,500 USDUp to 12 participants
KEEP DEVELOPING
Practice Support
Office hours and review for your existing workflow. A defined allowance for improvements, questions and evaluation after handover.
$1,500 USD / monthUp to four hours monthly
THE MICROSOFT PRACTICE
Agents. Workflows.
Execution you can inspect.
Give each layer a clear job. Copilot Studio handles the interaction. Workflows coordinate the steps. Reviewed code handles the calculations. Your people own the decisions.
Purpose-built agents
Instructions, knowledge, topics and tools shaped around a defined business task.
Microsoft Copilot StudioConnected workflows
Triggers, connectors, approvals and exception paths that move work between systems.
Power Automate · Agent flowsManaged runtimes
Calculation and validation code deployed to a managed service, with explicit inputs, outputs and logs.
Azure Functions · Microsoft FabricBuilt for the handover.Access boundariesEvaluation casesRelease & rollbackOperating runbooks
Architecture and access are agreed with your platform owner. We choose the services the workflow needs; hosting costs, monitoring ownership and support are explicit in the scope.
03 / THE PEOPLE BEHIND THE WORK
Meet the person
doing the work.
Felix Reyes · Founder & Principal
Felix is the author of The Skills Pack: Turning Finance Work into Tested AI Skills. He leads the engagement, from defining the task to teaching the team and reviewing the implementation.
You can inspect the thinking before you buy: the draft book and companion repository include finance skill instructions, sample data, checks and exercises. Reylio applies that method to your Microsoft environment.
Explore the book & examplesOPEN TO INSPECTION
The method behind
the engagement.
The draft bookThe Skills Pack, by Felix ReyesThe finance skill packsInstructions, inputs and outputsThe companion filesSample data, exercises and reference materialExplore the draft manuscript and illustrative finance examples, including the instructions and checks behind the outputs.
A FEW PRACTICAL QUESTIONS
Clear from
the start.
Is our team ready for this?
A good first project has one recurring task, a business owner, approved data and a platform contact. The programme suits finance teams that can participate in working sessions. If data access or platform setup needs substantial work, we identify that before proposing implementation.
What happens in the first conversation?
We spend about 20 minutes on the task, the current process and the Microsoft environment. The aim is to decide whether a workshop, an implementation engagement or prerequisite work is the sensible next step. You do not need to share confidential data.
Do we need Copilot Studio and Fabric?
Copilot Studio is the centre of the implementation offer. We choose Power Automate, Azure Functions or Fabric to suit the workflow; every engagement does not need every product. We confirm licences, permissions and data readiness before agreeing scope.
What do you mean by managed runtimes?
A Microsoft service runs the workflow’s code—for example, an Azure Function or a Fabric notebook. We design the inputs, checks, access and operating instructions around it. Monitoring ownership and any ongoing support are agreed separately.
Is this training or implementation?
Both. Your team learns the method while applying it to one agreed workflow. The programme includes working sessions, guided implementation, evaluation and a documented handover.
What does our team need to provide?
A business owner, approved inputs, participating team members and a technical contact who can support the agreed environment. A major data migration or platform deployment needs a separate scope.
How do we know whether it worked?
We agree criteria at the start: preparation and review effort, correct figures, unsupported claims, omissions and the team’s ability to operate the workflow. Production release depends on meeting the agreed criteria.
A SMALL FIRST STEP
Bring one workflow.
Let’s find the fit.
Start with a 20-minute conversation with Felix. We’ll look at the task, the environment and what a useful result would mean for your team.
hello@reylio.comEmail Felix directly, or use this short brief to prepare an email. Nothing is sent until you send it from your email app. Please leave out confidential data.
We’ll cover01 The work and its owner02 Your Microsoft environment03 A practical next step