Collab

Other eyes. Same manuscript. Not twelve Docs links.

Beta readers and coauthors should not require a ZIP of chapters. Invite them into the book with a seat and a role. Keep the binder as the source of truth.

The mess

Feedback dies in email threads

You export a DOCX. They comment in a fork. You merge by hand at midnight. That is not collab. That is archaeology.

  • Version soup across email
  • No clear roles (reader vs editor vs coauthor)
  • Fear of giving full edit access too early
  • Series betas without a clean seat model

What you get

Seats on the desk

Invite people into the workspace. Keep chapters in one place. Feedback lands where the book lives.

  • Invites and roles
  • Shared manuscript home
  • Pro for collab depth
  • You still own the book

How

Do this in order

Not a feature tour. The actual path.

  1. 1

    Know what you want from them

    Beta read? Line edit? Coauthor? Role clarity before the invite saves a friendship.

  2. 2

    Send the invite from the workspace

    Use invites under the workspace or book settings. Email or link. Assign the lightest role that still works.

  3. 3

    Point them at the chapters that matter

    Do not dump an unfinished 90k with no note. Tell them where to start and what kind of feedback you want.

  4. 4

    Merge decisions yourself

    You are still editor-in-chief. Accept feedback into the draft on purpose. Reject the rest without guilt.

Questions

Straight answers

Is collab on Free?

Solo drafting is Free. Invite workflows and series collab depth sit on Typewriter Pro. Check Pricing for the current seat rules.

Can invitees use CoAuthor on my book?

CoAuthor is a separate product with its own plans. Treat AI access as intentional, not automatic, for guests.

Invite people. Keep one master file.

Seats on the desk beat version soup in email.