Know what engineering actually costs.
Before the board asks.
TheMetrics turns the work already sitting in ClickUp and GitLab into cost per feature, delivery forecasts, DORA metrics, and reports you can send upstairs without a caveat. Setup takes 20 minutes, not 20 meetings.
14-day free trial · No credit card · Runs on your own data
Read-only OAuth. We work from the tickets your team already closes.
Sprint review and the finance deck finally quote the same number.
Every AI summary shows the delivery data it’s standing on.
Same payroll model used by Cost Analysis, sprint exports, and operating reviews.
82% confidence. Risk is concentrated in review and QA wait time.
Sound familiar
You have the data. You still can’t answer the question.
Every ticket, every status change, every sprint is already recorded. None of it adds up to an answer when the question arrives in a hallway.
“When will it ship?”
You give a date with a silent “probably” attached. Everyone hears the date. Nobody hears the probably, and a little more trust goes each time you slip.
“What does this cost?”
Finance can price every other department to the dollar. Engineering is the line item nobody can break down, which quietly makes it the easiest one to cut.
“Why are we slow?”
You can feel the drag. You just can’t point at it. So the retro produces opinions instead of a fix, and the same queue eats next quarter too.
What we built
We built the answer. You already own the raw material.
ClickUp and GitLab record what happens. Neither one was ever going to turn that into a number you can defend upstairs — that part is ours.
What you get
The same three questions. Now with numbers attached.
These are the ones that arrive in a hallway with no warning. Here is what each looks like once the ticket, the merge request and your payroll model are read as one thing.
Your CEO asked when it ships.
June 14. 82% confidence, and you hear about it the day that changes.
Forecast from how your team actually moves, not from the date someone committed to in planning. It recalculates nightly, so a slip surfaces in week two instead of the week it was due.
Reads ClickUp sprints against GitLab merge history.
Finance asked what it cost.
$847 a story point, and which 46% of the quarter went to features.
Every ticket priced against your own payroll model. Engineering finally breaks down the way every other line on the P&L already does — by feature, by team, by quarter.
Prices ClickUp tickets with your payroll model.
You asked yourself why it feels slow.
The review queue. 6.4 days at P85, and 2.1 of them come back if you split it.
The drag stops being a feeling and becomes something you can point at in the retro. Fix it, then look at the same number next month and see whether it worked.
Times GitLab reviews against ClickUp statuses.
Where it comes from
All of it out of what you already run.
We read ClickUp and GitLab directly — read-only on both — and join each ticket to the merge request that closed it. Nobody fills in a timesheet. Nothing about the way your team works has to change. It takes about twenty minutes.
Tasks, statuses, sprints, story points, assignees and milestones — plus the years of history nobody has ever gone back and read.
Merge requests, reviews, pipelines, deploys, failures and restores — with a timestamp on every one of them.
14-day free trial · No credit card · Read-only access
Figures shown are illustrative. Running Jira or GitHub instead? and we’ll tell you the week it goes live.
Operating system
The metrics a CTO asks for after the roadmap slips.
Five questions leadership actually asks, and where each answer comes from. Every number traces back to a ticket you can open.
Put a price on the roadmap.
Scope, people, and capacity in one model, so the conversation moves off headcount and onto what each outcome actually costs.
Find the constraint before it becomes a miss.
Watch work travel from request to done and find the queue eating your calendar. It is rarely where the retro said it was.
Send a report that survives follow-up questions.
AI summaries and KPI scorecards built on the same numbers as your dashboards. No second version of the truth for the board deck.
AI Reports · DORA metrics · KPI scores · Organization health
Not sure what half of these mean? Fair. Every one is defined in plain English in the engineering metrics glossary.
How It Works
Twenty minutes from OAuth to your first real number.
You connect ClickUp and GitLab read-only. We backfill your history while you get a coffee. Nothing about the way your team works has to change.
Connect ClickUp and GitLab 2 min
One OAuth click each, read-only. We can’t change anything in your workspace or your repos, by design.
We read the history 20 min
Not just today. Patterns need past sprints before they show up.
You decide Ongoing
Dashboards, bottlenecks, reports. The decision is the one part we can’t do for you.
Pricing
Per engineer, and you can start without talking to us.
Pay for the engineers you have. Fourteen days free on Team and Business, no credit card, cancel from the settings page.
- Velocity and SP cost
- Lead time, cycle time, throughput
- Bottleneck analyzer and inventory
- Milestone tracking and risk
- Time tracking and reports
- Support and rollout help
- Everything in Team
- Cost and ROI analytics
- Task and milestone cost distribution
- AI Reports and executive summaries
- Forecasting and delivery risk
- Org health, KPI scores, SPACE
- People, capacity, and Gini index
- Everything in Business
- DORA metrics and custom KPI scores
- Custom org health and flow metrics
- Custom AI reports and cost governance
- Custom integrations and retention
- SSO, audit log, security review
- Dedicated rollout, support, and SLA
We’re onboarding our founding teams.
We’re early, and we would rather have ten teams who tell us the truth than a thousand who quietly churn. So the first cohort gets us, personally, and we ask for honest feedback in return.
- Pricing locked for 12 months. The number you sign at is the number you keep.
- A direct line to the builders. A shared channel with the founding engineers — not a support queue.
- One condition: a 30-minute feedback call each month telling us what works and what doesn’t.
Fit call 30 min
We walk through how your team ships and what leadership keeps asking you. If TheMetrics won’t answer those questions, we say so.
White-glove setup Week 1
We connect ClickUp read-only, map your teams and statuses, and configure cost and capacity with you on a call — not through a docs link.
First report, together Week 2
We review your first delivery and cost report side by side and lock in the KPIs your leadership will track from then on.
FAQ
The questions we get on the first call.
Less than most people expect. Read-only OAuth gives us metadata: tasks, statuses, story points, sprints, and on the GitLab side, pipeline and merge request events. We don’t read the contents of your source files, and we never see your ClickUp password. Revoke our access whenever you want, or ask us to delete everything we hold. The full model is on our security page.
No. It’s built to show team patterns, not to score people. Reports tell you what the work cost, never what anyone earns. You will see ownership and work concentration, because a bus factor of one is a real risk worth naming, but that’s a signal about how work is spread, not a stack rank. And with AI writing a growing share of the code, counting individual output means less every quarter.
Two minutes of yours. None of theirs. You click through read-only OAuth, we backfill your history in about 20 minutes, and nobody starts filling in a timesheet or tagging tickets differently. If your workflow is unusual, mapping your statuses is one short call with us, not a project for your team.
For now, yes, and we’d rather tell you that than sell you a maybe. ClickUp and GitLab work today. Jira and GitHub are what we’re building next. Put your name on the and you’ll hear from us the week yours goes live. Nothing in between.
Because it ignores your estimates. Forecasts are built from what your team has actually finished, not what it planned to finish. You get a P50 and a P85 date instead of one number that’s quietly a wish, and both move as each sprint closes. The more history you have, the tighter the band, and we always show you which band you’re looking at.
Yes. Fourteen days on Team or Business, no credit card, your own workspace. Not a demo sandbox full of someone else’s tickets. If it hasn’t shown you something you didn’t already know by the end of the first week, don’t buy it.
Not a multiple we invented. What you get back depends on your team size, your salary mix, and how much delivery risk is sitting in your workflow. So on the demo we take one roadmap item you already shipped and model it end to end: what it really cost, how confident a forecast would have been, and which queues ate the calendar. You walk into that conversation with your number. Not ours.
See it on your own data. Then decide.
Connect a workspace, pick one roadmap item you already shipped, and find out what it really cost. If the number isn’t useful, you’ve lost twenty minutes.
14-day free trial · No credit card · Runs on your own data