Acqualytics Ask a question

Clarity · Value · Evidence

Acqualytics is software assurance.

We give owners evidence-based clarity on the software an outside team built for them — what you own, where you depend on vendors, and whether you’re getting the value you paid for.

Experience15+ years
DisciplinesSoftware delivery, engineering leadership & investment
ScaleStartups → enterprise
TeamsInternal & outsourced developers

Do you own it?

Do you actually own your software?

You paid to build it. We show you what you control, where you depend on vendors, whether you’re getting the value you paid for, and what to fix first.

~10Business days to a clear recommendation
19/31Of what you paid for, delivered
11% → 100%Software you can run yourself
Sample review · redacted Vendor-dependent
39
Independence 39/100 You couldn’t build, deploy, or recover this without your vendor.
Critical parts you can run yourself 8 of 71
Yours Vendor-controlled

Start from your situation

Who built it changes what’s at risk.

Pick the one that sounds like you.

The code, cloud and pipeline may live in their accounts.

You pay every invoice, but the things that let you build, deploy and recover can quietly sit under the agency’s control. Renewal becomes a conversation you can’t win.

What the review tells you
  • Exactly which components only they can reach
  • What leaving would actually take — time and cost
  • Whether you’re getting what you’re billed for

Knowledge and access sit far from you.

An offshore or outsourced team can deliver fast, but access, documentation and know-how concentrate off-site — and billed rarely equals delivered.

What the review tells you
  • Billed vs. delivered, line by line
  • Whether you could run it without them tomorrow
  • Where the single points of failure are

One person understood it — and then left.

When a contractor or former employee built it, the system often lives in their head. No documentation survives their exit, and every change is a risk.

What the review tells you
  • The bus-factor — how many people could safely change it
  • What’s undocumented and how to de-risk it
  • Whether the system can be rebuilt and recovered

What you get

Six documents. One recommendation.

Evidence, not opinion — the value of your spend made visible. Counts and pass/fail checks you can reproduce yourself, written for a board.

01

Executive brief

Two pages, plain English — the recommendation your board can act on.

02

Independence checklist

18 pass/fail checks: can you build, deploy and recover without the vendor?

03

Full technical assessment

Ten domains, every finding cited to the evidence.

04

Remediation roadmap

What to fix first, in order of risk and cost.

05

Transition risk model

What leaving your vendor would actually take.

06

Delivery record

Billed vs. delivered — what you paid for against what exists.

A 30-second read

How independent are you right now?

Tick the ones you can honestly say yes to. The read updates as you go.

Your read
0 / 6 under your control

Tick the statements that are true for you.

From hunch to evidence to a clear decision — that’s the review.

How it works

Ten days. Four steps. No disruption.

You give read access. We do the rest without disrupting your team — your developers don’t even need to know.

Step 01

Scoping call

A short call to understand the software and agree what we assess.

Days 1–2

Access

Read-only access to the code, cloud, and delivery record.

Days 3–8

Analysis

Ten domains, 18 independence checks, billed-vs-delivered.

Day 10

Readout

The brief, the evidence, and one clear recommendation.

Proof · one review

They controlled a tenth of their own software. We got them the rest.

Before the review11%
After11%

Software the company could build, deploy and recover without the vendor.

We proved how little they truly controlled, then helped their own team take over — with no interruption to a live regulated service. Scroll to watch the recovery.

~10 daysTo a clear recommendation
12 of 31Paid-for items that didn’t exist
0Interruptions to service
Read the case file →
Software under their control A tenth, at first
Under their control Vendor-controlled

Who’s behind it

Judgment from people who’ve run delivery.

15+ years across software delivery, engineering leadership, and investment — from early-stage startups to large software organisations, and across both internal teams and outsourced, offshore developers.

That mix is why our reviews come back as money and months — clear enough to act on, not a list of technical complaints.

A
[Your name][Your title, e.g. Founder]

“Most of the teams I look at are capable. The problem is usually the process around them, not the people in it.”

Placeholder — real name, photo and background to be added.

The engagement

Find out what you actually own.

You give read access; we do the rest without disrupting your team — and hand back clarity you can act on.

Independent · Fixed fee, not contingent on findings · We never sell you the fix