First Book ai

Product details
0e0b0dd3f6754365b27f521786b3910b0e0b0dd3f6754365b27f521786b3910b
0e0b0dd3f6754365b27f521786b3910bPLUS
Apr 1, 2026

Q: Roadmap Question: Iterative Ecosystem vs. Linear Workflow? (3/3)

The "Lock & Next" flow is a concern for non-fiction. A complex book is an iterative ecosystem, not a factory line. As I gain insights in Chapter 8, I often need to jump back and refine the "red thread" in Chapter 1.

Insights happen as the book evolves. If the system locks the path, it can hinder the creative process. While I could copy-paste into other tools, I’d much prefer for First Book to be the primary workshop where the book actually grows and matures.

Is your roadmap moving toward a more flexible, non-linear process where chapters remain "live" for refinements? I’m trying to see if your vision aligns with high-quality craftsmanship over a linear "fast-track" to export. I’d love to hear your thoughts on where you are taking the platform! (3/3)

Sorry for all the messages, but these Appsumo question boxes are too limited.

Founder Team
Casper_FirstBook.ai

Casper_FirstBook.ai

Apr 1, 2026

A: Great with a fellow Dane. And yes, those AppSumo question boxes are tight.

Short answer: we agree with your direction on all three points, and the roadmap is moving that way.

On ownership and input
The product is built around your knowledge, not generic output. That’s why the onboarding form pushes for your background, beliefs, anecdotes, and writing samples.

Right now, the main place to inject depth is:
– upfront in the book definition
– and inside each chapter before generation via intent and description

That’s already how you steer it to be your thinking, not “AI knowledge”.

What you’re asking for next is more granular input per chapter, like feeding research, notes, or transcripts directly. That’s a natural next step and very aligned with where we’re heading.

On editing and “surgical control”
You’re right. A full rewrite is blunt.

Today:
– you can regenerate sections
– and guide rewrites with instructions at chapter level

But not yet true highlight → instruct → refine.

We’re working toward more precise control, where you can:
– target a specific passage
– give a clear instruction
– and update only that part without losing the rest

That’s the direction. It’s a clear gap today.

On linear flow vs iterative writing
The structured flow is there to help people actually finish a book. Most first-time authors get stuck without it.

But we don’t see books as linear. Good books evolve.

Right now:
– you can go back and edit earlier chapters
– nothing is truly locked in a final sense

But the experience still nudges forward progression more than free movement.

We are moving toward a more flexible workflow where:
– chapters stay “live”
– you can refine across the manuscript
– and strengthen the red thread as insights develop

So the vision is not a factory line. It’s a guided system that still allows iteration.

Net:
You’re describing a more craftsmanship-oriented workflow. That’s exactly the direction we’re building toward, while still helping people not get stuck.

Hope to see you in the Skool community.

Greetings from Denmark!

Share
Helpful?
1
Log in to join the conversation

Verified purchaser

Awesome, thanks for the thorough answer, Casper! Great to clarify that chapters aren't permanently locked—that removes a major concern for me. It sounds like your roadmap is heading exactly toward the "craftsmanship" and "ghostwriting" approach I’m looking for.

I’m particularly looking forward to the surgical editing tools and the ability to feed deep context/research into each chapter. Thanks!

Related questions
View product details