One spine for works, editions, and contributors
Keep the work, every format-specific edition, identifiers, contributors, imprints, publication dates, descriptive copy, and status in a shared catalog that is ready for the next release conversation.
Private-beta capabilities
See what is working now — and what comes next.
Simply Publishing is preparing for publishing partner #1. Every capability below carries an explicit status so the invitation stays useful and honest.
Prepare accurate catalog and ONIX-ready metadata
Build title data once, review it with the publishing team, and prepare a traceable export for the recipients and formats a partner actually uses instead of maintaining another detached feed spreadsheet.
Import sales evidence before it becomes a royalty decision
Bring channel statements through a reviewed mapping, retain the source evidence and import version, isolate exceptions, and make the approval trail visible before a royalty run is finalized.
Terms, recoupment, and statements with a review trail
Model the terms a publisher agrees to, calculate only against approved evidence, and preserve the draft, approval, finalization, and correction history that authors and finance teams need to trust.
A private place for approved statements and documents
Give authors a focused, permissioned place to retrieve the documents intended for them, with protected access and clear publishing controls rather than an emailed attachment trail.
Track print work and digital editions beside the title
Keep production handoffs, proof milestones, stock movements, EPUB packages, reader access, and release evidence connected to the edition they describe — without treating every format as a separate business.
Partner #1
A working onboarding path, not a public signup form.
We review the catalog, contracts, statements, migration path, access policies, and success measures together before any private-beta data moves.
Bring us one publishing workflow worth making dependable.
Show us the title sheet, the statement review, the author-document path, or the production handoff that currently depends on a spreadsheet. We will discuss whether it is the right first-partner fit.