Capability template for finance and accounting
Investor update
Each month or quarter, the founder gets a drafted update for investors: the headline, key figures against plan and last period, cash and runway, wins, problems told plainly with what is being done, and specific asks. Every figure comes from the company's own reports. The founder approves and sends it.
The outcome
Your investors hear from you on time, in the same shape every period, and they hear the hard news from you first. The draft opens with your headline, then the same standing figures as last time, each set against plan and against the last period, so a reader sees at once what moved. Cash and runway are worked out from your cash report, with money from investors kept out of the burn and funding you expect but have not banked shown on its own line.
Every figure that is well behind plan lands under Problems, with your explanation and what you are doing about it, or with a plain marker where your explanation is still missing. Last period's problems and asks are followed up, so investors see that what you raised was handled. Each ask is checked for what you want, from whom and by when, because a named kind of person and a date give an investor something to do.
Gaps come first, as questions: a headline that skips the period's worst number, a figure that differs from the one you sent last time, an ask with no deadline or no clear target. The capability prepares. You write the words that matter, settle the questions, and send the update yourself.
Who starts the work, and when
The founder or CEO starts it, or whoever assembles the update for them: the finance lead, a chief of staff or an operations lead. They run it on the same day each month or quarter, once the period's billing, sales and cash reports are final and the founder has written a few notes, and again after the questions are settled.
Between regular updates, when news should not wait, it drafts a shorter note with the news, cash and runway, and any asks.
What they supply
- The figures: an export of the standing metrics, each with this period, last period, plan, which direction is better and the report it came from.
- The cash report for the last three months: opening and closing cash, funding received, other money in and money out.
- The founder's notes: the headline, wins, problems with their causes and what is being done, news on what the last update raised, asks and team changes.
- The last update as sent, to follow up on what it raised and check last period's figures.
- Your settings: the period, the greeting and sign-off, and the thresholds you want flagged.
No accounting system, bank or mailbox is connected, and no password is ever asked for. Everything is pasted or attached by a person.
What comes out
- Questions to settle, for the founder or the finance lead, each naming the section it affects.
- The update itself, ready to approve: headline, the numbers, cash and runway, wins, problems and what is being done, since the last update, asks and team, ending with the founder's sign-off.
- Checks for the founder: the word count, where every figure came from, any figure that is the founder's own and in no report, and anything left out and why.
Good looks like this: a reader who stops after the headline knows the period's best and worst news, and every number in the update can be traced to a report in under a minute.
An invented example
Illustrative example with invented data. The company, its customers, its people, its investors and every figure below are invented. Quellinby Routes is an invented 18-person company selling route-planning software to bakeries and food wholesalers. Its founder and CEO sends investors an update each month; the finance lead, who works part time, owns the reports. People are referred to by role.
The inputs come first, in full, so the template can be run on them. The draft the capability prepares follows.
The inputs
1. Settings
Company: Quellinby Routes
Period: October 2026, monthly. Type: regular.
Founder: signs as "Founder and CEO, Quellinby Routes".
Greeting: Hi all,
Confidentiality line, variance threshold, runway alert, word limit: use the defaults.
Today: Wednesday 4 November 2026. Planned send date: Thursday 5 November 2026.
2. Figures export, October 2026
Metric | Unit | This period | Last period | Plan | Better when | Source
Monthly recurring revenue | $ | 182,400 | 171,900 | 185,000 | higher | Billing report, October 2026
Paying customers | count | 412 | 396 | 410 | higher | Billing report, October 2026
New customers | count | 24 | 31 | 28 | higher | Billing report, October 2026
Customers lost | count | 8 | 5 | 6 | lower | Billing report, October 2026
Revenue churn | % | 2.9 | 1.8 | 2.0 | lower | Billing report, October 2026
Sales pipeline | $ | 640,000 | 590,000 | 600,000 | higher | Pipeline report, 31 October 2026
3. Cash report, August to October 2026
Month | Opening cash | Funding received | Other cash in | Cash out | Closing cash
August 2026 | 2,460,000 | 0 | 158,000 | 298,000 | 2,320,000
September 2026 | 2,320,000 | 250,000 | 166,500 | 311,500 | 2,425,000
October 2026 | 2,425,000 | 0 | 174,200 | 322,700 | 2,276,500
4. The founder's notes, Tuesday 3 November 2026
Headline: Strong month: MRR up 6% to $182K and pipeline at a record $640K.
Wins:
- Signed our largest customer yet, a 38-location bakery chain, at $4,200
MRR from November. Not cleared to name them.
- Pipeline at a record $640K.
- Self-serve setup wizard shipped on 14 October.
Problems:
- We lost 8 customers. Five were small bakeries closing for good or
pausing for the season. Three were in one co-op buying group and moved
to a competitor that bundles routing with ordering. Doing: the ordering
integration is brought forward and in testing; the CTO ships it by
15 December. The head of customer success is calling all 14 remaining
accounts in co-op groups by 20 November.
Since the last update:
- Onboarding: the wizard shipped on 14 October; October's new customers
reached their first route in 12 days on average (target 10).
- Wholesaler intros: thank you for three introductions; one became a
pilot with a regional wholesaler, who asked us not to name them yet.
Asks:
- Intros to heads of operations at food wholesalers running 20 or more
trucks in the Midwest, by 30 November.
- Any help finding people.
- 20 minutes with anyone who has negotiated a venture debt line, before
we sign in December.
Team: Joined: senior backend engineer (October). Left: support specialist
(October), moving to be closer to family. Open roles: account executive;
customer success manager.
Funding: September's $250K was the final tranche of our seed extension.
We have a verbal yes on a $400K venture debt line from a lender, expected
to close in December.
5. The last update as sent, Tuesday 6 October 2026
Subject: Quellinby Routes investor update: September 2026
Headline: MRR up 5% to $171.9K; onboarding is now our bottleneck.
The numbers, September 2026:
- Monthly recurring revenue: $171,900
- Paying customers: 396
- New customers: 31
- Customers lost: 5
- Revenue churn: 1.8%
- Sales pipeline: $585,000
Problems: Onboarding is slow. New customers take 19 days on average to
run their first route, against a target of 10. Doing: a self-serve setup
wizard, shipping in October.
Asks: Introductions to operations leads at regional food wholesalers.
The draft
INVESTOR UPDATE: Quellinby Routes, October 2026
DRAFT for the founder and CEO. NOT READY TO SEND: 9 questions to settle.
Prepared Wednesday 4 November 2026 from: figures export (6 rows, billing report, October 2026; pipeline report, 31 October 2026); cash report (August 2026 to October 2026); founder's notes (3 November 2026); last update (6 October 2026).
Type: regular. Settings used: variance threshold 10%; runway alert 12 months; word limit 600. Defaults used: variance threshold, runway alert, word limit, confidentiality line.
TO SETTLE BEFORE SENDING, for the founder and CEO only; remove before sending: 9
1. Headline, for the founder: new customers, customers lost and revenue churn are well behind plan, and the headline mentions none of them; and "record" is in no report supplied. Reword it, or keep it as written? Confirm "record", or supply the report behind it.
2. The numbers, for the finance lead: the export gives September's sales pipeline as $590,000; the September update said $585,000. Which is right? If $590,000 stands, the update will say September's figure was revised.
3. Cash and runway, for the founder: the $400K of the venture debt line is in no report supplied. Confirm it, or supply the report behind it.
4. Wins, for the founder: "largest customer yet", the 38 locations, the $4,200 MRR and the "record" pipeline are in no report supplied. Confirm each, or supply the report behind it.
5. Problems, for the founder: new customers were 24 against a plan of 28 (14.3% worse) and 31 in September. What caused it, and what is being done, by whom and by when?
6. Problems, for the founder: the notes explain the customers lost but do not name revenue churn, which is grouped with them below. Does the same explanation cover revenue churn of 2.9% against a plan of 2.0%?
7. Problems, for the founder: the split of the 8 customers lost (five small bakeries, three in one co-op buying group) and the 14 remaining co-op accounts are in no report supplied. Confirm each, or supply the report behind it.
8. Since the last update, for the founder: the 12-day average to a first route, and the three introductions of which one became a pilot, are in no report supplied. Confirm each, or supply the report behind it.
9. Asks, for the founder: ask 2, "Any help finding people", does not say which role, from what kind of person, or by when. The open roles are account executive and customer success manager.
---------------- THE UPDATE ----------------
Subject: Quellinby Routes investor update: October 2026
Confidential: for Quellinby Routes investors only. Please do not forward.
Hi all,
HEADLINE
Strong month: MRR up 6% to $182K and pipeline at a record $640K. HEADLINE CHECK: new customers, customers lost and revenue churn are well behind plan, and the headline mentions none of them; "record" is in no report supplied.
THE NUMBERS: October 2026, against plan and September
- Monthly recurring revenue: $182,400 (plan $185,000; September $171,900). Behind plan: 1.4% worse than plan; up 6.1% on September.
- Paying customers: 412 (plan 410; September 396). On or ahead of plan: 0.5% better than plan; up 4.0% on September.
- New customers: 24 (plan 28; September 31). Well behind plan: 14.3% worse than plan; down 22.6% on September.
- Customers lost: 8 (plan 6; September 5). Well behind plan: 33.3% worse than plan; up 60.0% on September.
- Revenue churn: 2.9% (plan 2.0%; September 1.8%). Well behind plan: 0.9 points worse (45.0%); up 1.1 points on September.
- Sales pipeline: $640,000 (plan $600,000; September $590,000). On or ahead of plan: 6.7% better than plan; up 8.5% on September. RESTATED: the last update gave $585,000.
CASH AND RUNWAY
Cash at 31 October 2026: $2,276,500.
Average net burn, August to October 2026: $144,500 a month (August $140,000; September $145,000; October $148,500).
Runway: 15.7 months at that rate.
Funding received in the three months: $250,000, September, the final tranche of the seed extension.
Not counted: a verbal yes on a $400K venture debt line from a lender, expected to close in December.
WINS
- Signed our largest customer yet, a 38-location bakery chain, at $4,200 MRR from November.
- Pipeline at a record $640K.
- Self-serve setup wizard shipped on 14 October.
PROBLEMS
- Customers lost and revenue churn: 8 customers lost against a plan of 6, and revenue churn of 2.9% against 2.0%. Cause: five were small bakeries closing for good or pausing for the season; three were in one co-op buying group and moved to a competitor that bundles routing with ordering. Response: the ordering integration is brought forward and in testing, CTO, by 15 December; calls to all 14 remaining accounts in co-op groups, head of customer success, by 20 November.
- New customers: 24 against a plan of 28, and 31 in September. Cause: CAUSE NEEDED. Response: RESPONSE NEEDED.
SINCE THE LAST UPDATE
- Onboarding is slow, raised 6 October: the wizard shipped on 14 October; October's new customers reached their first route in 12 days on average, against a target of 10.
- Introductions to operations leads at regional food wholesalers, raised 6 October: thank you for three introductions; one became a pilot with a regional wholesaler, who asked us not to name them yet.
ASKS
1. Intros to heads of operations at food wholesalers running 20 or more trucks in the Midwest, by 30 November.
2. Any help finding people. MAKE SPECIFIC: which role, from what kind of person, and by when.
3. 20 minutes with anyone who has negotiated a venture debt line, before we sign in December.
TEAM
Joined: senior backend engineer, October. Left: support specialist, October. Open roles: account executive; customer success manager.
Founder and CEO, Quellinby Routes
---------------- END OF THE UPDATE ----------------
CHECKS, for the founder and CEO only; remove before sending
Words, headline to sign-off: 500 of 600.
Cash tie-out: August to October 2026, each month ties and runs on from the last.
Figures traced: monthly recurring revenue, paying customers, new customers, customers lost, revenue churn: billing report, October 2026; sales pipeline: pipeline report, 31 October 2026. Cash: cash report, August to October 2026.
Founder's figures not in any report: "record", Headline and Wins; $400K debt line, Cash and runway; "largest customer yet", 38 locations, $4,200 MRR, Wins; the five and three customers lost, 14 accounts, Problems; 12 days, three introductions and one pilot, Since the last update.
Metrics well behind plan: new customers, customers lost, revenue churn. Each under Problems: yes.
Left out of the update: the reason the support specialist left (a person's circumstances); the bakery chain's name, which the notes say is not cleared, so the chain is described.
Draft only. Nothing has been sent, and no figure or record has been changed.
Where it fits
- Finance and accounting, which owns the reports behind every figure and the runway.
- Leadership, where the founder keeps investors' trust between funding rounds.
- Software technology, where venture-backed companies report recurring revenue, churn and runway every month.
- Consumer brands, where founders with angel and early-stage investors report sales, margins and stock.
- Hardware and physical technology, where long build cycles make runway the figure investors watch most closely.
- Startups & new ventures, where a steady update habit set early makes the next raise easier.
- Growth & scaling, when more investors, more metrics and more news make a fixed shape worth having.
What has to change for your company
Choose your standing metrics and their order once, and keep them; the capability shows every one every period. Map your reports' column headings to the ones it expects, or keep its defaults. Set the variance from plan that counts as well behind, the runway that should always be raised as a problem, and how long the update may be. Agree how your finance lead counts net burn, which customers may be named and who gives that permission, and where the sent update is kept so the next one can follow it up. It runs in ChatGPT, Claude, Copilot or Gemini; decide which reports the assistant may be given.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried on its invented example in Claude on 10 November 2026 in two runs; the template and example had small edits after the first, and the record of the second, with the findings of the first, is published with it. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on two or three past periods whose updates you already sent, plus hard cases written in advance: a cash report that does not tie, a metric well behind plan with no explanation, a figure that differs from last time, a metric that disappears, an ask with no deadline. The finance lead checks every figure against its report before the founder relies on the draft. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Bring a real piece of this work to a call. We’ll walk through what it takes to fit this capability to your rules, prove it on your work and put it in the hands of the roles that own it.