Platform and dependency work
Review and implement selected upgrades, check compatibility, and validate agreed publishing paths.
Docs Ops and maintenance - Keep your documentation system working after launch.
Keep dependencies, builds, and integrations from becoming a maintenance backlog. We help your team investigate issues and deliver the improvements you do not have time to tackle.
When maintenance keeps slipping behind
- Your team has a running platform and a growing maintenance backlog.
- Dependencies, builds, integrations, or search need regular attention.
- You need engineering capacity to investigate issues and deliver planned improvements.
Keep the platform healthy
Build and link health
Run the configured checks, investigate failures, and prioritize repairs with your team.
Issue investigation
Triage reported problems, communicate findings, and implement fixes within the agreed capacity and permissions.
A planned improvement backlog
Track work on performance, workflows, references, search, and the integrations included in your agreement.
A record of work and remaining risks
Report completed changes, check results, unresolved issues, and the next priorities at the agreed review cadence.
Clear capacity and support terms
Your agreement names the covered sites and repositories, included capacity, working hours, contact channels, review cadence, and any response targets. Planned work, consultation, and incident investigation use that capacity unless the agreement states otherwise. Additional work is quoted and approved before it begins.
Response targets describe when an issue is acknowledged and assessed. Resolution depends on the problem, permissions, third-party services, and available capacity. Any out-of-hours coverage is specified separately.
Choose the level of ongoing work
Docs Ops
A recurring engineering agreement for maintenance, issue investigation, and planned improvements across the defined documentation system.
Discuss ongoing supportFocused maintenance
A narrower agreement for a site with a stable platform and limited scheduled work. We define the included capacity and checks before starting.
Discuss maintenanceHow we take over ongoing work
Step 1
Review the system
Establish access, build and deployment paths, integrations, current issues, and customer responsibilities.
Step 2
Agree the operating scope
Define covered work, capacity, priorities, contact arrangements, and the evidence used to review progress.
Step 3
Maintain and improve
Deliver reviewed changes, report check results and open issues, and adjust the backlog with your team.
Platform-specific work
Get help with the platform your team uses, or compare the options before you move.
Keep guides and references useful
Targeted guides, reference corrections, and documentation gaps can be included where they affect the agreed platform or publishing work. Product experts review technical claims.
Options and pricing
Monthly pricing depends on the covered systems, capacity, and support terms. Scheduled work, consultation, and issue investigation use the agreed capacity unless the agreement states otherwise.
Docs Ops
Recurring engineering for the covered platform, integrations, and prioritized improvements. Final scope and monthly capacity are agreed before work begins.
$1,500–4,000/month
- Platform and dependency work
- Build-health and broken-link checks
- Issue investigation within agreed capacity
- Defined improvement backlog and review cadence
- Content drift or AI retrieval checks when included in scope
Focused single-site maintenance
A narrower option for a stable documentation site with limited scheduled work.
From $350/month
- Up to 3 hours each month, with no rollover
- Planned updates and validation within those hours
- Consultation and issue investigation use the same hours
- Additional work quoted and approved separately
Complex documentation estate
Ongoing engineering across the sites and integrations explicitly covered by the agreement.
Custom proposal
- Defined sites, repositories, and integrations
- Agreed capacity and customer responsibilities
- Monitoring, incident coverage, and response targets by agreement
- Onboarding, training, and reporting as scoped
Documentation teams we have worked with
Questions about this service
Work is delivered within the capacity and scope stated in your agreement. We discuss additional work before committing it.
Incident coverage, working hours, and response targets must be stated in the agreement. We assess your requirements before offering that coverage.
The agreement can include targeted technical corrections and documentation gaps that affect the system. A broader authoring program requires a separately defined scope and product reviewers.
We review the stack, source access, custom code, dependencies, and operating risks before agreeing what we can cover.
What is waiting in your documentation backlog?
Tell us which sites you run, who maintains them today, and what is waiting in the backlog. We will help you prioritize the work and choose a level of support.