Owner Reporting: The Weekly Doc That Replaces Three Meetings

Most small business owners manage their business through feel and ritual.

The ritual usually involves opening several tabs on Monday morning: Stripe for revenue, the CRM for leads, maybe a spreadsheet someone updates on Fridays, a Slack channel where the team posts status updates. The feel is what you assemble from all of those: a rough sense of how things are going.

It works. But it's slow, it's inconsistent, and the information is always a little stale.

A weekly reporting system replaces the ritual with a document. Not a dashboard you have to remember to open, but an email that arrives Monday morning before you sit down, already assembled, already formatted, ready to act on.

Here's what that document looks like and how to build it.

---

The metrics that actually matter

Before building anything, it's worth getting clear on which numbers drive decisions at your business. The answer varies (a solo consultant's key metrics are different from a service business with a team of 10), but there are categories that show up everywhere.

Lead and sales metrics

• New leads this week (by source)
• Lead-to-call conversion rate
• Calls booked vs. calls completed
• Deals closed this week / month-to-date

Revenue metrics

• Revenue this week / month-to-date / year-to-date
• Outstanding invoices (total and by client)
• Average deal size (trending up or down)

Operational metrics

• Open client projects and their status
• Team capacity (hours billed vs. hours available)
• Any escalated client issues

Retention and relationship metrics

• Clients who haven't been contacted in X days
• Upcoming renewals or contract end dates
• Net Promoter or satisfaction signals if you collect them

Not all of these apply to every business. The point is to identify the 5–8 numbers that, if you saw them every Monday morning, would tell you whether you're on track or off track, and what you need to pay attention to this week.

---

What the weekly doc looks like

Here's a sample structure for a service business that does consulting or agency work:

Week of May 26: Summary

LEADS
New leads: 6 (4 from website, 2 from referral)
Calls booked this week: 3 (from 6 leads = 50% conversion)
Open leads in follow-up: 11
Oldest open lead: 14 days (Sarah M., bookkeeping inquiry)

REVENUE
This week: $4,800
Month to date: $18,200 (goal: $25,000)
Pace to goal: 73% with 6 days left

OPERATIONS
Open projects: 5
On schedule: 4
Behind: 1 (Reynolds Media onboarding, needs action)
Capacity: 62% this week (team of 3)

ATTENTION NEEDED
- Sarah M. inquiry is 14 days old with no response, check lead system
- Reynolds Media onboarding is behind, check in today
- Invoice #047 ($2,400) 14 days overdue, send reminder

Week at a glance: Strong lead volume, revenue slightly behind pace, one project needs a nudge. Nothing critical.

The "Week at a glance" is the most valuable sentence. It's a human-readable one-liner that captures what matters. Writing it forces you to actually synthesize the numbers, which is the point.

---

Where the data comes from

A working reporting system pulls from real sources automatically. Here's a typical data map:

Metric	Source
New leads	Website form webhook → Supabase
Calls booked	Calendly API → count new bookings
Revenue	Stripe API → sum charges in date range
Outstanding invoices	Stripe or QuickBooks API
Open projects	Notion, Airtable, or Linear API
Oldest open lead	Supabase query on lead table

The key insight: most of this data already exists somewhere. It's not that you don't have it, it's that nobody has wired it together into a single view.

The reporting system is that wiring. A scheduled job (runs Sunday night or early Monday morning) queries each source, assembles the data, formats the document, and sends it to your email.

---

The "attention needed" section

This is the part that makes the report actually useful rather than informational.

Most reporting systems show you data. The attention section shows you what to do about the data. It's generated by applying rules to the numbers:

• If any invoice is more than 7 days overdue → surface it
• If any lead has been in the sequence for more than 10 days without a response → surface it
• If revenue pace is below X% of goal with fewer than 7 days left in the month → surface it
• If a project's scheduled completion date is in the past and it's not marked complete → surface it

These rules aren't complex to write. They're just queries: "Show me anything that matches condition X."

The result is a prioritized list of things that need human attention, not buried in the data, not requiring you to go looking for them.

---

Building it vs. buying a tool

There are off-the-shelf reporting tools. Databox, Geckoboard, Tableau, and dozens of others. Some of them are excellent.

The case for a custom build is specific: it applies when your metrics don't fit neatly into generic categories, when your data lives in non-standard places, or when the attention section needs custom logic that generic tools can't apply.

Custom doesn't mean complex. The system described here (a scheduled job, a data aggregation function, an email formatter) is typically a week of build time. The output is a system you fully own, not a subscription that shows you dashboards.

---

Sample build spec

If you were to scope this project, here's what it would include:

Data connections (read-only API access to):

• Stripe (revenue, invoices)
• Your lead source (Supabase, HubSpot, etc.)
• Your calendar tool (Calendly, Cal.com)
• Your project tracker if you use one

Logic layer:

• Data aggregation functions (sum, count, filter by date range)
• Attention rules (thresholds that trigger a "needs action" flag)
• Report assembly (format the document)

Delivery:

• Scheduled cron job (Sunday night, 10pm)
• Email delivery via Resend
• Optional: Slack DM or Telegram message

Storage:

• Supabase to keep a history of weekly reports

Total complexity: a first build ($800–$1,500), 1–1.5 weeks to build.

---

The real value

The weekly report doesn't replace judgment. It informs it. What it replaces is the cognitive overhead of assembling the picture manually, every Monday, from scattered sources.

When the picture is already assembled, you can spend the first 10 minutes of your week deciding what to do about it, not building it.

That's the shift. Less time on information assembly, more time on decisions and action. For most business owners, that shift is worth far more than the cost of building it.

The discovery form is where we scope this kind of system, 15 minutes to figure out what your specific data map looks like and what a first build would cost.