MK
All services
01Independent software review

Software code audit & technical review

The Second Opinion is a paid technical review for founders who need to decide whether to sign a proposal, continue a build, approve a rewrite or change supplier. We agree the question and the evidence first. I review the relevant code, architecture and delivery plan, then give you a written verdict with the limits of what I could verify.

Mayur Kale discussing software delivery with an engineering team
Start here

The Second Opinion

Five working days — in your hands before your date · Fixed fee, quoted after the discovery call
What you walk away with
  • The verdict on the decision you named at booking: sign, renegotiate, stop, or move the date
  • Whether the date you have been given is real, and what actually drives it
  • What it will cost to finish — the number, not a range with an asterisk
  • Whether the rewrite you have been offered is necessary or convenient
  • Whether the people building it are the right people to finish it
  • Where the key-person risk sits, and what happens if that person resigns on Friday
  • The next decisions ranked by when they fall due — this week, this month, this quarter
  • A named owner for checking the verdict gets done. If that owner is a hire and not me, the report says so
  • Included: the contract read — the contract, quote or offer on the table read against the IP, exit, acceptance and payment clauses before day one, returned as plain-English notes for your lawyer
  • Included: run the next one without me — the questions to ask on every status update for the next 90 days, so the next date can be checked in-house
  • Included: the date call — thirty minutes on or just before your date, re-reading the verdict against what actually happened

If it doesn't give you a decision you can act on before your date, you don't pay for it.

The report ends by naming who checks it gets done. Sometimes that is a hire, and the report says which one. Sometimes it is the seat — and that is the only way the seat is offered.

What this looks like
Agree the question and access
  • Bring the decision, deadline and current proposal or build.
  • Agree the repositories, documentation, demo and relevant delivery records needed.
  • The five-working-day review starts once agreed access is available.
Inspect the evidence
  • Review the agreed code and architecture against the intended product and delivery plan.
  • Check dependencies, ownership, handover and delivery risks within the agreed scope.
  • Record evidence gaps and assumptions; this is not a full penetration test or certification audit.
Return a decision
  • Receive a written verdict and prioritised findings.
  • Understand what to keep, challenge or investigate before committing.
  • Take the report to your existing team or another supplier; a build or retainer is optional.

Relevant engineering experience

These projects show the engineering work behind the service. Each case study describes its own scope and outcomes.

Bring the decision, the deadline and what you have been told. We will use the discovery call to check whether a review is the right next step.

How we engage

A standalone, fixed-fee review quoted after discovery. Five working days from agreed access, subject to confirming that the scope fits your deadline. Larger codebases or specialist investigations require an explicitly agreed scope before work starts.

What I guarantee

If it doesn't give you a decision you can act on before your date, you don't pay for it.

You book the review against a decision and a date. The report exists to put a verdict in your hands before that date — sign, renegotiate, stop, or move it. If it lands late, or lands without a verdict you can act on, the fee is waived.

  • The decision and the date are written down at booking. That is what the report is measured against.
  • Five working days run from the day the access we agreed is granted, and must finish before your date — if they can't, I say so before you book, not after.
  • Waived on written notice within 14 days of the report, or before your date, whichever comes first.
  • No build proposal appears in the report. The report is yours to take to anyone.
  • If the review concludes you do not need a CTO seat, it says so and the seat is not offered.
  • Excludes the investor due-diligence edition — that decision belongs to the investor, not to me.
Questions

Questions I get asked about this.

What does a software code audit include?

This review examines the agreed parts of your codebase, architecture and delivery evidence against a specific decision. You receive written findings, priorities and a verdict. Scope and access are agreed first; it is not an exhaustive security audit.

Can you review a proposal before there is any code?

Yes. The review can focus on the scope, assumptions, ownership, acceptance criteria and delivery plan in a proposal. The report distinguishes what can be checked from what still needs evidence.

How much does a technical review cost?

The fee is quoted privately after the discovery call, once the decision, codebase and required access are understood. You agree the scope and fee before the review begins.

Do I have to hire you to build the software afterwards?

No. The written report is yours to use with your current team or another supplier. An ongoing CTO engagement or production build is a separate decision.

Before you commit

A build you can't evaluate, a demo that has to ship, or a certificate a contract is waiting on.

Book a 30-minute discovery call. Bring what you're building, the decision you need help with, and your timeframe. We will check fit and agree the next step before any paid work.