The Wide Author’s Tech Stack

Every Tool You Need to Publish and Manage Your Books Across Every Platform — Built Around the ScribeCount OS

1. Why the Tech Stack Conversation Starts With ScribeCount

Managing a wide catalog across five or more platforms simultaneously is not difficult — but it is complex. Every platform has its own upload interface, its own royalty reporting schedule, and its own promotional ecosystem. Without the right tools and systems in place, managing a wide catalog becomes an administrative burden that competes with actually writing books.

The solution is a deliberate tech stack: a set of tools that handles each component of the wide publishing workflow efficiently, integrates with the others where possible, and scales as your catalog grows.

For most of the publishing tools conversation, “tech stack” means assembling five or six disconnected products — a formatting tool here, a link service there, an email platform somewhere else — and hoping they talk to each other. ScribeCount was built to collapse most of that fragmentation. Analytics, universal links, website traffic, email marketing, catalog management, and production tracking all live in one system, connected to the same verified sales data, accessible through a single login.

This guide walks through every layer of the wide author’s tech stack with that as the starting assumption: ScribeCount OS is the hub. Everything else is a spoke.

The table below maps every layer of a professional wide author’s publishing operation to its SC OS module, with fallback options for layers where the OS module is not yet live in your account. Green indicates an SC OS native module. Amber indicates layers outside the SC OS scope where a third-party tool remains the right choice.

3. Layer-by-Layer Guide

Layer 1: Royalty Analytics — Sales & Royalties Dashboard

This is the layer most wide authors underinvest in, and the one that causes the most operational pain. When you publish across five or more platforms, each reports royalties on its own schedule, in its own dashboard, in its own currency. Without a unified analytics layer, understanding your business requires logging into five portals, downloading five reports, and reconciling them manually in a spreadsheet — an exercise most authors abandon within months.

ScribeCount’s Sales & Royalties Dashboard is the direct solution. It connects to your Kobo, Apple Books, Google Play, Barnes & Noble, Amazon KDP, Draft2Digital, IngramSpark, and other platform accounts, pulling your royalty data into a single unified view. The Sunburst chart breaks down your business by platform, format, series, pen name, and territory simultaneously. The Historic tab shows your income over any time period. Per-platform donut charts let you see at a glance which retailer is carrying weight this month.

For wide authors, this is not optional infrastructure — it is the layer that makes every other decision in your business possible. You cannot make rational pricing, promotional, or catalog decisions without accurate income data across all platforms in one place.

Layer 2: Universal Links & Attribution — ScribeCount Linking

A universal book link is a single URL that routes each reader to their preferred retailer based on their device, location, and stored preferences. Wide authors use these everywhere they promote their books — social media, email newsletters, back matter, advertising — so that Kobo readers land on Kobo, Apple readers land on Apple Books, and Amazon readers land on Amazon, all from the same link.

ScribeCount’s Smart Linking & Attribution module is purpose-built for this, with a critical capability that third-party services cannot match: your link click data lives in the same system as your sales data. That means ScribeCount can show you not just which links got clicked, but which clicks converted to verified sales on which platform, in which territory, from which campaign. The traffic → retailer → revenue connection that fragmented tools can only approximate is a native first-party dataset inside SC OS.

Third-party alternatives like Books2Read (no sales attribution) and Geniuslink (no OS integration) are functional starting points but represent a significant data gap compared to SC Linking running inside the same system as your royalty data.

Layer 3: Website Traffic — Website Traffic Analytics

ScribeCount’s Website Traffic Analytics module tracks reader journeys — where they came from, which pages they visited, which links they clicked, and how those sessions connect to downstream sales activity. This is the layer that tells you whether your Facebook ads are actually moving books, whether your author website is converting visitors into buyers, and which traffic sources are worth your marketing budget.

The reason this matters more inside SC OS than in a standalone tool like Google Analytics is the data connection. Google Analytics can tell you a reader clicked a link. ScribeCount can connect that click to a verified sale on Kobo two days later. The attribution gap that forces most indie authors into guesswork — “I ran a promotion, did it work?” — closes when traffic, links, and sales live in the same dataset.

Layer 4: Email Marketing — ScribeCount Email (SCE)

Your email list is the one audience asset that no platform can take away from you. For wide authors, email is particularly important because it is the communication channel that exists above the platform layer — you can promote a Kobo deal one month and an Apple promotion the next, and the same subscribers receive both messages regardless of which retailer they prefer.

ScribeCount Email (SCE) is the native email marketing module inside SC OS, powered by the Author.Email infrastructure. What separates SCE from standalone email tools like MailerLite and Kit is attribution: SCE connects your campaign sends, open rates, and click-through data to the same verified sales data that your royalty dashboard tracks. When you send a launch email to your list, SCE can show you which campaign drove which sales, on which platform, in the days and weeks that follow. This is the capability that independent email tools cannot replicate without integration work they were not designed to do.

For authors whose SCE account is not yet active, MailerLite is the most widely recommended starting point in the indie author community — a generous free tier, reliable deliverability, and automation capabilities that scale well for authors building from scratch. Migrate to SCE when it is available in your account to gain the attribution layer.

Layer 5: Catalog & Asset Management — AuthorVault

AuthorVault is SC OS’s catalog and asset management module: the central repository for your ISBNs, blurbs, cover files, series data, pen names, retailer identifiers, and book-level metadata. Once your catalog is in AuthorVault, every other SC OS module can pull from it — your Linking module auto-populates retailer URLs from your Identifier Vault, your Digital Assistant can answer questions about your catalog, and your landing pages pull cover and description data without manual re-entry.

For authors managing a wide catalog across multiple formats and series, the alternative to AuthorVault is a growing tangle of spreadsheets, Airtable boards, and Notion pages that require constant manual maintenance. AuthorVault centralizes that into a single system-of-record that other modules depend on.

Layer 6: Production Tracking — AuthorFLOW

AuthorFLOW is SC OS’s production tracking module. It manages your manuscript pipeline — current projects, word count goals, series scheduling, editor and cover designer handoff dates — and connects production data to your revenue history. The question “does writing more books mean earning more?” becomes answerable when your output data and your sales data live in the same system.

Third-party production tools like Plottr handle story planning and series structure well, and authors who use Plottr for story beats and AuthorFLOW for business-level production tracking can run both in parallel without conflict.

Layer 7: AI Digital Assistant — Hey ScribeCount?

Hey ScribeCount? is the SC OS Digital Assistant — a natural language interface that lets you query your entire publishing business in plain English. “Which series is performing best on Kobo this quarter?” “What was my per-book royalty average last month?” “Which marketing campaign generated the most sales?” These are questions the DA can answer because it has access to your verified catalog, sales, linking, email, and traffic data through the Analytics Gateway.

No third-party alternative exists for this capability. It is OS-native by design — it only works because the underlying data it queries is unified in one system. Authors who try to replicate this with ChatGPT and manually exported CSV files are approximating something that SC OS makes genuinely operational.

Layer 8: Manuscript Formatting — Outside SC OS Scope

Manuscript formatting — turning your Word document into publish-ready ePub and print PDF files — is the one critical production layer that sits outside the SC OS ecosystem. The two recommended tools for wide authors are Vellum (Mac only, widely considered the gold standard for output quality) and Atticus (Mac and Windows, the recommended cross-platform alternative). Both produce platform-compliant ePub files for Kobo, Apple Books, and every other wide retailer, and both produce print-ready PDFs for IngramSpark and KDP Print.

This is a one-time or per-release tool cost rather than an ongoing subscription. It pays for itself on the first book you publish wide.

Layer 9: ARC and File Delivery — Outside SC OS Scope

Getting review copies and reader magnets onto readers’ devices across every format (Kindle, Kobo, Apple Books, Nook, Tolino) requires a dedicated delivery tool. BookFunnel is the standard across the indie author community: it handles the file delivery, provides technical support to readers who have trouble downloading, and integrates with email platforms to automatically add subscribers to your list after claiming a magnet.

For wide authors whose ARC readers may prefer Kobo, Apple Books, or Tolino devices over Kindle, BookFunnel’s cross-device delivery is not optional — it ensures every reader gets the right file in the right format for their reading device.

For authors just beginning the wide transition, here is the essentials-only list. Start with ScribeCount OS as the hub and add each spoke in order of priority.

5. Integration: Where the Stack Clicks Together

The best tech stacks are the ones where tools reduce manual work by talking to each other. Inside SC OS, this integration is native rather than stitched together:

• Your AuthorVault catalog feeds your Linking module — retailer URLs populate automatically from your Identifier Vault without manual entry per link.

• Your SCE email campaigns connect to your royalty data — click-through from a newsletter becomes an attributable sales event in your Sales Dashboard.

• Your Website Traffic data feeds your attribution picture — the reader journey from a Facebook ad through your author website through your universal link to a Kobo sale is a single traceable thread.

• Your Hey ScribeCount? Digital Assistant queries all of the above — a natural language interface across your unified dataset that no externally assembled tool stack can replicate.

For the tools outside SC OS — Vellum or Atticus for formatting, BookFunnel for file delivery — the integration points are simpler but real: BookFunnel connects directly to MailerLite (and to SCE as the integration develops) to add subscribers automatically after magnet delivery. Vellum and Atticus produce ePub files that go directly into your anchor platform portals. Neither requires ongoing maintenance once configured.

6. Common Wide Tech Stack Mistakes

• Trying to track wide royalties manually across five dashboards — this approach collapses under the weight of platform reporting complexity within a few months. The Sales & Royalties Dashboard in SC OS exists because manual reconciliation is not a viable professional workflow.

• Using third-party universal link tools that have no connection to your sales data — Books2Read and Geniuslink are functional, but they cannot tell you whether a click converted to a sale. SC Linking can, because it runs inside the same system as your royalty data.

• Routing all distribution through an aggregator and losing direct promotional access on anchor platforms — use D2D for the long tail and libraries; publish directly to Kobo, Apple, Google, and B&N for full promotional access.

• Using ePub files formatted for Amazon (Kindle) on wide platforms — Apple Books in particular is strict about ePub quality and will reject files that don’t meet its standards. Use Vellum or Atticus to produce platform-correct ePub.

• Not setting up universal book links from the first day of going wide — every promotional mention of your book from day one should use a SC Linking URL so that traffic and click data builds from launch rather than retroactively.

• Treating Hey ScribeCount? as a future feature rather than a planning priority — the DA’s usefulness scales with the breadth of data already in your SC OS account. Authors who populate AuthorVault, connect their platforms, and build their SCE list are building the dataset the DA will query. Start now.

7. The Stack That Scales With Your Career

I have been publishing indie for sixteen years. When I started, the wide author’s tech stack was a collection of disconnected problems: a royalty dashboard that only covered Amazon, link tools that could not tell you which clicks became sales, email platforms that had no connection to your actual income data. Every piece of information you needed to run your business lived in a different system, and reconciling it all required hours every month that should have gone to writing.

ScribeCount was built to solve that. Not as a reporting tool bolted onto a dashboard, but as an actual operating system for the indie author’s publishing business — one where your catalog, your links, your email list, your website traffic, and your royalties from every platform all live in the same dataset, connected to each other, queryable in plain English through the Digital Assistant.

The tools in this guide — Vellum or Atticus for formatting, BookFunnel for file delivery — are genuinely the right tools for the jobs SC OS does not cover, and I recommend them without hesitation. But they are spokes, not the hub. The hub is ScribeCount, and every other tool in your stack becomes more useful when it is orbiting a system that knows your whole business rather than just a slice of it.

Build the stack deliberately. Start with SC OS as the center. Add each spoke when you need it. Connect it all. And then spend your time doing the one thing no tool in this guide can do for you: write the next book.

- Randall