60,000 words. 9 months. 1 developer. Here is the production system that made it possible.
The 2,000-words-per-week cadence
Every week, I ship 2,000 words of lore. That is roughly 1 chapter per month (8,000 words per chapter). 9 months = 36 weeks = 72,000 words. The 60,000 words in the final manuscript is the result of cutting 12,000 words of filler.
The faction rotation
Every chapter focuses on 1 faction. The rotation goes: Sylvan → Aeldric → Cursed → Clockwork → repeat. The rotation ensures every faction gets equal treatment, and the alternating tone (peaceful → bright → dark → mechanical) keeps the writing fresh.
The outline-first workflow
- Week 1 (outline): 500 words of outline. The thesis. The faction decision. The NPC arc.
- Week 2 (draft): 2,000 words of first draft. Write fast. Do not edit.
- Week 3 (polish): Cut 500 words of filler. Add 300 words of detail. Read aloud.
- Week 4 (ship): Commit to GitHub. Announce on Discord.
Why this works
- Predictable. 2,000 words a week is achievable. 8,000 words a week is burnout.
- Stackable. Each chapter makes the previous chapter better (continuity, callbacks).
- Compound. After 9 months, you have a 60,000-word book — a real product, not a half-finished draft.
What this means for your project
If you are writing a book (fiction, lore, technical, anything), commit to 2,000 words a week. 9 months from now, you have a book.
Read 2 free chapters from the lore book.
📎 Related articles
Agree, disagree, or caught something off? The comment form is below — I read all of them.
