Daily Plan. A morning checklist that reads your own database.

The problem

A site that mostly runs itself still needs someone every morning. Things queue up for review, a nightly job quietly fails, a request sits unanswered. The usual fix is a to-do board — and a to-do board is only as current as the last time someone updated it.

How it works

Daily Plan reads your site's own database each morning, once the overnight jobs have finished, and sends one email: what needs you today, ranked by what it costs to leave it, each line linking straight to the page where you deal with it. The same list lives on an admin page, where you tick items off, add your own, act on some of them in place, and re-send the email if you need it again.

Most items tick themselves. They come from the data — a queue that's waiting, a nightly job that didn't run, content that has broken, a request nobody has answered — so when the thing is fixed, the item closes. Nobody maintains the list, which is exactly why it can't go stale.

Today's ceiling

Beside the list is a small panel for a different question: how much could the site ship today? It's worked out from the limits the site really runs under — its quotas, its budgets, the backlog already queued — and it shows what's waiting on you. You know what the day can hold before you start it.

Proposals, never actions

If you switch them on, an AI drafts a few pieces of work each morning from what came in overnight. They stay proposals. Nothing is saved, sent or published until you press Keep — and Keep makes a draft, never a live change. Prompts are capped per day, and every call is logged with what it cost.

The checklist itself is plain rules over your own data; the AI only drafts. That's the rule we use everywhere: if you can write down the rule, write the rule.

What you get

• The morning email — what needs you today, ranked, each line one tap from where you fix it.
• An admin page with the same list: tick items off, add your own, act on some inline, re-send the email.
• Items that open and close themselves from live data, alongside the ones you add by hand.
• The capacity panel: today's ceiling, and what's waiting on you.
• AI proposals, capped per day and logged with their cost. They never act on their own.
• A command-line hook, so your other tools and scripts can add items to the list.

What it needs

Daily Plan isn't a hosted dashboard you sign up for. It's set up per site, on your own stack, and it needs four things there:

• A web app with a database — Daily Plan reads your data where it already lives.
• A scheduler to run it each morning, such as Vercel Cron.
• An email sender for the morning email.
• An admin login, so the list stays private.

Running cost: one scheduled job a day, plus a few cents a day in AI calls if proposals are on.

The boundary: it only knows what your database knows. If a site has no data worth reading and nothing running overnight, a morning list has nothing to say — and we'll tell you that before anything starts.

Where it runs today

On Clipsboard, one of our own products, since October 2026. That's the whole track record so far: one site, and it's ours. It's how every app here starts — built to run something we operate, then offered to anyone else. The Clipsboard case study covers the product it was built for.