What shipped

Everything, at once

There is no history to list yet. This is what shipped on day one, and from here the entries get shorter and more frequent.

• Tasks are blueprints rather than to-dos: they hold steps and a schedule and produce a dated run each time they are due.
• Four kinds of step — open a link, copy a line, choose from variants, and a plain reminder that stays unticked because it is not work.
• Daily, weekly, monthly, one-off and manual schedules, with start dates so a task can wait.
• A board of the coming weeks computed from the rules, a history of every run, and an optional daily email listing what is due.

• Your own SMTP mailboxes, credentials encrypted at rest, with a daily cap per mailbox that refuses rather than queues.
• Several mailboxes per template, one picked at random per send, so volume spreads without anyone tracking it.
• Templates as sequences: an initial, follow-ups that belong to it, and manual ones kept only to be copied by hand.
• Follow-up day counts measured from the first message, so a late send never pushes the rest of the sequence out.
• A full sending record with reply marking, filters, and bulk follow-ups. Marking a reply drops the rest of the sequence at once.
• Test sends to any address, with the real variables, so you can see how it lands in a different client.

• Reports: which message got the reply, how much chasing it took, reply rate by template and by mailbox, and median time to answer.
• The browser extension: send with variables, mark replies and chase follow-ups from the page you found the lead on.

Honestly missing

• Shared team accounts. Everyone runs their own today.
• Importing a list. Sends are one at a time while the model settles.
• Inbox-side reply detection. You mark replies yourself, because only you know.