From 3 Hours to 20 Minutes: A Real Client Story
What two hours of setup actually looks like, and what it means six weeks later.
Parker Swanson
May 25, 2026 · 4 min read
Hey, I'm Parker. I run Clockworks, and I want to tell you about Mike.
Mike runs a 6-person HVAC company in the western suburbs of Minneapolis. He's been in the trades for 22 years. He's good at what he does. He has a full book of business and a team he trusts. What he does not have is time.
When Mike came to me, he wasn't looking for a tech transformation. He wanted to stop spending his Sunday nights writing reports and catching up on email. That was it. He'd heard AI might help. He had no idea where to start.
The before: Sunday nights at the kitchen table
Every week, Mike put together a report for his business: jobs completed, revenue, any issues with crews or materials, what was coming up the following week. He sent it to himself and to his business partner. It took about two hours. Sometimes two and a half, if the week had been messy.
He also had a chronic email backlog. Not because he ignored email, but because he spent too long on each one. He'd rewrite the same follow-up four or five times before sending it. He told me he often wrote and deleted entire emails without sending them because they didn't sound right. Meanwhile, leads went cold and customers waited longer than they should have.
He also had a handful of recurring customer service situations that he handled the same way, every time, from scratch. Seasonal maintenance reminders. Responses to "the heat isn't working" calls after hours. Requests for quotes on systems he'd quoted a dozen times before.
None of this was complicated work. It was just slow, manual, and relentlessly repetitive. Mike estimated he was spending 8 to 10 hours per week on this category of task.
This is the pattern I see most often: not one big problem, but a cluster of small, repetitive ones that together add up to a day and a half of lost work every week.
What we built in two hours
Mike and I did a two-hour Clockworks session on a Wednesday afternoon. Here's what we actually built:
The weekly report template. We created a Claude Project called "Weekly Report" with standing instructions about what the report needed to cover, what Mike's business partner cared about, and what format worked best. We also created a simple fill-in-the-blanks input form, a Google Doc that Mike fills in each week with raw notes: jobs done, numbers, any issues. He pastes those notes into Claude with one line: "Turn these notes into this week's report." That's it.
Five email templates. We built five prompts for the most common email situations Mike faces. Quote follow-ups. New lead responses. Post-job check-ins. Responding to after-hours calls. Seasonal maintenance outreach. Each prompt lives in a shared Google Doc Mike keeps open on his phone. He copies the relevant prompt, swaps in the customer name and a detail or two, and hits send.
A rough-draft habit. For emails he couldn't find a template for, we practiced the "rough draft first" technique: Mike types his messy version of what he wants to say, then pastes it into Claude with "clean this up." Two minutes instead of twenty.
That was the entire session. No code. No software integration. No new subscriptions beyond the Claude free tier. Two hours of setup.
The numbers, six weeks later
- 20 min: Weekly report (was 2–2.5 hours)
- ~6 hrs: Time saved per week on email and reporting
- 3 leads: Re-engaged in first two weeks from faster follow-ups
The report now takes Mike about 20 minutes on Sunday afternoon instead of 2+ hours at night. He still fills in the raw notes himself (that part takes about 10 minutes), but the writing is done in seconds. He reads through it, makes one or two small adjustments, and it's done.
Email went from his biggest time sink to something he mostly handles in the morning before his first job. The templates handle 80% of what he sends. The rough-draft technique handles most of the rest.
The lead re-engagement was a side effect he didn't expect. Because he was following up faster and more confidently, three leads who had gone cold came back in the first two weeks. One of them turned into a full system installation, a $6,400 job. That alone would have paid for years of AI subscriptions.
"I kept waiting for it to be more complicated than it was. But it's just... faster. Sunday nights are mine again. That's not a small thing."
Mike, HVAC business owner, western Minneapolis suburbs
What this actually teaches us
Mike's situation isn't unique. I see it constantly. The tasks that eat small business owners alive aren't complicated. They're just repetitive and slow because there's no system behind them. Every week you're reinventing the wheel on the same email. Every Sunday you're starting the report from scratch.
AI doesn't replace those tasks. It gives you a system for them. You still do the thinking. You still know your customers and your business. But you stop typing the same things over and over, and you stop staring at a blank screen when you know exactly what you want to say but can't quite get it out.
The two-hour investment paid for itself in the first week. The habits Mike built in that session are things he'll use for the rest of his career. That's the math that matters.
If you recognize yourself in Mike's story, reach out. The free call is for exactly this: figuring out which two hours would make the biggest difference in your week. No pitch, just an honest look at your situation.