Free Story Premise Generator

A spark is easy. A premise is the structural work — and the difference is everything.

A spark is any what-if that generates a moment of excitement. "A lighthouse keeper finds a sealed letter in the rocks." That is a spark, and it is a good one — it generates an image, a question, a flicker of curiosity. It is also, on its own, incapable of carrying a novel, because it contains no engine. There is no person yet who has to do anything, no pressure that will not let them alone, no cost that escalates across three hundred pages. The spark is a still photograph. A novel is a moving picture, and moving pictures require a motor.

A premise is the motor. It is built by taking the spark and forcing it to answer four questions it would rather not: who specifically is this happening to, what situation are they already in when it happens, what pressure does the spark put them under, and what does it cost them to respond. "A lighthouse keeper finds a sealed letter in the rocks" becomes a premise only when it becomes "a lighthouse keeper who has spent twenty years hiding from a crime he half-committed finds a letter naming the witness he thought was dead — and the letter is dated last week." Now there is a person, a situation, a pressure, and a cost. Now there is an engine.

This conversion is the work, and it is the work this tool exists to do. Most generators stop at the spark because sparks are easy and premises are hard, and the hard part — fitting a specific person to a specific pressure in a way that generates escalating pages — is exactly the part that matters. The three premises this generator returns are not three rewordings of your spark. They are three different engines built from the same raw material, each one a complete structural machine that a novel can actually run on.

• A spark generates excitement. A premise generates pages. They are different documents entirely.
• A spark contains an image or a what-if. A premise contains a person, a situation, a pressure, and a cost.
• Most abandoned manuscripts die because the writer started from a spark and never built the engine.
• A premise is a motor, not a summary. Its job is to keep the story moving, not to describe it.

Four load-bearing parts. Build them in order, and the engine assembles itself.

A working premise has four parts, and the order in which you build them matters more than the parts themselves. Start in the wrong place — start with the plot, as most writers do — and the engine fights you the whole way. Start with the person, and the rest of the machine tends to fall into place, because a specific person under pressure will tell you what they want, what stops them, and what it costs them.

The four parts are not a formula. They are a diagnostic. Build each one deliberately and you will discover, before you write a single scene, whether your premise has the capacity for a novel or whether it is actually a short story wearing a novel's ambitions. The table below maps each part to the question it answers and the way it tends to fail. Read your own draft premise against it, and mark which of the four you actually have — most stalled manuscripts are missing exactly one, and it is almost always the cost.

The whole engine hangs on one question: why this person specifically?

Of the four parts, the person is the one the whole engine hangs on, and the question that tests it is brutal in its simplicity: why this person specifically? If you can swap in a competent stranger and lose nothing, you do not have a story — you have a situation any protagonist could walk through, and situations do not generate novels. The person has to be the specific person for whom this pressure is the worst possible thing, so that pursuing or resisting it forces them to confront the exact thing they have organized their life around avoiding.

This is the same mechanism that powers a strong hook or a strong logline — the gap between what the character wants and what they need — but at the premise level it does structural work that scales across an entire manuscript. Cast the person correctly and every scene generates character change, because the plot and the wound are the same object. Cast them generically and the plot occurs near the character without ever penetrating them, which is the signature of a manuscript that beta readers describe as "well-written but I did not connect with her."

So the most valuable move in premise-building is the casting, and it is worth doing on paper before the generator runs. Ask yourself: who is the person for whom this particular pressure is the worst possible thing? The arson investigator who is secretly a arsonist. The grief counselor who cannot let go. The matchmaker who married the one person she was supposed to keep away from everyone else. In each of them the situation and the wound are the same object, which is why the situation generates change instead of merely occurring near the character. Build the person this way and the pressure, the situation, and the cost tend to suggest themselves — because a person with a wound will tell you exactly what pressure they cannot withstand.

Before you generate, answer one question on paper: who is the specific person for whom this pressure is the worst possible thing? If you cannot answer it, the premise is not ready — and you have found that out before writing sixty thousand words, which is the cheapest possible moment to find it out.

A spark, a premise, and a logline are three different documents

The confusion between these three is where most of the wasted effort in early-stage writing happens, and it is worth being precise about it. A spark is a what-if — an image, a question, a fragment. A premise is the structural engine built from that spark — the person, the situation, the pressure, the cost. A logline is the compression of that engine into a single sentence that proves the spine holds. They are sequential, and each one does a different job for a different reader.

The sequence matters because skipping a step costs you later. Skip the premise and jump from spark to logline, and you will find yourself trying to compress an engine you never built — which produces a logline that sounds generic because there is nothing specific underneath it to compress. Skip the premise and jump from spark to outline, and you will find the outline wandering, because there is no engine to keep the chapters moving in a direction. The premise is the load-bearing middle document, and it is the one most writers skip because it is the hardest and least glamorous.

Keep the three straight by asking what each is for. A spark is for generating excitement in yourself. A premise is for generating pages — it is the motor that keeps a draft moving. A logline is for proving to a professional that the motor works, in a single sentence. The premise comes first, and the others are downstream of it. Build the premise deliberately and the logline and the outline both get materially easier, because they are expansions and compressions of an engine that already exists.

• Spark: a what-if. Generates excitement in the writer. Worth almost nothing on its own.
• Premise: the engine. A specific person under a specific pressure paying a specific cost. Generates pages.
• Logline: the compression. Proves the engine works in one sentence, for a professional.
• Build them in that order. Skipping the premise makes both the logline and the outline harder, not easier.

Stress-test the engine: is this a novel or a short story?

Not every spark has the capacity for a novel, and finding that out early is one of the most valuable things premise-building can do for you. A short story can run on an image and a single turn. A novel requires an engine that can sustain escalating pressure across three hundred pages without exhausting itself, and that capacity is a structural property of the premise — not of the writer's stamina.

The stress test is simple. Take your premise and ask: can the pressure escalate at least three times, each escalation forcing a new decision and a higher cost? If yes, the engine has the capacity for a novel. If the pressure can only escalate once before it resolves or repeats, you have a short story, and trying to stretch it into a novel will produce the signature failure of padded first acts — a hundred pages of setup for a forty-page engine. Better to know that at the premise stage than at the draft stage.

This is also why the generator returns three premises rather than one. Each one is a different engine built from the same spark, and comparing them teaches you something about the spark itself — which versions of the engine have the capacity for a novel, which ones are really short stories, and which one is the version you actually want to write. The comparison is the point. Three premises forces you to choose between structural machines, which is a far better decision than choosing between rewordings of the same machine.

• Ask whether the pressure can escalate at least three times, each time forcing a new decision and a higher cost.
• If the pressure escalates once and resolves, you have a short story — stretching it produces a padded first act.
• Three premises lets you compare engines, not rewordings. The comparison is the point of the tool.
• A novel's capacity is a structural property of the premise, not of the writer's stamina. Build the engine before drafting.

A premise with a working engine is an outline waiting to happen. Carry it into BookWriter and build the chapter outline and your first chapter against the person, the pressure, and the cost you just defined — the first chapter is free, and a complete book is $19.99.