You will get an auto-generated product user manual
Project details
Your documentation screenshots went stale the moment you shipped. Most teams either let it rot, or pay someone to re-capture forty screens by hand every release.
I do it differently. I drive your app in a real browser and draw numbered callout boxes onto the live page before each screenshot is taken, so they land exactly on your buttons and fields. It is assembled into a structured manual with chapters and contents, delivered as Word, PDF and Markdown, ready to drop into Intercom, Confluence, Notion or GitBook.
You also get something a writer cannot. I spent eight years in QA before moving into delivery for enterprise software, most recently a tier-one bank in Southeast Asia. Walking every flow to document it is also a usability pass, so you also get a list of the inconsistencies and dead ends I hit.
On the top tier I hand you the generation pipeline itself. Describe the flow once as a specification, re-run it after your next release, and the whole document rebuilds.
Any region can be masked before capture, so account numbers or customer names never reach the image.
Send me your URL and the flow that matters most. I will tell you what is realistic before you order.
I do it differently. I drive your app in a real browser and draw numbered callout boxes onto the live page before each screenshot is taken, so they land exactly on your buttons and fields. It is assembled into a structured manual with chapters and contents, delivered as Word, PDF and Markdown, ready to drop into Intercom, Confluence, Notion or GitBook.
You also get something a writer cannot. I spent eight years in QA before moving into delivery for enterprise software, most recently a tier-one bank in Southeast Asia. Walking every flow to document it is also a usability pass, so you also get a list of the inconsistencies and dead ends I hit.
On the top tier I hand you the generation pipeline itself. Describe the flow once as a specification, re-run it after your next release, and the whole document rebuilds.
Any region can be masked before capture, so account numbers or customer names never reach the image.
Send me your URL and the flow that matters most. I will tell you what is realistic before you order.
Document Type
User & Training ManualTopic
Software, Technology, GeneralLanguage
English, Chinese (Simplified)What's included
| Service Tiers |
Starter
$99
|
Standard
$349
|
Advanced
$699
|
|---|---|---|---|
| Delivery Time | 7 days | 14 days | 21 days |
Number of Revisions | 1 | 2 | 3 |
Number of Words | 800 | 2500 | 3000 |
Number of Technical Illustrations | 10 | 40 | 40 |
Consultation | - | - | |
Proofreading & Editing | - | - | - |
Additional Research | - | - | - |
References & Citations | - | - | - |
Formatted Style Guide | - | - | - |
Optional add-ons
You can add these on the next page.
Fast Delivery
+$40 - $250
Additional Revision
+$35
Additional Technical Illustration
+$15Frequently asked questions
About Leon
AI Automation Engineer | Claude Code, MCP & Doc Pipelines
Nanjing, China - 3:56 pm local time
first time the data changes shape.
I'm a forward-deployed engineer: I sit between a client's business reality and
the system that has to serve it. 8+ years in QA and testing, 4+
in delivery and customer-facing roles, most recently building conversational-AI
platforms for a tier-one bank in Southeast Asia — where the systems I delivered
are still running in production today.
Plenty of people can write the automation. Fewer can tell you which half of
your process is worth automating.
WHAT I BUILD
▸ Documentation pipelines — point it at your web app, get back an illustrated
user manual with annotated screenshots, regenerable on every release.
▸ Report automation — spreadsheets, databases or APIs into client-ready
reports, on a schedule, in English and Chinese.
▸ Progress tracking — reconcile a client's spreadsheet against your internal
tracker into one source of truth, and generate the follow-up list.
▸ Custom MCP servers — wire Claude directly into your CRM, wiki or ticketing
so your team stops copy-pasting between a chat window and the real system.
Before any code, you get a written scope with a concrete acceptance criterion.
Delivery includes a runbook — you own the result, not a dependency on me.
Tell me what your team does by hand every week. I'll tell you whether it's
worth automating — sometimes the honest answer is no.
Steps for completing your project
After purchasing the project, send requirements so Leon can start the project.
Delivery time starts when Leon receives requirements from you.
Leon works on your project following the steps below.
Revisions may occur after the delivery date.
Confirm scope and access
I check that the URL and test account work, and we agree the exact flow to document before anything else. If I think part of it is not worth documenting, I will tell you.
Author the flow specification
I write the flow down as a specification: every step, every element that gets a numbered callout, and anything that needs masking. This is what makes the manual reproducible later.