We're building the writing tool we couldn't find.
WriteLoom started in 2025 with a simple frustration: every working writer we knew, novelists, screenwriters, memoirists, poets, was stitching five subscriptions together and losing the thread between the draft, the cover, the query letter, and the launch. One workspace, with every artifact reading every other, ought to do more for a writer than another isolated AI tool.
Chapter I·Our principle
The book is the unit.
Most writing software treats a chapter as the unit of work. We think that's wrong. A book is the smallest meaningful object, the synopsis matters to the cover, the cover matters to the comp set, the comp set matters to the line editor's voice critique, the voice critique matters to the query letter.
When the same project holds every artifact, the tools stop being separate. They become a single workspace that knows what you're trying to do, because what you're trying to do is finish this book.
That's what we're building.
Chapter II·What we believe
Quiet opinions, held firmly.
AI is optional, never required.
Every AI feature can be turned off. Plan, Media, and Design work as a structured workspace without a model in the loop, and the other studios ship manual modes on the Spool tier, list-builders, the submission organizer, the marketing calendar, for writers who'd rather drive themselves.
AI usage is included.
No per-call billing, no separate AI bill. The one exception is audiobook generation, which runs on your own ElevenLabs API key, they charge by character and most writers prefer to control that line item directly.
No lock-in, ever.
Every artifact, manuscript, cover, comp set, marketing plan, query letter, is exportable to a standard format any time. We'd rather you stay because the tool is good.
Your manuscript is not training data.
Nothing you put into WriteLoom trains any model. Full stop. The privacy doc spells out exactly which vendor sees what, and why.
Sustainability is a line item, not a slogan.
We plant one oak per active writer per year through verified reforestation partners, roughly 1 metric ton of CO₂ absorbed per writer over a decade, against a typical SaaS data-center footprint of 2–10 kg CO₂e per year.
We answer email.
Every message goes to a human on the team. If you write us about a bug, a missing feature, or a workflow we don't support, you'll hear back, usually the same week.
Chapter III·Contact
Say hello.
The fastest way to reach us is [email protected]. Feature requests, bug reports, “this isn't for me,” and “this changed my year” all welcome.
For partnerships, press, or anything that needs an NDA, write [email protected].