Prose-first vs beats-first: how to get AI to stop fighting you

Prose-first writing builds the surface and trusts the structure to sort itself out. Beats-first writing builds the structure and trusts the prose to sort itself out.

"Beat" is a slippery word - no two writers define it the same. To Robert McKee it's a tiny action/reaction exchange inside a scene. To the Save the Cat crowd it's one of fifteen big structural turning points. I'm going to use it in a third, more practical sense - as an outline mechanism. For me, a story beat is a single moment of your story, and everything in it. The setting, the action, the dialogue, what the characters are feeling and thinking. One unit of what happens.

A beat captures that moment explicitly - a description of what happens. Prose describes a moment implicitly - the weather, the tension, the thing a character won't say, all buried in word choice and in what the sentences choose to linger on. A beat states it plainly: who is here, what they do, what's said, what changes. She finds the letter and realizes her sister lied. The kitchen is too quiet; she doesn't sit down. That's the substance of the moment, written as structure. The prose gets rendered from it afterward.

Which points at the real divide between two kinds of storytellers.

Ask two people to write a novel and you'll often see two different instincts. One opens a blank page and starts writing sentences, feeling for the story in the prose. The unit of work is words. The other steps back and asks what happens, in what order, and what's in each moment - blocking out the structure before worrying about wording. The unit of work is beats.

Prose-first writing builds the surface and trusts the structure to sort itself out. Beats-first writing builds the structure and trusts the prose to sort itself out.

Both produce great books. Both leave something to emerge on its own. They just disagree about which half is safe to leave - and they each fail differently because of it when issues occur. Write the words first and the architecture has to hold itself up underneath, often by luck if the author doesn't backfill the structure separately. Which is why a lot of beautiful books die quietly around chapter fourteen, when the momentum runs out and there is no foundation under the words. It's also why AI has so much trouble with a prose-first approach: it has to infer and predict what the structure beneath the words is supposed to be when it's not present. Lay the beats first instead and the prose has a frame to hang on - the AI can riff off a structure it already knows, with confidence.

It's also the quiet divide in how writing tools get built. Most are word processors with AI bolted on - a better blank page, if you will. Wonderful if you already think in story, which a lot of authors do. It's why most tools out there are prose-first: they cater to those authors. And it's why AI is such a hard thing for a prose-first author to accept - the AI is actively taking over the one area of control they most prefer to own: the words.

The beats-first tools are a smaller, newer group, and they hand the AI a different job. These are the ones pushing the boundaries of what AI can actually do on the prose side. You lay your story out as beats, tell each moment what goes into it, and the blank page gets rendered from that structure, hopefully in a voice and style of your choosing. Move a beat and you've altered the structure, letting the words flow and change as needed. You build the infrastructure; the prose follows. That's what AI was built to do best.

Beats vs Prose is a choice about which half of the work you do on purpose - the surface, or the structure underneath it.