Ship at 80% and replace the file later: what done actually means
Perfectionism is expensive when updates are free. Here is how to define done for a digital product when everyone who bought gets the new version.
Open the folder. There is a guide at version 0.9 that has been at 0.9 since February, a course with five recorded modules and one you keep re-planning, and a template pack that only needs the cover redoing. None of them are unfinished in any way a customer would notice. They are unfinished in a way only you can see, and that is why they have been sitting there for five months.
Why the last twenty per cent takes half the year
The final stretch of any product is where the work stops being creative and starts being decision-making. Which of the three structures is right. Whether the tone is consistent. Whether the cover looks amateur. These are all questions you cannot answer alone, because the answer lives with the reader, so you circle them indefinitely instead.
Here is the honest part, and it is not a motivational one: shipping early does cost something. The first buyers get a rougher thing. Some of them will notice. A small number will judge the whole of you by it, and you cannot get that first impression back from those particular people. Anyone who tells you the trade is free has not made anything.
The trade is still worth taking, because the alternative is not a better product, it is no product plus a slowly growing conviction that you cannot finish things. And because the specific cost of shipping early has been reduced by how digital delivery now works, in a way that has not really been absorbed into how creators think.
Version one used to be permanent
That is the assumption underneath the anxiety, and on store.fan it is no longer true. Digital delivery goes to a private order page the buyer can return to, and replacing the file updates it for everyone who has already bought.
| When version one was permanent | When you can replace the file |
|---|---|
| A mistake in the PDF lives forever | Fix it, upload, and every buyer has the corrected version |
| Improvements mean a second product and a second launch | Improvements mean an upload on a Wednesday afternoon |
| Emailing updated files to past buyers is a manual job | Buyers return to the same private order page and find the current file |
| You hold back until it is beyond criticism | You publish the complete core and improve it against real use |
| Feedback arrives too late to change anything | Feedback from the first thirty buyers shapes version two |
| Scope grows while you wait, so it never ships | Scope is fixed at the promise, and extras become updates |
Defining your eighty per cent
Eighty per cent is not a quality level, it is a scope decision. Work through this before you write the sales page, because the sales page is what turns a scope decision into a promise.
Ready to ship when all of these are true
0/8How this plays out over a quarter
Suppose the guide ships in May at what you privately consider eighty per cent. Thirty or so people buy it over six weeks. Four of them reply with something useful, and two of those replies are about the same confusing section, which you had never once worried about. You rewrite that section, add the worked example three people asked for, replace the file in July, and send a short email saying so.
The version now on sale is better than the perfect version you would have produced alone, because it was corrected by use rather than by imagination. You also had a product earning for those six weeks instead of a folder. Compare that with the alternative: the same guide, published in September, at what you would still consider ninety per cent, with the same confusing section intact. The figures here are illustrative, but the asymmetry is not.
Upload the file you have been sitting on and put it on sale today.
Publish your productThe mistake most people make
They hold back the wrong twenty per cent. Polish is a fine thing to defer. The chapter you have not written is not, and neither is the workbook you listed as included. Buyers are remarkably tolerant of plain formatting and remarkably intolerant of a missing thing they were promised, because one is a taste judgement and the other is a broken deal. The other version of this mistake is announcing the roadmap on the sales page. The moment you write coming soon, you have sold the future version and made your buyers wait for it. Ship what exists, describe only what exists, and let the update be a pleasant surprise instead of a debt. If you are unsure what the buyer's side looks like, the FAQ walks through delivery and the private order page.
Yes. Digital delivery on store.fan sends buyers to a private order page they can return to at any time, and that page serves the current file. Upload a new version and every past buyer has it from their order page.
For anything more than a typo, yes. A short email is good manners and it is also good marketing, because it demonstrates that buying from you improves over time. Discount codes and scheduled campaigns are Pro features, but a plain update note is not.
No, and there is a case for not doing it. Keeping the price flat while the product improves is one of the simplest reasons for someone to buy now rather than wait. If you do plan to raise it, say so before, not after.
Refund anyone who asks and take the note seriously. If more than a handful ask, you did not ship at eighty per cent, you shipped at fifty and the sales page oversold it. That is a promise problem, not a perfectionism one.
The file in that folder is not waiting for another pass. It is waiting for thirty people to use it and tell you which twenty per cent actually mattered, and none of them can do that while it is on your hard drive.
Sell version one now and improve it for every buyer later.
Open a free storeTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.
