Hey there,
Matteo here from Kinetyca.
The GTM engineer job posts I keep reading have no quota on them. Base plus equity, engineering-style comp, median base around $127,500 in the US. The market has already decided this seat does not carry a number.
Then the same company hires the person and hands them a scorecard built for a number. Dials, emails sent, meetings booked. Six months later they conclude the role did not work.
The role was not the problem. The measurement was.
The scorecard you inherited was built for a different seat
An SDR scorecard measures dials, emails sent and meetings set against a quota. It sits on a comp plan built for exactly that: in the US, median base $60K, OTE $85K, and around 54% average quota attainment.
That is a good scorecard. It measures effort against a number, for a seat that is paid to put effort against a number.
A GTM engineer is not paid that way, and that difference is the whole point. Hand them those same rows and you will fire a good one.
What the seat actually does
A GTM engineer builds net-new automated systems. RevOps runs the CRM processes that already exist. One is a build function, the other is a run function, and you do not measure a build function on this month's activity.
A GTM engineer can go a month without making a single call and still be the most valuable seat on your revenue team. Every activity row reads zero while the output rows fill up.
The three numbers that belong there instead
1: Cost per meeting. Total system spend divided by the qualified meetings the system booked in the period.
- Spend is every recurring line the system consumes plus the engineer's time: Clay and Prospeo credits, Smartlead and HeyReach seats, and the loaded cost of their hours.
- Count only the meetings the system sourced and booked. Run it monthly on one definition and read the trend, not a single month.
2: Hours removed. The recurring hours your team no longer spends because a system does the work.
👉 Write down the weekly hours each manual job took before, times the people doing it. That baseline, minus the hours a human still touches, is the number.
3: Systems live. The automated loops running without a human touch, and how many shipped this quarter.
- A loop is live when a trigger fires it, it runs on its own, and it handles its own failures. One somebody starts every Monday morning is not live.
- Track total live and shipped this quarter separately. Total is the surface area they maintain, shipped is the build rate. Claude orchestrates, n8n runs the individual loops.
I am deliberately not giving you targets for any of these. Your first 30 days of measuring sets your own baseline, and a benchmark borrowed from someone else's stack is worse than no benchmark at all.
Where the hours actually come from
If hours removed still feels abstract, name the jobs. These are the ones we watch:
- List build and verification
- Reply routing
- Deliverability monitoring
- Lead replenishment
- The weekly report
The part that costs you the hire
A scorecard does not only measure the engineer, it tells them what to optimise.
Put meetings booked at the top and the fastest route to that number is doing the work by hand: sourcing the list yourself, writing the sequence yourself, sending it yourself. That hits this month's number and builds nothing. The system quietly stops getting built, and the person you hired to build it is now doing manual pipeline work on an engineering base.
Three questions for their next review
- What did cost per meeting do over the last three months, and what moved it?
- Which recurring jobs did the team stop doing, and where did those hours go?
- How many loops are live, how many shipped this quarter, and which one broke?
If you cannot answer those from what you track today, the scorecard is the thing to fix first.
So pull up your GTM engineer's scorecard. How many of those rows measure activity, and how many measure what the system produced? I would genuinely like to know what the split looks like on yours. Hit reply and tell me.
PS. If you want help building the system those numbers measure, you can book a call with us here
Lawyer by training, then operations at Amazon. Runs delivery: process, documentation and the detail corporates expect.
LinkedIn ↗YouTube ↗