Codocly

Codocly converts a low-margin chore (writing READMEs, OpenAPI references, C4 guides, and runbooks by hand) into a continuously synced deliverable that re-generates on every Git push. At ₹799/month per user for 40 docs and ₹1,499/month on the Team Plan for 100 docs with role-based access, an agency can bundle documentation into a client retainer at a fraction of the manual hours it replaces. The strategic stake is ownership of the documentation layer inside client engineering teams before a competitor or the client's own tooling does it.

Codocly's plans are gated by documentation volume, not seats alone, so agency margin depends on matching client repo count to the right tier before quoting a retainer. The Free Plan caps at 3 README generations monthly with README.md export only, which covers a single-repo evaluation but nothing billable. Pro at ₹799 per user per month raises output to 40 docs with all four export formats and REST API access, enough for one or two active client repositories. The Team Plan at ₹1,499 per month supports up to 100 docs with role-based access, which is where a dev agency running documentation retainers across several client codebases should sit. A shop delivering a $2,500 Starter Repo Docs engagement on a single repository can stay on Pro; the moment a second and third client repo enter continuous Git push sync, the Team tier absorbs the volume without per-doc overage surprises eating delivery margin.

AI code tools compress the cost of producing a first working version, but they do not compress the cost of owning it. The Scaffold Versus Steward Split separates two jobs agencies have historically billed as one: scaffolding (generating a full-stack app, wiring auth and payments, standing up a prototype) and stewardship (architecture decisions, review, and keeping consumer code in sync when contracts change). Scaffolding is where the speed advantage lives. Stewardship is where retainer value and liability live. Verdent illustrates the first half, turning a plain-English description into a working product with authentication, payments, and an admin dashboard. Ripple illustrates the second, detecting a breaking API change and opening pull requests across every affected repository. Agencies that price both halves at the same rate give away the margin on scaffolding and undercharge for stewardship. Split the two in your statements of work, and staff them differently.

The Agent Output Liability Line is the boundary between code an agency can ship under its own name and code that still needs a human signature. Agentic tools now generate full-stack applications from prompts and auto-fix breaking API changes across repositories, which moves the liability question from 'did we write it' to 'who reviewed it.' Agencies that blur this line absorb client risk without pricing it. A practical test: if an agent opens a pull request at 2am and no human reads the diff before merge, that code sits above the line and belongs in a maintenance retainer, not a fixed-scope build. Tools like Agent Monitor and Agent Desk exist specifically to make that review boundary visible by surfacing per-file risk levels and session histories. The framework matters because delivery speed without a defined liability line converts margin into unpaid warranty work.

Adopt Codocly only when a client's documentation need is continuous and billable monthly, and pilot it on one real repository through a live pull request before quoting any retainer.

Set a hard blast-radius limit per agent run, then require a named human reviewer before any change merges into a client branch.

IF your agency already bills software clients for technical documentation and needs README, OpenAPI 3.1, C4 architecture, and runbook output refreshed on every Git push, THEN start on the Pro Plan at ₹799/month per user (40 docs per month, all 4 export formats, REST API, 5 MCP keys) and only move to the Team Plan at ₹1,499/month when you need 100 docs per month plus role-based access across multiple client repos. IF documentation is a one-off deliverable rather than a recurring retainer, THEN the Free Plan at ₹0 with 3 README generations per month and README.md export only is enough to test output quality before committing budget.

Build a repeatable documentation retainer that turns client repositories into README files, OpenAPI 3.1 references, C4 architecture guides, and SRE runbooks, synced on every Git push and published to a branded domain.