Skills
Every skill in the sb-lab repo, so you can see what Claude can already do before asking for something new.
Who built each skill and who keeps working on it, from git history.
Repo File Tree
Context and skill files by folder. Staleness is days since last edit.
SB-suggestions
Everything Claude suggests, newest first: SP-upgrades to how we run things (sp-upgrades.md), Bryan-upgrades to how Bryan works (bryan-upgrades.md, every Friday), new skills (skill-suggestions.md) and content ideas from today's Radar.
Sponsorship Pipeline
Loading…
Movement
Renewals to start
Deal board
Every open deal, flowing left to right toward the win. Click a card to open it in Attio.
Campaign Tracker
Where every live campaign is up to, and what is still owed. Deliverables run left to right toward delivery. Pulled live from the Notion Deliverables database, so it is current whenever you open it.
Social Performance
Tom's organic posts on LinkedIn + X - reach, engagement, and what's working. From Eden every day, plus the hand-measured numbers in the Notion Social Performance Tracker.
Home
Big 3
Each person's 3 focused tasks this week, straight from Momentum 2.0. Working on the business, not campaign delivery. The rule: 3 each, every one pointed at a goal, nothing else gets the week.
Loading…
Shipping Leaderboard
Who is shipping changes to the sb-lab repo, and how much. Every commit that reaches main counts, whoever or whatever wrote it.
Delivery
Reading the sends and deliverables from Notion…
Revenue Calculator
Pick a scenario, then move anything. The answer at the top is 1 month of sponsorship revenue.
Reading the last 3 months from Notion…
Sold & Scheduled
Money already booked and confirmed - signed work with dates in the diary. Not proposals, not pipeline, not leads. Read from the Notion Money-Mirror and Deliverables databases, not Attio, so nothing here is a forecast of what might close.
Loading…
Research
Loading…
Recipe
Loading…
Kanban
Every Daily by stage. Drag a card to change its stage (Archive asks why). Slot a Daily into a day on Publishing, then click Migrate on its card here to build the beehiiv draft. Nothing is ever scheduled.
Publishing
1. Drag a Daily onto a send day. 2. Click Migrate to build its beehiiv draft with that day's ads. Nothing is ever scheduled.
Content Calendar
Loading…
Deliverables Calendar
Loading…
Audience Growth
Loading…
Recent sends
Open & click rate per edition — your engagement health.
| Sent | Edition | Recipients | Open rate | Click rate |
|---|
StrategyHub Funnel
How visitors become StrategyHub customers, from landing page through to purchase, with live revenue from Stripe.
Brand Guide
Colours, fonts, logos and brand files for Strategy Breakdowns, the Daily and quicker.chat. Carried over from the original Notion brand guide; the logos and animations are built in design/logo-lab.
Strategy Breakdowns is a weekly 3-minute email on the playbooks and growth hacks behind successful software, internet, or media companies.
Colour palette
From the brand guide, and the same values render-kit uses.
Typography
New Order for headings, Avenir Next for body.
Logos
Click any file to download it. Copy SVG puts the mark on your clipboard for Figma, Notion or code. Drive folder
Strategy Screenshots email header
A remix of the Strategy Breakdowns header GIF: same intro, then the folder drops and a screenshot drag draws the new logo, the name writes on, and it snaps off. 1500 × 1080 like the original, plus 750 for email.
Other header takes
The crop-corner explorations it was chosen from.
GIFs
Gmail avatar, email header and section dividers. Drive folder (with MP4s)
Covers, social image and Zoom background
Logo animations
Jump between the 4 batches with the buttons on top. Click a tile to restart it.
Brand Exploration
How the Daily got its name and logo, 15-17 Oct 2026: the brief, the prompts, every round and why each one changed. Built to be published; the standalone page is design/brand-exploration/page.html.
Final Mockups
The Daily #81 mark with each name contender, on the SB wordmark grid: lockup, email header, phone inbox, X profile and browser tab.
Filo Sandbox
Last run: never
What it is for. As we automate more of the newsletter operation, the risk stops being "did someone forget" and becomes "did the automation quietly not run". Filo is the second pair of eyes on that. It exists so a broken GitHub Action or a skill that silently failed gets noticed the next morning rather than the week a sponsor asks where their report is.
What it does today. Once a day it reads the Notion Automations List, scans the last 24 hours across Attio, Notion, Slack, beehiiv and Tally for anything that should have triggered an automation, then checks both directions: what should have fired and did not, and what fired that should not have. It posts one short table to #filo-sandbox with a forecast of tomorrow's expected workload, so each day's findings can be checked against yesterday's prediction.
What it deliberately does not do. Filo never does the work itself. It does not draft, send, or mark anything complete, and it never writes to a sponsor-facing surface. It only reports. Every run is logged below.