Run: 017 - Phase 1 Draft - Date: 2026-05-06 - Phase 1 author
Drafted the 3 page About Us PDF for Next Chapter aimed at 55 to 70 year old founders contemplating a sale. Page 1 leads with the operator origin story verbatim and ends on a beat that earns the page turn. Page 2 carries three counterintuitive deal lessons that read like field notes (slowest closer dies, the second LOI is the honest one, the seller who can walk closes faster). Page 3 above the fold explains the process in operator language and hands the reader a self serve shortlist demo where the CTA reads as their own curiosity. Email body is 88 words and treats the PDF as the substitute pitch, not a teaser.
I do not know whether the live shortlist demo on page 3 actually exists in production yet, or whether toggling between acquirers and targets is shipped on chapter.guide. If the demo URL or product flow does not match the copy, the reader hits a dead end and the entire trust arc collapses. I assumed parity with the buyside hunt skill output but did not verify the public facing route. Architect or quarterback should confirm the live URL and the toggle UI before this PDF goes to print.
This rhymes with run #008 and run #010, where writer produced operator voice deliverables and the post run feedback was that the copy still leaked one or two AI tells (compound hyphens, tricolons). For run #017 I ran the banned phrase scan before submitting and rewrote three compound hyphens (mid market, owner operator, route based) into spaced or rephrased forms, so the v2 banned list from 2026-05-05 is now load bearing on the first draft, not just the audit pass. Novel element vs prior runs: this is the first writer output I am aware of that includes a banned phrase appendix scoped to a single deliverable rather than relying on the global list.
Going forward I will run the banned phrase scan inline during drafting rather than as a final pass, and I will flag any reader facing CTA that depends on a live product surface I have not personally verified, so architect or quarterback can confirm the URL before the deliverable ships.
Generated from 017__writer.md — do not edit this HTML directly.