When a service business came to us, they weren't losing deals. They were drowning in the admin that came after winning them.
Every new lead that filled out their intake form triggered the same 45-minute manual process. A team member would stop what they were doing, open four different tools, and work through a checklist: copy the lead into the CRM, send a welcome email from a template, create a project folder, generate a task list, and schedule a discovery call. Then they'd move on — until the next form submission arrived.
At 10 new leads a week, that's 7.5 hours of admin. Per week. On work that required zero judgment, zero creativity, and zero human insight. Just copy-paste and clicks.
The before: where the time was going
When we mapped the existing process, it broke down like this:
- Copy contact details from the intake form into the CRM — 8 minutes
- Draft and send a personalized welcome email from a saved template — 10 minutes
- Create a project folder in their file management system and copy in the standard template — 12 minutes
- Generate a task list for the new client in their project management tool — 8 minutes
- Find a time slot, send a calendar invite, and confirm the discovery call — 7 minutes
Total: 45 minutes. Every. Single. Lead. Without exception.
And this was a team that was good at their jobs, using modern tools. The problem wasn't them. The problem was that none of their tools were connected to each other, so every handoff between systems required a human to carry the information across.
The build: what we automated
The workflow we built triggers automatically when a new intake form is submitted. Here's what happens next, without anyone touching it:
- Contact details are extracted from the form and a new CRM record is created instantly
- A personalized welcome email goes out within 60 seconds, using the client's name and project details from the form
- A project folder is created from the standard template and shared with the relevant team member
- A task list is generated in the project management tool and assigned based on project type
- A calendar invite is sent to the lead with available discovery call slots, using the team's live availability
Time per lead: zero. The workflow runs in under 90 seconds, regardless of the time of day or whether anyone is at their desk.
The after: what changed
The immediate result was the obvious one — 7.5 hours of admin per week returned to the team. But the less obvious result was just as valuable.
Because the workflow ran instantly, leads now received their welcome email and calendar invite within minutes of submitting the form — not 2 to 4 hours later when someone got around to it. Response speed went from variable to consistent. The client reported noticeably warmer discovery calls as a result.
And when the business doubled its lead volume three months later, the intake process didn't break. It just handled more submissions at the same speed.
What makes this kind of build possible
This wasn't a complex engineering project. It took a few days to build, test, and deploy. The tools were all connected via standard APIs — no custom integrations, no proprietary systems.
What it required was a clear map of the existing process, the right connections between systems, and a decision to stop treating manual admin as a fixed cost of doing business.
Most of the intake workflows we see are variations of this same pattern. The specific tools change — different CRMs, different project management software, different calendar tools — but the underlying structure is almost always the same: form submission → data distribution → communication → scheduling. All of it automatable.
The build pays for itself in weeks. Then it runs for years.
What stays human after intake is automated
Automation owns the copy-paste stretch. People keep the judgment. That boundary is the point of the build, not a compromise.
- Edge-case leads still get a human read — wrong fit, incomplete briefs, odd project types.
- Pricing exceptions and scope negotiations stay on a call or in a thread with a named owner.
- Relationship nuance on the discovery call is still human. The workflow just gets the call booked and the folder ready.
- What the path owns: CRM create, welcome email, folder from template, task list, calendar invite from live availability.
If your team is still spending judgment time on folder creation, the boundary is wrong. Fix the ownership map, not the meeting culture.
Failure paths that keep trust
Silent drops kill trust faster than a slow manual process. A finished intake path names what happens when a step fails.
- If CRM create fails, ping a named owner with the payload so the lead is not lost in a log.
- If calendar slots are empty, fall back to an email with a manual book link — never leave the lead with nothing.
- Never silent-drop a lead because one API timed out. Retry, then escalate with enough context to finish once.
That failure design is part of the workflow. It is not "phase two." If you cannot name the owner and the fallback, you are not ready to turn the path on.
How to know intake is the right first path
Intake is a strong first build when most of these are true:
- The same five-plus steps run for every lead, with almost no variation.
- Volume is high enough to feel — hours per week, not a rare event.
- The tools already have APIs (CRM, email, files, calendar, project management).
- Report or approval pain can wait if leads are aging in the inbox while someone copy-pastes.
If leads sit for hours before the welcome email goes out, intake usually beats a reporting project for immediate commercial return. Pick the path that hurts this week.
Related cost patterns (same studio, different path)
Intake is one owned path. The same studio pattern shows up elsewhere: the cost of manual reporting, quote follow-up that does not need more salespeople, approvals that became a part-time job, and what a first build looks like when you scope one path in weeks.
Prefer to see the boundary of a 2–6 week scoped build first? Read the scoped pilot. Ready to talk about your intake path? Book a discovery call.