SOFTWARE DELIVERY ECONOMICS

See your engineering from another orbit.

MetricMartian turns GitHub evidence, engineering cost, and AI-assisted baselines into a weekly mission brief founders can understand.

No keystrokes. No screenshots. No hidden scoring.

Martin connects cost, delivery, and quality evidence to a weekly Mission Brief.
10-minute setupGitHub evidenceNo invasive tracking

DOWN-TO-EARTH EVIDENCE

Cost, delivery, and context—together.

Martin does not rank a person's value. He shows what the repository supports, where evidence is missing, and which question to ask next.

01

Cost

Keep billed or allocated cost visibly separate from estimated repository work.

02

Delivery

Compare merged work with a directional, versioned baseline built for modern AI-assisted development.

03

Context

Expose quality coverage, confidence, missing work, and founder calibration before drawing conclusions.

MARTIN'S NOTES

A sample result, with the evidence left attached.

This example says the week's merged work is aligned with its current comparison baseline. It does not claim exact hours, unseen work, or a conclusion about the engineer.

“The delivery pattern is aligned. Two pull requests have limited review or test context, so open those receipts before deciding what to ask next.”

SAMPLE · NOT CUSTOMER DATA

What supports this result

Grade B
Evidence window
Aug 3–9 · 7 merged pull requests
Delivery range
6–9 repository-visible hours
Comparison
Aligned with the current AI-assisted baseline
Quality context
Good coverage; two items need review
Entered cost
$2,240, shown separately from effort

Directional evidence only. Repository activity is incomplete by design and is not a timekeeping record.

ONE BRIEF. FOUR RECEIPTS.

Read the signal, not the person.

Every weekly result keeps the observation close to the evidence and gives you a direct path into the Flight Recorder.

01

Observe the period

See the week, merged work, repositories, and author coverage.

02

Compare the ranges

Keep repository-visible work, billed time, and the modern baseline separate.

03

Check confidence

See which quality and context signals are present, missing, or provisional.

04

Open the receipt

Inspect each pull request, version, explanation, and founder calibration.

OPEN METHODOLOGY

A method you can inspect.

MetricMartian combines deterministic GitHub evidence with constrained, versioned AI decisions. Confidence falls when the evidence thins out, and every calibration remains visible.

Evidence, not surveillance

Pull requests, commits, reviews, and checks—not keystrokes, screenshots, messages, or screen time.

Ranges, not a stopwatch

Repository-visible sessions and an AI-assisted baseline produce directional ranges, never exact-hours claims.

Missing stays missing

Unavailable quality signals lower confidence. They are never quietly counted as failure.

Every result has a receipt

The Flight Recorder keeps the period, evidence, versions, calibrations, and limitations beside the result.

Read the full methodology

PRIVATE-BETA PRICING HYPOTHESIS

Start with 14 days of evidence.

Proposed packaging for research—not a public offer. No card is required for the trial. Billing remains in test mode during private beta, so no real payment is collected yet.

SOLO · HYPOTHESIS

$79/ month

For a founder working with up to two active engineers.

  • Weekly Mission Brief
  • Flight Recorder evidence
  • Email and optional Slack digest
Apply as a Solo design partner

Research hypothesis only. These prices are not a public offer or a proven willingness-to-pay result. Plan limits are enforced server-side; live pricing and trial length require founder approval.

READY FOR LIFTOFF?

Bring your next engineering question into focus.

Request a design-partner conversation or join product updates. A person reviews every private-beta request before any repository is connected.

Request early access