Every serious tool starts as a selfish one.

Storyforge didn't begin with a pitch deck or a market gap. It began because a friend built something — a tool that turned images into stories. It was charming; it was fascinating to link characters to images and build a story around them. And it planted an idea that wouldn't leave.

What if you could build something like that, but for a bigger ambition? Not children's storybooks. Not quick social content. The kind of storytelling that keeps you up at night — a novel, a screenplay, a series with a universe so wide you need a map to navigate it.

That idea started as a UX exercise, a side project, a weekend sketch. Then it became something else entirely.

The walls we kept hitting.

The first prototype didn't come from user research. It came from trying to write a story in Notion.

Twelve chapters in, the cracks were obvious. Every character lived on a different page. Every location, every timeline, every thread of backstory scattered across tabs you'd forgotten you opened. You could write a scene, but you couldn't see the world around it. You couldn't hold the whole thing in your head while working on a single paragraph.

And it wasn't just the tools. It was the process. How do you structure a story when you've never built one before? What frameworks exist? How do professionals think about worldbuilding, character arcs, plot structure? That knowledge is out there, buried in craft books and screenwriting courses, but it's never in the place where you're actually writing.

So we started building. Not from theory, but from the specific frustrations of trying to write something ambitious with tools that weren't designed for it.

What writing tools have been missing.

The last real leap in writing tools was the move from typewriter to screen: the ability to edit, rearrange, undo. That was transformative. Everything since has been incremental. Better formatting. Cloud sync. Collaboration. Useful, but not a leap.

We think the next one is here.

Not because AI can write your novel for you — it can't, and it shouldn't. But because the combination of the right experience and intelligent assistance changes what's possible for a single writer sitting down with an idea.

No more staring at a blank page for an hour. No more losing the thread of your story because your world is fragmented across a dozen documents. No more waiting until a draft is perfectly polished before sharing it for feedback. Everything just happens faster, and the experience makes it easier to stay immersed in the work.

Where we draw the line.

There's a version of this that writes the story for you. We're not building that.

Storyforge is built on a simple principle: you steer, and the tools remove friction. When you're stuck, the assistant helps you move. When the structure feels tangled, it helps you see the shape. When a draft is rough, the editor highlights what a second pair of eyes would catch — so you don't have to wait weeks for that feedback.

But the voice is yours. The choices are yours. The story is yours.

We're also not prescriptive about how much AI a writer uses. Some want a constant collaborator. Some want it to stay quiet until called. Both are right. The platform adapts to how you work, not the other way around.

Built for the work, not the format.

A novel and a screenplay are different documents. But the work underneath — building characters, shaping worlds, structuring narrative, breaking through the moments where you're stuck — that work is the same.

Storyforge gives each format its own tailored editor. Write a novel. Write a screenplay. Build a storyboard to bring a scene to life visually. Run a writers' room where a team builds together. And if your universe spans multiple stories, a shared world connects them so a character introduced in one story carries into the next without you rebuilding them from scratch.

The ambition isn't to be a better document editor. It's to be the place where serious stories get built.

Why we can't stop using it.

This isn't the part where we pretend to be objective. The person who designed Storyforge wrote twelve chapters of their own story on it and couldn't stop. The people we've shown it to have asked when they can get in. We start testing soon.

We built this because we wanted it to exist. We kept building because using it felt like something we hadn't felt from a tool in a long time: that rare thing where the software disappears, and you're just doing the work.

If you write stories or want to, we think you'll feel it too.