Hiring a Make.com consultant or Zapier expert: what to ask before you sign

Four jobs look similar from the outside and need different people. A build is new automation from a clear brief. A repair is fixing something that already broke. An audit is reading everything you run and saying what to keep, fix or retire. A migration is moving work between platforms, which for Zapier is usually a rebuild, because Zap exports (JSON, on Team and Enterprise plans) are for importing into Zapier again, not into another platform, and for Make is easier if the blueprints have been kept, since Make exports and imports scenarios as JSON blueprints.

Say which one you want. A consultant who answers every brief with a new build, including the repair, is selling the job they prefer. Our position is that an audit comes first when you have more than a handful of automations, since most accounts have a few that do most of the work and a few that fail quietly. Where this breaks: if you have one broken Zap and one owner, skip the audit and fix it.

1. 01The outcome, in one sentence: when a deal is won in the CRM, an invoice draft exists in the accounting tool.
2. 02One real example record, start to finish, including a messy one.
3. 03The systems involved and who administers each, since access is the usual delay.
4. 04Volume: how many a day or a month, and how bursty.
5. 05What must never happen: duplicate invoices, emails to the wrong person, deleted data.
6. 06Who is told when it fails, and who fixes it afterwards.

If you cannot write the volume, say so. A consultant should ask, because on Zapier cost scales with tasks and on Make with credits per module run, and the same flow can be cheap or expensive depending on how it is built. Our automation cost and Make.com credits articles explain how to count them.

References help, but a reference for a Zap that ran for a week says little. Ask how long an automation has been live and whether the same person fixed it when it broke. If you hire through a marketplace, the reviews and job history are public, which is a better starting point than a portfolio of screenshots. Certifications show someone studied the tool; they do not show how the person handles your data. Treat them as one signal.

Fixed price works when the brief names the systems, the trigger, the output and what counts as done. The risk shifts to the consultant, so expect a careful scope and a refusal to include things you did not mention. Hourly works for discovery, audits and repair, where nobody knows the size of the job until they have looked. Insist on an estimate in hours and a check-in at a set point, so hourly does not mean open-ended.

Skofi's authorised rates, in US dollars: Make, Zapier and CRM work (monday.com, HubSpot, Airtable and similar) at $25 an hour, estimated in hours before we start. Custom systems start from $2,000, most projects come in at $2,000 to $5,000, and bigger builds with several features or an app are around $5,000 to $10,000. These are typical ranges, not quotes; we quote after a discovery conversation. The platform subscription is separate and paid to Make or Zapier. Compare any rate with the hours it implies, not just the number.

A HubSpot integration consultant is not the same as someone who knows Make or Zapier. The hard part is deciding what HubSpot owns and what the systems around it own, which direction each field syncs, and how duplicates are avoided. Tools are secondary. HubSpot's own workflows are the right place for logic inside the CRM; anything crossing into billing, delivery or another system belongs on a platform with proper error handling, or in code against HubSpot's API with a scoped private app.

• Ask which object and property each system owns, and whether any field syncs both ways. Two-way sync on one field is how systems drift apart.
• Ask how contacts are matched so an integration does not create a second record for the same email.
• Ask which HubSpot tier your plan needs for what they propose, since some features depend on it. HubSpot's current plan pages are the source for that.
• Ask who creates the private app token and where it is stored.

Our HubSpot platform page covers how we approach that boundary. We bill HubSpot work at the same hourly rate as other CRM work, as above.

• Everything built under the consultant's own login and connections, with no plan to transfer them.
• A promise that the automation will never fail. Everything fails; the question is who finds out.
• No handover, no names on the scenarios, no notes.
• A fixed price offered before anyone asked about volume or edge cases.
• Pushing a platform you have not discussed. The best tool depends on your logic and volume, as our Make vs Zapier vs n8n comparison sets out.

When not to hire: if the automation is simple, linear and low risk and someone in your team can maintain it, build it yourself. A consultant is worth the cost when the failure would be expensive, the logic branches, or nobody on your side wants to own it. Our comparison of agency, freelancer and in-house covers that choice.