Closed beta
One knowledge base for the whole house — series bibles, style rules, the prompts your best editor wrote — readable by every writer and by the AI sitting next to them. Some of it readable by everyone. Some of it not.
Most writing teams we talked to run on a documents folder, a wiki, and whatever chat assistant each writer happens to prefer. It works until it does not, and it fails in three specific ways.
Every writer re-explains the world, the voice and the rules at the start of every session. The answers differ because the briefings differ.
A wiki page, a pinned message and a Google Doc all describe the same character, and all three are out of date in different directions.
The prompt library that took two years to write is one folder download away from being on somebody else's laptop, and there is no record it ever happened.
The team area used to be ten flat tabs. It is now grouped by what you are doing there — getting work done, feeding the team's shared brain, or running the place — and each pane has a URL you can send someone.
Mark a skill confidential and it keeps working — a writer's AI conversation still uses it, still follows it, still produces the house voice. What changes is that the text itself never reaches their device, and only owners and admins can open it.
What this stops and what it does not: it stops casual copying, a leaving employee packing the folder, and bulk export. It does not stop someone deliberately coaxing the content out of a model, an owner or admin choosing to share it, or a photograph of a screen. We would rather you know that before you buy than after. The classification, the differentiated permissions and the contemporaneous access log are also the three things courts tend to look for when deciding whether information was actually kept secret — though what that is worth in your jurisdiction is a question for your own counsel, not for us.
Four roles, and they stack — one person can be an admin and a writer at once. A reviewer reads, comments and approves without occupying a seat.
| Role | Write | Use team AI | Manage members | Takes a seat |
|---|---|---|---|---|
| OwnerOne per team. The only role that can transfer ownership or close the team. | ● | ● | ● | — |
| AdminInvites, removes, manages skills and rules. Cannot remove the owner. | ● | ● | ● | — |
| WriterCreates and writes team books. Sees their own books plus the knowledge base. | ● | ● | — | ● |
| ReviewerOpens team books in a read-only workspace to comment and approve. | — | — | — | — |
During the closed beta we set your seats up with you rather than asking you to buy them from a page. Tell us the shape of the team on the form below and we will size it.
Not a project management tool bolted on the side. Three states on the chapter itself, and one table that shows the whole book.
A target word count and a state the writer sets. The editor sidebar and the manuscript table both show where each chapter stands.
Submitted chapters collect in the team overview across every book, so an editor works one queue instead of opening eight projects.
Approve it or send it back. Either way it is a state on the chapter, visible to the person who wrote it without anyone having to send a message.
There is no self-serve checkout for this yet, and that is deliberate. We set each team up by hand, watch how it goes, and fix what breaks before the next one. Tell us about yours and we will get back to you.
Two minutes on the form. A reply from a person, not a sequence.
Before we count anything
Analytics and advertising cookies stay off until you turn them on. The ones that keep the site working, and the one that remembers this choice, are always on. The detail is in the Privacy Policy.