A formatting quote is meaningful only when the deliverables match. One price may cover a novel PDF from a clean manuscript; another includes custom design, EPUB, complex tables, accessibility work, revisions, source files, printer corrections, and a new cover spine. Comparing the headline numbers without scope rewards the least complete quote.
Describe the hardest page before requesting a price
Count parts, chapters, subheads, extracts, lists, footnotes, endnotes, tables, figures, captions, poetry, code, indexes, and full-bleed images. A quote based only on word or page count cannot capture a cookbook, academic monograph, or illustrated manual. Send representative difficult pages and state the intended trim, platforms, formats, and release date.
Make print and ebook deliverables explicit
A print PDF and reflowable EPUB are different production files. Confirm whether the price includes both, plus hardcover or large-print variations, validation, navigation, accessibility checks, and retailer-specific uploads. Ask whether a change in print pagination triggers a revised cover spine and whether that correction belongs to the formatter or cover designer.
Compare revision and source-file terms
Record the number and type of revision rounds, what counts as an author change, and the response to a printer rejection. Require a clear handoff: final files, editable sources where promised, font licenses or documentation, export settings, and a path for later editions. A low quote becomes expensive when every typo requires a paid rebuild.
Put DIY and software time in the same calculation
Word and Google Docs can have zero purchase cost, but the author supplies cleanup, styles, sections, page rules, PDF export, ebook conversion, preflight, and repairs. Guided software exchanges some design freedom for repeatable automation and re-export. Count learning, proof copies, delays, and the risk of rebuilding after a late edit, not only the checkout amount.
Choose service, software, or a hybrid from risk
A straightforward novel can be a strong software project when the author can proof it carefully. Complex notes, tables, poetry, images, indexes, or accessibility requirements benefit from specialist judgment. A hybrid workflow creates the base book in software and pays an expert to audit difficult pages or final outputs, concentrating labor where it changes the result.
Sources and verification
Platform specifications, software behavior, licensing, and accessibility guidance can change. Recheck the linked source before final production.
By Coverfairy Editorial · Published · Updated