Skip to content
Assess

DevOps consulting

Short engagements against a specific question — an architecture review, a second opinion on a plan, or an assessment before you commit a budget.

You need an answer, not a supplier

Sometimes the requirement is not a project. A decision is pending, the team is split, and the cost of being wrong is larger than the cost of an outside opinion — but every enquiry turns into a proposal for a six-month engagement.

What the work involves

  • Architecture & reliability review — a fixed window agreed before start, read-only, a written report ranked by effect against effort, including the findings that say the current plan is fine. Probes, disruption budgets, topology spread, priority classes, and what a zone loss would actually do.
  • Second opinions on a proposal, a vendor choice or an estimate, delivered against the specific question asked. why we count a saving once →
  • Pre-commitment assessments: what this will actually take, before the budget is approved rather than after.
  • Incident post-mortems facilitated by someone with no stake in the conclusion.
  • Short mentoring engagements where the goal is that you stop needing us.

How the work goes

  1. Scope the question

    A call to establish what is actually being decided. If the answer is that you do not need us, that call is where you find out.

  2. Work

    A fixed window — typically days, not months — with the access needed and the question agreed in writing.

  3. Answer

    A written response with reasoning and the alternatives considered, and a walkthrough with whoever has to act on it.

Is this the right call?

A good fit when

  • A pending decision where an outside view is cheaper than being wrong
  • Teams who want a specific answer rather than an engagement

Not us when

  • Reviews commissioned to support a conclusion that has already been reached