Author’s Haven is my beta reader platform, and the pitch is simple: authors upload a manuscript, readers answer survey questions chapter by chapter, and the author ends up with structured feedback instead of “loved it, keep going.” There’s a free tier that stays free, not a trial that expires on you, and I built the thing because I needed it for my own books.
In one stretch of a few weeks I got two sets of messages that, read side by side, sound like they’re describing different products.
The first came from an author on the free plan, subject line “Looks Like A Con.” I’ll paraphrase lightly, because I don’t want to put words in anyone’s mouth. There are, he wrote, no readers on the site, so the whole thing is a waste of time. He has 56 chapters and has to upload them one at a time, when he could just email an attachment. The software is primitive, and questions had to be answered three or four times because his input kept vanishing. Then the line that actually stuck: I read your article about how you studied all the other beta reader sites to build the best one, and what a disappointment.
Then a support ticket arrived from the same address, subject in capitals, demanding that I delete the account and all associated data immediately and confirm by email. The body called me a cheat and a beggar with nothing to offer except begging for money, and the software crap, and the time spent an inordinate waste.
I deleted the account within the hour, because that part isn’t complicated, whatever else I think of the message.
The second person is a beta reader who writes as well. Her first message opened with how much she was enjoying the platform, and then singled out inline comment categorisation as something she hadn’t seen on any of the other sites she’d used. The bug report came after that: whenever she switched to another window, the page refreshed and everything she had typed into the survey was gone, consistently, in Firefox. She was tabbing away to check the forum or to look at the story map, and coming back to an empty box. Her question was polite to the point of generosity – is this intentional, or could it be a bug?
It was a bug, and the page had been refetching in the background when it lost focus, and Firefox in particular blanked the open survey while it did so. Two changes went out the same day: survey answers now save to the browser as you type, and the background refetch stops while a survey is open. She wrote back to say the whole beta reader group had tested the fix on mobile and on desktop, that several of them had hit the same thing, and thanks.
Here’s the part I keep turning over. *Both of them hit the same bug*, lost survey input, almost certainly a variant of the one thing, and one report ended with the platform being a con run by a beggar while the other ended with a fix shipped in a few hours and a group of readers who trusted the tool more that evening than they had that morning.
Same bug, two different products
Both of them were right about the facts. The software was losing people’s typing. What separated the two messages was never accuracy, it was what each of them had come for in the first place.
The difference had a price, and it wasn’t paid by the polite one. She told me the browser, the trigger, and what she was doing when it happened, so I could reproduce her version in minutes and ship the fix. He told me his input kept vanishing and then closed the account before I could ask a single question, so his variant of the bug may still be sitting in the code, waiting for the next author who writes long survey answers in whatever browser he was using. The furious report was worth less to me than the friendly one, and it cost more to receive.
She came to read manuscripts and be useful to authors, so the platform’s job, from where she stood, was to stay out of her way. When it failed at that, the gap between what she wanted and what she got was one broken behaviour, and describing it precisely served her own interest, because she wanted to keep using the thing.
He came for readers. He had 56 chapters and no audience, and what he needed from me was traffic, so everything else was noise. The upload flow annoyed him and the survey bug annoyed him, but neither was the actual complaint, which was that a free account could not hand him a waiting queue of beta readers for a 56-chapter book, and against that expectation no interface work I could have shipped would have registered. The bug wasn’t his problem with the product, it was evidence for a conclusion he had already reached.
Which is why “you can’t make everyone happy”, true as it is, is the lazy version of this lesson. The useful version is that identical feedback means two different things depending on what the person walked in wanting, so my job is to work out which want I’m looking at before I decide what the message is worth.
What I do with it in practice
On the 56 chapters he was wrong about the facts and right about the product. Bulk import already exists, and has for a while. You open your book, press Import, drop in an EPUB or a DOCX, and it splits into chapters on its own, reorderable afterwards, and pasting a whole manuscript works too. There’s also Send to Kindle, if you’d rather the reader got the book as one file, with feedback still coming back chapter by chapter. He never found any of it, and he had 56 chapters in front of him and a page that looked like it wanted them one at a time, so he did the arithmetic and concluded the software was primitive. A feature nobody finds might as well not exist. That’s a discoverability problem, not a primitive one, and it’s worth knowing which of the two you’re being shouted at about.
Being insulted and being wrong are separate conditions, and I read my inbox with them kept apart.
On the reader supply problem he was right, and that one is much harder, because a beta reader platform is a two-sided market and the empty side is readers. That’s the reason I’ve spent recent weeks on the reader experience instead of more author tools: categorised inline comments, autosave, a “load older feedback” button that someone wrote in specifically to thank me for. There’s a public shelf at authorshaven.io/shelf where a cover and the first 500 words of chapter one go live for anyone browsing, opt-in from your book settings, and most authors here bring their own beta readers and use the site for the feedback part. Authors turn up on their own, since they need something badly enough to go looking. Readers turn up only if the work is pleasant, and they leave the moment it stops being pleasant. So every hour I spend on their side of the platform is an hour spent on the thing authors are actually asking me for, even when it doesn’t look like it from the author’s side of the screen.
The “beggar” line still irritates me, so let me be plain about it. The free tier on Author’s Haven is permanent, and it isn’t a countdown to a card form, whatever he assumed. There’s a paid tier on top of it for authors who want more pen names and the AI features. I want manuscripts and readers inside the system, which is what the free tier is for, and servers and my hours cost money, which is what the paid one is for. If charging for software is begging, then every author selling a novel on Amazon is running the same racket.
Where the two of them were standing
The line that landed hardest wasn’t the insult, it was the disappointment. He had read my article about studying every beta reader platform I could find before building mine, and he measured what he found against the platform that article implied.
She had read nothing about it. She showed up, started reading somebody’s manuscript, and judged the thing by whether it let her do that.
So one of them arrived with a picture in his head and compared the product to the picture, and the other arrived with a task and compared the product to the task. That difference decided everything that followed, including how they each described a bug that was, underneath, the same bug. It isn’t a story about a good user and a bad one. It’s a story about how much of an opinion is already formed before anybody logs in.
Two people, one week, one bug, and I fixed it for one of them and deleted the account of the other, and both were the correct response to what was in front of me.
If you write, or if you read for people who do, Author’s Haven is at authorshaven.io, and the free tier stays free. Tell me what’s broken, in detail if you can manage it. I would much sooner hear it in a bug report than in a subject line.
That sounds frustrating, my friend. It's hard to determine actions and fixes when a critique tends to be more about the critic that the product or service.
Good luck with the site!
I didn't even know there were programs/sites out there like this, so that's a very good find.