Vendor-blind audit
You engaged a consultancy. Months in, the status reports are green and ceremonies are happening. Nothing is actually shipping except for PowerPoint presentations.
Find out what your consultancy actually delivers.
We read the code, the pipelines, and the deployment logs, then tell you in writing whether the work matches the pitch you were sold. One report with a fixed price, and no next phase to sell.
They said "CI/CD". They said Agile. They said AI.
Those are already tells. The audit looks past the words and at the artefacts: the code that is shipping or supposed to be, the pipelines that exist or are claimed to exist.
What this is not
- Slideware, decks, or presentations
- Certifications, maturity scores, or five-point scales
- Workshops, facilitation, or offsites
- Individual developer metrics
- Pitches for follow-on work
What about AI
AI gets nobody off the hook. Code arrives faster and in greater volume, and every line still has to integrate, test, deploy, and survive production. A vendor claiming AI productivity should have a pipeline that proves it. That's auditable.
Why vendor-blind
We have worked for, beside, and on the aftermath of well-known consultancies. To keep the audit bias-free, we require you to withhold their names for the duration of the engagement.
Who does the work
Nat Young. Former Lead Consultant at Thoughtworks. Fifteen years in delivery, auditing outsourced teams and leading critical launches. Practising what most teams only claim: continuous delivery, test-driven development, trunk-based development. Lowercase-a agile. Based in New South Wales, Australia. Remote by default.
The engagement
Two weeks · Written report · One engagement at a time
Findings, with evidence, in writing
An independent technical reality check.
Specific findings against named practices: integration strategy, test strategy, delivery flow, incident patterns. Each finding cites the actual artefacts.
AUD 40,000 ex GST · fixed
Contact hello@mainline.systems