Premium · Numbers and blind spots
Data Analyst
Deliver one page every Monday on the goals that are slipping.
It reads the numbers your client never opens: billing, the product database, analytics. Every Monday it writes the Blind Spot Report, the few goals most off track, each with its number, its source and one move for the week. You run it and deliver the page.
- 2 weekdays
- 1 weekly
- 2 monthly
The deliverable
The page your client reads every Monday.
A sample report for Lanternfield Studio, a made up design subscription business. Every number on it is fictional.
Blind Spot Report, week of 2026-10-19
Trials are still not turning paid: 2 new paid customers in 30 days against a target of 12 (money.read: S-billing new paid subscriptions report, read 2026-10-19).
The one you would least want to hear
Trials are not turning paid · goal G-1 · 2 against a target of 12 (83% short of target) · source: money.read: S-billing new paid subscriptions report, read 2026-10-19
Why it leads: seen on 3 Mondays and still not acknowledged, and a finding nobody has answered is the costliest kind.
Move: Draft the reminder email for the fifth day of the trial, three sentences, in one sitting · owner: you
Key: DAT-paid-new-trial
Also off track
1.Cancellations are above your ceiling · 5 vs 3 · source: money.read: S-billing cancelled subscriptions report, read 2026-10-19 · move: Read the reasons for cancellations since 2026-10-14, when the pause option went live, and name the most common one · owner: you · key DAT-cancellations-month
2.Newsletter growth is behind · 46 vs 100 · source: analytics.read: S-site-analytics newsletter signup event, read 2026-10-19 · move: Put the signup form on the three most visited pages · owner: you · key DAT-newsletter-new-signups
For other employees
·This report: reports/blind-spot-2026-10-19.md, written 2026-10-19, window 2026-09-19 to 2026-10-18
·Issue register: issues/register.jsonl, appended 2026-10-19
·Escalations: issues/escalations.json, written 2026-10-19
How to read it
Every number carries its source
Each figure sits beside the connection, the report it came from and the date it was read. A number that cannot be traced back is a defect.
The lead says why it leads
Three rules in order: an issue raised on two Mondays with no answer, then the biggest miss on the top priority goal, then the biggest miss overall.
Small numbers stay small
Under 30 events in a window it reports counts and days, never a rate. Two paid customers out of nineteen trials is a fact.
Zero to five issues
A quiet week is one line. It never pads the page to look busy, and every issue gets one owner and one move.
Five scheduled routines behind one Monday page.
Weekday readings feed the Monday report, and the monthly runs keep every definition honest.
- Weekdays
Anomaly read
Reads every metric in the dictionary through its read only route, writes one dated reading per metric with its source, and flags each one that left its usual range.
- Weekly
Blind Spot Report
Every Monday, compares the last 30 days against the goals and writes zero to five issues ranked by how far each goal misses its target, leading with the one nobody wants to hear.
- Weekdays
Standup
Folds the owner's one line notes on each issue into the register, rebuilds the dashboard, and writes the morning brief only when something changed.
- Monthly
Intake and map
First run finds the metric sources, writes the metric dictionary, builds the dashboard and registers the schedule. Each month after, it re-tests every definition and recomputes the usual ranges.
- Monthly
Issue review
Re-measures every open issue, names the ones whose numbers recovered, and scores its own calls for the month. Only the owner ever marks an issue fixed.
Safe to point at a client's billing and database.
- Read only routes: billing on a restricted key, the database on a read only role, one single read at a time.
- Nothing in the kit sends, spends, publishes or changes anything in the systems it reads.
- Counts and totals only. No customer name, email or identifier lands in any file it writes.
- The goals stay the owner's. No routine writes the goals file, and only the owner marks an issue fixed.
What it needs from the client
- The goals, in the owner's own words: a metric, a target, a date and a priority for each. Three is plenty. The kit drafts candidates beside the file and never writes the goals itself
- At least one read only connection to where the numbers live: billing on a restricted key, the product database on a read only role, or analytics
- A local working folder outside OneDrive, Dropbox, Google Drive and iCloud, on a machine that is awake at the times in SCHEDULE.md
Free with an account
Run the Monday report by hand, free.
The Monday Blind Spot Report prompt pack is the report as four pieces you paste into a desktop agent app: the goals file, the issue log, the Monday report prompt and the fix research prompt. Run it on a client's numbers this week.
- 1. The goals file
- 2. The issue log
- 3. The Monday report prompt
- 4. The fix research prompt
- Rules that keep the page honest
- Corrections
Free with an account
Get the prompt pack.
- Three goals, each with a number
- A log that remembers what was decided
- The prompt that writes the Monday page
- A research prompt with links you can check
No card. Google sign in works too. Already a member? Log in
Premium, inside the club
Delivered inside the club under the member license.
Arrives for members in November. Pro yearly and Lifetime download every premium employee; on Pro monthly it counts in the fair use allowance of 3 premium downloads a month.
- Customize it to fit each client you set it up for.
- Install and run it inside a client's environment, under your own brand, at a price you set.
- Run it on your own machine and deliver the Monday page as a managed service.
- Never hand the kit itself to a client, publish it, or list it as a product.
Running a business and want it set up for you instead? Done for you AI Employees