Process
How an engagement runs
From first note to readout: the stages of a Site Maple Hub CI/CD audit or DevOps enablement engagement, including access, artifacts, and handoff.
We keep the same skeleton whether you book a flagship CI/CD pipeline audit, an enablement sprint, or a release readiness review. The depth changes; the sequence does not.
- Inquiry & fit
You describe the stack, the pain, and any hard dates. We confirm whether an audit, sprint, or readiness pass is the right shape—or decline if the ask is pure staff augmentation.
- Scoped proposal
You receive a short statement of work: pipeline family in scope, access needs, calendar, fee, and deposit. No work starts until both sides sign.
- Access & intake pack
Read-only pipeline access, a recent failure sample, and a stakeholder list. If escorted access is required, we schedule those windows up front.
- Fieldwork
Walkthroughs, failed-run archaeology, and interviews. Enablement sprints replace some of this with paired implementation hours.
- Readout & artifacts
Written findings, prioritized actions, and a live session with owners. You keep the documents; we do not hold them hostage behind a portal.
- Optional follow-on
If you want coached implementation, we quote an enablement sprint separately. The audit never silently becomes open-ended labor.
What you prepare
- A counterpart who can answer within a business day
- Clarity on which environments are off-limits
- Honest notes about “hero” steps people still run by hand
What we prepare
- A shared agenda before every working session
- Findings written so a new hire could act on them six months later
- A clear stop date
Ready to begin?
Browse engagements or request a pipeline audit with your CI product and service count in the first message.