Skip to content
∎ Proof QEDTechnical documentation

Technical writing for software & IT teams

Make the complex
usable.

I write installation guides, troubleshooting documentation, and team procedures that people can follow. Start with your notes, a working system, or an existing draft.



Documentation portfolio

Clear instructions. Tested workflows.

Explore my Forge API guide, with practical examples, troubleshooting, and recorded verification.

View gallery →

Matt Kotys · Independent technical writer · Remote collaboration

Illustrative guide01 / Setup

What a guide includes

From setup to a working result.

Each guide explains what you need, what to do, and how to check the result.

  1. 01
    PrepareRequirements, tools, and starting conditions.
  2. 02
    Follow the stepsSpecific actions in a sensible order.
  3. 03
    Verify the resultExpected outcomes and troubleshooting.
Written for the reader.
Clear instructions, useful examples, and checks at each important step.

How I can help

Documentation services

Create a new guide or improve the documentation you already have.

01 / GET STARTED

Installation & setup guides

Help users install and configure your software or systems with step-by-step instructions, prerequisites, examples, and verification checks.

02 / GET UNSTUCK

Troubleshooting documentation

Turn recurring support questions into help articles and troubleshooting guides covering symptoms, likely causes, and steps to resolve them.

03 / KEEP IT REPEATABLE

Runbooks & team procedures

Document routine tasks, onboarding, and handovers so your team can follow a consistent process without relying on one person’s memory.

About Matt

A writer with hands-on IT experience

I’m Matt Kotys. My background spans systems administration, software development, networks, and technical troubleshooting. I’ve worked in IT since 2003, and I bring that hands-on perspective to every guide I write.

I have expertise in Python, Linux, SQL, and the practical details that make a system work. I can read the code, ask useful questions, and explain a process without assuming the reader already knows the answer.

PythonLinuxSQLSystems & networksClear explanationsAPIs

How we’ll work together

01. Share what you have

Notes, screenshots, an existing draft, or a walkthrough. We agree on the audience, scope, and deliverable.

02. Make it clear

I organize the material, write the guide, and flag gaps or assumptions that need your input.

03. Review & put it to use

You check the details. I refine the document and deliver an editable version you can maintain.

Start a project

What needs documenting?

Email me a brief description of your software or process, who the document is for, and any notes or drafts you have. We’ll agree on the scope and deliverable before work begins.

Email Matt →matt@proofqed.net

Installation guides · Troubleshooting · Runbooks
Small projects welcome.