About

Why Abstract exists

Abstract started as a workaround. Leading a security certification with a skeleton crew, I ended up managing two dozen policy documents as plain files, with AI helping me keep them consistent, because no document tool could do it.

The workaround turned out to be better than the tools. It kept being better for strategy documents, for research, for board reporting, and eventually the conclusion was unavoidable: this is how document work should feel, and someone has to build it properly.

Who's building it

I'm Tom Frauenfelder, a Melbourne-based product leader with around fifteen years across SaaS, PropTech, architecture and applied AI. I trained as an architect, led product, design and engineering as one team as Head of Product at a B2B SaaS company, and taught design at RMIT and the University of Melbourne. These days I build solo with AI tools.

Abstract is built the way it says work should be done: one person, a folder of documents, and agents doing the legwork.

How we're releasing it

We're letting people in gradually and working closely with early users, so the product grows around real work rather than a feature list. If your week lives across more than one document, I'd love you to try it.

Want to say hello first? hello@abstractdocs.com

FAQ

Questions

Where is Abstract based?

Melbourne, Australia. Early access is worldwide.

Why 'Abstract'?

It's a writing word, a thinking word, and a description of where this generation of tools sits in the stack.

If your week lives across more than one document, we'd love you to try it.

Early access · free while in beta · no credit card