Make won't let you change the creator of a scenario once it exists. When an admin asked how to hand seven scenarios to a colleague on the Make community forum, the fix that worked was to export each blueprint and have the other person import it as a brand new scenario.
That one detail is most of the case for a full-time hire. A freelancer who builds in their own account, or under their own login in yours, leaves you with automations you run but don't really hold. Twenty scenarios in, the person who knows why the router has four branches is the only documentation you've got.
Make is named in about one in six automation posts
In the job posts we tracked between 3 May and 5 October 2026, Make was named in 15% of the 137 AI and automation engineer posts and 16% of the 98 GTM engineer posts. n8n beat it in both, at 26% and 34%. Zapier came in at 7% of the automation posts.
None of the most common titles in our data mention Make. People hire an automation engineer or a GTM engineer, and Make is one tool in the description. Make appeared in 16% of the HubSpot admin posts too, though that set is only 38 posts, so read it as a hint.
The work those automation posts describe is broader than one tool: 72% mention automation, 64% workflows, 53% AI agents or LLMs, and 47% integrations. Only 24% mention APIs or webhooks directly, but the moment Make lacks a module for something you're writing HTTP calls and parsing JSON. A hiring thread on the Make forum asks for exactly that. One poster wanted someone comfortable structuring JSON for an API request and using the HTTP module, starting hourly and "then quickly to full time".
My read is that you should hire for the second skill and treat Make as the thing they'll learn your setup in. Someone who can only drag modules around gets stuck the first time a vendor has no module.
What the freelancer actually costs
Upwork's 2026 rate guide puts advanced or expert freelancers at $60 to $120 an hour and up, and intermediate ones at $25 to $60. It doesn't list Make on its own, so I've priced at the expert band below. At intermediate rates, halve everything.
At those rates a 20 hour monthly retainer runs $1,200 to $2,400. That's cheap, and for a small setup it's the right answer. If you've got a dozen scenarios that mostly run and need a fix when a field changes, a good freelancer on a small retainer is better value than anyone full-time.
The maths turns when the hours climb. Forty hours a month at the same rates is $2,400 to $4,800. A full-time equivalent of 160 hours would be $9,600 to $19,200.
The US full-time number
The AI and automation engineer posts we tracked that printed a salary had a median midpoint of $135,000 base, with the middle half between $91,000 and $180,750. Only 25 posts listed pay, so it's directional. The analyst and specialist level was lower, at a median of $87,500, but that's from seven salaries, which is barely a sample.
Base pay is only part of it. In the BLS June 2026 compensation release, private employers paid management and professional staff $54.06 an hour in wages and $24.82 in benefits, so about 46% on top of every wage dollar. Put that on the $135,000 median and you get roughly $197,000 a year loaded, or about $16,400 a month. I used the same method in our GTM engineer cost breakdown.
| Option | Monthly cost | Hours you get |
|---|---|---|
| Freelancer, 20 hours | $1,200 to $2,400 | 20, shared with other clients |
| Freelancer, 40 hours | $2,400 to $4,800 | 40, shared with other clients |
| US hire, median automation post | about $16,400 loaded | full-time |
| Full-time global hire through Bubblegum | from $4,000 all-in | full-time, on your team |
The 40 hour freelancer and our price overlap. At that point you're comparing a quarter of someone's month with all of it.
Ownership is a setup choice, so make it on day one
Whoever you hire, the scenarios should live in your Make organization, not theirs. Make's own academy course on team roles says teams are a Teams plan feature, which Jetadmin's September 2026 pricing check lists at $29 a month billed annually. The same course describes a Team Operator as having read-only access but able to start, stop and schedule scenarios, and a Team Restricted Member as having full access except publishing.
Your builder gets Team Member or Team Admin. A freelancer you bring in for one job gets a restricted role in a separate team. Someone in ops gets Operator, so they can switch a broken scenario off at 2am without editing it.
The other half is connections. Have the hire authorize integrations with shared service accounts you control rather than their personal logins, so a departure doesn't quietly break every scenario that uses those connections.
When to keep the freelancer
My own rule is to stay freelance under about ten hours a month, or when the job is one build with an end date. Same if your team is moving to n8n. In the automation and GTM engineer posts we tracked, n8n is already named more often than Make, and hiring a full-time Make specialist into a migration is backwards.
Requests sitting in a queue for a week are the first sign you've outgrown a retainer. The invoices are the second, and they're easier to check. Pull the last quarter's tonight. If the monthly average is close to $4,000, you're already paying for a full-time person and getting a part-time one, and our automation engineer role page covers what full-time looks like.