Product

One track, from the evidence to the measured result.

Tracks finds what to build next, puts it in front of you with the evidence, builds what you approve, and measures whether it worked. Four steps, one page.

01 · Find

It finds the work. A tracker only records it.

Tracks reads your code and your usage data side by side and works out what to build next: the step where people leave, the error that reaches the most users, the screen nobody opens.

An example from Leafbox, a sample product

  1. Reads

    src/pricing.jsyour code
    orders tableread only
  2. Finds

    19 of 99 orders were charged less than their shipping cost.

  3. Proposes

    CheckoutLEAF-2
    Stop coupons from pushing an order total below zero
    Bug · Small · low risk

Reads your code

On your own repository, through GitHub. Tracks reads what the product actually does, not what a ticket says it does.

Reads your usage data

It reads your data and cannot change it.

Brings the evidence

Every finding comes with the number that shows why it matters, in plain words.

Plugged into the tools your product and data already run on.

Tracks reads where your code, your usage data and your errors already live. It reads your data and cannot change it.

02 · Decide

Why this, why now. You decide.

Each idea lands on a board as a card: what is wrong, what to change, and the evidence behind it. In plain words, so the person deciding never has to read code. Open a proposed card to see one.

Leafbox · Board
Needs you3 proposals to decide
Proposed 3
CheckoutLEAF-2
19 of 99 orders were charged less than their shipping cost.
Bug · Small · low risk
CheckoutLEAF-3
About 70% of orders are on the plan that pays shipping every month.
Feature · Medium medium risk
ActivationLEAF-1
35% of sign-ups finish onboarding; 39% stop at step 1 or 2.
Improvement · Medium · low risk
Approved 0
Building 1
ActivationLEAF-4
Remind people who stopped half-way
The builder is writing the change
In review 0
Shipped 1
CheckoutLEAF-0
Show the shipping cost before checkout
Improvement · Small KPI improved

Leafbox is a sample product. One card crosses its board by itself.

A card you can read

What is wrong, what to change, and the evidence behind it. No code to read.

Approve, ask, or reject

Approve it, ask a question, or reject it and say why. The team remembers the reason.

Only what needs you

The strip at the top of the board lists what is waiting on a person. Everything else keeps moving.

03 · Build

What you approve gets built. Checked, and delivered as a pull request.

Tracks's own teams run on Claude: they read your product, propose cards, challenge each other's proposals and build what you approve. Or add Tracks to the assistant you already use.

From approval to pull request

  1. Built

    By Tracks's teams, or by your own assistant with its own tools.

  2. Checked

    Tracks checks every change before it reaches review. When a check fails, the builder reads why and fixes it.

  3. Delivered

    A pull request on your own repository, explained for people who do not read code.

Pull request · In reviewLEAF-2

A coupon can make the plan free, never the total negative

How to try it

  1. Add a plan to the cart.
  2. Apply a coupon worth more than the plan.
  3. The total shows the shipping cost, never less.
Checks passBug · Small · low risk

Runs on Claude

Tracks's own teams run on Claude, and they challenge each other's proposals before one reaches you.

Your assistant, through MCP

MCP is the open standard for connecting assistants to tools. Your assistant reads the board, proposes cards, attaches designs and builds approved work.

Checked before review

Whoever does the work, Tracks keeps the record and checks every change before it reaches review.

04 · Measure

Then it measures. Did the change do what the card said?

Afterwards Tracks reads the number again. Improved, unchanged or worse: the card says which. Every decision, by a person or by an agent, leaves a record you can go back to.

Orders with a wrong total

19 → 0

KPI improvedLEAF-2 · measured after shipping

The card says which: ImprovedUnchangedWorse

Record

Leafbox, a sample product · LEAF-2
  1. 09:02Checkout teamRead src/pricing.js and the orders table.
  2. 09:03Checkout teamProposed LEAF-2.
  3. 09:03CriticDropped "Add a dark mode to the dashboard": there is no dashboard in the code, and no evidence that anyone asked for this.
  4. 09:10YouApproved LEAF-2.
  5. 09:14BuilderDelivered a pull request. Checks pass.
  6. 09:31YouMerged LEAF-2.
  7. laterCheckout teamMeasured: 19 → 0.

05 · Control

You set how far it goes.

How far it goes

You approve a card. Tracks builds it, checks it and delivers the pull request.

At every level

  • It reads your data and cannot change it.
  • It stops at the daily budget you set.
  • It cannot touch the parts of your code you mark as protected.
Build what you approve: each step and who does it
StepWho does it
Finds the workTracks
Writes the cardTracks
DecidesYou
Builds and checksTracks
Merges the pull requestYou
Measures the resultTracks

every row is written to the record

Fast work, kept on one track.

Connect a repository and Tracks puts its first cards on your board. Start with propose only: nothing is built until you say so.

Get started