Assessment

Is your team actually
AI-native,
or just using AI tools?

A 1–2 week paid engagement for tech leaders. Interviews, artifact review, and a scored report that tells you honestly where your foundations are — and what to fix first.

Book an intro call

Who it's for

Series A–C. 20–200 engineers.

You've shipped AI features. Your engineers use Copilot or Cursor. You've run an LLM workshop. But when you look at how your teams actually build — the handoffs, the decisions, the testing, the way product and engineering talk to each other — you're not sure the foundations have changed. This assessment tells you the truth.

What you get

A scored report. No fluff.

Scored assessment

Your team scored across four dimensions: product discipline, engineering practices, AI integration, and operating model. Not a narrative — numbers you can track.

Honest gap analysis

Where the real problems are — not the polished version your team presents in retrospectives. Based on interviews and direct artifact review.

Prioritised roadmap

What to fix first, second, and what can wait. Ordered by impact and feasibility, not by what's easiest to say in a board deck.

Readout session

A live 90-minute session with you and any relevant stakeholders. Walk through findings, debate them, align on next steps.

The process

1–2 weeks. Minimal disruption.

  1. 01

    Kickoff

    60-minute call with you. Scope the team, align on what's in and out, agree on who I interview.

  2. 02

    Interviews

    4–6 people: engineers, PMs, a designer if there is one, and you. 45 minutes each. I ask the same questions in different ways and compare what I hear.

  3. 03

    Artifact review

    I look at how you actually work: a sample of your PRs, tickets, decision logs, testing setup, deployment pipeline, how you write product specs. The artifacts don't lie.

  4. 04

    Report + readout

    Written report delivered first. Then a live session to walk through it, debate the findings, and align on what to do next.

Investment

Fixed price. Fixed scope.

The assessment is a fixed-price engagement — no surprises, no scope creep. Price shared on the intro call based on team size and scope.

If the assessment surfaces work worth doing, you can choose to continue into an embedded engagement. That's always your call, never a condition.

Book an intro call

FAQ

Common questions.

Why a practitioner and not a consultancy?
Big consultancies diagnose from the outside with frameworks. I've been inside teams doing this work. I know what it looks like when product and engineering actually build well together — because I do it.
How much time does it take from my team?
4–6 interviews of 45 minutes each. Access to some artifacts (PRs, specs, tickets). That's it. I don't need a dedicated team lead or a project kickoff ceremony.
What's the difference between this and a regular audit?
An audit tells you what you have. This tells you what's getting in the way — and why. The report is opinionated, not neutral.
Is this a sales pitch for a longer engagement?
No. The assessment stands on its own. Some teams take the report and run with it internally. If you want to continue working together, we talk about it. There's no pressure built into the process.

Ready to find out where you actually stand?

Book a 30-minute intro call. No pitch deck — just a conversation about your team and whether this makes sense.

Book an intro call