If you’ve logged into Storyverse Author recently, you’ve seen the same version number every visit: v3.40.0. Same lobby, same dashboard, same feature set. Three subdomains all reporting the same thing.

That’s not a stall. It’s a freeze. And it’s deliberate.

This post explains what we’re doing, why we’re doing it, and what comes next.

The decision: finish the storefront before opening the doors

Storyverse Author is not a brand-new app. The codebase covers a writing dashboard, a production tracker, a 19-structure plotting library, scene-level methodology tagging, a relationship graph, a knowledge base, manuscript editing, an interactive universe map, and infrastructure for the Fiction Frameworks marketplace. By release-cycle math, we should be shipping a feature every two weeks.

We’re not. The reason is that the app’s home — the marketing site, the membership tiers, the framework sales pages, the member dashboard, the account-management flows — wasn’t ready to receive new members. So we made a call: stop shipping app features until the storefront is production-grade, then reopen the doors.

The math behind that call is simple. A new member who signs up today and lands on a half-finished membership page has a worse first impression than a new member who signs up next month and lands on a complete one. Compounded across the early growth window, the difference is enormous. A first impression is only first once.

So the app froze, and the website work began.

What’s actually shipping during the freeze

The freeze isn’t idle time. It’s a different category of work. A short summary of what’s gone live on the marketing side during the v3.40 plateau:

The full pricing page rebuild, with five-tier feature comparisons that actually parse. The membership-tier sales pages — Explorer, Navigator, Architect, Master Cartographer — each with their own value proposition and CTA flow. The Fiction Framework offer pages and starter-kit pages for all three frameworks. The lead-magnet opt-in pages. The checkout pages, redesigned around a single canonical template that’s now being cloned across the remaining nine. The member dashboard at /account/ with native order history, downloads, and subscription management. The login page with proper error handling. The account profile editor. The Site Chrome plugin that ties all of it together visually.

Most of that wasn’t a redesign. It was a rebuild from scratch, on a different page system, with a coherent design language for the first time. By the time the freeze ends, the site you see at signup will look like the work behind the app — not like a placeholder for it.

The blog you’re reading is part of this work

This very post is one of the first three published under the new blog system. The blog scaffold went live this week — categories created, templates configured, the OptimizePress ThemeBuilder integration validated against the rest of the site. We picked three categories to start: Craft, Frameworks, and Platform Updates. You’re reading the first Platform Updates post.

The blog matters because the conversation between us and the writers we’re building for can’t only happen via email. Some ideas need to be permanent, indexable, linkable. The blog gives us that channel. Expect it to fill in steadily — craft essays, framework deep dives, behind-the-build notes, platform release notes — once the website sprint completes.

What comes next

The website sprint is in its final stretch. After it lands, the order goes:

Beta access reopens. A small cohort first — five to ten testers, capped at 25 absolute maximum. Beta isn’t a free-for-all. It’s a structured pass at the platform with people we can support directly, fix bugs for in-flight, and learn from before the wider rollout. Beta testers get the betaauthor subdomain, dedicated feedback channels, and a real say in what ships next. If you’re interested, the application path will be announced through the newsletter.

Custom Structures during beta. The most-requested feature on our backlog is letting members build their own plotting methodologies on top of the 19 we ship — name your beats, define your structure, tag scenes against it, get the same report views the built-in structures give you. Custom Structures will land mid-beta, on the betaauthor subdomain first.

Manuscript export after beta. Docx, EPUB, Markdown, PDF, and plain text. The manuscript editor is already built — Tiptap-based, with chapter and scene navigation, full revision history. Export is the missing piece, and it’s first up after beta closes.

Mood music library after that. A curated library of original Suno-generated tracks tagged by tone — for writers who want a soundtrack while drafting and don’t want to assemble it themselves. This one’s further out.

Additional Fiction Frameworks throughout. Maple Creek, Prometheus Protocol, and Shattered Throne are the launch three. More are scoped. We won’t announce specific titles until they’re closer to ready, because Frameworks take months of work and we’d rather under-promise.

A note on transparency

We could have shipped app features through this period and let the website finish in the background. Most software teams do exactly that. We didn’t, because the website is the product to people who haven’t signed up yet — and the people who have signed up deserve a complete experience for the price they’re paying, not a partial one with the rest perpetually “coming soon.”

We’d rather hold features and ship them in a context that does them justice. If that means a quiet release period, that’s the cost of doing the work properly.

The next version bump will be v3.41, and it will land the moment beta opens. We’ll write a post about it when it does.

Where to follow along

Three places we’ll announce the freeze ending:

• The Story Architect newsletter (one email a week, Thursday mornings)
• This blog, under the Platform Updates category
• The member dashboard, for anyone already inside

Thanks for the patience. The work matters more than the cadence.