How do small presses manage publishing operations?
- Three-layer system: per-book workspace, press-wide calendar, weekly sync.
- Each book has a named project manager.
- 3-5 staff can ship 10-20 books a year with this structure.
- The weekly sync resolves dependencies and surfaces slippage.
- A press-wide calendar shows every book’s current stage.
Small presses manage publishing operations through a per-book shared workspace, a press-wide editorial calendar, and a weekly all-team sync. Each book has a named project manager who owns its workflow; the calendar shows every in-flight book’s stage; the weekly sync resolves dependencies and slippage. Most successful small presses use this three-layer system to ship 10-20 books a year with three to five staff.
Chapter i·Why it matters
Small presses fail more often from coordination problems than from quality problems. Without a per-book workspace, manuscript versions blur; without a press calendar, deadlines compete invisibly; without a weekly sync, problems compound. A three-layer system replaces these failure modes with structure that scales from one staff to five.
Chapter ii·What to include
- A shared workspace per book: manuscript, metadata, calendar, team roster.
- A press-wide editorial calendar listing every in-flight book and stage.
- A weekly all-team sync (30-45 minutes) reviewing every book.
- A named project manager per book.
- Explicit role assignments: editor, designer, marketer, project manager.
- A "lessons learned" doc per book, reviewed quarterly.
Chapter iii·Example
A small press with four staff and twelve books a year runs the three-layer system. Each book lives in its own WriteLoom workspace; the press-wide calendar is an Airtable board; the team meets every Friday morning at 9 AM. Across two years they have not slipped a launch and the team turnover has been zero.
WriteLoom supports per-book workspaces plus a press-wide view of every in-flight project — the three-layer system without separate tools.
See WriteLoom for teams