SOFTWARE · STUDIO · FUND · TECH DDMELBOURNE · SYDNEY · AUCKLAND · SAN FRANCISCOBUILD · BACK · FUND · VET6 INDUSTRY SECTORSFIRST BUILD IN ~60 DAYSFIRST TO BUILDSOFTWARE · STUDIO · FUND · TECH DDMELBOURNE · SYDNEY · AUCKLAND · SAN FRANCISCOBUILD · BACK · FUND · VET6 INDUSTRY SECTORSFIRST BUILD IN ~60 DAYSFIRST TO BUILD
Full Flight — Menu
HomePrivacyMelbourne · Sydney · Auckland · San Francisco
What it is

Most deals price the revenue. Almost nobody prices the code underneath it.

Technology due diligence is the part of a deal — or a board's risk picture — that most advisors wave through. The spreadsheet gets audited line by line; the platform the whole business actually runs on gets a confident nod and a wishful slide. We open it up properly: the architecture, the code, the security, the team and the technical debt that won't surface until after you've signed.

Then we translate engineering reality into the language a board or an acquirer decides in — what's solid, what's a liability, what it will cost to fix, and how much of the valuation is resting on something held together with tape. No jargon for its own sake, no forty-page deck nobody reads. A clear, ranked picture of the risk you're taking on.

Buying a company, raising or selling one, or just trying to understand the systems you already own — we tell you what's really there, and what it means in dollars and months.

What we
look at

The review

Six lenses on the same question: is this technology an asset you can build on, or a liability you'll inherit? We go deep on each one — automated analysis plus senior engineers actually reading it.

/ 01

Architecture & scalability

Will it carry ten times the load, or fall over the first time growth gets real? We pressure-test the architecture for where the business is going, not just where it has been.

/ 02

Code quality & technical debt

How much of what you're buying is an asset, and how much is a mortgage? We read the code, not just the README — maintainability, test coverage and the debt nobody has written down.

/ 03

Security & compliance

Where are the holes, what's exposed, and which regulation is one audit away from a fine? Security posture, data handling and the compliance gaps that become your problem after close.

/ 04

Team & key-person risk

Who actually holds the system in their head, and what happens the day they leave? We map the people, the gaps and the single points of failure the org chart hides.

/ 05

Delivery & engineering practice

Can this team ship predictably, or is every release a coin toss? CI/CD, release cadence, incident history and how work actually gets from idea to production.

/ 06

IP, licensing & third-party risk

Do they own what they think they own? Open-source licences, third-party dependencies, contractor IP and the AI-generated code that may not be anyone's to sell.

When teams
call us in

Six moments
BUY-SIDE

M&A due diligence

You're acquiring, and most of the target's value is its technology. We tell you what you're really buying — before the price is locked and the risk becomes yours.

Acquirer
SELL-SIDE

Vendor / exit readiness

You're raising or selling. We find the red flags before the buyer's diligence does — so you fix them on your terms, not theirs, and defend the valuation.

Founder / vendor
INVESTMENT

Investor diligence

You're writing the cheque. We give your investment committee an independent read on the technical risk behind the deck and the team behind the demo.

Investor / fund
ASSURANCE

Board & CTO health check

No deal — just a board that needs to know the technology is sound, and a CTO who wants an honest outside read on architecture, risk and best practice.

Board / CTO
RECOVERY

Insolvency & restructuring

An administrator, lender or board facing a distressed business needs answers fast: is the technology an asset worth saving, what will it take to keep it running, and what is it worth to a buyer?

Administrator / lender
INDEPENDENT

Independent expert opinion

When a deal or dispute needs an arm's-length technical read — a related-party transaction, a scheme of arrangement, a warranty claim or a matter headed for court — we give a defensible, independent opinion.

Expert / counsel

How a
review runs

The rhythm

Tight loops and a real readout at the end — not a black box you wait weeks for. You see findings as they firm up, so there are no surprises in the final report.

STEP 1

Scope & access

We agree what's in scope, sign the NDAs, and get read access to the code, the cloud and the people. Days, not weeks.

STEP 2

Dig in

We work through the architecture, codebase, security, infrastructure and delivery — automated tooling plus engineers reading the real thing.

STEP 3

Pressure-test

We interview the key people, probe the scariest assumptions, and separate the genuine risks from the merely cosmetic.

STEP 4

Readout

A ranked findings report and a live session with your deal team or board — red flags, remediation, cost and the questions to ask next.

What you
walk away with

The output

A ranked risk register

Every finding scored by severity and business impact — not an undifferentiated wall of issues, but a prioritised list you can actually act on.

Red flags, called early

The deal-breakers and the hidden liabilities, surfaced while you can still renegotiate, fix or walk — not after the ink is dry.

A remediation plan & cost

What it takes to make it sound, in real time and dollars — so “we’ll fix it later” comes with an actual number attached.

Impact on the deal

How the technical reality should move the price, the earn-out or the conditions — translated into the terms you negotiate in.

Book a diligence review →

Operators,
not auditors

Why us
What you actually getFull Flight · Tech DDBig-4 advisoryIn-house review
Reads the actual codeYes, line by lineRarelyIf there's time
Who does the workEngineers who shipGeneralist consultantsYour own team
IndependentYesYesNo — too close to it
TurnaroundDays to weeksWeeks to monthsWhenever it fits
Remediation planCosted & sequencedHigh-levelInformal
The outputRanked, plain-EnglishA long deckA verbal “seems fine”

Diligence
questions

Before you engage us
How long does a tech due diligence take?
Most reviews run one to three weeks end to end, and we can move faster when a deal clock demands it. Scope and access are agreed in days; the depth of the dig scales to the size of the codebase and the stakes of the decision. We'd rather give you a sharp, ranked read in time to act on it than a perfect one that lands after close.
What do you need access to?
Read access to the codebase and cloud, the architecture and any existing documentation, and time with the key engineers. We work under NDA as a matter of course, handle everything confidentially, and can run a limited-access review where a deal is still sensitive — though the more we see, the sharper the findings.
What happens if you find a dealbreaker?
We tell you plainly, early and in writing — a fast, honest red flag is the entire point. A real dealbreaker found before close saves you from the most expensive mistake in M&A: buying a liability at an asset price. More often we find things that are fixable, and we tell you what it costs to fix them so you can price or renegotiate rather than walk.
Can you help fix what you find?
Yes. Because we're operators, not just assessors, we can scope and run the remediation — or stand up a team to — once the deal closes. We'll always flag that up front so the diligence itself stays independent, and there's never any obligation to use us for the fix.
Ready when you are

Let's get it
to full flight.

Start a flight plan →