Writing & Documentation.
Documentation that machines can read and humans can use. Copywriting that ships ready, without the revision-loop tax.
For ops, marketing, product, legal, compliance, HR, and IT leaders with content or documentation that needs to scale.
Writing scope set per project: book, system, or campaign. Delivered in English. Pricing established at the discovery.
Most content problems are the same problem from different angles: scattered information that no one can find, or clear information that doesn't read clearly enough to act on. We cover both: the documentation architecture that gives content structure, and the senior copywriting that gives it voice.
Documentation work is cross-functional by design: developers, analysts, operations, risk, legal, compliance, and business teams own the systems we document. The deliverable is content the next person can find, understand, and maintain without calling the writer. Copywriting runs alongside (landing pages, product messaging, campaign assets, executive bylines, conference materials) built to ship without back-and-forth between draft and final. Both strands share the same discipline: structure before style, reader before writer, judgment stays human.
The discipline
Documentation and copywriting are different crafts. Five principles run through both.
-
Structure before style
Architecture first. A clear structure outlasts every later edit.
-
Reader before writer
Written for the person who has to act on it.
-
Judgment stays human
AI-augmented where it adds value; never where judgment is the deliverable.
-
Built to ship
Copy that lands without the draft-to-final revision loop.
-
Maintainable without us
Content the next person can find, update, and own.
Three engagement scopes
Book
A single deliverable: a user guide, SOP, style guide, technical specification, or editorial asset produced to brief. Fixed scope, fixed output.
Typical duration: 1–4 weeks depending on complexity
System
A documentation library or content architecture built from the ground up or rebuilt from existing scattered content. Includes structure, governance, tagging standards, content schemas, and AI-readiness. The organization owns and operates it after delivery.
Typical duration: 4–12 weeks depending on scope and number of source systems
Campaign
A set of coordinated assets for a product launch, conference, initiative, or communications push: landing pages, email sequences, bylines, scripts, booth materials, and supporting copy produced as a coherent package.
Typical duration: 2–6 weeks depending on number of assets and approval cycles
What's inside
Technical writing and documentation
User guides and product documentation · SOPs and process flows · FAQs and knowledge base articles · API-facing content · Documentation libraries and architecture · Content schemas and content models · AI-ready content systems · Style guides, tagging standards, and content governance · Compliance and data-privacy-aligned documentation · Onboarding, business continuity, and operational documentation · Plain-language rewriting of legacy or technical content · Contributor coaching for internal documentation teams
Copywriting and editorial
Landing pages and web copy · Product descriptions · Email campaigns · Headlines, taglines, and calls-to-action · Launch, roadshow, and conference materials · Booth panels, demo scripts, presenter notes, and follow-up collateral · Executive bylines and thought leadership · Website and brochure optimization for non-native English teams · Legal, compliance, and high-visibility document editing · Non-native English editing and rewriting
What clients walk away with
-
Reduced time spent hunting for information across scattered content systems.
-
Improved documentation quality and consistency.
-
More accurate responses from internal search tools and chatbots.
-
Clearer, higher-performing campaign and product copy.
-
A stronger international brand voice for non-native teams.
-
Fewer revision cycles on high-visibility content.
-
Documentation the next person can find, understand, and maintain without calling the writer.
Worked examples: Documentation rebuild, Website & product messaging, Campaign delivery. All case studies
Plain-language editing for APAC teams
A specific strand of our work is editing and rewriting non-native English content so it reads as natural, executive-ready English, preserving the original intent and technical accuracy while removing the friction that signals non-native drafting. Legal documents, compliance filings, board materials, investor communications, and high-visibility external copy all benefit from this pass before anything ships.
Coaching internal teams to maintain what we build
Documentation engagements include contributor coaching (writing workshops, editorial review sessions, and style-guide onboarding) so the organization builds its own capability rather than depending on an external writer indefinitely. The goal is a documentation system the team can run without us.
What the edit looks like
The same board update, before and after a plain-language edit. The facts and the intent are unchanged — what's gone is the friction that signals non-native drafting.
As drafted
In regard to the matter of the third-quarter figures, it should be noted that a certain decline has been observed, which we believe to be attributable to the seasonal factors that typically affect this particular period of the year.
Edited
Third-quarter revenue fell. The cause is seasonal — Q3 is consistently our slowest quarter.
Common questions
Do you work with our existing CMS?
Yes. The work is platform-agnostic: SharePoint, Confluence, Notion, GitBook, or whatever the organization already uses. We deliver content and structure into the system in place rather than requiring a migration.
Can you work within our existing style guide?
Yes. If one exists, we work within it. If it doesn't, or if it needs updating, we can build or refine one as part of the engagement.
How do you handle version control and handover?
Documentation is delivered in the organization's existing version control system. Handover includes a content map, contributor guidelines, and (where scoped) coaching sessions for internal teams taking ownership of the library.
How do you handle confidential or sensitive content?
NDAs are standard. Documentation engagements frequently involve proprietary systems, internal processes, and compliance-sensitive material. Confidentiality terms are established before any work begins.
How long does a typical engagement take?
Depends on scope. A single deliverable runs one to four weeks. A documentation system runs four to twelve weeks. A campaign runs two to six weeks. All timelines are confirmed at the discovery call.
A Cornell University study published in Science (December 2025) analyzed more than two million papers across three major preprint platforms and found that AI substantially increased writing output, while many AI-assisted papers failed to deliver real scientific value. The gap between polished writing and meaningful content widened as AI use increased.16 Volume is not the problem AI solves well. Judgment is. AI-augmented where it adds value, never AI-replaced where judgment is the deliverable.
Where this connects
Documentation rebuilds often surface the workflow gaps that lead to AI integration. Change communications frequently need documentation support. Executive bylines connect to coaching: the positioning built on the page gets rehearsed in front of the room.
16Kusumegi, K. et al. Scientific production in the era of large language models. Science, Vol. 390, Issue 6779. December 24, 2025. DOI: 10.1126/science.adw3000. Source: science.org/doi/10.1126/science.adw3000.