Every project you are responsible for, on the cadence you promised it.
Cadence keeps a quiet ledger of everything you run: sites, writing, the books, the lease, the side thing. It tracks how often you mean to touch each one, tells you what has slipped, and lets an assistant handle the mail and the reminders so you can glance instead of worry.
Early access · invite only
Refresh the services page · next swap the hero copy
Issue 41, pricing experiments · next draft the intro
Reconcile August
Lease renews in October
Most of what you run has no due date. It has a rhythm. Cadence keeps the rhythm honest.
If the page is quiet, the fleet is fine. When something wants you, it is obvious without being loud.
The assistant reports what it did in plain prose. Everything it touches is reviewable and undoable.
Three decisions, then it mostly runs itself.
- 01Name the fleet
Add every project you are responsible for. Websites, a newsletter, the books, a lease, the thing you keep meaning to get back to.
- 02Set a cadence
Decide how often each one deserves your attention. That promise is the only schedule Cadence keeps.
- 03Check in, or let it check in for you
A check-in resets the clock. Forwarded mail, calendar changes, and repository pushes count too, so the ledger stays honest without data entry.
Enough to run a small fleet. Nothing that performs.
- Cadence, not deadlines
- Give each project a rhythm: daily, weekly, monthly, quarterly. Cadence measures how long it has been since you touched it and sorts the ledger by who needs you. Overdue reads as a warm mark, not an alarm.
- A console you can read in one glance
- Three bands: needs you, on cadence, at rest. Each row carries the current focus and the next step, so the answer to "what now?" is on the page before you start reading.
- An inbox that files itself
- Forward mail to your workspace address. The assistant reads it, files it to the right project, extracts tasks and dates, and asks you when it is unsure. Every action is logged and can be undone.
- Digests written from your ledger
- A daily to-do, a Monday week-ahead, an end-of-week recap, and a first-of-month report. Each one is composed from what actually changed, then written in plain prose. Sent at the hour you choose, in your timezone.
- The repository is the source of truth
- For software projects, keep a small project file in the repo. Focus, next step, tasks, and cadence sync from there on every push. Edit it in your editor; the console follows.
- Calendar in two tiers
- Cadence check-ins and personal commitments live on separate calendars. Changes you make in your calendar sync back to the ledger every hour, so a moved meeting is a moved task.
- Support intake, then a pull request
- Drop a small form on any site you run. Reports arrive in triage, get routed to the project, and can be handed to a coding agent that investigates and opens a pull request for you to review.
- Reminders that know the project
- One-off reminders and task due dates are swept hourly and delivered by email. Each one links straight to the project page it came from.
It reads the mail, keeps the ledger, and writes you the plan.
The digests are composed from what actually changed, then written in plain prose so they read like a note from someone who has been keeping an eye on things. The in-app assistant takes instructions the same way and shows you exactly what it changed.
Two things want you this week. The studio website is four days past its monthly touch; the next step on file is swapping the hero copy. The weekly letter is due today.
Bookkeeping and the rental unit are on cadence and can wait. Three emails were filed since Friday. One needs an answer: a vendor asking about invoice terms, filed under Bookkeeping.
Nothing is scheduled for the podcast pilot. It stays parked.
Move the letter to Thursdays and remind me Wednesday night.
Done. Weekly letter now checks in on Thursdays. Reminder set for Wednesday at 9:00 pm.
- forwarded email
- Google Calendar
- git pushes
- support forms
- reminders
- check-ins
Free, and invite only, while it is in early access.
Cadence is being used daily by its makers and a small group of operators. New workspaces are opened by invitation. If you have one, the link in your email signs you in. When paid plans arrive, early workspaces will hear about it first and will not be surprised.
- Unlimited projects and check-ins
- Inbox filing with an allow-list of senders
- Daily, weekly, and monthly digests
- In-app assistant with undo
- Calendar and repository sync
- Support intake for the sites you run
- Who is this for?
- One person running many things. Cadence is built for a single operator, not a team. A workspace can be shared, but the product is designed around the question one person asks several times a day: what needs me right now?
- What does the assistant do without asking?
- It files forwarded mail, extracts tasks and dates, and writes your digests. When it cannot classify something, it asks instead of guessing. Anything it does is attributed, logged on the project, and undoable from the activity feed.
- Where does my data live?
- In a Postgres database with row-level security. Every table is scoped to your account at the database layer, and the assistant works through that same boundary.
- Do I have to use email?
- No. Email is one input. You can also check in from the console, edit a project file in a repository, move things on the calendar, or just talk to the assistant.
Glance instead of worry.
Add the things you run, give each one a cadence, and let the first Monday digest tell you where you stand. Early access is by invitation.