N.v. · Work · Case studies

What the work
actually looks like.

Four engagements, described honestly. Client names changed; numbers kept as they were.

01.

Juice & smoothie bar · solo operator

Running a business through Instagram DMs and a handwritten notebook.

A single-person fresh juice bar was operating entirely through Instagram DMs, Venmo, and a spiral notebook. Every order came in through a message, every question got answered manually, and she had no record of who her regulars were or how often they ordered. She was spending close to two hours a day on logistics that had nothing to do with making juice.

We built a five-page website with an online ordering form, connected Square so payment was collected at order time rather than at pickup, and set up a lightweight CRM in Airtable that automatically logged every customer. A simple email automation handled the rest: new customers got a welcome with her seasonal menu; anyone who hadn't ordered in 30 days got a brief note.

DM volume dropped roughly 70%. She stopped taking orders in the evenings because customers could submit them any time and she'd fulfill them on her schedule. She now knows her top 20 customers by name and order history without having to remember any of it.

Time3 weeks
ScopeWebsite · CRM · Automation
Result~70% fewer DMs
02.

At-home laundry pickup & delivery · solo operator

Scheduling by text message, collecting cash on delivery, no record of anything.

A one-person laundry service — pickup, wash, fold, deliver — was coordinating everything through SMS. Customers texted to schedule, she confirmed manually, and payment happened at pickup. About 15% of pickups resulted in a no-show or a payment conversation that went sideways. She had no record of her regulars, no way to see her week at a glance, and no leverage when a customer disputed a charge.

We built an online booking system where customers chose a pickup window and paid upfront. Automated texts went out two hours before each scheduled pickup. A simple dashboard gave her a clear view of her day without having to scroll through a text thread to reconstruct it.

The no-show rate dropped to under 2%. Payment disputes went to zero — payment was collected before she ever picked anything up. She recovered roughly eight hours a week that had been going to scheduling follow-up and manual confirmations.

Time2 weeks
ScopeBooking · Payments · Automation
ResultNo-shows: 15% → <2%
03.

Roofing company · 4-person team

Leads arriving through three different channels. No system. No follow-up.

A small roofing company was getting job inquiries through their website contact form, two personal cell phones, and one shared Gmail account. If the right person didn't see the message first, nobody followed up. They were also paying for three separate tools that substantially overlapped: a CRM they barely used, a project management app from a vendor demo two years prior, and a scheduling tool from a promotion they'd forgotten about.

We consolidated to two tools, canceled the third, and built a lead intake system that routed every new inquiry to a shared inbox with an automatic same-day acknowledgment to the customer. A simple pipeline — lead, estimate, job, complete — became visible to everyone on the team for the first time.

Estimated annual savings from the subscription cleanup: $3,200. Lead response time moved from "whenever someone notices the email" to the same business day, consistently.

Time3 weeks
ScopeLead routing · Pipeline · Cleanup
Result$3,200 / yr saved
04.

Insurance agency · 12-person office

Shared logins, passwords on sticky notes, and a vendor pitching them AI they didn't need.

A regional insurance agency had a real security problem: most systems ran on shared credentials, passwords were on physical notes near monitors, and when someone left the company their access didn't reliably end with them. At the same time, an AI vendor was pitching them an expensive document-processing solution for handling policy applications.

We started with access. Individual logins, a password manager deployed across the team, and a clear offboarding checklist so that when someone left, their access ended the same day. We then looked at the AI pitch. The problem the vendor was solving — faster policy application processing — could be handled with a combination of their existing Microsoft 365 subscription and a properly configured document workflow. No new AI spend required.

Security cleanup took two weeks. The document workflow took three. Policy application processing time dropped from a four-day average to under 24 hours. Total cost was a fraction of the vendor proposal.

Time5 weeks
ScopeSecurity · Workflow · Automation
Result4-day turnaround → <24 hrs

Sites & products I've built.

Website design is a service — it helps to see what that looks like in practice.

Working in a specific field?

Ready to do this for your business?

If you saw something in one of these stories that looks familiar, that's where we start. Book a call and we'll figure out what to fix first.