Before we built the editor we built the timeline. That choice shaped everything that came after. It’s the reason Tandaan looks the way it does — and the reason this post exists.
The problem
Every doc tool saves the latest version. Most save a few past versions too. None of them save the thought. The trail of small revisions that turned a draft into a brief into a thing the team actually agreed on.
When you open a finished document, you’re reading the survivor. You don’t see what was cut, what was renamed, what someone almost said in a Slack message and then walked back. You don’t see the decisions. You just see the result.
The trail
Tandaan models every meaningful edit as a checkpoint. Not a save — a checkpoint. The difference matters. A save is something the system asks you to do. A checkpoint is something the system gives you back.
“We kept losing the whybehind the work. So we built a writing tool that holds onto it for you.”
The replay button is the most-used UI in the editor. Hover, scrub, land. Read the version you used to have. Decide if you still want it.
What we cut
We almost shipped a “share as image” button. We talked about templates. Folders. Workspaces. AI suggestions. We cut all of it. Not because they were bad ideas — because they weren’t this idea.
- No templates. Start from anywhere.
- No folders. Use the timeline.
- No reactions. Use the margin.
Where it goes next
The next thing we’re building is replay search — find a sentence that used to be there. Followed by replay export, so any document’s timeline can be archived as a self-contained bundle.
We’re a small team on a long timeline. If this resonates, write to us. We answer every email.