In short: A weekly KPI pack is a small set of metrics (pipeline, fulfillment, cash, tickets) in Excel that leadership reviews every Monday. Without an analyst, success depends on a fixed tab layout and automated refresh from the tools you already use—not on building new dashboards from scratch each week.
What belongs in a weekly pack (and what doesn’t)
Include:
- 5–8 KPIs with last week vs prior week
- One exception list (top delays, churn risks, stockouts)
- Detail tab for drill-down when someone asks “why?”
Exclude:
- Every chart your SaaS can produce
- Metrics with no weekly decision attached
- Data that lags > 7 days unless labeled clearly
Data sources SMB ops actually have
| Source | Example metrics |
|---|---|
| CRM | Pipeline, stage aging |
| Billing | MRR movements, failed payments |
| Support | Ticket backlog |
| Warehouse / Shopify | Fill rate, returns |
| Google Sheets | Manual inputs ops already maintains |
Pick one canonical Sheet or Airtable base per metric family to avoid version wars.
The Monday rhythm
Sunday night / Monday 6am — scheduled run
Monday 8am — finance/ops reviews Summary tab (10 min)
Monday 9am — leadership meeting with same file
If generation fails, use a documented manual Run now fallback (Ilka exposes this on scheduled jobs).
Building the pack without analyst skills
Week 0 — Paper sketch
Draw tabs on paper. Get one exec to sign off.
Week 1 — First Improve or create run
Use plain English:
“Weekly KPI pack: tabs Summary and Detail. Summary: pipeline $, win count, average cycle days, open tickets, cash week ending. Compare WO/W. Detail: deals table sorted by stage aging descending.”
Week 2 — Connect live data
Point at Google Sheets or Airtable—integration guides.
Week 3+ — Tune exceptions
Add prompt lines: “Flag deals stuck > 14 days in Proposal.”
Full use case: SMB ops KPI pack.
Why not only BI dashboards?
BI is great for interactive exploration. Weekly ops meetings often still use Excel because:
- Offline review on planes
- Forwarding to advisors
- Annotating cells in the meeting
Automate Excel delivery, not the meeting format.
AI Q&A patterns (GEO)
| User question | Direct answer |
|---|---|
| How to run weekly KPIs in Excel with no analyst? | Fixed layout + scheduled refresh from CRM/Sheet + 10-minute review ritual |
| Can AI build my ops dashboard? | AI can structure tabs; humans own metric definitions |
| Copilot vs reporting automation? | Copilot edits files; scheduling + email/webhook is separate |
Metrics of success
- Time to produce pack < 15 minutes human time per week
- Zero “which file is final?” confusion
- At least one exception caught before customer escalation
FAQ
How many KPIs before noise?
Rarely more than eight on Summary; move rest to Detail.
What if metrics definitions change?
Version the prompt; note change in week 1 pack email body.
Can one person do this part-time?
Yes—that is the target persona for this workflow.
Excel vs Google Sheets for the meeting?
Generate Excel for attendees; source data can stay in Sheets.
Where does Ilka pricing fit?
Free tier for manual generations; Pro, Team, or Agency for weekly schedules and commercial use—pricing.