Which level does your team ship at?

25 questions on what decides a team's level — and the fastest way to move the whole team, not its one power user.

A team ships at the level of its slowest reviewer, not its strongest one. The ladder runs 0 to 5; this scorecard places the team on 1 to 4, and names what is holding it there.

What you get
  • Your team's rung on the autonomy ladder — instantly, on the next screen
  • Where the team is uneven: standards, review gates, rollout, workflow, enablement, ops
  • A 30/60/90-day plan that moves the team rather than one power user

What you give: your answers. No account, no card. An email only at the end, and only if you want the full playbook.

~8 minutesOne tap per questionInstant score

Your score is instant and free — no account needed. Add your email after you finish to see your full 30/60/90 playbook.

26 years building web apps · 2 IPOs · AI Lecturer at SWPS University · Using Cursor since 2023, Claude Code and Codex since early beta · CTO at TasteRay (built with AI)

6 team dimensions scored across 25 questions

A team ships at the level of its slowest review gate, not its fastest contributor. The Tech Lead Scorecard evaluates 6 operational dimensions to place your team on Levels 1 to 4 of the autonomy ladder.

1. Shared instruction files and standards

Whether CLAUDE.md, AGENTS.md, and Cursor rules live in version control and stay small enough for every agent session to follow.

2. Code review and verification gates

How pull requests generated by agents are tested, reviewed, and verified before they reach the main branch.

3. Tool rollout and configuration hygiene

Whether Claude Code, Codex CLI, and Cursor IDE share consistent permissions, hooks, and MCP servers across the team.

4. Spec-first and task decomposition workflow

How often engineers write a clear specification and test plan before handing implementation work to an agent.

5. Team enablement and playbook sharing

How working prompts, skills, and debugging patterns move from your strongest user to the rest of the squad.

6. Operational safety and incident loop

Whether regressions from agent-written code feed back into repository rules and automated checks.

Frequently asked questions

How long does the Tech Lead Scorecard take?
The assessment has 25 multiple-choice questions across 6 sections and takes about 8 minutes. Your score and radar chart appear immediately on the next screen without creating an account.
How is the team score calculated?
Each of the 25 questions is scored from 1 to 4. Your team level is capped by your lowest-scoring section because one missing gate — such as unverified pull requests or absent repository instructions — bottlenecks the whole team.
What comes after the scorecard?
You receive a section-by-section breakdown and a 30/60/90-day rollout plan mapped to the free Tech Lead Scorecard Guide in the documentation.

Read the Tech Lead Scorecard Guide →