The Network Change Assurance Sprint
A two-week paid assessment that shows you exactly how a bad change would reach your production network today — and what it would take to stop it.
The Assessment
The assessment stands alone. It is not a sales document with a proposal attached. If the recommendation is “your process is sound, spend your money elsewhere,” that is what it will say.
A documented comparison of your inventory of record against what is actually running. Every discrepancy listed and categorised.
How a change actually travels from request to production today — including the steps that are informal, undocumented, or done by one person.
The specific ways a bad change reaches production undetected, ranked by likelihood and blast radius.
Every gap, sized and ordered by risk reduced per unit of effort.
What to do, in what order — usable with or without OperiProof.
The Implementation
Taken only if the assessment justifies it, and only for one workflow at a time. We deliberately start with change validation, configuration compliance, or provisioning — never a platform rewrite.
One production workflow automated end to end
Validation that runs before anything touches the network
Verification that proves the intended outcome
A tested rollback path, not a documented intention
A pipeline your team owns and can run without us
Written for your engineers, not for us
A cryptographically signed, machine-readable record of every change, with a human-readable report generated from it. This is the artefact you hand to your own leadership, your auditor, or your funding agency.
The Assurance Retainer
Ongoing operation and extension of the pipeline, new workflows added as agreed, and evidence bundles produced for every change.
You are buying a defined outcome, not time. Where a brownfield estate is genuinely unknown, the assessment is quoted time-and-materials with a hard ceiling, and converts to fixed scope once the unknowns are mapped. Pricing is scoped and quoted before work starts — ask on the first call.
The fifteen-minute demo
An emulated topology driven by CI that catches a deliberately broken change and produces the evidence bundle. It uses no client data and runs on a laptop.
It shows a failure being caught, not a success passing. A demo that only ever goes green proves nothing about the gate — and the gate is the product.
Ask to see the demoStated plainly, because the boundaries are the credibility.
No trenching, splicing, cabling or construction.
No 24/7 on-call, no NOC, no help desk.
Nothing changes production without a human approving the specific change.
We start with one workflow.
If the right answer is a tool you can run yourself, that is what we will say.