How it works
How managed book production works
Five stages across twenty working days. Three of them need your desk — the scoping call, and two approvals your editors already do today. Your team spends hours on a title, not weeks.
The five stages
Twenty working days, to scale
Drag the marker, or pick a stage below
- Needs your desk — 3 of 5 stages
- Ours alone — 2 of 5
- 11 consecutive days with nothing on your desk
The transformation
What you send, and what comes back
Scroll — the page composes itself in the order a compositor builds it.
What you send
GRADE 6 · CBSE- Unit 1 — Food: where does it come from?
- Unit 2 — Components of food; balanced diet
- Unit 3 — Fibre to fabric
- Unit 4 — Sorting materials into groups
- Unit 5 — Separation of substances
- Your previous edition
- Your composition template
- Your printer’s specification
rounds
What arrives
PRESS-READY- Print-ready PDF, fonts embedded
- Editable source package
- Curriculum mapping annexure
- Change log against the old edition
Your control
Two review rounds. Your book, your call.
Before production — you approve the chapter plan
We return the curriculum map, chapter sequence and page budget. Nothing is produced until your editor signs it off or redirects it.
Round one — you mark up the composed proof
You receive fully composed pages, not a draft manuscript. Mark them up exactly as you would a vendor proof today.
Round two — you confirm the corrections
We return the corrected pages for a second pass. Both rounds sit inside the quoted fee, with a defined response window.
At handoff — you receive a page-level change log
A record of what changed from your previous edition and why, so your editorial head reviews by exception rather than reading the book twice.
Before any of that, our own subject editors review every chapter. You review a clean proof, never a first draft.
The pipeline
The pipeline behind the twenty days
Specialised agents in four clusters, operated by our production team. You never touch it — which is why there is nothing to learn.
Planning
Curriculum to blueprint
- TOC Builder
- Lesson Planner
Content
Generate and integrate
- Author
- Manuscript Ingestion
- Q&A Builder
Visuals and QA
Refine and validate
- Illustrator
- Editor
- QA Validator
Coordination
Ship and orchestrate
- Layout Engine
- Comparison
- Managing Agent
The difference between this and a general AI tool is not the model. A tool gives fifteen editors fifteen different standards and hands you all the risk. A pipeline gives one standard across a whole grade band, composed to press, with a delivery date attached.
What we need from you
Three things, once
The clock pauses while we are waiting on you
Whenever delivery depends on something from your side, the schedule pauses and the pause is logged in a tracker you can see. That is the only condition attached to the delivery commitment.
One named point of contact who can approve the blueprint and return review rounds.
The source files for the title — your previous edition, your template, and your printer’s specification.
Review rounds returned inside three working days so the schedule holds.
The twenty days, day by day
| Days | Stage | What we do | What you do |
|---|---|---|---|
| 0 | Discovery | Walk your process, scope the title | Join a 45-minute call |
| 1–3 | Blueprint | Curriculum map, chapter plan, page budget | Approve or redirect |
| 4–14 | Production | Content, exercises, figures, composition, internal editorial review | Nothing |
| 15–18 | Review | Return composed proof; apply corrections | Two rounds of mark-up |
| 19–20 | Handoff | Final files, annexure, change log | Take the files to press |
Twenty days starts with a forty-five minute call
No files and no NDA needed for the first conversation.