Daily Founder Context
Personalized emails know a lot about the person they go to and nothing about the person who sends them. The founder's week lives in a private journal. This plan adds one Shareable section to the journal, copies only that section into the company OS every morning, and has every personalization routine read the copy. The emails get the founder's real week, and no send ever depends on reading the journal live.
Snapshot daily. Never read the journal at send time.
A send that reads the journal live depends on the journal being reachable and on the page looking right at that minute, and nobody can say afterwards what the email was built from. A daily snapshot in one table separates the two: the sync can fail without stopping a send, and every email points to the exact lines it used.
Define the problem
The first hand-written run of weekly learner emails worked because each email opened with something true about the founder's week: back from a retreat, a talk coming up, the article just published. Finding that took longer than writing any single email. Someone had to read the journal, decide what was safe to share, and paste it in. That does not repeat every week, and it cannot run without a person.
What goes wrong today
- The founder's week sits in a journal mixed with numbers, plans and private notes
- Each email routine would need its own way to read it, and they would drift apart
- A routine that reads the journal at send time fails when the journal is slow or the page is half written
- Nobody can show which line of the journal a sent email used
The goal
- By 7am every day, the founder's Shareable lines from the journal are in one company OS table
- Zero lines from outside the Shareable section are ever stored
- Every personalization routine reads the founder's week from that table, and from nowhere else
- A failed sync is visible on the routines page the same day
Discover the data
Most of the founder's week is already recorded somewhere. The journal is the one source that holds the human part, so it is the one this plan adds.
| Source | What it gives you | How it is used |
|---|---|---|
| Daily journal, Shareable section | Where the founder is, what they shipped, what they are learning, in their own words | Copied daily into the context table. The rest of the page is never stored |
| Events | Retreats and talks: where the founder has been and where they are speaking next | Read directly; already in the company OS |
| Published blog posts | What the founder is thinking about this week | Read directly; already in the company OS |
| Calendar | Everything, including client meetings and private appointments | Not used. Client names never go in an email, and the events table gives the same signal safely |
Design the workflow
Two jobs that never wait on each other. Once a day a small routine copies the shareable part of the journal into one table. Whenever a personalization routine writes an email, it reads that table and nothing else.
One fixed heading in the daily journal page, Shareable, with short lines under it: where they are, what they shipped, what they are learning, where they are speaking next. Written as if a client will read it, because one might. Everything else on the page stays private.
A launchd job on the always-on Mac mini, never a laptop that sleeps. It asks the journal for pages edited since the last successful run, so a line added to yesterday's page still arrives.
The routine keeps the blocks under the Shareable heading and drops the rest of the page before anything is written. No heading, no rows: a page without the section contributes nothing, which is the safe failure.
Each line becomes one row keyed by its journal page and block, so running twice changes nothing, an edited line updates its row, and a deleted line is archived rather than removed.
Every run writes one routine-run row: pages read, lines kept, rows changed, or the error. A missed morning shows up on the routines page the same day.
One helper returns the founder's last seven days of lines. The weekly learner emails, event follow-ups and the letter all read it, so they all tell the same week. If the last sync is more than 36 hours old the helper returns nothing, and the email is written without the founder's week rather than with a stale one.
| Column | What it holds |
|---|---|
| person | Whose week it is. The founder today; any leader who keeps a Shareable section later. |
| occurred on | The journal date the line was written under. |
| body | The line, exactly as written. |
| source page and block | Where it came from, so every email can point back to the line it used. |
| synced at | When the routine last saw the line. |
| archived at | Set when the line disappears from the journal. Rows are never deleted. |
Determine the ROI
What it costs
- One table, one migration through the normal review
- One small routine on the Mac mini, and one read helper
- A minute a day of the founder's time: two or three lines under one heading
What it returns
- The slowest part of the weekly learner emails, finding the founder's week, drops to zero
- Every personalized email, not just one routine, sounds like it came from a person having a real week
- Every email can show the exact lines it used, which is what makes a no-approval routine auditable
- The honest measure is reply rate: emails that open with the founder's week against those that do not
Deploy, and the definition of done
| Gate | What happens | Moves on when |
|---|---|---|
| Prototype | The table ships through the normal migration review. The sync runs by hand for a week. | Every row matches a line under a Shareable heading, and nothing else was stored |
| Pilot | The sync runs daily on the Mac mini. The weekly learner emails read the helper. | Two weeks of runs with no missed morning, and the emails used the lines without edits |
| Production | Every personalization routine reads the helper. None reads the journal. | The founder stops pasting their week into anything |
Guardrails, always on
- Only the Shareable section is ever read into the table. No heading means no rows
- Rows are archived, never deleted, so a sent email can always be traced to its line
- Context older than 36 hours is not used. A missing week is better than a stale one
- The routine runs on the always-on Mac mini, never a laptop
- No client names in the Shareable section, the same rule as every email
Definition of done
- The context table exists, with a data dictionary entry and comments on every column
- The routine has run every morning for two weeks, each run logged
- Running it twice in a row changes no rows
- The weekly learner emails read the founder's week from the helper, not from a person
- Every email that used a line records which one