For writing teams · closed beta

One knowledge base, every writer's AI reads it.

Publishers, writers' rooms and ghostwriting studios keep the series bible, the style rules and the prompts in one place — readable by every writer on the team, and by the AI sitting next to each of them.

Apply for the closed beta See the team workspace
app.slima.ai · Team Workspace
✦ Northlight Press 4 writers
▾📂 Knowledge base18
▾📁 Series bible5
📄Style guide312
📄The Harbour books · voice2,140
📄Recurring characters1,602
▸📁 Skills7
▾📂 Team books
👤Low Tide · in review
+ New chapter
TEAM BOOK›LOW TIDE · CH. 7

7. What the Harbour Keeps

The fog came in low over the breakwater, and the lamp at the end of the pier blinked twice before it caught.

Mara drafted it against the series bible the whole house works from. The editor's queue picked it up the moment she submitted.

Chapter 7 · In review · submitted 2h ago

✦ Ask coachTightenContinue
✓ Saved · v92,140 wordsAwaiting review
Writing Coach
HAS READ THE KNOWLEDGE BASE
Does this match the house voice for the Harbour books?
Mostly. The style guide asks for restraint in the second paragraph — trim two adjectives and it sits with the earlier books.↳ from Knowledge base · Style guide
House voiceSeries continuity
Knowledge base
Shared · every writer's AI reads it
💳 Review queue
3 chapters waiting · 1 approved today
👥 Roles
Owner · Admin · Writer · Reviewer
★ Closed beta
Set up by hand, one team at a time
Built for houses that write together
PublishersWriters' roomsGhostwriting studiosAgenciesCourses
Built for groups

The house style stops living in three people's heads.

Most writing teams run on a documents folder, a wiki and whichever chat assistant each writer prefers. It works until it does not.

📁

One knowledge base, read by every AI

Series bible, style rules, the prompts your best editor wrote. Every writer's AI conversation draws on the same source, so the answers stop varying by who asked.

💳

Writing and approving are different jobs

Owner, admin, writer, reviewer. Writers write in team books; reviewers read, comment and approve without taking a seat.

★

Skills you can mark confidential

A writer's AI still uses the skill. The text itself never reaches their machine, and every read is logged.

The knowledge base

Everyone works from the same facts.

The bible lives as a file tree the whole team can read, with semantic search over it. What the AI learns about your world goes into a review queue first — a manager confirms it before it becomes shared truth.

  • Import Word and PDF; edit a file without leaving the tab
  • Team-level rules for the AI Coach, mandatory or advisory
Knowledge base
Read by every writer and their AI
✓ Series bible 14 files
✓ Style guide confirmed
✓ AI memory · needs review 2 entries
✓ Confidential skill read 42× this week
Roles and seats

Sized with you, not bought from a page.

There is no self-serve checkout for teams yet, and that is deliberate. During the closed beta we set each team up by hand — the seats, the roles, the knowledge base — and watch how it goes before the next one.

  • Writers take a seat; reviewers do not
  • Seats are set up with you during the beta
Members & Seats
Set up together during the beta
Mara R. · WriterPro
Jonas P. · WriterPro
Priya K. · ReviewerPro
3 members · set up by hand
The full studio, for every seat

Every writer gets the whole studio.

No stripped-down team tier. A seat on the team gets the same six file types, the same coach and the same version history a solo writer gets.

🧠

Full-book memory

A coach that has read every chapter — and the team's knowledge base behind it.

🕓

Version control

Every save restorable. See who changed what, and keep both drafts.

👥

Chapter review

A state on every chapter — drafting, in review, done — and one queue across every book for the editor.

📤

Exports for the team

PDF, EPUB, Word, Fountain. The work is yours to take anywhere.

Reader reports per writer

See the slow chapter before the room does.

Each writer gets a full read of the book, usually within 30 minutes. The team sees where readers lean in, where they slip, and the one thing to fix first, together.

  • Attention curve with drop and peak detection
  • Scores for pull, voice, pace, and character
Attention curve
Where readers lean in, where they slip
Stopped reading · Ch. 3
Iris, 3482
David, 4764
Pia, 2291
“I get distracted easily and writing flow is hard to find. Before Slima, whenever I had two different directions for a plot, I had to manage two versions myself — and just switching between them would break the flow I'd barely settled into. Now I can edit freely and, once a writing session wraps up, pull out whichever version I need.”
SC
Sewer Crocodile
A creature dwelling in the sewers

Tell us about your team.

Two minutes on the form, a reply from a person. We onboard one team at a time during the beta.

Apply for the closed beta See the team workspace