← /services [DOCS]

[services / documentation]

documentation

How-tos · knowledge base · incident and customer copy · READMEs · docs a tired first-time user can finish

USD $120 · 4-hour minimum · engagement rules on the hub

NeuroShell README ↗ · writing ↗

Docs Audit

$1,800 USD

Typically 5–10 business days

includes

  • Inventory of existing help text, READMEs, and knowledge-base gaps
  • Written findings: what to rewrite first, what to delete, who the reader is
  • Sample rewrite of one high-traffic article — not a checkbox PDF

excludes

  • Full rewrite of the set (see How-to Pack or retainer)

How-to Pack

$5,400 USD

40 focused hours · ~1 week calendar

includes

  • A scoped set of task-oriented how-tos from engineer notes, Slack threads, or a live system
  • Incident or customer-facing explanation when the brief includes an outage
  • Handoff in Markdown / GitHub · one revision round

excludes

  • Open-ended backlog without a written scope · software feature builds

Documentation Retainer

$9,600 USD / month

80 hours · monthly cadence · half-time capacity

includes

  • Sustained senior technical writing across your product docs
  • How-tos, KB, incident notes, README upkeep, and edit passes
  • Same USD $120 hourly floor as the rest of the page
  • Remote, hybrid, or on-site · async standups — no meeting theatre

excludes

  • CMS · finance · medical · ecommerce · member login · software feature builds

Request documentation → Clarify package, product, and where the notes live — one section at a time.

One section at a time. Answer what you know; skip what you do not. The raven waits until the last step.

Who is sending this raven?

Audit, a how-to pack, or a retainer — which floor are we on?

How-tos, knowledge base, incident copy. You supply product facts; I write the page a tired first-time user can finish.

What system are we documenting?

Where do the messy facts live today?

Anything the brief still needs — timeline, constraints, the thing you almost didn't say.