BROTHERS_AUTOMATE / CASE_STUDY · PAVING COMPANY ● LIVE BUILD · DEPLOYED
CASE STUDY · CLIENT ONBOARDING AUTOMATION
Onboard a client. Without sending a single email.
Contract signs, questionnaire goes out, accounts get provisioned, kickoff lands on the calendar. Same experience every new client. You don't lift a finger. Built for a paving company — works for any service business.
CLIENT
Paving Company
INDUSTRY
Service / Trades
TIMELINE
2–3 weeks to production
TECH STACK
Make.com · HubSpot · DocuSign · Google Workspace
0
Manual steps
100%
Consistency
10
Steps automated
12 hrs
Saved per client
01 THE PROBLEM
Every new client means the same manual onboarding.
New project comes in. You pull the client info. Send the welcome email. Schedule the walkthrough. Prep the docs. Set up the accounts. Same exact steps every time — different client, different address, different details. All done by hand. Steps get missed when things get busy. Clients notice.
✗Every new client triggers the same 10-step onboarding sequence
✗Client details get copied and pasted between systems manually
✗Steps get missed when you get busy and clients feel it
✗Welcome email tone varies depending on who sent it
✗Account provisioning takes a day longer than it should
✗You know it could run itself — nobody's built it yet
02 THE AI SOLUTION
Your onboarding flow, fully automated end to end.
We build a system that pulls new client info from your database the moment a contract is signed, then runs the entire onboarding sequence automatically. Welcome email goes out, intake questionnaire fires off, account is provisioned, kickoff meeting lands on your calendar — same flow every time, every client. Built around your exact process, not a SaaS template.
PIPELINE · 6 STEPS · ONBOARD_A_CLIENT_● LIVE
01
CONTRACT SIGNED
DocuSign webhook fires. The system pulls signed contract details into the onboarding queue.
02
INTAKE
Welcome email + branded intake questionnaire goes out within 5 minutes of signature.
03
PROVISION
Client gets logins, project workspace, and shared folders auto-created and shared.
04
SCHEDULE
Kickoff meeting lands on your calendar with prep notes pre-filled from intake answers.
05
BRIEF
Project brief auto-generated from the intake form and dropped in your team channel.
06
KICKOFF
You walk into the meeting prepared. The client feels like a $50K account. Same every time.
F.01
Database-driven
Pulls client name, address, project details, and preferences automatically. No copy-paste between systems.
F.02
Automated comms
Welcome emails, scheduling confirmations, and follow-ups fire on time, every time. Tone stays on-brand because the templates do.
F.03
Document prep
Contracts, checklists, and project docs get generated with the right details filled in. Branded PDFs land in the client folder before the kickoff call.
F.04
Custom to your flow
Built around the exact steps your business already runs. We don't make you change your process — we automate the one you already have.
03 THE TRANSFORMATION
Before vs after.
METRIC
BEFORE
→
AFTER
Time per onboarding
12+ hours of manual work
→
0 hours — runs itself
Steps that get missed
A few when things get busy
→
Zero — every step fires
Client experience
Varies depending on who handled it
→
Identical white-glove every time
Time to provisioned account
1–2 days
→
5 minutes after signature
Owner involvement
Pulled into every onboarding
→
Owner sees it on the calendar
RESULTS · ONBOARD_A_CLIENT_● VERIFIED
04 THE RESULTS
Built for a paving company. Works for any service business.
0
Manual steps
Fully automated flow
100%
Consistency
Every client, same experience
12 hrs
Saved per client
That you can put back into delivery
05 NEXT STEP
Want this for your service business?
We map your current onboarding flow on the discovery call, scope it, then build it on your accounts. Most teams ship in 2–3 weeks. 30-day guarantee.
10 key insights, core concepts, real workflow examples, and the right tools for automating your service business. Written for operators, not engineers.
What to automate first (and what not to)
How lead funnels actually work under the hood
The exact tool stack we use for clients
Mindset shifts that save you from overbuilding
No spam. We send useful stuff only.
Field Guide
AI Automation for Business Operators
The technology to build a digital assembly line for your business already exists. This guide explains what it is, how it works, and what you actually need to know to use it.
The core idea: Define your inputs and outputs clearly. Let the machine handle everything in between. You don't need to understand every technical detail -- you need to understand your own operations.
What Business Owners Need to Know
Tap each to expand
The real value isn't saving clicks. It's offloading the mental load of evaluating options, routing information, and following up consistently. Every time you manually run a process, your brain loads every possible path before choosing one. That energy compounds into exhaustion. Automation does the evaluation for you -- because you already did the thinking when you built the system.
Automation doesn't fix a broken or undefined workflow. If you can't explain the steps manually, a system can't run them for you. Start by mapping what you already do. If you can walk through it step by step, with clear branches and decisions, it can be built and offloaded.
You don't need to understand what happens in between -- that's the machine's job. But you need to be specific: What data enters the system? What result do you want on the other end? Don't ask for 30 reports you won't read. AI can process everything; the constraint is knowing what you actually need.
A weekly email summarizing new leads in your CRM. A form submission that automatically adds a contact and sends a personalized follow-up. These aren't flashy, but they run every day without you. Small systems compound into large amounts of reclaimed time and mental energy over a year.
You can collect a few answers from a prospect, have AI research them, and automatically send a response tailored to their specific situation. What used to require a dedicated person can now run on its own. The result feels personal to the recipient -- because it is, based on what they told you.
If you're an expert in your field, you can turn that knowledge into an automated funnel. Prospects answer a few questions, AI matches their answers to your best content or recommendations, and you capture their information in the process. You're using AI to automate the selection -- not replace your expertise.
If something always happens the same way, use a workflow. If it requires interpreting context or choosing between options -- like triaging a new lead or responding to a varied inquiry -- that's where an AI agent adds value. Knowing which tool fits which task saves you from building the wrong thing.
CRMs, email platforms, forms, databases, research tools, image generators -- almost anything can be connected to anything else today. The tools exist. The hard part is knowing what you want connected, why, and being specific enough about it that a system can be built to do it reliably.
Build the system, find the gaps, fix them. The goal is a machine that runs cleanly -- not a perfect machine on day one. Every iteration makes it more reliable. Error handling is part of the build, not a sign that something went wrong. Expect to refine it.
Even when a task only takes one path, your brain loads every possible option before ruling them out. A 100-branch process might only ever use one branch -- but you consider 50 before choosing. Multiply that cognitive load across a full work day and it's significant. Automation doesn't just save time. It preserves focus for things that actually need your judgment.
Core Concepts
The building blocks, in plain language
Data Layer
API
A precise, predefined connection between two software systems. You specify exactly what call you're making -- get this data, post this record. Because they're explicit, they're reliable and predictable.
Think of it as: a specific form you fill out to make a specific request. Same form every time, same result every time.
Intelligence Layer
MCP
Model Context Protocol -- what AI agents use to interact with connected tools natively. Instead of one specific call, it opens a range of possible actions. The agent decides which action fits the situation.
Think of it as: giving an employee full access to a system and trusting them to figure out the right action, rather than scripting every click.
Trigger Layer
Webhook
A push notification between platforms -- when something happens somewhere, data is immediately sent somewhere else as a JSON payload. The entry point for most automations.
Think of it as: a form submission that automatically fires a signal to your systems the moment someone hits submit -- no manual checking required.
Process Layer
Workflow
A defined, repeatable sequence. Trigger, then Action, then Action, then Output. Same path every time. Best for structured, predictable processes that don't require interpretation.
Think of it as: a checklist that runs itself. Every step is predetermined. No judgment needed.
Intelligence Layer
AI Agent
An LLM with access to tools and the ability to make decisions. It can interpret varied inputs, choose the right action from its available options, and execute across connected platforms.
Think of it as: a smart employee who has access to all your systems and can figure out what to do based on what they're given -- without needing step-by-step instructions every time.
Language Layer
LLM
Large Language Model -- the AI brain (like Claude, GPT). Exceptional at processing, interpreting, formatting, and generating text. The reasoning engine behind agents and many workflow steps.
Think of it as: the smartest intern you've ever had -- can process any information, draft anything, research anything, but needs direction on what matters to you.
How It Actually Works
A real example: form submission to personalized outreach
01
Someone fills out your form
A prospect submits a contact or inquiry form on your site. This is the trigger -- the event that starts the whole chain.
02
Webhook fires to your automation platform
The form submission immediately sends a data payload -- name, email, answers -- to a tool like Gumloop or Make. This is your entry point.
The platform extracts the relevant fields. From here, you can run parallel tracks -- one route adds them to your CRM, another begins the outreach flow.
04
Option A: Simple personalized email
Name and email go to an email tool (Resend, Gmail). A template pulls in their first name and the specific interest they mentioned. Sent within seconds of their submission.
"Hi Sarah, thanks for your interest in accounting automation. Here's what we do for firms like yours..."
05
Option B: AI-researched, fully tailored outreach
Name, email, and company get passed to an AI agent. Using tools like Perplexity or Exa via MCP, it researches them, then generates a response specific to their situation before sending.
Agent finds Sarah's firm handles 40+ clients, specializes in e-commerce. Email references this specifically.
06
You receive a summary, not the work
A simple report lands in your inbox. New lead added. Outreach sent. Anything that needs your judgment is flagged. Everything else ran without you.
The Tool Stack
What connects to what
Workflow BuilderGumloop
Visual workflow builder and agent platform. Good for connecting systems without deep coding knowledge.
Database / CRMAirtable
Flexible database that works as a CRM. Easy to connect to automations via API.
Email SendingResend
Programmatic email sending via API. Clean, reliable for automated outreach and notifications.
Research ToolPerplexity / Exa
AI-powered search and research. Agents use these via MCP to research leads or gather market data.
Web ScrapingFirecrawl
Scrapes websites at scale. Useful for competitive research, content gap analysis, SEO data.
AI BuilderClaude Code
LLM-powered coding tool for building custom internal software. Good for one-off tools tailored to your exact process.
Landing PagesFramer
Fast, design-quality landing page builder. Quick to spin up funnels and lead capture pages.
Image GenerationGoogle ImageFX
AI image generation for ad creatives, landing page visuals, and content assets.
WorkspaceNotion
Documentation and knowledge base. Can serve as a lightweight internal tool or client-facing resource.
The Knowledge Funnel
Turning expertise into qualified leads -- click each stage
You have expertise. Prospects want specific information they can't easily find elsewhere. The knowledge funnel connects these two things -- and captures what you need to convert them in the process.
Why they do it: They're getting something specific in return. Not a generic newsletter -- information tailored to their answers. The specificity of the promise is what gets them to fill it out.
You've already done the hard work: building the knowledge base from your expertise, defining what good answers look like. The agent just does the matching -- fast and at scale. It's not replacing your expertise. It's automating the selection.
The personalization isn't superficial. It's based on what they actually told you. People know when they're getting something generic. When the response reflects their specific situation, they notice -- and they're more likely to take the next step.
Their answers tell you what matters to them, what stage they're at, and how to position your offer. Your follow-up can reference this directly. Instead of a cold pitch, you're continuing a conversation they already started.
The Right Mindset
How to think about this before building anything
"Ford took every process of manufacturing a car and systematized it so it ran on its own. He couldn't do that with his accounting. Now you can -- digitally, for the back end of your entire business."
Define your assembly line before you build it. Know every step of your process. The clearer your manual process, the better your automated one will be. Vague in, vague out.
Complexity is fine. Ambiguity is not. Your process can have 100 branches. That's okay. What isn't okay is not knowing which branches exist. A complex but clearly defined process can be automated. An undefined one can't.
Start with what you already do manually. Don't try to automate something you haven't done yet. Pick one process you run regularly, map it out, and build that. Get one system running cleanly before adding another.
Build in error handling from the start. Assume things will break. Add notifications when they do. An automation that fails silently is worse than no automation. Know when your system needs your attention.
The goal is to stop thinking about things that should think for themselves. Every time you save a future version of yourself from having to load a process into working memory, you've created real leverage. That's what this is for.
