Clarityships soon.
One studio. Sprawling codebases, dense APIs, half-documented platforms — turned into documentation that reads like the product explaining itself.
Documentation is not
decoration.
Peel back each layer. Watch a real API reference transform from a wall of caveats into a developer's first instinct.
GET /v2/events?limit={limit}&cursor={cursor}&type={type}&status={status}
Returns a paginated list of events. The events are returned in sorted order, with the most recent events appearing first. The list object contains an array of up to limit events. If additional events exist beyond the first limit events, the list will be truncated. See pagination docs. Note: this endpoint does not return deleted events. The cursor param is optional. If not provided, the first page of results will be returned. type can be one of: payment_intent.created, payment_intent.succeeded, payment_intent.failed, charge.succeeded, charge.failed, charge.refunded, customer.created, customer.deleted, invoice.created, invoice.paid, invoice.payment_failed. (See full list in Appendix D.)
/v2/eventsList webhook events
Call this endpoint to fetch your 20 most recent webhook events, newest first. Use the cursor parameter to page through older events. Filter by type to watch for specific lifecycle events like payment_intent.succeeded.
limitintegerEvents per page. Default: 20. Max: 100.cursorstringPagination token from the previous response.typestringFilter to a specific event type. See event types →Call this endpoint to fetch your 20 most recent webhook events, newest first.
Lead with the outcome, not the mechanism. "Call this"→ action frame."newest first" → answers the implicit next question.
Use the cursor parameter to page through older events.
Removed 47 words about what cursor is. Replaced with what it does for the reader.
Filter by type to watch for specific lifecycle events like payment_intent.succeeded.
One concrete example outperforms "see Appendix D" every time. Specificity is trust.
Original: 148 words, 1 useful sentence buried in paragraph 3.
Rewritten: 62 words, scannable, actionable from line one.
Three kinds of
documentation debt.
Each engagement is scoped differently. All of them start with the same question: what does a reader need to understand in the first 90 seconds?
Engineering Leads
Series B, 40–120 engineersYour Confluence has 847 pages. Maybe 60 are accurate. New hires spend their first week lost, and your senior engineers are writing docs instead of shipping.
An internal knowledge system developers actually use — searchable, current, and written at the level your team thinks.
DevRel Managers
Launching public-facing docsYou have a product engineers love and a docs site that makes them feel abandoned. The API reference is auto-generated. The guides don't exist yet. Launch is in 6 weeks.
A developer portal with a narrative — quickstart that converts, reference that answers before it's asked, guides that build mental models.
OSS Maintainers
Open-source projectsThe README hasn't been touched since the initial commit. Issues are 40% "how do I install this." Contributors can't onboard without a DM.
A README that earns the star before they run a single command, and a contributing guide that turns drive-by users into returning collaborators.
One studio. Three to four engagements per quarter. The next intake opens in Q2 2026.
Q2 2026 Intake
Documentation
is the product's
first impression.
Reserve a spot in the next quarterly intake. Three to four engagements only — scoped, unhurried, and built to last.