The short answer
Hire a GTM engineer when your motion repeats and needs someone running it daily, go fractional when you need a senior builder to design the system without a full-time role, and use an agency when you need several skills at once and a faster start. If you cannot yet say who buys, start there instead.
Key points
- A full-time hire is the most expensive route and the slowest to pay back, since the median advertised salary in 1,000 GTM engineer job postings1 was $127,500 and wages make up only about 70 percent of what a US private employer spends on a worker, according to the Bureau of Labor Statistics2.
- The role asks for a rare mix of data, automation, CRM and messaging skills, which is why one person seldom covers all of it well and why the second hire is often the one that makes the first one productive.
- Fractional help buys senior judgment at a fraction of the cost, but it runs on borrowed hours, so it suits design and setup better than daily operation.
- An agency brings a team and a running start, and the risk it carries is knowledge leaving with it, which a deliberate handover plan removes.
- Sometimes the honest answer is none of the three yet, because a system built before you know who buys only automates the guessing.
What does each option give you?
A full-time hire gives you one person who owns the system every day, a fractional GTM engineer gives you senior design for a few days a month, and an agency gives you a whole team from the first month. They are often compared on price alone, which misses the point, because each one buys a different thing and fails in a different way.
| Option | What you get | Works best when | The usual failure |
|---|---|---|---|
| Full-time hire | One person who owns the system every day and learns your business deeply | The motion repeats, volume is growing and someone senior can manage the role | A lone hire without a clear owner or the data they need, who ends up maintaining tools |
| Fractional GTM engineer | A senior builder for a set number of days a month | You need the architecture designed and your team can run it afterwards | Hours run out before the system is stable, and nobody inside can extend it |
| Agency | A team covering data, automation, content and outreach from the first month | You need several skills at once, or results sooner than a hire can ramp | The knowledge lives with the agency and nothing is written down |
None of these is the grown-up version of the others. Plenty of companies move from an agency to a hire once the system has settled, and plenty move the other way when a single hire turns out to be carrying five jobs.
When does hiring a full-time GTM engineer make sense?
A full-time hire makes sense when you can already describe who buys from you and why, when the manual work around that motion is capping how much of it you can run, and when there is a senior person who will own the role and give it priorities. Those three conditions matter more than the budget, because a GTM engineer without them tends to become the person who fixes the CRM and connects tools, which is useful but far below what the salary is paying for.
The cost is substantial, since the median advertised salary in Bloomberry’s analysis of 1,000 postings was $127,500 and the best-funded companies were paying well above $200,000. Salary is also not the whole bill, because the Bureau of Labor Statistics found that wages and salaries were 70 percent of what private employers spent on compensation in June 2026, with benefits making up the remaining 30 percent. On our own arithmetic, that puts a median US hire at roughly $182,000 a year before recruiting fees, tools and data subscriptions.
Skills are the other constraint, given that SQL and Python each appeared in 38 percent of the postings Bloomberry analysed, HubSpot in 52 percent, Salesforce in 45 percent and Zapier in 39 percent, and on top of the technical work the role usually involves writing the first version of the message a salesperson will send. Few people are strong at all of it, so the question to ask before hiring is which half of the job matters most to you now, and what you will do about the other half.
The planner below helps with that question. Mark what you expect the role to deliver in its first year, and it shows which skills to weight, what to ask in interviews and whether one person can realistically cover it.
Mark what you expect the role to deliver in its first year. The profile on the right updates as you go.
The profile you need
Mark at least one outcome
Skills to prioritise
Ask in the interview
How to fill it
When is a fractional GTM engineer the better call?
A fractional GTM engineer is the better call when your problem is design rather than capacity, meaning you need someone experienced to decide which signals matter, how the data should flow and what the CRM should hold, but you do not yet have a full week of work for them once it is built. A few days a month of senior judgment will often get further than a full-time junior hire, because the expensive mistakes in this work are architectural and happen early.
Its limit is time, because fractional help works on borrowed hours and so tends to struggle with daily operation, with the steady tuning that a signal-based system needs, and with anything that breaks on a day the person is not working for you. It works best with a clear handover in mind, where the fractional builder designs and documents the system and someone inside the company, even part time, learns to run it.
When should you use an agency instead?
An agency makes sense when you need several skills at once, such as data work, automation, content and outreach, and you need them working together from the first month rather than hired one at a time over a year. It also makes sense when speed matters more than ownership, since a team that has built similar systems before can usually reach a working first version sooner than a new hire can finish learning your market.
The main risk is dependence, since if the agency holds all the knowledge, the logins and the logic, then ending the relationship means starting again, so the arrangement is only as good as the handover it allows. Before signing with anyone, including us, it is worth asking three things: who owns the accounts, data and workflows that get built, how the system is documented, and what a handover to an in-house person would look like if you hired one next year. A good agency will have ready answers, and the ones that hesitate are telling you something.
When is the honest answer none of the three yet?
The honest answer is none of the three when you cannot yet say which customers buy from you and why. A GTM system multiplies whatever it is pointed at, so pointing it at a guess produces more of the guess at greater speed, which is the same pattern we described in why AI outbound fails.
There are a few signs you are in this position. Most of your customers still come through the founder’s own network, the last ten deals do not share an obvious pattern, and nobody owns the CRM, so its records only hold what someone remembered to type in. In that situation the better first step is a few weeks of looking closely at the deals you have won and lost, which a founder can often do alone, and the system can follow once the pattern is clear. Our longer piece on what GTM engineering is covers how to tell when a company is ready for it.
How do you decide which one is right for you?
Decide by asking whether you know who buys, whether the work is design or daily operation, how many skills you need at once, who will own the system and how soon you need results. Those five questions usually point one way quite clearly.
- Can you describe who buys from you and why? If not, start with that, and hold off on all three options.
- Is the work design, operation or both? Design suits fractional help, daily operation suits a hire, and both at once suits an agency or a hire supported by one.
- How many different skills does the next six months need? One or two can be hired, whereas four or five at once is usually faster to buy as a team.
- Who will own the system inside the company? A hire needs a manager who owns pipeline, and fractional or agency help needs someone to hand over to eventually.
- How soon do you need results? A hire takes time to recruit and then time to learn your market, while an agency or an experienced fractional builder starts from a working pattern.
Illustration
Three invented companies, to show how the questions play out.
- A seed-stage software company, founder still closing every deal, no CRM discipline. Its customers come through the founder’s network and do not yet share a pattern. Next best action: none of the three for now, and a month spent studying won and lost deals before any system is built.
- An IT services firm with a proven offer, a small sales team and a messy CRM. The motion repeats, but nobody has time to build signals, data and outreach together. Next best action: an agency for the first six months with a written handover plan, then a full-time hire to run what was built.
- A software company with a RevOps lead and clean data, whose reps spend hours on research. The foundations exist, and what is missing is a better design for signals and routing. Next best action: a fractional GTM engineer for a quarter to design the system, with the RevOps lead taking over its daily running.
Sources
Figures last checked on 22 September 2026. We revisit them every quarter, because pay and hiring data move quickly.
- 1 Bloomberry, “I analyzed 1,000 GTM engineering jobs”. Median advertised salary, top-paying companies, and the share of postings asking for SQL, Python and specific tools.
- 2 U.S. Bureau of Labor Statistics, “Employer Costs for Employee Compensation, June 2026”. Wages at 70 percent and benefits at 30 percent of private employers’ compensation costs.