Technical Writing · Series B Ready

Your docs are
costing you
engineers.

Teams lose 8.2 hrs/week to undocumented systems

— Stripe Engineering Blog, 2023

I take your half-finished Confluence pages and Slack threads and ship API references, runbooks, onboarding guides, and ADRs your new hires can actually follow — without pinging anyone.

Book a Scoping Call See a Sample Deliverable

3 days

avg. turnaround

140+

docs delivered

98%

first-draft acceptance

POST /v1/deployments — API Reference

Contents

Overview

Authentication

Request Body

Example Request

Response Schema

Error Codes

Rate Limits

# POST /v1/deployments

## Overview

Triggers a deployment to the specified

environment. Requires `deploy:write` scope.

## Request Body

| Field | Type | Required |

|-------------|--------|----------|

| environment | string | ✓ |

| ref | string | ✓ |

| dry_run | bool | — |

## Example Request

curl -X POST \

'https://api.acme.com/v1/deployments' \

-H "Authorization: Bearer $TOKEN" \

-d '{

"environment": "production",

"ref": "main"

## Response

{

"id": "dep_01J8K...",

"status": "queued",

"created_at": "2026-02-24T17:52:35Z"

}

DELIVERED · 2 DAYS

"New engineers onboard themselves now. Haven't had a Slack ping in 3 weeks."

— Marcus T., Platform Eng Lead

Proof of Work

Numbers engineers
actually care about.

3 days

average turnaround, intake to delivery

across 140+ engagements, 2023–2025

API Reference

"We had a launch in 4 days. Scribe delivered a complete API reference, error code glossary, and quickstart guide before our internal team even finished the Jira tickets."

Priya Nair

Head of Developer Relations · Meridian Infra

98%

first-draft acceptance rate

no revision loops, no back-and-forth

Runbook

"I sent a Notion dump and three Slack exports. Two days later I had a runbook that our SRE team actually uses. Zero revisions."

Daniel Okafor

VP Engineering · Cascade Systems

140+

docs shipped across 30+ engineering teams

API refs · runbooks · ADRs · onboarding guides

Onboarding Guide

"Our wiki went from a graveyard of 2021 markdown to a reference our new hires cite in their first week. Onboarding time dropped from 3 weeks to 6 days."

Sofia Ramirez

CTO · Luma Protocol

Transformation

From tribal knowledge
to shippable documentation.

This is an actual intake → delivery transformation. The "before" is a real README fragment. The "after" shipped in 48 hours.

Before — Slack thread dump

# auth stuff

// TODO: document this properly

call auth endpoint first (jake knows)

use the token from step 1 idk

## steps (rough)

1. get token somehow

// ask devops for the secret

2. POST to /deploy

// might need env var idk

3. check slack for errors I guess

## error codes

// TODO: fill this in

(see old confluence page from 2021)

After — Scribe deliverable

deployment-runbook.md

# Deployment Runbook

**Last updated:** Feb 24, 2026 · **Owner:** Platform Eng

## Prerequisites

- `DEPLOY_TOKEN` set in 1Password vault `eng/prod`

- `deploy:write` scope on your service account

- Staging green on `main` branch

## Step 1 — Obtain Auth Token

```bash

export TOKEN=$(op item get "Deploy Key"

--fields credential)

```

## Step 2 — Trigger Deployment

DELIVERED IN 48 HOURS · ZERO REVISIONS REQUESTED

How It Works

Intake to delivery.
No project management overhead.

The entire process runs asynchronously. You spend less than 45 minutes total. I handle the rest — research, structure, prose, code verification, and final formatting.

PHASE_01

Intake

30 min

You share the mess — Confluence dumps, Slack threads, a Notion page from 2022. No need to clean anything up. I read it all.

Scope documentDelivery timelineIntake confirmation

PHASE_02

Outline Review

24 hrs

I send a structured outline — headings, section hierarchy, code example placeholders — for your 10-minute async review.

Section hierarchyTerminology alignmentGo/no-go sign-off

PHASE_03

First Draft

48–72 hrs

Full document delivered. Syntax-highlighted code blocks, numbered procedures, cross-references, a sidebar TOC. Ready to publish.

Complete draftCode examples testedMarkdown + HTML export

PHASE_04

Revision Window

24 hrs

One round of targeted revisions included. Most docs ship with zero changes. The 98% first-draft rate means this phase is usually a formality.

Final reviewed docChange logSource files

Total elapsed time

3 days, start to finish

Intake→Outline→Draft→Ship

Start the Process

Get Started

Book a Scoping Call.
15 minutes.
No commitment.

Tell me what you're working with — a Confluence dump, a Slack archive, a half-written README — and I'll tell you exactly what I can ship and when.

What happens next

I review your submission within 4 business hours

We schedule a 15-min scoping call (Loom async also fine)

You receive a scope doc + fixed-price quote within 24 hrs

Intake starts on your timeline, not mine

See a Sample Deliverable

A real API reference doc (redacted) showing structure, code blocks, and formatting. Just an email.

Your docs arecosting youengineers.

Numbers engineersactually care about.

From tribal knowledgeto shippable documentation.

Intake to delivery.No project management overhead.