Launching today

Handlio
Screenshot guides with version-specific client receipts
1 follower
Screenshot guides with version-specific client receipts
1 follower
Know which handover version your client acknowledged receiving. Create screenshot guides, publish a fixed release, and record explicit receipt. For freelancers and small agencies. Free drafting; publishing and sharing require a paid project pack.




Free Options
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hey Product Hunt! I'm building Handlio for freelance web developers and small agencies handing websites or software over to clients.
Which version of your handover did the client acknowledge receiving?
Handlio pairs screenshot-based instructions with explicit receipt acknowledgements tied to a specific published version. My aim is to make the handover easier to follow and give both sides a clear record of the release that was received.
Here's the workflow:
1. Prepare and redact screenshots locally, then turn them into illustrated steps with instructions and expected results.
2. Publish a fixed version and invite clients to a private reader where they can ask questions against individual steps.
3. Ask the client to explicitly acknowledge receipt of that version. The record includes the version, confirming email, and time. Opening or reading the guide never counts as confirmation.
4. Deliver the published handbook online, as a PDF, or as a self-contained offline HTML package.
Want to try it? Start at https://www.handlio.cloud and draft a guide for one website task, such as updating a homepage headline. Free authoring includes one draft project, 3 guides, and 20 steps.
Publishing, client sharing, and exports require a $19 project pack with 90 days of hosting. A 90-day hosting extension costs $9. Payments are one-time, with no automatic renewal; applicable taxes are additional.
I'm looking for 5 freelancers or small agency owners to try the drafting workflow and share candid feedback. Email support@handlio.cloud with the task you tried and what helped or got in the way. You can also ask questions about publishing and version receipts there, or in the comments below.
Would a version-specific receipt help your handovers? What would you need to see before using it with a client?
The screenshots use fictional demo data. Receipt acknowledgement is a workflow record, not contract acceptance or an electronic signature.
Thanks for taking a look. I'm happy to discuss the workflow and product decisions.