Closed beta · Invitation onlyDoTillDone is not publicly available yet.Join the mailing list ↗
How it works · product preview

An open loop in.
Follow-through out.

DTD is being developed as an email-first assistant for the tasks that need chasing. Here’s the intended experience we’re testing with invited beta users.

Join the beta list ↗
A familiar interface

Use the email you already have.

The aim is to keep task follow-through in ordinary conversations—not require a new workspace for everyone involved.

Email

Send DTD a clear task or outcome once you have beta access.

Forward

Share a thread with context and tell DTD what needs to happen next.

CC

Add DTD to a conversation when there's a promise or deadline to track.

Stay in control

Pause, redirect or cancel follow-ups through plain-language replies.

Closed beta: The above describes the intended experience. The public task-handling inbox is not accepting new users. To express interest, email addme@dotilldone.com.
Illustrative lifecycle

From one instruction to a closed loop.

An example of what an email-driven follow-through workflow is designed to do.

Step 1

Share the notes

“Turn these into action items for next Monday.”

Step 2

Find commitments

Identify owners, deliverables, deadlines and missing details.

Step 3

Follow up

Ask the owner for an update when a commitment comes due.

Step 4

Recognize changes

Take account of a revised deadline or reassigned owner.

Step 5

Watch for completion

Check whether the promised file or answer arrives.

Step 6

Close the loop

Bring the final status back to you—rather than leaving another reminder.

Design priorities

Keep context. Respect decisions.

A useful follow-up agent needs to react to the conversation, not just follow a timer.

Changed dates

A person who commits to a new deadline shouldn't get chased on the old one.

New owners

If responsibility changes, the tracked task should change with it.

Completion signals

An actual deliverable should close the task, not trigger another reminder.

Human approval

Unclear or consequential actions should be confirmed instead of guessed.

Closed beta · Join the list

Interested in shaping the first release?

Join the closed beta mailing list to hear about development and potential test invitations.

Get on the list ↗