You just won a new client. Now you’re staring at a blank document, trying to turn a messy email thread and a few call notes into a proper scope of work. Again. Every project starts the same way: the same questions, the same copy-paste, the same hour you never get back. The good part is you can hand that whole job to an automation and still send something that looks like you wrote it by hand.
Quick answer: To automate a scope of work, connect a client intake form to Make.com, pass the answers to Claude AI with a prompt that turns them into a structured scope, then auto-generate a Google Doc and email it to the client. Once it’s built, every new enquiry produces a ready-to-review scope in minutes instead of hours.

What is a scope of work, and why does it matter?
A scope of work, or SOW, is the document that spells out what you’re going to deliver, what you’re not, how long it’ll take, and what it costs. It’s the line in the sand that protects both you and the client when someone asks for “just one more thing” three weeks in.
A scope of work usually covers the deliverables, the timeline and milestones, the price and payment terms, and any assumptions or exclusions. Tools like Asana have a useful breakdown of how a scope of work differs from a statement of work if you want the textbook version. For most NZ service businesses, though, it’s simpler than that: it’s the thing you send before you start so nobody’s surprised later.
The catch is that a good scope of work is specific. It pulls real details from the client, which is exactly why it’s so slow to write from scratch every single time.
Why does writing a scope of work by hand cost you so much time?
Because you’re not really writing. You’re chasing. You ask the client what they need, wait two days for a vague reply, ask three follow-up questions, then translate all of it into something structured and professional. By the time you hit send, you’ve spent the better part of a morning on admin instead of paid work.
You’re not alone in that. Almost half of freelancers spend around six hours a week on non-billable admin like proposals and paperwork, according to Clockify’s 2025 data. Six hours a week is the better part of a working day, gone, every week, on tasks a client never sees and never pays for directly.
An automated scope of work doesn’t make the document less important. It just takes the typing, formatting, and chasing off your plate so you can spend that time on work that actually earns.

How do you automate a scope of work from a client intake form?
The whole system rests on one idea: if you ask the right questions up front in a structured form, an AI can turn those answers into a scope of work without you touching it. Here’s how the flow comes together.
- Build a proper intake form. Use a tool like Tally, Typeform, or even a Google Form. Ask for the project type, the outcome the client wants, their budget range, deadlines, and anything they specifically don’t want included. The better the questions, the better the scope.
- Send the answers to Make.com. Connect the form to Make.com with a webhook or the built-in app. Every time someone submits, their answers land in your scenario as clean, labelled data.
- Hand the data to Claude AI. Add a Claude (or OpenAI) module and write a prompt that says: “Turn these intake answers into a professional scope of work with deliverables, timeline, exclusions, and pricing notes.” Feed in the form fields and let it draft.
- Drop the draft into a template. Push Claude’s output into a Google Doc or PDF template that already has your logo, terms, and branding. The structure stays consistent, only the project details change.
- Add a review step before anything sends. Route the draft to you in Slack or email first. You read it, tweak the pricing if needed, then approve. Nothing reaches the client without a human glance.
- Email it to the client automatically. Once approved, Make.com emails the finished scope of work straight to the client and logs the project in your sheet or CRM. Done.
Set it up once, properly, and every new enquiry runs through the same path. A client fills in your form on a Tuesday night, and by the time you’ve had your coffee on Wednesday there’s a polished draft waiting for your approval.
A quick example of the flow in action
Say you run a small web design studio in Hamilton. A lead lands on your site and fills in your intake form: they want a five-page site, a booking system, copy help, live in six weeks, budget around $4,000 NZD, and they specifically don’t want e-commerce yet.
Make.com catches that submission and passes it to Claude with your standard prompt. Thirty seconds later you’ve got a draft scope of work that lists the five pages, breaks the build into three milestones, flags that e-commerce is out of scope, and notes the $4,000 budget with a 50% deposit. It drops into your branded template and pings you in Slack. You read it, bump one line, hit approve, and it’s in the client’s inbox before they’ve finished their morning coffee. No blank document, no chasing, no lost morning.
What tools do you actually need?
Fewer than you’d think, and the monthly cost is small. You need three pieces: a form, an automation engine, and an AI writer.
The automation engine doing the heavy lifting is Make.com. If you’ve never used it, start with our guide on what Make.com is and why everyone’s talking about it, which covers what it costs in NZD and what it can connect. Make.com is where your form, your AI, and your email all meet.
The AI writer is Claude (or ChatGPT, if that’s what you already pay for). It’s the part that reads the raw intake answers and writes them up like a human would. This is the same engine plenty of NZ businesses already use for client work, the same way they automate their entire client onboarding in Make.com from welcome email through to contract.
The form can be anything that sends structured data, so a free Google Form is fine to start. You can always upgrade to Tally or Typeform later when you want conditional questions or a slicker look.
Where I’d be careful with this
Here’s the honest bit. AI is brilliant at structure and terrible at knowing your real prices. If you let a scope of work go straight from the AI to the client with no human in the loop, you will eventually send out a number that’s wrong, or commit to a deliverable you didn’t mean to. That’s not an AI problem, it’s a process problem.
So always keep that approval step. A simple checkpoint where the draft pauses for you to approve or reject is the difference between a system you trust and one that scares you. We’ve written before about why every agency needs a Slack approval gate, and a scope of work is exactly the kind of thing it’s built for.
The other thing: spend your time on the intake questions, not the output prompt. A vague form gives you a vague scope no matter how clever your AI prompt is. Get the questions right and the rest mostly takes care of itself.
Frequently asked questions
How long does it take to set up an automated scope of work?
If you’ve used Make.com before, you can build a basic version in an afternoon. If you’re starting cold, budget a weekend to learn the tools and get your form, prompt, and template right. After that, it runs on its own.
What does it cost to run in NZ?
Most setups run on under $50 NZD a month. Make.com has a free tier to start, Google Forms is free, and an AI plan like Claude or ChatGPT is around $30 NZD a month. The cost barely moves whether you send two scopes a month or twenty.
Will the scope of work sound generic or robotic?
Not if your template and prompt carry your voice. You’re giving the AI real client details and a clear structure, so the output reads specific. Your review step is also where you add the human touches that make it sound like you.
Do I need to know how to code?
No. Make.com is a no-code tool, so you’re connecting boxes and writing plain-English prompts, not programming. If you can build a spreadsheet, you can build this.
Is it safe to send client information through these tools?
Make.com, Google, and the major AI providers all use encrypted, business-grade infrastructure. Use strong passwords, turn on two-factor authentication, and only collect the client details you genuinely need for the scope.
Can I use this for quotes and proposals too?
Yes. The same intake-to-AI-to-document flow works for quotes, proposals, and onboarding packs. Once you’ve built it for a scope of work, reusing the pattern for other documents is quick.
Ready to put your scope of work on autopilot?
You didn’t start your business to spend mornings reformatting documents. If you’d rather have a system that turns every new enquiry into a ready-to-send scope of work while you stay focused on the actual work, we can build it with you.
See how Overcomers AI can automate your scope of work and client admin here.

Leave a Reply