← Back to the Lab / Own product · Cranely

Delegate the work. Keep the judgment.

A scorecard tool for engineering teams. The measuring is automated, the judgment stays with the coach.

Go to Cranely ↗

cranely.app

Type: SaaS
Status: Live · since 2026
Works in: Browser
Stack: Laravel · Inertia · Vue

Why it exists

Cranely is deliberately the counterexample in my own work. Everywhere else I delegate the execution to agents; here the judgment itself is the product.

Delegate the work, keep judgment where it matters.

How it works

One pillar, three sources, one judgment.

The Operational Excellence pillar of a CTO programme: three indicators, each with the measured numbers beneath it.

What you see here

Under Release reliability sit three sources: deploy frequency, failed deploys and lead time from PR to production, with start, now and target.
The score on the indicator, 5 towards a target of 7, is the coachs judgment, not an average of the sources.
Goals, attention points and actions belong to the pillar and come out of the conversation with the team.

Screens from the app, with sample data. The interface is shown in Dutch.

What it does

Structure

Pillars and indicators

Four columns of different heights on a plate, the tallest with a red top.

A scorecard is built from pillars, with indicators underneath them, each carrying a score from 0 to 10.

Pillars
Indicators
Score 0 to 10

Evidence

Sources under every score

A magnifying glass on a sheet with a table, one cell filled red.

Under each indicator sit the measured numbers that back it up. Every value needs a note: where did this come from?

Sources
Note per measurement

Judgment

The judgment stays with the coach

Scores, attention points and actions cannot be changed automatically. They belong in the conversation between coach and team.

Attention points
Actions

What it looks like

Three screens, no manual.

From the conversation to the measurement to the series.

The worksheet of a pillar in Cranely: where are we now, and the score the team chooses. — **Worksheet.** Coach and team pick a score per pillar together and write down where they want to be in three, six and twelve months.

Entering a measurement in Cranely: per pillar the indicators with score and target. — **Measurement.** Enter scores and source values per pillar, with a reference date and a note.

The measurement history in Cranely: monthly snapshots with scores and sources. — **History.** Every measurement is a snapshot; the series shows how the team moves.

Also through MCPCranely talks to your assistant too. Recording measurements and reading scorecards works through an MCP server, the same technique as the Connector. The scores stay handwork there as well.

See the Connector

← Back to the Lab Next: Vocaboo →

Built here, run here.

What I build here for myself, I also build for organisations that want to take AI beyond the pilot.

See The Build