Technical writing and documentation services
I develop technical documentation and build custom knowledge bases, portals, and tools that help your customers and teams find answers and complete their work.
Bring me a new documentation project, guides that need updating, or a publishing process that needs to work better.
David YoungTechnical writer and information architectWork directly with me throughout the project.
See how billing reviewers and integration developers use one documented workflow to resolve source records and prepare an implementation handoff.
Watch the project walkthrough Project names and records have been changed. The workflow and deliverables are presented as a complete project.How I can help
Describe what you need written, reviewed, or built, and we’ll agree on the deliverables.
Tell me what people need to accomplish. I’ll determine whether the project calls for documentation, a knowledge base, an onboarding experience, an interactive tool, or a combination.
I identify tasks the documentation doesn't cover, confusing steps, and problems with how the content is organized.
I write the instructions people need to set up, use, and maintain your product or follow your processes.
I build searchable knowledge bases, documentation portals, and reference tools around the information people need to use.
Describe the project or problem. Share a defined scope or explain what needs attention.
Featured project
A customer-preparation handbook, field contract, exception procedures, and structured handoff connect billing review with the requirements integration developers need.
Project names and records have been changed. The project page preserves the workflow, decisions, and deliverables.
Selected work
The work combined product guides and internal procedures with preview workflows and custom features for organizing the documentation.
Working together
You bring the goals and source material. I research, write, and build the agreed deliverables.
Share the product, process, or documentation you have. We identify the intended readers and the tasks the documentation needs to support.
We agree on deliverables, access to your team and materials, review responsibilities, and what the finished work needs to do.
I check the work against the agreed requirements. Your designated reviewers verify the product or process details. Together, we agree on handover instructions and who will be responsible for ongoing maintenance.
Practical documentation advice
Measure the time developers need to make a first successful API request.
Read the articleUse recurring support questions to identify articles that need attention.
Read the articleWhere contribution, review, and publishing become difficult after the tools are in place.
Read the articleCommon questions
Yes. I can work alongside your writers, engineers, support staff, and subject experts. We agree on who provides information, who reviews the work, and who handles maintenance.
A clearly defined writing or build project can start with its own scope. An audit helps identify questions the documentation doesn't answer, instructions that need clarification, and priorities for the work.
The price depends on the agreed deliverables, available material, technical access, and review needs. We clarify those details and agree on the scope and price before project work begins.
I review the project details you share. We clarify the deliverables, any questions that affect the scope, and the proposed price before project work begins.
Your next documentation project
Tell me what needs to be written, organized, or built. A few sentences are enough to start.
I read what you send and reply with questions about the scope. We agree on the deliverables and the price before any project work begins.