Internal Comms & Meetings

How to write a weekly team update as DTC Brand Founders

Internal Comms & MeetingsFor DTC Brand Founders3 apps12 steps~24 min to set up

Every Monday you spend 45 minutes rebuilding the same Slack message or Google Doc from scratch: pulling last week's ad spend from Meta, checking what Shopify actually shipped, guessing at refund volume from a Gorgias queue you haven't fully cleared, and estimating whether inventory will last another two weeks. The numbers live in five different tabs. You write the update in a sixth. Half the team doesn't read it anyway because it arrives Tuesday at noon. And next week you do it again.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor DTC Brand Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated weekly digest that pulls your Shopify orders, Meta Ads spend, and Klaviyo campaign performance into a single structured summary — drafted by Starch, sent to your team on a schedule you set.

A searchable archive of every weekly update and the decisions that came out of them, so 'what did we decide about the reorder threshold in February?' has an actual answer.

A project-management layer that converts action items from your update into assigned tasks with due dates — no separate tool, no copy-paste.

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

Project Management Knowledge Management Meeting Notes

Data sources & config

Shopify connects from Starch's integration catalog — the agent queries your orders and refund data live when the automation runs. Meta Ads connects from Starch's integration catalog for live spend and ROAS data. Klaviyo connects from Starch's integration catalog for campaign and flow revenue. Starch syncs your Slack data on a schedule so the digest posts to the right channel automatically. Knowledge Management stores the archive natively inside Starch — no external sync needed.

Prompts to copy

Every Monday at 8am, pull last week's Shopify orders (total revenue, units by SKU, refund count), my Meta Ads spend and ROAS from the integration catalog, and my Klaviyo email revenue. Draft a team update with a one-paragraph summary, a table of those numbers vs. the prior week, and a section called 'What needs attention this week.' Post it to our team Slack channel.

Create a Knowledge Management space called 'Weekly Updates' and auto-archive every weekly digest there with the date as the title. Make it searchable so anyone can find decisions we made in past updates.

After each weekly update is posted, extract any action items mentioned and create Project Management tasks — assign each to the person named, set a due date of Friday, and tag them 'weekly-update'.

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

Walkthrough

Step-by-step

1 Connect Shopify from Starch's integration catalog. The agent will query orders, SKU-level units sold, and refund count for whatever date range your automation specifies.

2 Connect Meta Ads from Starch's integration catalog. Confirm which ad account you want — if you run multiple brands, you can scope this to a single account or pull all of them and break them out by campaign.

3 Connect Klaviyo from Starch's integration catalog so the agent can pull email-attributed revenue, open rates, and unsubscribe counts for the prior week.

4 Connect Slack from Starch's integration catalog and tell Starch which channel gets the weekly digest — typically your general or ops channel.

5 Open the Project Management app (pre-built in the Starch App Store) and set up your team members so tasks can be assigned by name when the automation extracts action items.

6 Open the Knowledge Management app (pre-built in the Starch App Store) and create a space called 'Weekly Updates.' This is where every digest will be auto-archived and made searchable.

7 Describe the automation to Starch: 'Every Monday at 8am, pull last week's Shopify, Meta Ads, and Klaviyo numbers, draft a structured team update with a summary paragraph and a metrics table, compare to the prior week, call out anything that moved more than 15% in either direction, and post it to #ops-weekly in Slack.'

8 Add a second instruction: 'After posting, extract every action item from the update and create a Project Management task for each one — assign to the named person, due Friday, tagged weekly-update.'

9 Add a third instruction: 'Save the full text of every weekly update to the Weekly Updates space in Knowledge Management, titled with the date.'

10 Run it manually once to review the draft format. If the table layout or the 'What needs attention' logic isn't quite right, tell Starch in plain language — 'Add a row for return rate and move the Klaviyo section above the Meta section' — and it adjusts.

11 Once you're satisfied with the format, schedule it and let it run. Your Monday morning job is now reading the update instead of building it.

12 Two weeks in, check the Knowledge Management archive and the Project Management board together — this is your paper trail for what you said you'd do and what actually happened.

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

Week of March 17, 2026 — Spring campaign week 2

Sample numbers from a real run

Shopify revenue (7 days)	84,300
Shopify units shipped	1,140
Refunds issued	3,200
Meta Ads spend	18,500
Meta blended ROAS	4.6
Klaviyo email revenue	11,200
Net revenue after refunds	81,100

Starch fires at 8am Monday. It queries Shopify and sees $84,300 in revenue on 1,140 units — up 12% week-over-week — but also $3,200 in refunds, almost all on the 'Linen Oversized Tee' SKU, which is flagged in the 'What needs attention' section because the refund rate on that SKU jumped from 4% to 9%. Meta spend was $18,500 at a 4.6x ROAS, which is down from 5.1x the prior week; Starch calls that out as a 10% drop and surfaces it alongside the refund spike so the team knows to look at whether the creative hitting new audiences is sending the wrong size expectations. Klaviyo added $11,200, driven by the restock flow for a sold-out colorway. The full digest is posted to #ops-weekly by 8:03am, archived to Knowledge Management under '2026-03-17 Weekly Update,' and three tasks are created in Project Management: 'Investigate Linen Tee refund rate — assign to Maya, due Friday,' 'Pull top-performing ad creative from last week for creative review — assign to Dev, due Wednesday,' and 'Restock flow: check inventory threshold trigger — assign to you, due Thursday.' The team reads it before standup. Nobody asks you what the numbers were.

Measurement

How you'll know it's working

Blended ROAS (Meta spend vs. total attributed revenue, week-over-week)

Net revenue after refunds (not gross Shopify revenue)

SKU-level refund rate (catches quality or sizing issues before they compound)

Klaviyo-attributed revenue as a percentage of total (email channel health)

Action item completion rate from the prior week's update (team accountability)

Comparison

What this replaces

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

Manual Google Doc + Slack copy-paste

Free but costs 45+ minutes every Monday and produces an update nobody trusts because the numbers are always slightly stale by the time you post it.

Notion weekly template

Better structure, still requires you to pull every number manually — Notion doesn't know what your Shopify revenue was last week.

Triple Whale or Northbeam

Strong for paid media attribution specifically, but won't write your team update, manage tasks, or archive decisions — and adds another $500-$1,000/month to your stack.

Zapier + Slack + Google Sheets

Can automate parts of the data pull but requires you to build and maintain the zap logic yourself, and won't draft narrative copy or extract action items from it.

On Starch RECOMMENDED

One platform — project management, knowledge management, 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

Can Starch pull Shopify data directly, or does it need a third-party connector?

Shopify connects from Starch's integration catalog — the agent queries it live when your automation runs. You don't need a separate integration tool.

What if I also want inventory levels in the update — can Starch pull stock counts from Shopify?

Yes. When you describe the automation, add 'include current inventory levels for my top 10 SKUs by revenue' and Starch will query that data from Shopify the same way it queries orders. If your inventory lives somewhere else — like a 3PL portal with no API — Starch can automate through your browser to pull it, no API needed.

Does Starch store my Shopify and Meta data, or is it queried live each time?

For Shopify and Meta Ads connected from the integration catalog, data is queried live when the automation runs — it's not stored in Starch's database between runs. That means the numbers in your update are always current as of Monday morning, but Starch isn't building a historical data warehouse on your behalf. The weekly update archives themselves (text) are stored in Knowledge Management.

What if my team is split between Slack and email — can the update go to both?

Yes. Tell Starch to post to the Slack channel and also send a formatted email to your team distribution list. Starch connects directly to Gmail or Outlook and can send the digest to both places in the same automation run.

Is Starch SOC 2 certified? We're cautious about connecting ad accounts and Shopify to third-party tools.

Starch is not SOC 2 Type II certified yet — that's on the roadmap. If your brand is at a stage where SOC 2 is a hard requirement for any new tool integration, that's worth knowing upfront. Most early-stage DTC founders we work with are comfortable connecting Shopify and ad accounts given the read-only nature of the data pull, but we'd rather you make that call with accurate information.

Can I customize the update format — like adding a section for customer support ticket volume?

Yes, and this is where Starch's composability matters. Start with the basic automation described above, then tell Starch 'add a section for customer support' and connect Gorgias or Zendesk from Starch's integration catalog. The agent will query open ticket count, average response time, or whatever metric you specify, and add it to the template. You describe the change; Starch rebuilds the automation.