Why Readerling

When I have a new book coming out, I have a checklist of things to do that has nothing to do with writing the book.

I post in Facebook groups. I draft a newsletter. I post on Twitter, then Bluesky too because some of my readers moved over there, and I keep telling myself I should figure out BookTok one of these months. I keep my author website current. I make sure I show up — regularly enough that the algorithm remembers I exist, because if I go quiet for a couple of weeks, my royalties remember it for me.

I'm an indie author. I write full-time. I'm also a developer with ADHD, which means I know exactly what it costs to context-switch between five social platforms, a newsletter tool, my writing app, and the storefronts. I do it because that's how books get marketed in 2026. I don't have to like it.

And after all of that, I still don't know who my readers are.

Amazon will tell me how many followers I have and where each book ranks. They'll tell me when sales drop and when they spike. They will not tell me who clicks through to book two. Who finished the book on Kindle Unlimited and who put it down on chapter three. Who left a review because they loved it. Who asked for a refund. Which titles get returned more often than others, and why.

The storefronts hoard everything they collect about my readers, and the highest bidder for that data is never going to be the author. It's never going to be me.

Where Readerling came from

I started thinking about Readerling about three-quarters of the way through building Scribi.

I was already thinking about what else Scribi might do for me — wire in a newsletter API, automate my social, build a publishing pipeline. Anything that pulled my workflow into one place and lowered the cognitive load. The depressing realization was that even if I solved the workflow, I still wouldn't be heard. Not consistently. Not even by readers who specifically chose to follow me. The algorithm decides whether they see my post on any given day, and the algorithm has already decided that someone else they follow is more interesting this week.

Newsletters do better, but only if you've built one to scale, and most of us haven't and most of us never will. Even readers who do open every email have inboxes that look like ours — fifty newsletters, a hundred pieces of book promo, the same signal-to-noise problem on a different surface.

What I wanted was a focused space. Something with real value to a reader and an author at the same time, where I could share a moment from the book I'm working on — the line that made me laugh, the chapter that wrecked me, the cover I'm finally proud of — and have it land with the people who chose to be there for it. Not get mixed in with everything else. Not get filtered out.

What it is, on day one

Here's what Readerling looks like the day Scribi 1.0 launches.

You flip a switch in Scribi. Your Readerling page is live. It has a sign-up URL you can put anywhere — in the back of your books, on your link tree, in the newsletter for the readers who do open every email.

The books you've published — and the ones you have on pre-order — appear on your page automatically. Pen-name organized, story-world organized, series organized, with covers and store links and descriptions, in whatever order makes sense for your catalog. Your readers see a clean sales page that updates whenever you do.

When you're working on something and a thought hits, you click a button in your editor, type a quick update, and it goes to your followers' feeds. The reader on the other end gets a push notification on the Readerling app — straight from you, the moment you posted it. No reordering. No "we thought you'd be more interested in this other thing." Pre-orders work the same way: you announce it once, your followers get notified, and they get reminded as the date approaches.

That's the whole shape of it on day one. It's small on purpose, and it's free.

Why it works through Scribi

For now, the only way to post on Readerling is through Scribi. That's a deliberate choice, and it's worth explaining.

The first reason is practical. Plot Foundry isn't venture-funded. There's no marketing budget, no growth team, no investor money waiting to be spent on user acquisition. Scribi licenses and cloud subscriptions are how the platform stays afloat, and they're how Readerling stays free for authors and readers. Tying the two together is what makes it possible to not monetize Readerling aggressively — no ads, no algorithmic boosting for pay, no selling reader data to the highest bidder. The math works because Scribi exists.

The second reason is trust. Gating access through Scribi means it's not trivial for bad actors to flood the platform with fake pen names, impersonate real authors, or automate a thousand AI-generated slop books. The license requirement is a meaningful speed bump. It also means there's a thread to pull on when something goes wrong — Readerling activity is tied to a Scribi account, which raises the cost of abusive behavior considerably.

The third reason is what it signals. Readerling is for working authors and for the readers who want to follow them. The Scribi gate isn't there to keep anyone out — it's there to make sure the people inside actually mean it. As we add features for readers, I want to be able to tell them with confidence that the authors they'll find here are serious about what they're doing. That promise gets a lot harder to keep if anyone can spin up a profile in thirty seconds with no friction at all.

I know this won't sit right with every author. There are writers who'd rather work in tools they already trust, and asking them to adopt Scribi to get a Readerling presence is asking for something real. I've tried to make Scribi worth the ask on its own — a flexible, modular tool that doesn't force any decisions about how you write. But I won't pretend the bundle isn't a bundle. It is. The honest pitch is: Scribi is a good writing tool, Readerling is a useful reader-facing platform, and together they cost less to run as a single thing than they would as two separate things. That's why it works this way for now. It may not always work this way. When the platform is healthy enough to support an open author API without compromising the things that make it trustworthy, we'll talk about that.

Where it could go from here

Where Readerling goes next depends partly on whether other authors find it useful. Here's where I'd like to take it.

If enough readers gather, I want to make Readerling a place where authors can sell books directly and keep ninety percent of every sale. I'd like to give authors actual insight into how readers engage with their work — not surveillance, not anything tied back to a specific person, but real aggregated signal. What holds attention. What gets reread. What kinds of readers your audience is actually made of. Which tropes and themes they're searching for next. The data the storefronts collect and refuse to share.

I want discovery to work by reading habit instead of buying habit, so that the next reader looking for hockey-romance-with-enemies-to-lovers actually finds your book — even when Amazon's recommendation engine has decided to point them somewhere safer for its margin. Reading circles and book clubs, eventually, for the readers who want a more communal experience. A quiet feed for the ones who don't.

We're not chasing a billion-dollar valuation here. Plot Foundry — the studio behind Readerling and Scribi — isn't venture-backed. There are no investors waiting on an exit. The goal is to be sustainable and honest, not enormous. We grow when authors and readers want it to grow, in directions that make the experience better for both.

If you want to read more about how Plot Foundry is structured and how Readerling stays funded, Our Approach goes into more detail.