Gabriel Philip General
Technical Writer (Systems & Processes)
(You read the bio. Now here's what it actually means.)
The problem
Most teams are held together by people, not processes. There's always that one person everyone goes to because they just know how things work. Mark, usually. And that's fine, until Mark is on leave, gets promoted, or moves on.
Then everything slows down. Questions pile up. Work gets redone. And nobody really knows where to start.
That's where I come in.
I take the things that only exist in someone's head and turn them into documentation anyone can follow. No jargon. No assumptions. Just clear, straightforward guides that anyone can follow, even if they're hearing about it for the first time.
The blueprint maker
An architect doesn't build the house. But nothing gets built without the blueprint.
A bad blueprint means your team is guessing, making mistakes, redoing work, and calling the one person who just knows.
A good blueprint means anyone can pick it up and know exactly what to do, in what order, and why. Even when you're not in the room.
That's what I make. Not just a good blueprint, but a great one.
The real value isn't just documentation. It's continuity. Your business keeps running even when the person who built the system leaves, gets promoted, or goes on leave.
Who I work with
I work best with small to mid-sized teams where things are growing faster than the documentation can keep up. Sound familiar?
- Your onboarding process is "just ask someone"
- Only one person on the team fully understands a certain process
- Your team uses tools like Notion, ClickUp, or Google Workspace but nothing's actually documented inside them
- You're preparing to hire, delegate, or scale and you know things will get messy if nothing's written down
- You've said "we should really document this" more than twice in the last month
If any of that sounds familiar, you're in the right place.
What I actually deliver
Not a Google Doc full of bullet points. Documentation that's structured, readable, and built for the person who has to use it, not the person who already knows everything.
SOPs
Step-by-step guides for your repeatable tasks, written so clearly your newest hire can follow them without asking anyone for help.
Process Maps
A clear picture of how work moves through your team. Everyone sees the full flow, not just their part of it.
Internal Guides
Tool guides, onboarding docs, and how-to references that people actually open when they need help.
Knowledge Bases
One organized place where your team can find answers on their own. Less back and forth. More getting things done.
One thing worth knowing
I don't redesign how your business runs. I don't tell you which tools to use or rebuild your workflows from scratch.
What I do is take what you already have and make sure it's written down clearly enough that it works without you having to explain it every time.
You build it. I make sure everyone else can follow it too.
Sound like what you need?
Let's have a real conversation about what's not written down yet and what it's costing you.
Work With Me