A book is ready to be read long before it is ready to be sold.
When I started thinking about the first book we could sell, I didn’t start with a price or a launch date. I was following a reader through the whole experience: finding the book, deciding it was worth paying for, opening it, leaving it, and expecting to return.
We were not selling books through ReaderPub yet, but I had reached the point where the system had to be designed for that possibility. A readable book had to become a book whose access made sense over time.
Once payment entered the picture, “can the reader open the book?” was no longer enough. The question became: who should be able to open it, and why?
Readable is not sellable
An openly available book can answer a simple question: can someone open it and read?
That question had been useful. It helped me test the reading surface with a real text and notice how people move through chapters, return to passages, and stay with a book over time. But open access kept some other questions out of sight. No one had to prove who they were before reading. No one had to find the book again because they had a lasting reason to return to it.
That was the threshold I had been circling: access had become part of the publication’s design.
That sounded like a small change in wording. It was not. It moved the book from a page anyone could visit to a publication with a continuing relationship to a particular reader. The reading experience had to remember something about the access, even if I had not yet decided exactly what that something should be.
This was why I resisted treating commerce as a button added at the end of publishing. The reading problem came before the transaction. If the book was going to be offered for purchase, access had to be part of what the book was.
The word “mine” got complicated
With a file, “my book” can mean a copy that sits on my device. With a web-native book, the phrase can mean several different things: a work I paid to read, a page I can return to, an edition that may change, or a place associated with my account.
I did not need to settle the language immediately to feel the pressure. Imagine a reader finding a book, deciding it is worth paying for, and opening it on one device. The real test isn’t the first successful opening. It would be what happens later, when the reader comes back from somewhere else and expects the book to still be theirs to read.
Return was not a support case after the payment cleared. It was part of what the product had to make intelligible from the beginning.
That was the moment when “book” stopped being enough as a product description. The work, the reading place, and the reader’s permission to come back were starting to form one connected problem.
Access has a before and after
A commercial reading experience begins before the reader opens the book. Someone has to find it, recognize it, decide it is worth their attention, and understand what will happen after they choose it.
It also continues after the first session. A reader may leave halfway through a chapter and return later.
This exposed a limit in the way I had been describing the earlier reader. For an open public-domain text, it was enough to say that the page should be easy to find and pleasant to read. For a paid book, the page also had to be clear about the relationship between the person and the book over time.
The link first solved a location problem. It gave a reader and me one place to look at the same words. After the commerce question appeared, the link acquired another responsibility: it had to lead back to an access relationship that meant something to the reader.
The same address could take a person to a public discovery page, a reading session, or a book they had a reason to return to. Those experiences might share a title and a passage, but they could not mean the same thing. Discovery asks whether the book is worth opening. Purchased access asks whether this reader should be able to keep opening it.
That distinction helped me avoid an easy mistake. I did not want to treat a commercial book as a free reading page with a price attached. The price changed the expectations around identity, return, updates, and the relationship with the person reading.
The first commercial question, then, was not “how much should this cost?” It was “what exactly are we asking a reader to come back to?”
The first book we could sell
The first book we could sell was not the first book with a price written beside it. It was the first book that made me take the reader’s future access seriously. That realization marked a deeper threshold in the story, before any commercial catalog was ready.
I left the practical rules unresolved. They belonged to the next layer of work, not to a neat ending in this one.
The question itself had changed. A web-native book was no longer only a reading surface or a place for conversation. Once access acquired a price, the publication also had to remember who could return, what they were returning to, and why.