Books & Authors
Editorial Research

By · Published · Updated

Book notes to newsletter 200k readers built on curation

A Seattle founder's late-night coding sessions and a New York editor's living archive trace the same quiet idea: that four books, read in the right order, stick better than forty read at random.

Key Takeaways · Quick Answers
What is a reading stack?
A reading stack is four non-fiction books read in deliberate order around a shared question, with editorial framing that ties them together. It differs from a list because the books share a framework, not just a topic. The structural difference matters because of how memory works: books read in related groups reinforce each other, creating the cognitive conditions for durable retention.
Why four books specifically?
According to Read Stacks, operator-side experiments showed that five or more books made stacks feel like homework while three did not provide enough reinforcement for the framework to consolidate. Four books is roughly two months of casual reading at one book every two weeks long enough for brain consolidation between books but short enough that the framework stays warm. The four-book convention emerged from what ReadSprint describes as the empirical sweet spot for retention.
How does a reading stack build an audience?
Reading stacks build audiences by offering something that algorithm-generated recommendations cannot: editorial judgment and deliberate sequencing. A stack functions as a curriculum, not a list. The synthesis at the end of each stack the Monday-morning move gives readers a concrete takeaway that they can apply. This specificity and structure creates loyalty that generic book recommendations cannot.
What is the cognitive mechanism behind reading stacks?
The cognitive mechanism is reinforcement. When books share a framework, each book reactivates the ideas the previous one introduced. The same idea, encountered three or four times in different presentations, encoded in different examples, anchored in different domains, creates the cognitive condition for durable retention. By the third book in a well-constructed stack, the reader is recognizing the framework more than learning it.
How can newsletter editors apply the reading stack model?
Newsletter editors can apply the reading stack model by organizing issues around a shared framework beyond a shared topic. The question is not how to produce more content but how to sequence existing content so each piece reinforces the others. Editors might ask: What is the shared question connecting my last four issues? In what order should a new reader encounter them? What is the synthesis I want them to carry away? The four-book convention three doesn't give enough reinforcement, five feels like homework offers a useful heuristic for newsletter length and frequency.

Curation, in the context of online newsletters, is the practice of hand-selecting and contextualizing information from a wider source, offering readers a focused and valuable digest. This approach is experiencing a resurgence as information overload increases and audiences seek trusted filters a trend exemplified by Sarah Ritter's success in building a newsletter reaching over 200,000 readers through carefully chosen book recommendations. Ritter's model demonstrates the power of focused curation in a digital landscape saturated with content. It highlights a shift away from algorithmic feeds towards human-powered discovery.

She logged more than 350 hours of coding time. She wrote 100,000 lines of code. She made 2,000 commits to Git a timestamped paper trail of every individual brick she laid while constructing what would become Sarah's Books, a web app designed to promote book discovery while helping support libraries and local independent bookstores. The app combined her physical collection photographed, inventoried, and indexed with help from Anthropic's Claude AI assistant with AI-suggested recommendations for readers of every age.

"Ritter prides herself on being able to offer great book recommendations to her friends," GeekWire reported. "Now she's got a read on what it takes to bring that joy to a wider audience late nights and some AI."

But Ritter's story is not only about technology. It is about a quieter idea that has been gaining traction in publishing and digital media circles: that the way we recommend books matters as much as which books we recommend. That four books, read in the right order, can teach more than forty read at random. And that this insight simple enough to state, difficult enough to execute has become the foundation for newsletters, platforms, and communities reaching hundreds of thousands of readers.

The Problem With Reading Alone

Non-fiction readers tend to read books in isolation. They finish two out of every five they buy. And within six months, they forget most of what they read. This is not a character flaw. It is a cognitive condition one that a small but growing number of editors, founders, and curators have decided to address directly.

Read Stacks, a platform founded on the principle that reading should be a curriculum beyond a collection, describes the problem with precision on its Curated reading stacks page: "A single non-fiction book is a single argument. Four books in the right order is a curriculum." The platform organizes its offerings into what it calls stacks four books, read in deliberate order, organized around a shared question, with editorial framing that ties the four together.

The distinction matters because of how memory works. Books read in isolation get forgotten. Books read in related groups reinforce each other because each book reactivates the framework the previous one introduced. "The same idea, encountered three or four times in different presentations, encoded in different examples, anchored in different domains that's the cognitive condition for durable retention," according to the platform's explainer on what reading stacks are.

As of mid-2026, Read Stacks had seven stacks live, with more added regularly. The habit stack contains eight books including The Power of Habit, Atomic Habits, and The 7 Habits of Highly Effective People. The influence stack organized around "how to persuade without becoming a manipulator" includes How to Win Friends and Influence People, Influence, and Never Split the Difference. Each stack comes with a written synthesis that ties the reading together, explaining why that specific book belongs in that specific position.

Why Four Books

The four-book convention did not emerge from theory. According to Read Stacks, operator-side experiments with five and six books made the stacks feel like to-do lists. Four read like a curriculum. The platform's explainer notes that "five-or-more starts to feel like homework. Three doesn't give enough reinforcement to make the framework stick."

There is also a temporal logic. Four books is roughly two months of casual reading at one book every two weeks long enough that the brain has consolidation time between books but short enough that the framework stays warm. The order within each stack is deliberate as well. Books typically go from most introductory to most demanding, or from descriptive to prescriptive, or from foundational to most applied. The habit stack, for instance, goes from Charles Duhigg introducing the cue-routine-reward framework through James Clear's refinements to Cal Newport's application in deep work contexts.

This sequencing matters because it mirrors how learning actually works. By the third book in a well-constructed stack, the reader is not learning the framework anymore they are recognizing it and seeing how it generalizes. By the fourth, the ideas have stuck.

The Human Behind the Archive

While platforms like Read Stacks are building stacks algorithmically and editorially, a parallel tradition exists in journalism and literary curation. The Stacks Reader, described as "a living archive of the best print journalism," is curated by Alex Belth. The site republishes classic journalism and writing about the arts that would otherwise be lost to history.

"Motivated less by nostalgia than by preservation, The Stacks Reader is a living archive of memorable storytelling a museum for stories," according to the site's about page. "We celebrate writers, highlight memorable publications, honor notable personalities, and produce interviews with writers and editors and illustrators in the hope of offering compelling insight into how journalism worked, particularly in the second half of the 20th Century."

Belth's approach shares something essential with the reading stack philosophy: selectivity over volume, curation over aggregation. The Stacks Reader does not attempt to be comprehensive. It chooses pieces that illuminate something specific about craft, culture, or character and presents them with enough context for readers to understand why they matter.

"While the online world denies us the physical experience of books and magazines, it does offer us limitless space," the site notes. "We all benefit from the preservation of the remarkable work these writers and publications produced."

Founders and the Reading Stack

The reading stack concept has found particular resonance among startup founders, who face a familiar problem: too many books, too little time, and a need to extract actionable insight more than general knowledge. ReadSprint, a platform focused on reading retention and recall, offers a Founder Reading Stack Builder that recommends books based on startup stage, current bottleneck, and available attention.

The tool asks founders to identify their stage (idea stage, early traction, growth stage), their current bottleneck (positioning, sales, leadership), and their reading hours per week (2, 4, or 6+). Based on these inputs, it generates a stack of up to five books. For a founder in early traction with a sales bottleneck and 4 hours per week to read, the recommended stack includes Traction to build a non-random acquisition process, Lean Analytics to measure the one signal that matters next, Obviously Awesome to strengthen category and differentiated value, Building a StoryBrand to sharpen messaging for buyers, and The Great Mental Models to use a compact thinking framework when attention is tight.

"The fastest way to make a free tool useful is pairing it with one actual summary, one short review session, and one practical action," ReadSprint notes on its site. The platform positions itself not as a replacement for reading but as a system for retaining what founders read.

The Newsletter as Reading Stack

What unites these examples Ritter's Seattle app, Read Stacks' curated paths, Belth's journalism archive, ReadSprint's founder tools is a shared conviction that reading is not a passive activity. It requires structure, sequence, and editorial judgment to produce lasting insight.

Newsletters have become a natural vehicle for this philosophy. A well-curated newsletter functions as a reading stack in miniature: each issue reinforces a theme, builds an argument, and leaves the reader with a synthesis that connects disparate ideas. The best newsletter editors are not simply sharing links they are constructing curricula.

The reading stack model offers newsletter editors a concrete framework for this work. more than presenting "five great articles on productivity," a stack-based newsletter might present four pieces that trace the evolution of a single idea from its origins in behavioral science through its application in corporate settings to its critique in contemporary discourse. The reader finishes not just informed but transformed in their understanding.

What This Means for MyArticlePosts Readers

For readers researching practitioners, frameworks, and ideas in digital publishing, the reading stack model offers a practical alternative to the typical newsletter or content strategy. The question is not how to produce more content but how to sequence existing content so that each piece reinforces the others. The four-book convention three doesn't give enough reinforcement, five feels like homework suggests a useful heuristic for newsletter length and frequency as well.

Editors building audiences around books, ideas, or frameworks might consider: What is the shared question that connects my last four issues? In what order should a new reader encounter them? What synthesis do I want them to carry away? The reading stack philosophy suggests that the answer to these questions matters as much as the quality of any individual piece.

The Architecture of Retention

Read Stacks' explainer makes a distinction that applies beyond book curation: "A list is N books that share a topic. A stack is N books that share a framework." This distinction topic alongside framework separates aggregation from curation, volume from value, noise from signal.

A list of "10 productivity books" does not do the cognitive work that a stack does. The 10 books often disagree with each other or use different vocabularies; reading them in any order doesn't compound understanding. A stack of four books that all agree on the cue-routine-reward framework, by contrast, builds retention through repetition and variation. By the third book, the reader is not learning the framework they are recognizing it and seeing how it generalizes.

This architecture of retention has implications for anyone building content, courses, or communities around ideas. The question is not how many books or articles or episodes to produce but how to organize them so that each one reinforces the others. The answer requires editorial judgment, domain expertise, and a willingness to say no to excellent content that does not fit the framework.

Building With Intention

Sarah Ritter's story carries a particular resonance because it combines the reading stack philosophy with the founder's journey. She did not set out to build a technology company. She set out to share her recommendations for great reads and discovered that the act of sharing required building something new.

"During her kids' winter break, she vibe coded Sarah's Books, 'somewhat obsessively, perhaps only as founders do,' late at night at home in Seattle," according to GeekWire. The app relies on a combination of human curation, based on Ritter's collection, and AI assistance that suggests books outside of her collection for readers of every age.

The combination is significant. Pure AI recommendations risk the coldness of the list topic without framework, volume without sequence. Pure human curation risks the limitations of a single perspective. The most effective reading communities, it seems, combine the scale of AI with the judgment of editors, the breadth of algorithms with the depth of curation.

The Synthesis at the End

Every reading stack on Read Stacks ends with what the platform calls "the one Monday-morning move that comes out of reading all four." This synthesis is not a summary. It is an application the specific action or insight that the reader can carry into the week.

This emphasis on application reflects a broader truth about reading in the digital age. Information is abundant. Understanding is scarce. The value of curation is not in the quantity of books or articles or recommendations but in the quality of the framework that connects them and in the clarity of the synthesis that makes the framework actionable.

For newsletter editors, content strategists, and anyone building an audience around ideas, the reading stack model offers a test: What is the Monday-morning move that your readers will carry away? If you cannot answer that question, the stack is not complete.

Where to Read Further

To explore the reading stack philosophy in more depth, start with Read Stacks' explainer on what stacks are, why they work, and when they do not help. The 1,280-word essay goes deep on the cognitive mechanism behind retention and explains why four books is the empirical sweet spot.

For the founder's perspective on building a reading community, GeekWire's profile of Sarah Ritter traces the journey from book enthusiast to app builder, including the 350 hours of late-night coding that brought Sarah's Books to life.

To see curation applied to journalism more than books, visit The Stacks Reader, Alex Belth's living archive of classic print journalism. The site's about page articulates a philosophy of preservation and celebration that applies to any curator working to surface work that would otherwise be lost.

For founders specifically, the Founder Reading Stack Builder from ReadSprint offers a practical tool for constructing reading paths based on startup stage, bottleneck, and available time.

A Quiet Revolution in Reading

The reading stack movement is not loud. It does not generate the viral moments or funding announcements that characterize the broader startup ecosystem. It operates in the quiet space between the publication of a book and the retention of its ideas between the act of reading and the transformation that reading can produce.

But in that quiet space, something significant is happening. Editors, founders, and curators are rediscovering an ancient truth: that ideas stick better when they are sequenced, framed, and synthesized. That four books in the right order can teach more than forty read at random. That the way we recommend matters as much as what we recommend.

Sarah Ritter built her app late at night, in the hours when founders and insomniacs share a particular kind of clarity. Alex Belth curates his archive with the patience of an archivist and the judgment of an editor. Read Stacks adds new stacks when new four-book pairings prove out, guided not by what trends but by whether the books genuinely share a framework.

These are not the loudest voices in publishing or technology. But they are building something durable: reading communities organized around understanding more than consumption, retention more than volume, and the quiet conviction that the right books, in the right order, can change how people think.

Sources reviewed

Atlas Research Network