Surface technical risk before the deal is priced.

I score the technology risk in your deal before price is locked, then stay on when engineering has to deliver the thesis.

Asim Mohammad — editorial portrait pending final photograph
  • $600M exit: technical readiness
  • SOC 2 Type II in 6 months
  • 38% cloud spend reduction
  • 15+ portfolio companies advised

The problem

The technology risk that does not show up in the CIM.

Debt that surfaces after close

The architecture that looked fine in the data room cannot fund the growth case once you own the P&L.

An org that breaks the model

Headcount and velocity assumptions in the CIM assume an engineering system that does not exist at the scale you underwrote.

Security that fails first enterprise review

SOC 2, FedRAMP, or a single customer security questionnaire exposes gaps that reset the revenue plan by a year.

Engagement models

How the work is scoped.

Diagnostic Sprint

3 weeks · fixed scope

A time-boxed read on technology risk before you commit more capital or change the plan.

  • Findings report for the deal team or board
  • Scored risk register with severity and owners
  • 90-day remediation plan with sequencing
  • Live readout with Q&A

For deal teams needing a fast read

Full engagement details

Most common engagement

Embedded Technology Leadership

per month · 3-month minimum

Operating seat alongside management while the engineering plan is rebuilt and executed.

  • Weekly operating cadence with the leadership team
  • Hiring and org design decisions documented
  • Architecture and delivery roadmap owned end-to-end
  • Board-ready technology updates each cycle

For portfolio companies on the critical path

Full engagement details

Technical Due Diligence

per transaction

Pre-acquisition assessment of architecture, security, scalability, and the team.

  • IC-ready written diligence report
  • Architecture and scalability assessment
  • Security and compliance posture review
  • Team and delivery-capacity evaluation

For deal partners before price is locked

Full engagement details

The assessment

Twelve questions. Four minutes. A scored view of your technology risk.

The score gives you a shared artifact for partners: where architecture, delivery, security, and team stand relative to peers at your stage, before any conversation is booked.

Insights

Recent writing.

All insights

Leadership

The CTO Skill Nobody Trains For: Saying "No"

Every technical leader knows the feeling: constant requests, endless priorities, and the quiet pressure to say yes to everything. But the most important technical decision is often deciding what not to build.

February 9, 2026 · 4 min read

Newsletter

Operating notes for people who underwrite technology risk.

Used only for this list.

Start with the risk, not the retainer.

Complete the Technical Risk Assessment, or request a confidential conversation if you already know the shape of the work.

Two engagement slots for Q4 2026.