Internal Comms & Meetings

How to write a weekly team update as Small Finance Teams

Internal Comms & MeetingsFor Small Finance Teams3 apps12 steps~24 min to set up

Every Friday afternoon, someone on your three-person team spends 90 minutes pulling this week's numbers together for a weekly update that goes to the CFO, the CEO, and maybe the board observer. You pull cash from Plaid or a Stripe payout report, check the QuickBooks AP aging for anything overdue, manually copy AR balances into a Google Sheet, write a paragraph about where the 13-week cash forecast stands, and then format all of it into a Slack message or a Google Doc that half the leadership team ignores anyway. Nothing is wrong with any individual data source — the problem is that stitching them together by hand every single Friday is a full hour of a finance analyst's week that could be spent on actual analysis.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Finance Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A weekly finance update that auto-drafts itself every Friday morning by pulling live data from QuickBooks, Stripe, and Plaid — cash position, AP aging, AR outstanding, and a one-paragraph cash flow narrative — so your team reviews rather than builds it.

An email agent that formats the final update and sends it to your distribution list (CFO, CEO, board observer) with one click, including a subject line that flags whether cash is up or down week-over-week.

A meeting notes and action-item tracker tied to your weekly finance sync, so any follow-up questions from leadership get logged and assigned before the call ends.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Investor Reporting Meeting Notes

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, bills, payments, vendors — all entity-level data) and syncs your Plaid transaction and balance data on a schedule. Stripe charges, payouts, and subscription data sync on a schedule as well. Gmail is connected so Starch can draft and send the weekly update email from your existing account. Meeting Notes captures your Friday finance sync via real-time transcription. Project Management tracks the action items that come out of that meeting.

Prompts to copy

Every Friday at 8am, pull this week's ending cash balance from Plaid, total AR outstanding from QuickBooks, total AP past-due from QuickBooks, and net Stripe payouts received this week. Write a 3-paragraph weekly finance update: paragraph 1 is cash position and week-over-week change, paragraph 2 is AR and AP status with any items more than 30 days overdue flagged, paragraph 3 is one sentence on where we stand against the 13-week cash forecast. Format it as a Slack message and also as an email draft ready to send to cfo@company.com and ceo@company.com.

When the weekly finance update email is drafted, check if cash is lower than last week. If it is, prepend the subject line with '[Heads Up]'. If cash is higher, use '[Finance Update]'. Send me the draft for review before sending.

After our Friday 9am finance sync, transcribe the call, extract all action items, assign each one to a name mentioned in the meeting, and create a task in Project Management for each with a due date of the following Friday unless another date was mentioned.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect QuickBooks under Starch's scheduled-sync providers — invoices, bills, payments, and vendor data will refresh automatically so Friday's pull is always current.

2 Connect Plaid so Starch syncs your operating account balances and categorized transactions on a schedule; this gives the weekly update its cash position and week-over-week delta without any manual export.

3 Connect Stripe so net payout data and any subscription revenue recognized this week flows into the update automatically alongside the bank data.

4 Start from the Investor Reporting app in the App Store as your base data surface — it already knows how to pull from QuickBooks, Stripe, and Plaid and display the numbers your leadership team wants to see.

5 Type your first prompt into Starch describing the exact weekly update format your CFO expects — cash, AR aging, AP past-due, and a narrative paragraph. Starch drafts the automation; you review the output once and adjust the format if anything is off.

6 Set the automation to run every Friday at 8am so the draft is waiting in your Gmail by the time your team starts their day — connect Gmail from Starch's integration catalog so the agent can create a ready-to-send draft in your actual inbox.

7 Add the subject-line logic: tell Starch to flag '[Heads Up]' when cash is down week-over-week and '[Finance Update]' when it's flat or up — this takes one additional prompt line and means leadership can triage the email before they open it.

8 Wire the Email Triage app (Founder Inbox) to your CFO's inbox so any reply questions from the CEO or board observer get auto-triaged and summary-drafted, not buried under vendor emails during close week.

9 Before your Friday 9am finance sync, open Meeting Notes in Starch and start the transcription — the app captures the call in real time and generates a summary with key decisions highlighted.

10 At the end of the meeting, tell Starch: 'Extract all action items from this meeting, assign them to the person mentioned, and create a task for each due next Friday.' The Project Management app receives those tasks automatically.

11 At end of quarter, the same data connections that power the weekly update also feed your Investor Reporting app — the board pack that currently takes three days gets most of its raw numbers from the same QuickBooks, Stripe, and Plaid syncs you already set up here.

12 Review the weekly update draft before sending the first three times; once you trust the output, flip the automation to send automatically and reclaim that 90 minutes of Friday-afternoon assembly work.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Friday April 18, 2026 — Weekly Finance Update

Sample numbers from a real run

Ending cash (Plaid, operating account)	1,847,200
Week-over-week cash change	-42,300
AR outstanding > 30 days (QuickBooks)	214,500
AP past-due > 30 days (QuickBooks)	38,900
Net Stripe payouts received this week	91,400

By 8:05am Friday, the weekly update draft is already in the Gmail drafts folder with subject line '[Heads Up] Finance Update — April 18.' Cash is down $42,300 week-over-week, driven by a $61,000 payroll run on Wednesday that hit before the Thursday Stripe payout of $91,400 cleared — Starch's narrative paragraph explains the timing gap so the CFO doesn't fire off a Slack at 9am asking why cash dropped. The AR section flags two invoices over 30 days: a $130,000 invoice to Acme Corp (net-60, still within terms) and a $84,500 invoice to Meridian Partners that hit day 38 yesterday — that one gets bolded automatically because it's outside terms. AP shows $38,900 past-due, all from one vendor (cloud hosting), flagged for the AP approval call. The finance analyst reviews the draft in three minutes, adjusts one number where a wire posted after the Plaid sync cutoff, and hits send. The Friday 9am call runs 22 minutes; Meeting Notes captures it, pulls four action items, and creates four tasks in Project Management assigned to the right team members before anyone has closed their laptop.

Measurement

How you'll know it's working

Time to produce weekly finance update (target: under 15 minutes of human touch, down from 90 minutes of manual assembly)

AR days outstanding and percentage of AR past-due by aging bucket (30/60/90+)

Week-over-week cash delta with variance explained (not just the number — the reason)

Action-item close rate from weekly finance sync (tasks created vs. tasks completed by the following Friday)

CFO and CEO email reply rate on the weekly update — a proxy for whether the format is actually useful

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Sheets + manual export

Copying data from QuickBooks, Stripe, and Plaid into a Sheet every Friday is reliable but takes 60-90 minutes and breaks every time a report format changes upstream.

QuickBooks built-in reports emailed on a schedule

QuickBooks can email canned reports but they're ledger-formatted, not narrative, and can't combine Stripe payout data or Plaid cash balances into one leadership-friendly update.

Notion + manual weekly doc

Notion is fine for writing the narrative but someone still has to pull the numbers manually each week — the data doesn't flow in automatically from your ERP or bank.

Mosaic or Cube (FP&A software)

Purpose-built FP&A tools give you beautiful dashboards but cost $2,000-$5,000/month, require a multi-week implementation, and are overkill if you just need a weekly update email and a Friday call with action items tracked.

Zapier + Google Sheets + Gmail

You can approximate this workflow in Zapier, but building it requires a developer or a Zapier-fluent ops person, it breaks when field names change in QuickBooks, and it produces no narrative — just raw numbers.

On Starch RECOMMENDED

One platform — investor reporting, founder inbox, meeting notes all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Our QuickBooks is on QuickBooks Online but we use the P&L report view to check gross margin by product line every week. Can Starch pull that?

Honest answer: QuickBooks report views — P&L, Transaction List, Vendor Expenses — are temporarily disabled while an upstream connector issue gets fixed. Entity-level data (invoices, bills, payments, vendors, journal entries) syncs normally. For the weekly update, cash, AR aging, and AP aging all work fine today. For a gross-margin-by-product-line view, you can build a custom Starch app that calculates it from the invoice and journal entry entities — it's just one more prompt to describe what you want. The report view fix is on the roadmap.

We use NetSuite, not QuickBooks. Does this still work?

Yes. Starch syncs your NetSuite data on a schedule — invoices, expenses, journal entries, balance sheets, and income statements. The weekly update recipe works the same way; you just tell Starch to pull from NetSuite instead of QuickBooks when you describe what you want to build. The Investor Reporting app in the App Store already lists NetSuite as a primary connection.

Can Starch actually send the email automatically, or does someone have to click send every Friday?

Both modes work. You can have Starch create a Gmail draft that a human reviews and sends with one click — which is what most finance teams prefer the first month while they're building trust in the output. Or you can flip it to fully automated after you've reviewed enough drafts to know the numbers are right. Gmail is connected through Starch's integration catalog so the agent can draft and send from your existing account.

Is my financial data stored in Starch? We're nervous about QuickBooks and Plaid data living somewhere new.

The scheduled-sync connections (QuickBooks, Plaid, Stripe, NetSuite) do sync and store data in Starch's database so the automation can run on a schedule without querying your ERP in real time. Starch is not SOC 2 Type II certified today — that's worth knowing if your company has formal data governance requirements. If that's a blocker, it's worth asking the Starch team directly about their security posture; it's a known item on their roadmap.

We also need someone to chase AR — sending reminder emails to customers who are 45 days past due. Can Starch do that?

Yes. Describe it to Starch: 'Every Monday morning, pull all invoices from QuickBooks that are more than 45 days past due, draft a reminder email to the billing contact on each invoice, and put the drafts in my Gmail for review.' Starch builds that automation from the same QuickBooks sync that powers your weekly update. If you want to find billing contact emails for customers you don't have on file, Starch can also query contacts through its integration catalog or automate a lookup through your browser — no separate tool needed.

What if our 13-week cash forecast lives in a Google Sheet? Can the weekly update pull from that too?

Google Sheets is reachable from Starch's integration catalog — the agent queries it live when your automation runs. So yes: you can tell Starch to pull this week's forecast row from your 13-week model in Sheets and include the variance against actual cash in the weekly update narrative. You don't have to rebuild the forecast in Starch to get the benefit.