I will write software user manual, product documentation, help guide, knowledge base
Technical documentation and data automation for software teams
About this Gig
Scrivimi pure in italiano.
Your software works. The problem is the twenty minutes you spend on the phone every time a new user opens it for the first time.
I write the manual that replaces those twenty minutes.
HOW IT WORKS
1. Give me access to the software, or a screen recording, or a demo call. I use it myself - I do not write from a feature list.
2. I write the steps in the order a real user meets them, not in the order your menus are arranged.
3. You get a draft, we fix what I misunderstood, you get the final file.
WHAT YOU GET
- Getting started: install, first login, first useful result
- Every task as numbered steps, with annotated screenshots
- The things that go wrong, and what to do about them
- A glossary, if your product has its own vocabulary
- Word, PDF and Markdown, so it can go on your site too
- A knowledge base structure with article drafts (Premium)
If a step does not work as documented, it does not ship.
Document type:
User & training manuals
•
Documentation
Industry:
Software
Language:
English
•
Italian
Delivery style preference
Please inform the freelancer of any preferences or concerns regarding the use of AI tools in the completion and/or delivery of your order.
My Portfolio
FAQ
How do you get the screenshots?
I take them myself from a trial or demo account you give me, so they match the current version and your branding. If you prefer, send me your own and I will crop, annotate and keep them consistent throughout.
Can you publish it straight into our help centre?
I deliver in the format your platform imports: Markdown, HTML or structured Word. Intercom, Zendesk, HelpScout, Notion and most static site generators all take one of these. Tell me which you use before you order.
Our product is still changing. Is it too early?
Not necessarily. We start with the parts that are stable and structure the document so new sections drop in later without a rewrite. If a core flow is about to change, I will tell you to wait rather than bill you twice.

