LogoRedline
/ Technical Writing
Overhead view of architectural drawings, annotated code printouts, and documentation spreads arranged on a drafting table with drafting tools and red-pen markups
folio 01
redline.doc
Technical Documentation · Contract

Clarity is a deliverable.

API references engineers actually use. Help centers that cut tickets by 40%. Documentation that compiles — in every sense.

Download Audit ChecklistSee the Work ↓
Scroll
Measured outcomes
40%
Reduction in support tickets
Meridian Cloud, 2024
12×
API docs adoption rate increase
Vantage DevTools
94
Readability score avg (was 61)
Corpus SaaS
3 wks
Average onboarding doc turnaround
Across engagements
Trusted byMeridian CloudVantage DevToolsCorpus SaaSArchway FintechLumen Health
01
STC Distinguished Technical Communication Award2023
Vantage DevTools

The API reference engineers actually bookmark.

12× increase in API docs page visits within 60 days of rewrite.

Vantage's REST API had 847 endpoints documented in a single 340-page PDF generated from Swagger defaults. Developers were filing "how do I?" tickets at 23 per week. The engagement began with a full information architecture audit, then a complete rewrite into a structured reference system with runnable code examples, error code taxonomies, and contextual guides.

API ReferenceDeveloper DocsInformation Architecture

"Our developer NPS went from 31 to 67 in one quarter. The docs were the only thing that changed."

Priya Nair
VP Developer Relations, Vantage DevTools
Document diff
After: Structured reference
← revised
+## Create a User
+POST /api/v2/users
+
+**When to use:** Provision a new user account
+in your organization. Requires `admin` scope.
+
+```bash
+curl -X POST https://api.vantage.io/v2/users \
+ -H "Authorization: Bearer $TOKEN" \
+ -d '{"email":"dev@corp.com","role":"viewer"}'
+```
11 additions3 deletions
02
40% Support Ticket Reduction — Meridian Cloud Q3 20242024
Meridian Cloud

When the help center actually helps.

Support ticket volume dropped 40% in 90 days after help center overhaul.

Meridian's help center had grown organically over four years — 1,200 articles written by seven different teams with no shared style, no search taxonomy, and no feedback loop with support data. The project began with a ticket-to-article gap analysis: mapping the 50 most-filed tickets to the documentation that should have prevented them. Result: a restructured help center with task-based navigation, plain-language rewrites, and embedded troubleshooting decision trees.

Help CenterSupport DeflectionContent Audit

"We were spending $180k/year on support tickets that documentation should have prevented. Now we're not."

Marcus Webb
Head of Customer Success, Meridian Cloud
Document diff
After: Task-based guide
← revised
+# Update your payment method
+
+**Time:** 2 minutes
+**You'll need:** Admin access + new card details
+
+1. Go to **Settings → Billing**
+2. Click **Payment Method → Edit**
+3. Enter card details and click **Save**
+
+> **Note:** Changes apply to your next billing cycle.
10 additions3 deletions
03
Readability Score: 94 (from 61) — Corpus SaaS Onboarding Rewrite2024
Corpus SaaS

Developer onboarding from 14 days to 3.

Time-to-first-API-call dropped from 14 days to 3 days average.

Corpus had a powerful NLP platform that developers struggled to integrate. The onboarding documentation assumed PhD-level ML knowledge for tasks that required only basic HTTP familiarity. A complete onboarding path rebuild — starting with a "Hello, World" integration tutorial, progressive disclosure of advanced concepts, and a troubleshooting runbook — cut the time-to-value dramatically and reduced onboarding support load by 60%.

Developer OnboardingTutorial WritingReadability Audit

"Jordan rewrote our onboarding docs and our activation rate went from 34% to 71% in two months."

Saoirse Ó'Brien
Product Lead, Corpus SaaS
Document diff
After: Progressive disclosure
← revised
+# Send your first request
+
+In this guide you'll analyze a sentence and
+get back its sentiment score. Takes ~5 minutes.
+
+**Prerequisites:** A Corpus API key (free tier works)
+
+```python
+import corpus
+client = corpus.Client(api_key="YOUR_KEY")
+result = client.analyze("This API is clear.")
+print(result.sentiment) # → 0.94
+```
13 additions3 deletions
¶ conversion
folio 04
Free Resource

The Documentation
Audit Checklist

The same 47-point checklist used on every engagement. It covers information architecture, readability scoring, API reference completeness, search taxonomy, and support ticket correlation — the exact criteria that separate documentation that deflects tickets from documentation that generates them.

Information architecture audit framework
Readability scoring rubric (Flesch-Kincaid adapted)
API reference completeness matrix
Support ticket-to-article gap analysis template
Style and voice consistency checklist
+ 42 more criteria
checklist.pdf — access request

No spam. One email with the checklist PDF. Unsubscribe anytime.

Not ready to download?

See My Full Case Library →
Engagements

Four ways to work together.

All engagements begin with a scoping call and a written brief. Work is delivered in documented sprints with tracked changes visible throughout. Every project ships with a handoff guide so your team can maintain what we build.

01

API Reference Rewrites

From Swagger exports to structured, developer-first references with runnable examples, error taxonomies, and contextual guides. Priced per endpoint cluster.

Typical: 200–800 endpoints · 4–10 weeks
02

Help Center Overhauls

Full audit, gap analysis against support ticket data, information architecture redesign, and plain-language rewrites. Measured against ticket deflection.

Typical: 300–1,500 articles · 6–14 weeks
03

Developer Onboarding Programs

Quickstart tutorials, progressive disclosure paths, and troubleshooting runbooks. From "Hello, World" to production-ready in days, not weeks.

Typical: 5–30 doc pages · 2–6 weeks
04

Documentation Audits

The 47-point audit: information architecture, readability, completeness, searchability, and support ticket correlation. Delivered as a prioritized remediation roadmap.

Fixed scope · 1–2 weeks

Ready to scope a project?

hello@redline.doc

Start a ConversationGet the Audit Checklist