Why Doomsday Pivot! Is Climbing Royal Road, and What Writers Can Learn

Where does Doomsday Pivot! stand, and why is it climbing?

Where it stands. As of October 22, 2026, it is #1 on the main Rising Stars list, the LitRPG view and the Fantasy view. Chapter 1 went up on October 6.

Why it is climbing. Three things stand out to us, and only the first is hard to repeat.

1. He brought readers. Wales has been publishing web fiction for years, and reviews name Worth the Candle, Thresholder and This Used to be About Dungeons. Some readers were ahead on Patreon from the start. The next section has his numbers.
2. The launch had depth and a rhythm. Nine chapters went up on day one, and since October 12 a new chapter has gone up every day at about the same hour. The first book was written before launch, which makes that schedule easy to keep.
3. The twist fits in one sentence. Startup founders in a System apocalypse. The title is a pun on the startup "pivot," so the twist is on the cover before anyone reads a word.

Readers are rating and favoriting, too. Its ratings and favorites are the most among the six serials we checked near the top of Rising Stars this week. For how the list itself works, see our guide to Royal Road's algorithm and Rising Stars.

How big is the audience Alexander Wales brought with him?

A long track record. Wales has been publishing web fiction for years. On Royal Road, his profile lists Worth the Candle at 2.7k pages, and his author box shows achievements for publishing at least 3,000,000 words and for reaching 5,000 followers on a single fiction.

Three of his finished serials are sold as ebooks and audiobooks, listed in the table below.

A Patreon that runs ahead. His Patreon calls Doomsday Pivot! "already-written" and says it updates there on Mondays, five to seven chapters at a time, "keeping it well ahead of RoyalRoad." Patrons at $5 a month get it, along with his serials AGARES and Wisteria.

Readers followed him there. Two early reviews mention reading on Patreon, quoted below. Wales shows both his member count and his monthly earnings on the page, which is why we can report them.

Paid members rose from launch day. Graphtreon, which logs public Patreon figures daily, shows paid members flat from late August to October 5, then up every day from October 6. It can't say why people joined, but the climb begins on October 6, the day chapter 1 went up on Royal Road.

What does the fiction page promise?

The title. A pivot is what a startup does when its plan stops working, and the end of the world is a big reason to change plans. There are no genre keywords in the title. Wales's name does that job, and reviews lead with it.

The blurb. It opens on an image. Duluth has been separated from Earth "like someone took a giant cookie cutter and slammed it straight down from the sky." Then it lists side effects of the new classes, from birds flying in grid formation to "accountants walking around with their heads on fire."

Only after that does it introduce Nat and his small company. The hook lands as a startup joke. They were already planning to take on bigger companies, so how much harder could alien demons be?

The "What to expect" list. It mixes real promises ("Rational decision-making," "Steady escalation," "Local politics") with oddly specific jokes, like "A digression on squirrel species" and "Octopus-based recipes." Vehicular manslaughter is listed twice, once "(but not like you think)" and once "(like you think)."

The jokes do two jobs. They show the voice, and they are specific enough that you believe they are real scenes.

The AI disclosure. The blurb ends with one. No AI was used to write the story, some was used to catch mechanical errors, and a link leads to a longer post. Three short sentences answer the question before a reader has to ask it.

The tags. LitRPG, Kingdom Building, Male Lead, Action, Adventure, Fantasy, Thriller, Apocalypse, Magic, Survival and System Invasion. Together they sell the stakes. There is no Comedy tag, even though the blurb and chapter 1 are funny, so the blurb carries the humor on its own.

Kingdom Building fits the startup angle, because the story is as much about building a group as about one person getting stronger.

The cover. It is an illustration in two colors, mustard yellow and deep red. Three people seen from behind look out at a burning skyline with Duluth's Aerial Lift Bridge in it, under a large hand-lettered title. There is no armored hero, no glowing weapon and no status window. It sells the trio and the place.

The author's disclosure post says the cover began as a 2023 mock-up that someone else stitched together from AI image generator output. He then paid an artist to clean it up and repaint it, adding the bridge. For more on covers, see Royal Road cover design that converts.

How was the launch timed?

The posting record. The table of contents shows a big batch on October 6, three chapters over the next four days, a day off on October 11, then one chapter a day at a fixed hour from October 12. All times here are UTC.

Three details matter more than the totals.

The launch batch ends on a hook. Chapter 7 ends with a system alert that an incursion is coming in 45 minutes. Chapter 9, the last chapter posted on day one, ends as the incursion begins. A reader who binged the whole batch on October 6 had a reason to come back on October 7.

The first arc closes inside the first week. The battle runs through chapters 10 to 12. Chapter 12, posted October 10, closes the battle with a system message.

"Sector Alert: First Incursion Defeated! Skill Descriptions Revealed! Grace Period: 168 Hours"

Four days after launch, new readers had a complete first arc, a reward (the skill descriptions) and a new clock (168 hours until the next threat).

The book was already written. In his AI disclosure post, dated September 21, 2026, Wales says only the first book is written and that the bulk of it was written in 2023. A reviewer recalls reading "the first few chapters back in 2023 when they were written."

The same post says the serial follows "the usual webfiction model" of releasing chapters on Patreon first, with Royal Road on a slower cadence. A finished book is what makes a daily post at a fixed hour easy to hold.

If you are planning your own backlog, see how many chapters to stockpile before launching and the best time to post on Royal Road.

How do the opening chapters hook readers?

Chapter 1 is narrated in first person, past tense, by Nat, a startup founder. It is shorter than the serial's average, and it does four things quickly.

1. The first line sets the tone. The team is "intent on saving the world" and "that was before the apocalypse." One sentence gives you the narrator's ambition, his humor and the genre.
2. It opens on character, in an office. Nat is arguing with his company's education AI, which insists that an ostrich runs faster on all fours. Jake, his cofounder, asks whether he checked. The banter shows who these two are before anything strange happens.
3. The system arrives a quarter of the way in. A blue Class Selection pop-up with no close button covers Nat's screen. The first class on offer is Fighter. The second is Octokinestithist. From there the chapter is the genre promise in action.
4. Each lead meets the system in character. Jake clicks Confirm on Fighter, joins the first guild he finds and earns an achievement. Charlotte finds warnings printed under some classes, including one that can violate consent. Nat refuses to pick yet and thinks the list should have been a dropdown. Three reactions, three personalities, no description needed.

The chapter ends on the title line, with Nat telling the others, "I think this company is going to have to make a major pivot."

Chapter 2 keeps the pressure on. Charlotte counts the classes and eight kinds of warning, and the chapter ends with a plane exploding where Wisconsin should be. Reviewers enjoy the system's bad design as much as its danger.

The pattern matches our chapter 1 template. The genre promise arrives early, and the scene before it does character work.

What are early readers saying?

Most reviews give five stars, as the chart below shows. Here are the themes that come up most.

The author's track record. Many reviews start with Wales himself. One says simply that "this author has a good track record in my books."

A worn subgenre taken seriously. One reviewer likes the focus on realistic consequences and "treating the 'System Apocalypse' as an apocalypse."

Strange classes. A reviewer says the classes are "intended to be as weird and oblique as possible." Names like Octokinestithist and Analeptic give readers something to guess about between chapters.

Leads who think. Readers like that the characters plan and that the story does not flatter them.

Tone and prose. One reviewer says the narration and dialogue switch "smoothly from comedic to serious and back again." The style and grammar scores in the first section back that up.

The criticism. Most of it is mild so far, and much of it comes from fans of his earlier books who measure this one against them. Two reviews are harsher.

• A thin supporting cast, for now. "Jake and Charlotte are kind of just there so far," writes one reviewer, who adds that Nat "more than makes up for it." A 4.5-star review is unsure what isn't clicking, and guesses at "An opening that's a tad too quick" or an introduction that makes the trio "come off a bit flat."
• Characters who serve the argument. A 3-star review, "Technically Sound but Hollow," finds that the characters "blend into each other" and that their words and actions read as "token positions in an argument."
• The class pick. A 2-star review posted October 22 says the five-chapter wait for Nat's class raised its writer's expectations, and that the pick itself was "one of the most generic, overused classes imaginable."
• Characters who adapt very fast. Another reviewer finds it hard to picture three adults who "instantly go full throttle on adapting to the apocalypse."
• The startup pitch. One reader thinks the startup angle makes sense but "doesn't bring hype like gimmicks do." Another notes that the lead's background in tech and AI "may filter some people."
• Chapter length. One reviewer's "only minor gripe" is chapters kept "around 2k words to optimize for Royal Road," though the same reviewer says the pacing works.

How is the story built under the hood?

Point of view. First person, past tense, one narrator. Everything comes through Nat.

The wider world arrives through the guild message board Jake joins in chapter 1, where players post threads about sectors, incursions and the dead. That board lets the story report on New York, Mumbai and China without leaving Duluth.

Chapter length. Chapters are short and fairly even. For how that compares, see how long Royal Road chapters should be.

Arc shape so far. The 22 chapters fall into three movements, laid out in the table below. The grace period works as a ticking clock. By chapter 18, Nat is counting six days until the next incursion, and every local problem is weighed against it.

Chapter endings. By our reading, four of the six hard cliffhangers sit around the first battle (chapters 7, 9, 10 and 11). Others end on a reveal, a decision or a joke, such as Jake staring at a tree he has just cut down with one sword stroke and announcing that he has become a badass.

One reviewer counts the endings in the story's favor, quoted below. Every ending still gives a reason to open the next chapter.

Exposition. The rules arrive when someone needs them. In chapter 9, in the back seat on the drive to the battle, Nat runs through what the team knows about levels, attributes and skills. The reader gets the rules just before they matter.

How does the progression system work on the page?

There are 261 classes, and the system refuses to explain them. Class names come with no descriptions, only the occasional warning. The team has to guess from names and rumors, and Charlotte keeps a spreadsheet. The author's disclosure post says he filled out a spreadsheet of all 261 classes himself, then reworked it.

The table below shows what the team has worked out by chapter 9, all of it told in prose. We found no full stat sheets in the first 22 chapters. System messages appear as single plain lines, like the Sector Alerts.

Information is the reward. Skill descriptions stay hidden until the first incursion is beaten at the end of chapter 12. In chapter 13 they appear as short plain-text entries, and the reader finally learns what Nat's shadow minions can do.

Nat decides that everything up to the first incursion was the system's onboarding process, which is how a product person would see it. The battle earns the knowledge, so the knowledge feels like loot.

Powers have costs and side effects. The blurb's accountants with their heads on fire are the joke version. The serious version comes later. A new ally can burst into a swarm of squirrels, loses some of them in a fight in chapter 21, and in chapter 22 comes back a foot shorter.

The group is the build. Nat's class gives him shadow minions, and he tries to think of them as employees. One reviewer sees building the group as part of progression, quoted below. That is the Kingdom Building tag in practice.

If your own system has this many moving parts, our guide to tracking LitRPG stats shows one way to keep them straight.

What should you borrow, and what shouldn't you copy?

Worth borrowing:

• A twist you can say in one sentence. Write yours down before the blurb, then see whether the title can carry part of it, the way "Pivot" does here.
• A blurb that opens on an image. Lead with the strangest true thing in your first chapters, then the cast, then the hook.
• A specific "What to expect" list. List real scenes and real promises in your own voice. A line like "A 200mph fastball" does more work than a row of trope names.
• A short AI disclosure, if it applies. Say what you did and didn't use, in plain words. For the platform side, see Royal Road's AI tag rules.
• A day-one batch that ends on a hook, and a first arc that closes in week one. Plan the batch so its last chapter leads into your first big set piece.
• A fixed hour. Once the batch is out, post at the same time on the days you promise.
• A system that withholds things on purpose. Hold back descriptions, menus or ranks, and hand them out as rewards for surviving.
• Character through first contact. Let each lead react to the first system prompt in a way only they would.
• A continuity pass on your backlog. After his own editing pass, Wales uploaded the book to NotebookLM and asked about continuity. It caught Duluth numbered as sector 145 in four places and 152 in three, a name misspelled twice and Nat calling Jake's car "my car." He adds that some flags were wrong and all of it needs double-checking.

Not worth copying:

• A title with no genre keywords, unless your name already sells. Wales's name is the draw for many of his readers. Other serials near the top of Rising Stars this week spell out their genre, like Fight Dirty (Stealth Archer LitRPG in brackets) and Midnight's Monster (LitRPG, Vampire Evolution and Dark Fantasy after a pipe).
• The famous-name effect. Nobody can borrow a review that says "It's Alexander Wales." You can build toward your own version with earlier work, a Patreon and readers who know your name.
• The startup premise itself. The lesson is to use a lens you know. Wales writes that Duluth is where he lives and that he has been part of a few startups. Use your own job, town or obsession.
• Co-leads drawn mostly through their reaction to the system. It is quick and funny, and some readers still found Jake and Charlotte flat in the early chapters. Give each co-lead a want of their own early on.
• A delayed class pick with no reason behind it. Nat waits five chapters because he is a planner, and his friends level up in the meantime, so the story keeps moving. A lead who waits for no reason reads as stalling.

A launch checklist you can use

1. Write your twist in one sentence, and put it, or a pun on it, in the title.
2. Open the blurb on the strangest image from your first chapters, and end it with a short, specific list of what readers will get.
3. If you used AI anywhere, add a plain disclosure line that says exactly how.
4. Pick tags that sell the stakes, and let the blurb sell the voice.
5. Make sure the cover shows who the story is about and where it happens.
6. Finish at least your first arc before you post chapter 1.
7. Post enough on day one to reach your first big set piece, and end the batch on a hook.
8. Close the first arc in week one, with a reward and a new clock.
9. Pick a posting hour and hold it.
10. In chapter 1, deliver the genre promise by about a quarter of the way in, and let each lead react to it in character.
11. Check the backlog for continuity before launch, then check each new chapter before it goes up.

Where PlotWrite fits. Doomsday Pivot! already has 261 classes, a growing cast, numbered sectors, ranks and skills that level up. Wales finished and edited his first book before launch, then ran a continuity check across all of it.

If you write a few chapters ahead of what you post, there is no finished book to check at the end. PlotWrite is built for that case.

Its Story Bible keeps a page for every character, class, place and skill, with what is true at each chapter. Check chapter compares each new chapter with everything before it and flags contradictions before you post.

It works with the Claude or ChatGPT plan you already pay for, and memory and checks need no AI tag.