The truth, ranked and in writing.

Who it's for

You can feel it. You can't prove it.

Fifteen engineers, and somehow less shipping than when there were six. A roadmap that keeps slipping without anyone able to say exactly why. A board asking pointed questions the CEO can't answer with confidence. The team insists it's technical debt; the board suspects it's leadership; nobody outside the room actually knows.

• CEOs and boards who need an independent read before the next hire, the next raise, or the next rewrite gets approved on a hunch.
• New COOs and CTOs inheriting an org they didn't build and can't yet judge.
• Companies post-acquisition whose underwritten roadmap isn't shipping, and nobody can say whether the cause is architecture, process, or people.

What gets read

The code, the process, and the meetings.

Slow shipping is rarely one cause. The audit reads all three lenses, because the fix is different for each:

• Architecture drag — a system fighting the team that has to change it: brittle coupling, missing tests, a data model nobody trusts enough to move fast around.
• Process drag — where releases actually stall: reviews that queue for days, an on-call rotation nobody owns, a definition of "done" that keeps moving.
• Org drag — where authority and knowledge concentrate in one person, where the org chart and the real decision-making don't match.

Distinguishing these matters, because a team that reaches for a rewrite when the real problem is process wastes a year fixing the wrong thing.

The deliverable

An ordered list of what to change first.

Not a slide deck of observations — a written verdict a CEO can act on and a board can read without a translator: what's actually slowing delivery, which of it is architecture and which is organizational, and the sequence for fixing it. Findings ranked by what they're actually costing, not listed alphabetically.

How it runs

Three weeks inside the code, the process, and the meetings.

1. A 30-minute call

   What's prompting the question, what the board is asking, and what a useful answer would need to cover.

2. A fixed-scope proposal

   In writing, within 48 hours. Fixed price — no hourly billing, no meter running while the scope is worked out.

3. The read

   Code, process, and — where the engagement allows it — conversations with the team. The audit is framed as being for the engineering org, not a case being built against it.

4. The verdict

   The written findings, ranked, followed by a call to walk them and answer the question that always comes next: what do we do first?

The shape of it

How this engagement usually goes.

Client work is confidential by default, so what follows is pattern, not portfolio. Named references are shared in conversation.

Why this firm

An outside read, from someone who's run the inside.

Diagnosing organizational drag takes someone who has actually carried delivery, hiring, and architecture decisions at the executive level — not just read the code. That's the judgment behind every audit, principal-led, with a constructive posture toward the team being read: the goal is a fixable answer, not a verdict against anyone in the room. More on the entity and the person on The Firm.

MSA + SOW on every engagement · Fixed scope, fixed price, no hourly billing
NDA on request · Confidentiality both ways · USD invoicing, worldwide