Guides written to be useful whether or not you ever hire us.
Free to read, no email, most with a full edition to keep. Pick the line you came for.
Software
For founders and engineering leads: quality, due diligence and the security review that stalls deals.
The AI SDLC Playbook
The two ceilings nobody warns you about, why a green test suite can sit over a broken product, six practices that hold quality as a codebase grows, and the lifecycle around the code. A short read, and the full edition.
Read it now →What technical due diligence actually looks for
Auditors rarely fail a deal on ugly code. They fail it on unmanaged risk. What gets examined at Series A, and what you can still fix.
Read it now →Surviving the enterprise security questionnaire
Your deal has stalled in security review and SOC 2 is months away. What you can answer from evidence in the meantime, and what you must never claim.
Read it now →IT & security
For firms without an IT person: what to set up, what to do in the first seconds of a suspected compromise, and a monthly briefing.
Setting up IT for a small firm
Six things worth building properly when nobody owns the IT: remote access, the office network, filtering, file sharing, licences and accounts. What each costs you to skip, and the order to do them in.
Read it now →The first 15 seconds
A one-page plan for the moment you suspect a machine or account is compromised: isolate, freeze the accounts, call for help. With the data on why the window is that short.
Read it now →Monthly security highlight
A monthly document for CISOs and IT heads: what changed in the vulnerabilities attackers are using, the trends behind it, and the decisions for the next thirty days, with the method printed.
Read it now →The CVE Triage Handbook
How to read a CVE record, notice when it changes, find the precondition, and decide what to do first. 63 pages, worked through 10 real cases, with scripts, templates and a one-page triage card.
What it is, and subscribe →Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us