Skip to main content
Evidence, not claims

How we evidence delivery

Published
Nothing yet, by choice
Every study
The same four parts
Under NDA
More we can walk through

The standard

Every case study here will have the same four parts.

Problem, approach, technology, outcome — in that order, with no room for a vague claim. If a piece of work cannot be described that way, it does not go up.

The sign-off

And none of it goes up without written approval.

Not a name, not a logo, not a figure, until the client has signed off the exact wording. Any number published here is one they have confirmed — security work in particular is often contractually confidential.

The offer

So judge us on the conversation instead.

What we cannot publish we can usually discuss: comparable work walked through under an NDA, or an introduction to a reference. Ask, and we will tell you what we can and cannot say.

Case study structure

What every case study here will contain

Four sections, in this order, with no room for vague claims.

  1. Problem

    The situation before we were involved, described in the client's own terms — including what the status quo was costing them.

  2. Approach

    What we built or changed, and why we chose that route over the alternatives we considered.

  3. Technology

    The stack and infrastructure involved, so a technical reader can judge whether the work is comparable to theirs.

  4. Outcome

    The measurable result, with figures published only where the client has confirmed them in writing.

Our policy

Why this page isn't full of case studies

Three commitments that explain the gap — and that outlast it.

Client approval, in writing

Nothing is published — not a name, not a logo, not a figure — without the client's written sign-off on the exact wording. Security work in particular is often contractually confidential.

Verified numbers only

Any percentage or figure on a case study is one the client has confirmed. We would rather describe an outcome qualitatively than attach a number we cannot stand behind.

Detail available under NDA

What we cannot publish we can usually discuss. Ask, and we'll walk you through comparable work — or introduce you to a reference — under an NDA.

Evaluating us for a formal procurement?

Our capability statement is a direct download — what we do, how an engagement runs, what you own at handover, and what we have not yet confirmed. For completed answers to a standard security questionnaire, ask and we'll send them.

Download capability statement (PDF)

Start a conversation

Judge us on the conversation instead

Bring us a real problem on a call. You'll learn more about how we work in thirty minutes than any case study would tell you.