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.
For independent publishers ready to leave the spreadsheet relay behind
One publishing operation, from manuscript to reader.
Simply Publishing brings title metadata, edition history, channel sales, contracts and rights, production work, and reader delivery into one carefully connected operation. Start with the publishing workflows you need and keep the operation connected as your catalog grows.
Built for independent publishers and their teamsUnlimited users — yes, reallyPublic pricing, on this sitePowered by Simply360
CatalogWorks & editionsTitle metadataFormats & identifiersContributors
OperationsStatements to sales linesMapPreviewImport
Private experienceAuthor documentsShared documentsProtected downloads
oneconnected record of each work, edition, contributor, and release
clearimport history for every sales line: the statement file, the mapping you previewed, and the row it came from
$69per month for up to 6 live titles, with unlimited staff
humanreview points for the decisions that affect authors and readers
Why publishers need an operations layer
The list is creative. The operation should be legible.
A publishing list grows across manuscript folders, title sheets, distributor reports, contributor agreements, print schedules, and reader files. Simply Publishing is designed to keep those threads connected without asking an editorial team to become a systems department.
Yes — including the version of the title sheet that only one person knows how to update.
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 channel sales without retyping them
Bring each channel’s statement export in with Record Imports: map its columns once, preview the result before anything is written, and keep every sales line tied to its edition, channel, and source row. An import made from the wrong file can be undone.
Contracts, royalty terms, and rights beside the work
Record each agreement and its versions, royalty terms, payees, and territory grants next to the work they cover, with reversion and option review dates in view. Royalty calculation is not built yet; it will be shaped around a partner’s real contracts.
A private place for author 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.
How it fits together
From acquisition to reader, one accountable line.
The title record starts the shared history. Editions carry the formats and identifiers. Channel sales land beside the edition they describe, and contracts sit with the work they cover. Every handoff keeps its source and status.
Works, editions, contributors, imprints, and publication metadataFormat-specific release and distribution evidenceSales lines imported from channel statements, previewed before they are writtenContracts, royalty terms, payees, and rights grantsReader delivery and production follow-through
For publishers and operations leads
See the list, the release work, and the evidence behind the number.
Move from a disconnected title tracker to a shared operating picture: what is publishing, what is missing, what has been reviewed, and what needs a person to decide next.
See the operating modelFor editorial, production, and rights teams
Keep each discipline close to the same title history.
Editorial metadata, edition detail, production evidence, contracts, and sales lines can stay distinct without losing the relationships that explain the title to the next person.
See pricingWorks with any website
Your website, or ours — same system underneath.
Simply Publishing is being shaped as the operating system behind a publisher’s existing public presence. Keep your existing reader storefront and author relationships while connecting internal title, document, and delivery work to a shared record.
Title catalogEdition metadataSales importsRights and contractsDigital delivery
Works even better together
Tools that work hand in hand with Simply Publishing.
Four companion tools from the Simply360 family can extend Simply Publishing: tags and scans in the physical world, live maps for spaces, a standalone website builder, and connected raffle fundraising.
Use a simple tag or QR action at an event, warehouse shelf, proofing station, or author packet to open the exact controlled workflow the team needs — with the action linked back to the right operating record.
Explore Simply Action Tags
Keep shared editorial rooms, proofing space, launch events, or stockroom locations visible when the work depends on people finding the right place as well as the right title.
Explore Simply Spaces
Need the public site first? Simply Websites gives independent publishing teams the same Website Studio as a standalone builder: draft free, publish for $39/month, and connect Simply Publishing when the site needs live data.
Explore Simply Websites
Running a fundraiser? Simply Raffles gives independent publishing teams connected raffles, ticket packages, public and offline entry paths, prizes, eligibility, reports, and recorded winners — using the same people and data Simply Publishing already manages.
Explore Simply RafflesBring us one publishing workflow worth making dependable.
Show us the title sheet, the sales statement export, the author-document path, or the production handoff that currently depends on a spreadsheet. We will map the workflow, confirm the right plan, and walk through implementation.