Geoff Brandt Technical Communications
Your app works.
Your help system doesn’t.
25 years writing field-level software documentation. For in-house teams, dev shops that got stuck writing docs nobody wanted to write, and now the AI-built apps that shipped without any.
What I Fix
You built something fast. The docs didn’t come with it.
I write the FAQ pages, in-app help text, onboarding copy, and error messages your users actually search for — and I test your UI while I’m in there, because the fastest way to find a documentation gap is to try to use the product like a stranger would.
If your help search comes up empty on a basic question, that’s not a documentation problem. That’s a lost sale. I’ve watched it happen from the other side of the screen.
This is built for solo founders and small teams shipping fast – one product, one core flow. If you’ve got multiple products or a stakeholder chain to manage, tell me anyway. I’ll just scope it differently.
Geoff Brandt, CEO GBTC
Why Me?
I’ve been writing software documentation since before “prompt-to-app” was a category – help files, FAQ systems, UI copy, the kind of writing that has to be exactly right because a confused user can’t ask it to clarify. I also run a business consulting practice, so I know what a broken support experience actually costs you in churn, not just in annoyance.
Most people offering documentation work right now learned the format last month. I’ve been doing it since before AI could.
How it Works
Send me your app. I audit it in a day – search, onboarding, error states, help content – and send back what’s actually broken, specifically, not generally. If you want me to fix it, I quote a flat fee and turn it around in days. No retainer, no discovery call (unless you insist), no twelve-page proposal.
System & User Docs
Docs your users actually find.
You built something fast. The docs didn’t come with it. I write the FAQ pages, in-app help text, and error messages your users actually search for. The answers your engineering team assumed didn’t need explaining.
If your help search comes up empty on a basic question, that’s not a documentation gap. That’s a lost sale. I’ve watched it happen from the other side of the screen.
UI Troubleshooting
The docs are a symptom. I find the cause.
Writing your docs means using your product like a stranger would. And its strangers that keep finding the same three or four places people get stuck. I’ve been fixing that since before I fixed it with words.
If the audit turns up friction better copy can’t solve, I’ll tell you exactly where it is and what’s causing it. What you do with that is up to you.
Services
| Service | Price | What it covers |
|---|---|---|
| Help Docs & FAQ | $500–1,500 flat | FAQ pages, in-app help text, error messages |
| Knowledge Base / Help Center Build | $2,000–4,500 flat | Full help center — categories, structure, articles |
| UI Troubleshooting | $1,500–3,000 flat | Friction points found and fixed, not just documented |
| In-App Onboarding Copy | $300–600 flat | First-run walkthrough, tooltips, empty-state copy |
| Launch Copy | $300–500 flat | Product Hunt / App Store listing copy |
| Release Notes | $150–250/mo | Monthly changelog, written from your tickets |
| Error Messages & Empty States | $300–600 flat | Rewritten to say what happened and what to do next |
| Support Macros / Canned Responses | $250–500 flat | Ticket-response templates from your real ticket history |
Prices assume a normal-sized problem. Bigger company, bigger scope, bigger number. I’ll tell you which one you are after I look.
Tell me what you’re building. I’ll tell you what’s missing.
Full Product Documentation
Sometimes the fix isn’t a page. It’s the whole manual.
Everything above this is a fast fix for a specific gap. This isn’t that.
Some products need the complete functional record — every screen, every flow, every edge case a user can actually hit, documented start to finish. Not what an audit happens to catch in a day. All of it.
This is the work documentation used to mean, before “docs” shrank down to a FAQ page. Enrollment systems. Approval workflows. Applications where a wrong sentence had real consequences, not just an annoyed user. I’ve built full documentation for products at that scale. Most apps aren’t that complicated — but if yours needs the whole manual instead of a patch, that’s what this is.
What’s included:
- Full feature/screen inventory, confirmed with you before work starts
- Complete documentation written to that inventory — not just the loud gaps
- UI/UX friction flagged as I find it, no extra charge
- One structured revision round
| App Size | Price | Timeline |
|---|---|---|
| Small — under ~15 core features/screens | $3,000 – $6,000 flat | 3–5 weeks |
| Mid-size — 15–40 features/screens | $6,000 – $12,000 flat | 6–10 weeks |
| Large / multi-module | Custom quote, starting at $12,000 | Scoped after review |
Tell me what you’ve built. I’ll tell you what it takes to document it right.
Get the Docs Gap Checklist
Ten questions that expose a broken help system in five minutes. The same ones I run before every audit. Drop your email, get the doc. No newsletter attached.
Join the list (over 3000 strong)
You supply the grid paper…