VantalectFulcrum

Leverage measurement for AI-native engineering

The leverage record your board can audit.

Fulcrum logs every agent-assisted task at the time of the work: the senior-engineer hours it would have taken, the agent minutes it took, and the operator minutes you spent. It turns “we use Claude Code” into an execution factor you can defend, publish, and improve.

$1,199 per year · installed in your environment · API, dashboard, CLI, and MCP server · included for a year with every Vantalect leverage engagement

A steel lever balanced on a small wedge, a small weight lifting a massive stone block, indigo rim light.

Measured on our own build

31×Aggregate execution factorA ratio of sums over every logged task
3,552Tasks loggedSince February 22, 2026, every row published
22.5×Median task factorThe middle task, not the mean
1EngineerOne operator with full product authority

Fulcrum is the instrument behind the public leverage record at charlessieg.com/leverage: 3,552 tasks since February 22, 2026, every row recomputable. Measured on our own build, not promised for yours. Yours gets measured.

What a record holds

Measured facts on one side. Estimates on the other. Never mixed.

Every field belongs to one of four evidence classes, and the dashboard never lets an estimate pose as a measurement.

01

Measured execution

Captured at the time of the work, not reconstructed afterward.

  • Agent-session minutes and wall-clock span
  • Token counts with exact, estimated, or unavailable provenance
  • Provider, model, session, repository, and commit
  • Prompt, supervision, correction, and review minutes
02

Estimated counterfactual

How long the work would have taken without the agentic path, with its basis and author on the record.

  • Qualified-senior-equivalent hours
  • An optional operator-unassisted low, likely, and high range
  • Estimate basis and author: agent, operator, or joint
  • Feasibility: can do, can do with learning, not reasonably feasible
03

Operator conditions

The circumstances the result was produced under, recorded as boundaries rather than multipliers.

  • Experience and product authority
  • Work cadence and tooling
  • Subscriptions and parallel orchestration
  • Never used as a multiplier coefficient
04

Capability expansion

Work that needed substantial new learning, or was not feasible unaided, is classified rather than assigned an invented hour count.

  • Time compression, skill extension, or otherwise infeasible
  • Counts and shares, never a fabricated multiplier
  • A concise rationale travels with the classification
  • Historical estimates are never multiplied in place

Inside the product

What the dashboard shows.

The dashboard gives the summary, the leverage trend, and the project breakdown. The cost page prices the same work by model and by activity. Both run in the dark and light themes, and the records list reads on a phone.

The Fulcrum dashboard with summary cards, two charts, a project table, and the records table (dark theme).The Fulcrum dashboard with summary cards, two charts, a project table, and the records table (light theme).
Dashboard. The personal view for the last 30 days: summary cards, estimated human hours per day, daily leverage, the project breakdown, and the records table. Demo data: every figure belongs to StrataForge Robotics, a fictional company.
The Fulcrum cost page with spend figures, by-model and by-activity tables, a yield table, and an optimizer finding (dark theme).The Fulcrum cost page with spend figures, by-model and by-activity tables, a yield table, and an optimizer finding (light theme).
Cost and ROI. Total spend, cost per task, hours saved per dollar, and leverage per dollar, with a breakdown by model and by activity and an optimizer grade. Demo data: every figure belongs to StrataForge Robotics, a fictional company.
The Fulcrum records list on a phone with search, a project filter, and stacked record cards (dark theme).The Fulcrum records list on a phone with search, a project filter, and stacked record cards (light theme).
Records on a phone. The records list at 375 pixels wide: search, a project filter, export, and sorting, with each record as a stacked card. Demo data: every figure belongs to StrataForge Robotics, a fictional company.

Demo data. These screenshots come from a demonstration installation. Every figure in them belongs to StrataForge Robotics, a fictional company, and none of it is a customer's record.

All 33 features

How it works

Recorded by the agent. Reviewed by you. Published on your terms.

The record is written while the work happens, by the tool that did the work, and confirmed by the person who supervised it.

  1. 01

    Record

    At the end of a task the agent calls record_leverage over MCP, or you run leverage add. A client-generated record id makes every retry idempotent: the same task never lands twice.

  2. 02

    Review

    Drafts become confirmed records in the dashboard. Corrections keep the original row and supersede it, so the ledger is auditable end to end.

  3. 03

    Publish

    Confirmed, reviewed records feed the summary, the time series, the team leaderboard, and, if you choose, an immutable public snapshot with a manifest and hashes.

Every surface your team already uses

Agents write it. People read it.

One PostgreSQL-backed service behind four front doors, so the record gets written by whatever did the work.

  • MCP serverTools an agent calls directly, from record_leverage to get_fatigue_assessment
  • CLIleverage add from any shell, idempotent by record id
  • REST APIAPI keys, mTLS, or JWT, with the same service layer underneath
  • DashboardSummary, time series, per-project breakdown, teams, and cost, in light and dark

From an agent session

# the agent, at the end of a task, over MCP
record_leverage(
  task="Split services and certifications into pages",
  human_estimate_hours=12, estimate_basis="qualified_senior",
  agent_session_minutes=41, wall_clock_minutes=41,
  operator_minutes_total=5, tokens=404000, token_source="exact",
  capability_class="time_compression",
  client_record_id="8DDB198D-…")

# or from any shell
leverage add --task "…" --human-hours 12 --agent-session-minutes 41

The part nobody else measures

Decision fatigue, on the record.

By the thirteenth task of the day the operator has made hundreds of supervisory decisions. Fulcrum counts them, scores the day, and hands the agents guidance to match: fewer questions, more conventional defaults, completed work instead of options.

Fatigue levels and how agents adapt
Records todayLevelWhat the agents do
0–3LowNormal operation. Present options, ask clarifying questions.
4–7ModerateFewer questions. Reasonable defaults when intent is clear.
8–12HighMinimize decision points. Front-load the reasoning.
13+Very highMaximum autonomy within the constraints. Present finished work.
  • A fatigue level and score from today's confirmed records
  • Recommendations for the operator and guidance for the agents
  • Read by the agents themselves through get_fatigue_assessment

Published metrics

Six numbers, each with a formula. None of them called “average leverage.”

The ratio of sums is not the mean of ratios, and Fulcrum refuses to blur them. Every published figure carries its formula identifier and its coverage.

Aggregate execution factor

60 × sum(H) / sum(A)

The primary execution metric: senior-hours saved per agent minute, summed over every record.

Median task factor

median(60 × H / A)

The middle individual task, immune to the outliers that dominate a mean.

Aggregate operator leverage

60 × sum(H) / sum(O)

Senior-hours per operator minute, over records with complete operator-time coverage, with the coverage count published beside it.

Calendar compression

60 × H / wall_clock

How much sooner the work landed. At period level the denominator is the union of intervals, never a naive sum.

Arithmetic task mean

mean(60 × H / A)

Kept for continuity and labeled as the task mean, never presented as the headline.

Capability expansion

counts and shares

How much of the work was skill extension or otherwise infeasible unaided, reported as counts, never as an invented factor.

Read the full measurement contract

Licensing

One license. Your environment. $1,199 a year.

Fulcrum is licensed for installation where your engineers already work. The record it builds is yours, whether or not you renew.

Included

With a Vantalect leverage engagement

Year one included

Both the Assessment and the Embed install Fulcrum on day one, so week six is measured with the same instrument as week one. Then $1,199 per year, only if you choose to continue.

See the engagements

Terms, what you need to run it, and the questions people ask first

Licensing

Measure it before you argue about it.

One annual license installs Fulcrum in your environment: the API, the dashboard, the CLI, and the MCP server your agents already know how to call. $1,199 per year. Included for a year with every Vantalect leverage engagement.

Request a license

Installed in your environment, on your hosts, under your identity provider.