Nice, tidy problem to go after. The "which version did the client actually sign off?" argument has cost plenty of freelancers unpaid rework, so a lightweight fix has a market. A few thoughts from the buyer side, plus some UK practicalities worth sorting before you take money.
On the product itself - What is the "portable file"? This matters more than anything. If it's a PDF or Word document, clients will open it. If it needs a viewer or a browser tool, half of them won't bother and you're back to email. Spell this out in your pitch.
- The approval needs to be evidential. The real value isn't tidiness, it's being able to say "you approved version 3 on 14 March at 10:42" when a client disputes an invoice. A name, date and time stamp attached to the approved version, ideally something the client can't quietly edit afterwards, is what people will pay for.
- Revision notes should be threaded per version. Feedback on v2 mixed in with feedback on v4 is exactly the mess you're trying to avoid.
- Position against the free alternatives. Most freelancers currently use Google Docs comments, a shared Notion page or a "please reply APPROVED" line in an email. Explain why your file beats those in one sentence, because that's the comparison every buyer will make.
On the €19 price Quote in pounds for a UK forum. Seeing euros on a UK marketplace makes people assume a foreign card charge and hesitate. £15 or £19 one-off is a perfectly sensible impulse price for a freelancer. Agencies will pay more, so consider a team or multi-user tier later rather than leaving that money on the table.
One thing to be honest about: a one-off price for a downloadable tool means zero recurring revenue and you still carry support and update costs. That's fine if it's a side product, less fine if you want it to fund itself. A "pay once, updates for 12 months" model is a common middle ground.
UK compliance bits people forget - Digital content and cancellation rights. Under the Consumer Contracts Regulations 2013, consumers normally get 14 days to cancel. For downloads you can remove that right, but only if the buyer expressly consents to immediate delivery and acknowledges they lose the cancellation right before downloading. A tick box at checkout with the right wording covers it. Without it, refund requests are legally hard to refuse.
- Consumer Rights Act 2015. Digital content must be as described, of satisfactory quality and fit for purpose. Keep marketing claims modest until the prototype is stable.
- VAT. In the UK you only register once taxable turnover passes £90,000, so no worry there initially. Selling to EU consumers is different. Digital services to EU private customers attract VAT in the customer's country from the first sale, no threshold, which usually means registering for the EU's non-Union OSS scheme or using a platform such as a merchant-of-record that handles it for you. If you're planning to sell in euros, this is the thing to sort out first.
- Income. Even as a side project, HMRC expects it declared. If total self-employed income is under the £1,000 trading allowance you're fine, above that you need to register for Self Assessment.
- Collecting emails for the demo. That's personal data. Have a short privacy notice, don't add demo testers to a marketing list without asking, and check whether your set-up needs an ICO data protection fee (most small businesses processing personal data do, it's £40 a year at the lowest tier).
Practical suggestion Rather than emailing demos one by one, put a fictional-content sample file somewhere people can download instantly, and ask testers to reply here with what confused them. You'll get more honest feedback in public than in private, and the thread itself becomes your proof that real people tried it.
Happy to look at the demo if you post it. The one question to answer before anything else is whether the approved file can stand up when a client says "that's not what I agreed to". If the answer is yes, and a non-technical client can open it without installing anything, the price is almost irrelevant. If the answer is "sort of", fix that before polishing anything else.
Two quick tests worth running - Send the sample file to someone who has never seen it, with no explanation, and time how long it takes them to find the approved version and the date it was approved. Under a minute is the target.
- Ask a freelancer who has been burned by a version mix-up whether they would have used this on that particular job. Their hesitation, if any, tells you what's missing.
On the prototype stage Be upfront in the listing that it's early. UK buyers are generally tolerant of a beta if they know that's what they're getting, and far less tolerant of paying full price for something that later feels unfinished. A lower launch price for the first batch of buyers, clearly labelled, tends to work better than a quiet discount.
Post the sample when it's ready and people here will give you straight feedback. That's worth more than any amount of guessing at pricing.
