01 · Method
How do you price a red flag?
Price a red flag as the engineering effort to fix it, in weeks of named roles, then decide whether it moves the price, becomes a condition of close or becomes a post-close plan.
- 01
We give effort, not a rate card; rates differ by team. Our technical due diligence report attaches an effort range to each finding.
02 · Flags 1 to 6
Which red flags show up first in the repository?
| Red flag | What it looks like | Why it matters | How to price it |
|---|---|---|---|
| 1. No automated tests | Empty test folder; releases tested by hand | Every change is a gamble | Effort to add tests around the money paths |
| 2. Unsupported frameworks | Runtime or framework past its vendor's patch window | Security fixes stop arriving | Upgrade effort per application |
| 3. Secrets in the repository | Keys and passwords in code or history | Exposure and forced rotation | Rotation and clean-up effort; condition of close |
| 4. One author | Most commits from one person, no backup | Knowledge walks out | Handover and documentation effort; retention terms |
| 5. Copyleft code | Strong-copyleft components in the shipped product | Obligations travel with the asset | Replace or relicense; your lawyers advise |
| 6. Unowned contractor work | Code by contractors with no signed assignment | Unclear ownership | Legal fix before close, not an engineering cost |
03 · Flags 7 to 12
Which red flags show up in how it is built and run?
7
No repeatable build. Looks like a build that works only on one laptop. Matters because nobody else can ship. Price as the effort to script the build and release.
8
A monolith nobody understands. Looks like modules everyone avoids. Matters because change is slow and risky. Price as the effort to document and pin behaviour with tests; see legacy code refactoring.
9
Unreviewed generated code. Looks like large commits with no review and no tests. Matters because nobody can explain how it works. Price as review and test effort per module.
10
Backups never tested. Looks like backup jobs with no recorded restore. Matters because the first restore is a real outage. Price as one restore test plus fixes.
11
Unpatched dependencies. Looks like known-vulnerable libraries in the lockfile. Matters as an exposure that can be found by any scanner. Price as upgrade effort.
12
No documentation. Looks like no architecture notes and no runbooks. Matters because the team's knowledge is the only record. Price as writing time, and as a signal for flag 4.
04 · Calibration
What looks like a red flag but is not?
An old but stable stack, a small test suite on non-critical code and a monolith that works are findings to note, not reasons to walk. The question is whether the cost to fix is bounded and whether the team can do it.
An older framework that is still patched by its vendor.
Low coverage on screens nobody changes.
A single deployable that the team understands well.
A framework the buyer does not use, in a stack the team knows deeply.
05 · Evidence
How do you confirm a red flag is real?
Confirm it with something you can show: a command output, a file path, a commit or a document.
- 01
A finding that rests on someone's say-so goes back to management as a question.
- 02
For example, run the dependency scan yourself, search the history for keys, and read the commit log for authorship. Each takes hours, not weeks, and turns an impression into an item you can price.
06 · Decision
What should a buyer do with the findings?
Sort each finding into three bins: change the price, make it a condition of close, or plan it for the first 100 days.
- 01
A red flag that the seller can fix cheaply before close is a bargaining point, not a reason to walk.
- 02
Use the evidence list in the technical due diligence checklist to find the flags, and if several are severe, ask for a deeper code audit of the repositories involved.
07 · For sellers
Can a seller fix these before a buyer looks?
Yes, many of them.
- 01
Secrets, dependency versions, a repeatable build and basic documentation are fixable in weeks. Fixing them first, and explaining the rest, protects the price; see sell-side technical due diligence.
08 · Next step
Who can check these red flags for you?
Ace8 is the modernization practice of AceMQ, and AceMQ engineers run the review on buy-side and sell-side deals.
- 01
Start from technical due diligence. Quote on request.