You hit a wall. Clients are coming in, proposals are going out, and you are the one building every workflow, writing every prompt, and troubleshooting every broken Zap at 11pm on a Tuesday. You are the bottleneck.
Every agency owner who has scaled past $20K/month has solved this exact problem the same way: they stopped doing every build themselves. They hired subcontractors, built a repeatable training process, and created quality checkpoints that made the client experience consistent regardless of who did the actual work.
This post walks you through that entire system. Where to find good subcontractors, how to vet them fast, what to train them on, how to structure the payment and project flow, and how to make sure a client never knows they are working with anyone other than you.
Why Subcontractors (Not Full-Time Hires) at This Stage
Before you post a job on LinkedIn, understand the math. A full-time developer in the US costs you $80,000 to $120,000 per year in salary alone, plus benefits, taxes, and management overhead. A skilled automation builder in the Philippines, Eastern Europe, or Latin America, working on a per-project basis, costs you $15 to $40 per hour with zero overhead when there is no work.
At $20K/month in revenue, you do not have enough stable work volume to justify a full-time hire. You have spiky demand: three new clients in February, one in March, five in April. Subcontractors absorb that variance. You pay for output, not seat time.
The model works like this:
- You sell the engagement and set the price (usually $3,000 to $15,000 per project, or $1,500 to $5,000/month retainer)
- You handle discovery, strategy, and client communication
- Your subcontractor builds the automation under your direction
- You review, QA, and deliver
- You keep 40 to 60 percent of the project fee as your margin
A $5,000 project where you pay a sub $2,000 to build it and spend 4 hours on discovery and delivery is $3,000 profit for roughly half a day of your time. That is the business you are building toward.
Where to Actually Find Builders Who Know What They Are Doing
Generic freelance platforms give you volume but not quality. Most people listing themselves as "Make.com experts" on Fiverr have built three automations and watched two YouTube tutorials. You need to filter harder than that.
The platforms worth your time:
- Upwork is still the best for finding vetted automation builders, specifically if you filter for $30+/hour, 90%+ job success scores, and look at the actual portfolio work they describe in proposals. Search "Make.com automation," "n8n workflow," or "Zapier automation" and look for people who describe building multi-step workflows with conditional logic, webhooks, and API connections, not just basic two-step Zaps.
- Pallet and Contra are newer platforms where a lot of serious freelance developers have moved because they hate Upwork fees. Quality tends to be higher.
- AI/automation-specific communities are often where the best builders live. The n8n community Discord, the Make.com Facebook group, the Zapier community forum, and subreddits like r/nocode and r/automation have active builders who pick up freelance work. Post what you are looking for there directly.
- NURO University's own community is worth checking, because you will find builders who have gone through the same training framework you have, which makes onboarding dramatically easier.
- LinkedIn outreach to people with "automation specialist" or "workflow automation" in their headline, specifically those who list Make, n8n, or Zapier as skills, and who have posted about builds they have done. People who share their work publicly are almost always better than those who do not.
The Vetting Process: Three Steps Before You Trust Anyone With a Client Build
Hiring the wrong subcontractor costs you a client. Here is the vetting sequence that filters out the pretenders fast.
Step 1: The Async Video Screen
Before any call, send them a Loom explaining a simple automation scenario and ask them to record a 5-10 minute Loom walking you through how they would build it. The scenario should be something like: "A new lead fills out a Typeform, we need to add them to Airtable, send a personalized email via Gmail, notify our Slack channel, and if the lead came from a specific referral source, also add them to a separate list."
What you are looking for is not perfection. You are watching for how they think. Do they ask clarifying questions in the video? Do they mention edge cases like what happens if the email field is blank? Do they know the tools or are they guessing? A great builder will catch two or three things you did not even mention.
Step 2: A Paid Test Project
Never ask for free work, but always pay for a small test build before handing over a real client project. Pay $100 to $200 for a one-to-two hour build that mirrors something you actually need. Give them a Make.com or n8n scenario, a dataset in Airtable or Google Sheets to work with, and a deadline of 48 hours.
You are evaluating three things: does it actually work, did they communicate if they hit a snag, and did they deliver on time. Two of those three failures and you move on.
Step 3: A Direct Reference from Another Agency Owner
If you can get a referral from another agency owner who has used this person, weight that more heavily than anything else. A warm referral from someone who has paid them for real work beats any portfolio or test project. This is another reason why being active in automation communities pays off: you build the network that lets you give and receive these referrals.
What to Train Them On Before They Touch a Client Project
Even good builders need to be trained on your specific standards. Your clients hired you because of how you work, not just what you build. The training should cover three areas.
Your tech stack and naming conventions
You probably have a preferred set of tools. Maybe you always use Make.com as the automation layer, Airtable as the database, and Claude via API for AI logic. Document this and make it non-negotiable. Subcontractors should not choose their own tools on client projects. Consistency means you can troubleshoot any build without needing to relearn a new tool every time.
Naming conventions matter more than most people think. Every scenario in Make should be named "ClientName - Function - Version" (for example "DentalEdge - Lead Nurture - v2"). Every Airtable base should follow your template structure. Every webhook URL should be logged in a shared Notion doc. When you have six clients and three subcontractors, chaos is one badly named field away.
Your communication standards with clients
Subcontractors do not talk to clients. Full stop. You are the account manager, strategist, and point of contact. The subcontractor builds in the background. If a client ever reaches out asking why their automation broke, you handle it, even if you then relay the message to your sub to fix it. This protects your reputation and keeps the relationship clean.
Train your subs to communicate with you via a shared Slack channel or ClickUp project, to update task status daily during active builds, and to flag blockers within two hours rather than going quiet for a day.
Your QA checklist before anything goes live
Before any automation goes to a client, it should pass through a QA checklist. Build this in Notion or Airtable and make your subs complete it as part of every handoff. A solid checklist includes:
- Every trigger has been tested with real or realistic dummy data
- Error handling paths are in place (what happens when a step fails)
- The scenario/workflow is named correctly and documented
- All API keys and credentials belong to the client's accounts, not yours or the sub's
- A screen recording walkthrough has been created explaining how the automation works
- The build has been stress-tested with at least 10 test runs
- Any connected tools (Airtable, Google Sheets, CRMs) are organized and labeled
This checklist is not optional. If a sub skips it, they do not get paid until it is done.
How to Structure Payment and Project Flow
The payment structure signals professionalism and protects your margin. Here is the framework that works.
When a client signs, you collect a deposit (usually 50 percent upfront). Once the project is scoped, you hire your sub and pay them 30 to 40 percent of the total project fee in two installments: half when they start, half when they deliver a QA-passing build.
Never pay a subcontractor more than you have collected from the client. Always have a signed subcontractor agreement that covers intellectual property (all builds belong to you and the client, not the sub), confidentiality (they cannot poach your clients or share client details), and deliverables (specific outputs with deadlines, not vague "build automations" language).
Use a tool like Bonsai, Deel, or even a simple DocuSign template for the agreement. For international subs, Deel makes payments and compliance much simpler. For US-based subs, a basic contractor agreement plus ACH or PayPal works fine.
Project flow in practice:
- You close the client and collect 50 percent deposit
- You create a project brief using your intake notes and scoping call recording
- You assign the project to your sub with a clear deadline and the QA checklist
- Sub builds, communicates blockers to you in Slack
- Sub submits completed build with a QA checklist and a Loom walkthrough
- You review, test yourself, and either approve or send back with revision notes
- You deliver to the client, collect the remaining 50 percent
- You pay your sub the second half of their fee
This flow keeps you in control without requiring you to build anything.
Protecting Client Relationships When Using Subs
The number one fear agency owners have about subcontracting is that the client will find out and feel deceived. Here is the reality: almost no client cares who builds their automation as long as it works and their account manager (you) is responsive and accountable.
That said, you can protect the relationship in a few practical ways.
All client-facing accounts, logins, and credentials should be set up under your agency's name or the client's own name, never the subcontractor's personal accounts. If a client logs into their Make.com account or Airtable base, they should see a clean, organized setup, not a bunch of folders labeled with a random person's initials.
All communication with the client happens through you or your agency's email. Never CC your sub on client emails. If a client asks directly who built something, you can say your team or your technical team without naming individuals. This is standard practice in agencies of all sizes.
The walkthrough videos your sub records as part of QA? You re-record them in your own voice before sending to the client. This takes 20 minutes and makes the delivery feel premium and personal. Clients love seeing their account manager explain how the system works, not a stranger.
Scaling From One Sub to a Small Team
Once you have one reliable subcontractor and a working process, scaling to two or three is straightforward. The variables that usually break a sub relationship are unclear expectations, payment disputes, and inconsistent work volume. Your documented process and project brief templates eliminate the first two. Growing your sales pipeline eliminates the third.
At three active subcontractors, you should also be thinking about a project manager, someone (often a part-time VA at $8 to $15/hour) who tracks deadlines, chases QA checklists, and keeps you updated without you needing to check in on every project daily. This frees you to focus almost entirely on sales and strategy.
The end state you are building toward looks like this: you spend 60 to 70 percent of your time on business development and client strategy, 20 percent on QA and delivery, and 10 percent on team management. Your subcontractors handle 100 percent of the actual building. At that point, you are running an agency, not a freelance practice.
Common Mistakes to Avoid
- Skipping the paid test project because someone seems good in a call. Calls are cheap. Real work is not. Always test before trusting.
- Paying the full subcontractor fee upfront. Hold the second half until the QA checklist is complete and you have approved the build.
- Using the same subcontractor for every vertical. Some builders are great at CRM automations and weak on AI prompt logic. Build a small roster with complementary strengths.
- Not documenting anything. If your best sub disappears tomorrow, can you onboard a replacement in a week? If the answer is no, you have not built a business, you have built a dependency.
- Letting subs communicate directly with clients. Even once. This sets a precedent that is very hard to walk back.
Join NURO University
Building an AI automation agency is not just about knowing Make or n8n. It is about building a system that runs without you being the only person doing the work. That is what we teach at NURO University.
Inside, you get step-by-step courses on selling, scoping, building, and delivering AI automation services, plus community access to other agency owners who are in the same trenches and are often the best source of subcontractor referrals you will ever find.
If you are serious about turning AI automation into a real business, not just a side project, this is where you start.
Join NURO University and start building your agency the right way.