Finance Agent
How Sasha builds your Finance Agent the way you would induct a new colleague, with the job, the access, the first piece of work and the feedback.
Status: available now.
The Finance Agent looks after your costs. Each period it reads your bills, checks the figures, splits them by product and sends one short email. The email starts with the answer and gives at most three things to do.
You do not write this agent. Sasha builds it for you, from what it already knows about your business. This page shows how, step by step.
About the examples on this page. Northwind Advisory is an imaginary company: a small UK consultancy with two products, Advisory and Training. Its people, accounts, suppliers and figures are invented to show what Sasha builds. Your agent holds your own products, people, rules and numbers.
The story: a new colleague joins your finance team
Imagine that Northwind hires a new finance assistant. On their first day, Sam, the operations director, sits down with them and explains the job:
- "These are the questions I need you to answer every month."
- "This is what normal looks like here, so you can tell when something is wrong."
- "This is where the bills and the accounts are. That account belongs to a client, so never count it."
- "These are the rules we use to split costs."
- "You can do these things on your own. For anything else, ask me first."
- "Tell these people. Send it on the first working day."
- "These are the methods we use, and why."
Then Sam gives them access to the systems they need, and no more. The new colleague comes back with questions about what they could not find. Sam checks their first piece of work before anyone else sees it. From then on they work on their own, keep a log of what they did, and take feedback in their one-to-ones.
The Finance Agent is that new colleague, and Sasha runs the induction for you. Sasha already knows your business from your documents, your meetings and your connected systems, so it prepares most of the induction itself. You correct it, as Sam would.
| With a new colleague | With the Finance Agent | On this page |
|---|---|---|
| Sam explains the job | Sasha writes the brief, in eight sections | Step 3 |
| The colleague asks about what they could not find | Sasha shows what it found, and asks only about the gaps | Step 4 |
| Sam gives them access to the right systems | An admin approves the tools and permissions | Step 5 |
| Sam checks their first piece of work | You check the first report | Step 6 |
| The colleague keeps a log of their work | The agent keeps a work log | After the build |
| Sam gives feedback | You correct the brief through Sasha | After the build |
How Sasha builds it, in six steps
A simplified view. This page shows a simplified, conceptual version of how Sasha builds an agent. The questions in the terminal panels and the brief excerpts show the idea in a few lines. In the product, the instructions that Sasha follows are much longer and more detailed: they include checks, rules for sources and evidence, and tested scripts for every figure.
- You ask for it (you decide to hire). An admin opens Agents that work for me, chooses Finance Agent and clicks Set it up.
- Sasha reads your contour data (it learns about your business before the first day). Contour data is what Sasha already holds about your business: your documents, your meeting notes and your connected systems. Sasha uses only what is about your business, not your clients.
- Sasha drafts the brief, section by section (the induction). For each of the eight sections it asks one question of your contour data, and it writes down where each fact came from. The next part of this page shows each section, with Northwind's example and the question that Sasha asks.
- Sasha tells you what it found, and asks only about the gaps (the new colleague's questions). It shows three lists: what it can already see, what it knows about but cannot read yet, and what is probably missing. For example: "A consultancy like yours usually spends on eleven things. I can see six." Then it asks you about the gaps, a few questions at a time.
- Sasha sets up the tools and permissions (access to the right systems). It asks an admin to connect each source read-only, for example your cloud bill. It writes the agent's Permitted actions from what the admin approves.
- Sasha runs the agent once, and you check it (the first piece of work). The first report shows where each figure came from. You correct the brief where it is wrong, and you approve. From then on, the agent runs on its schedule.
Step 3, the induction: how Sasha writes each section of the brief
Every Sasha agent's brief has the same eight sections. Each section is one part of the induction: what Sam would tell a new colleague, written down so that the agent reads it before every run.
For each section below you see what you would tell a new colleague, the section as it appears in Northwind's brief file, and the question that Sasha asks of your contour data to write it. You can ask the same question yourself, to check a section or to draft it again after your business changes. Sasha shows you the result before it saves it.
1. The questions it answers
What you would tell a new colleague: "These are the questions I need you to answer every month."
## 1. The questions it answers
Each month, answer:
1. What did we spend, in total and for Advisory and Training?
2. What moved, broke a budget or looks wrong?
3. Which card payments failed or are late, and how much is at risk?
4. Is Training still profitable after its share of shared costs?
The first three questions come with every Finance Agent. Northwind added the fourth.
Sasha figures this out from your contour data by asking:
From our documents and meetings, what questions do we keep asking about money? List the ones a monthly finance report should answer, in our own words.
2. What normal looks like
What you would tell a new colleague: "This is what we usually spend, and what is coming up. Then you can tell me when something is wrong."
## 2. What normal looks like
**Budgets, per month**
- Advisory: 2,400 GBP
- Training: 1,700 GBP
**Usual size:** compare each cost with its average over the
last six months. Flag a cost above 1.5 times its usual size,
or below two thirds of it.
**Known events**
- 2026-10: Training launches a new course. Expect higher
cloud costs for Training in October and November.
**Known problems**
- The old test server is still running.
Known since 2026-09-03 (operations meeting). Not new.
Known events are new with the eight-section update. Budgets, usual size and known problems are in the brief today.
Sasha figures this out from your contour data by asking:
What are our budgets for each product, and what do we usually spend each month? List the events coming up that will change our costs, and the cost problems we already know about. Give the document or meeting for each one.
3. What it reads
What you would tell a new colleague: "This is where the bills and the accounts are. That account belongs to a client, so never count it."
## 3. What it reads
| Account | Whose | Product | Connection |
|--------------------|--------------------------|----------|-----------------|
| Cloud account 4417 | Ours | Shared | aws-cost |
| Stripe acct_1Nv0 | Ours | Advisory | stripe-advisory |
| Stripe acct_8Kq2 | Ours | Training | stripe-training |
| Cloud account 9902 | Harbour Foods (a client) | - | never counted |
**Suppliers**
- Cloud hosting: shared, from the cloud bill
- Video hosting: Training, from the cloud bill
- Accounting software: shared, entered by hand
- ... and six more
**Costs entered by hand**
- Accounting software: 42 GBP a month, confirmed
Sasha figures this out from your contour data by asking:
List every cloud, billing and card payment account in our documents. For each one, say whose it is, ours or a client's, which product it is for, and where you found it. Then list our suppliers and the product each one is for.
4. How it judges
What you would tell a new colleague: "These are the rules we use to split costs, so that your answer is the same as mine."
## 4. How it judges
**Product tag:** the tag `Product` on the cloud bill names the
product. The value `web` means Advisory.
**Shared costs**
- "Load Balancing": shared, split by what each product spends.
Why: both products use the same load balancer.
**What counts as a change:** a cost that moved by more than
10 GBP since the last report.
**Sales against card payments:** flag a gap of more than 2%.
Tested scripts apply these rules and do every sum, to the penny. The AI explains the results. It does not do the arithmetic.
Sasha figures this out from your contour data by asking:
How do we tag cloud costs by product, and how do we split a cost that serves more than one product? Quote the document that says so. Tell me where we have no rule.
5. Permitted actions
What you would tell a new colleague: "You can do these things on your own. For anything else, ask me first." Every Sasha agent shows this in the same table.
## 5. Permitted actions
<!-- Written by Sasha from the approved permissions. Do not edit. -->
| Action | Tool | Alone or ask first | Limits |
|-----------------------------------------|-----------------------|-----------------------------|------------|
| Read the cloud bill and card payments | Read-only connections | Alone | Reads only |
| Suggest at most three actions | None | Alone | Text only |
| Cancel a service, refund, pay a bill | None approved | Ask first (Held items) | - |
| Anything not listed | - | Never. It asks | - |
This section does not come from your documents. Sasha writes the table from the permissions that an admin approved. Editing the brief does not give the agent more permission. The approved permissions decide.
Sasha figures this out from the approved permissions, not your contour data, by asking:
What may the Finance Agent do on its own, and what waits for approval?
6. Who follows up
What you would tell a new colleague: "This is who owns what. Tell these people."
## 6. Who follows up
**Owner of the actions:** Sam Shah, operations director
**People**
- Tom Reed: looks after the cloud bill
- Ana Costa: looks after card payments
**Who gets the report:** sam@northwind.example, tom@northwind.example
**Who hears about problems:** tom@northwind.example
Sasha figures this out from your contour data by asking:
Who makes the finance decisions here, who looks after the cloud bill and who looks after card payments? Give each person's role and email address, and the document that says so.
7. When it reports
What you would tell a new colleague: "Send it on the first working day, before our monthly meeting."
## 7. When it reports
**Schedule:** monthly, first working day, 08:00 Europe/London
**Email:** one a month. The answer first, then the cost by
product, then at most three things to do.
**Alerts:** none between reports.
Sasha figures this out from your contour data by asking:
When do we review our finances: in which meeting, on which day and how often? Suggest a schedule so that the report arrives before that meeting.
8. Reading list
What you would tell a new colleague: "These are the methods we use, and why. Read them before you start."
## 8. Reading list
- Shared costs are split by what each product spends: the
usual way to share overheads by activity, and simple to check.
- A cost is compared with its own history, not with a
benchmark from another business.
- Sales are checked against card payments: two independent
sources show a missing figure quickly.
Status: planned. You will be able to check the list and add to it. See How agents learn.
Sasha figures this out from your contour data by asking:
Which methods do we use for budgets and for sharing costs between products? Name any book, framework or adviser that our documents mention.
Step 4, the new colleague's questions: what Sasha found, and the gaps
What a good new colleague does: they tell you what they could not find. They do not guess.
Sasha compares what it can see with what a business like yours usually pays for. Then it tells you what it found, and it asks only about the gaps.
A consultancy like yours usually spends on eleven things. I can see six.
I can already see (6)
- cloud hosting
- video hosting
- card fees on two Stripe accounts
- accounting software
- domain renewals
I know about these, but cannot read them yet (2)
- web hosting: named in the March board pack, not connected
- office broadband: on the supplier list, but no bill
These are probably missing (3)
- professional indemnity insurance
- payroll software
- a customer relationship tool
Three questions for you:
1. Do you pay for professional indemnity insurance? If so, about how much a year?
2. Can you connect your web hosting account, read-only?
3. Who looks after card payments?
Sasha figures this out from your contour data by asking:
Compare what you can see of our costs with what a consultancy like ours usually pays for. List what you can see, what you know about but cannot read, and what is probably missing. Then ask me only about the gaps.
Step 5, access to the right systems: tools and permissions
What you would do for a new colleague: give them access to the systems they need, and no more.
The Finance Agent needs one source to start: your cloud bill, connected read-only. Each source that you add makes the report more complete: card payments, web hosting and domain renewals, your sales platform, and costs that you enter by hand.
Connections (read-only)
- aws-cost Cloud account 4417 connected
- stripe-advisory Stripe acct_1Nv0 connected
- stripe-training Stripe acct_8Kq2 connected
- web hosting - not connected: Tom asked to connect it
Approved actions
- none. Any action waits in Held items for a person.
Approved by: Sam Shah, admin, 2026-09-28
Sasha holds the passwords and keys. The agent uses a connection, but it cannot read or copy the key. When a source is missing, the report says "Not complete" and tells you how to fix it. A figure that Sasha could not read shows as "not read", never as zero.
Sasha figures this out from your contour data by asking:
Which systems hold our costs and card payments, and which of them are already connected to Sasha? For each one that is not connected, tell me who can connect it, read-only.
Step 6, the first piece of work: the first report
What you would do for a new colleague: check their first piece of work before anyone else sees it.
Sasha runs the agent once and shows you the report before it goes to anyone else. From then on, the same report arrives on the schedule in section 7.
Northwind Advisory: Finance Agent, September 2026
September 2026 cost: 4,210.00 GBP
- Advisory 2,338.89 GBP (2,000.00 direct + 338.89 shared)
- Training 1,871.11 GBP (1,600.00 direct + 271.11 shared)
What to do
1. Training is 10% over budget.
Owner: Sam. Tell Sasha: show me Training's cloud costs for September by service.
2. Two card payments failed: 380 GBP at risk, the oldest 9 days.
Owner: Ana. Tell Sasha: list the failed Training payments with the customer names.
3. The old test server still costs 64 GBP a month (known since 3 September).
Owner: Tom. Tell Sasha: what runs on the old test server?
Cannot see: nothing this month.
After the build: the work log, what it did and why
What a good colleague does: they write down what they found, what they did and why.
Every run is recorded: the sources it read, what it could not read, and the report it sent. The Work log button in the agent's page shows it.
Status: built (Sasha 1.0.1556 and later). The work log records each run, each finding of Sasha's script with its reason, and each approval, mark and brief change. You can mark a line Useful or Not relevant. For example:
2026-10-01 08:00 run Started. Read: cloud bill, Stripe Advisory, Stripe Training. Not read: none.
2026-10-01 08:01 found Training cost 1,871.11 GBP.
2026-10-01 08:01 judged 10% over budget (1,700 GBP). No known event in September.
2026-10-01 08:02 recommended Sam to review Training's cloud costs.
2026-10-01 09:15 marked Sam: "Expected, the new course started early." Useful.
With it, you can ask "why did you say this?" about any line, and the agent does not tell you the same thing twice.
After the build: feedback, and how it learns
What a good colleague does: they take a correction once, and do not need it again.
The agent does not change its own brief. It suggests a change, and you decide. Under Make this agent better, Northwind's next report suggests a request. Sam sends it to Sasha:
Change the known event in the Finance Brief: Training's new course started in September, not October.
Sasha changes section 2 of the brief and records the reason in the work log. The next report judges Training with the launch in mind.
The eight sections in the app today
Today the Finance Brief in the app holds the same content under these headings: Products, Accounts, Suppliers, People, Product tags, Shared costs, Domains and Settings. An update will arrange it into the eight sections above. Your content stays the same.