Book proofs and bound titles on a publishing production worktable

Publishing operations · Discovery pilot

InPublish

See the blocker. Assess the printer date. Review the next follow-up.

Bring three book titles. Together, we map the milestones, make vendor handoffs visible and monitor agreed turnaround times in a 14-day assisted setup.

Assisted pilot proposal. Scope, price and start date agreed after discovery.

14 days
Assisted setup
3 titles
Focused pilot scope
Your SLAs
Agreed turnaround targets

Advisory desk

What could move the printer date?

Calculated demo advice · Fictional remaining effort · Not live AI

Snapshot 2026-10-28

Committed printer date

2026-11-06

Calculated print-ready

2026-11-10

Printer date at risk · 2-day slip

Proof approval is holding the dependency chain. The calculated print-ready date is 2026-11-10, 2 business days after the printer slot. Request a confirmed turnaround before discussing a replacement slot.

Dependency evidence

  1. Proof approval2026-11-02

    Maya Chen · 3 business days remaining (assumed) · Target 2026-10-26

  2. Preflight checks2026-11-06

    Eli Ross · 4 business days remaining (assumed) · Target 2026-10-30

  3. Print-ready approval2026-11-10

    Eli Ross · 2 business days remaining (assumed) · Target 2026-11-02

Monday–Friday, no holidays. Each unfinished step starts after its dependencies; completion is no earlier than its scheduled target. Remaining effort is illustrative, not vendor history. Printer date is a fixed fixture; this is not a delivery guarantee.

Recovery scenario

Scenario print-ready: 2026-11-10

2 business days beyond the printer date · Preview only

A shorter turnaround needs owner confirmation. No dates, completions or commitments are changed.

Follow-up outbox

Owner: Maya Chen · Trigger: Printer date at risk

Operational follow-ups require agreed recipients, sending rules and a verified email domain. No automatic follow-up sequence runs here.

The three-title offer

Less status chasing. More visibility.

Start with titles already in production, not a company-wide migration. Your production editors and vendors retain their responsibilities.

One milestone map

Connect editorial handoff, typesetting, proofs, corrections and print-ready approval. Record owners, dependencies and target dates for each title.

Agreed SLA monitoring

Set turnaround targets for selected vendor handoffs. Review due, overdue and blocked work against your agreed business-day rules.

Governed AI assistance

Explore evidence-linked status summaries and proposed follow-ups. Editors review messages and approve consequential actions; AI does not approve a title for press.

Your 14-day assisted setup

The proposed schedule starts once access, title scope and pilot terms are agreed. Integration work is scoped separately.

  1. Days 1–3

    Discover & scope

    Select three titles, understand the workflow and agree owners, handoffs and success measures.

  2. Days 4–7

    Map & configure

    Set milestones, vendor turnaround targets, calendars and escalation responsibilities.

  3. Days 8–12

    Monitor & refine

    Review title status together, inspect late handoffs and tune alerts against actual production updates.

  4. Days 13–14

    Review & decide

    Assess coverage, data gaps and team usefulness. Agree whether a broader rollout is worth pursuing.

Bring the workflow, not the manuscript.

Discovery needs a production process and a willing operations owner. Confidential content can stay outside the initial conversation.

  • Three representative titles and their current stages
  • Milestone dates, owners and vendor handoff targets
  • An existing tracker or a redacted workflow example
  • A production lead for setup and review

Pilot review

Measure what changes.

Review milestone coverage, update freshness, handoffs outside target and time spent preparing status reports. Establish a baseline together—no promised percentage savings or guaranteed deadline improvement.

SLA monitoring means tracking agreed targets. It is not a vendor performance guarantee or an automated replacement for your production team.

Your data, your model

InPublish maps your process. It never takes your business.

Our structured model of your workflow exists to serve you. These are the commitments we make to every client.

You own your data and your model

Your records and the way your process is configured belong to you. We own only the generic industry templates.

No cross-client learning

One client's rates, margins or schedules are never used to advise another client without written consent.

We won't compete with you

InPublish will not become a publisher, and InNumber will not become an accounting practice that pursues your clients.

Advisory, never autonomous

Suggestions are proposals. Nothing changes dates, vendors or balances until an authorised person on your team approves it.

Minimum data

We ask only for the fields a report needs, and keep each client's workspace separated from every other.

Leave any time

Export your titles, milestones and reports whenever you choose; your process map goes with you.

Independent security certification is planned as we grow; we will not claim it until it is completed.

Before the pilot

Apply for a pilot

Where does your production handoff stall?

Tell us about your publishing house and the three titles you'd start with. Our team reviews every application personally and replies by email.

No payment collected. Please do not include manuscripts or confidential title data.