AI Automation

Your busywork,
automated.

I build custom systems that eliminate repetitive manual work for small businesses — automations that run on their own, so you can focus on what actually moves the needle.

The first call is free — I'll find you at least 5 hours a week back, or tell you straight there's nothing worth building.

40+
Subscribers served by one automated system
0
Manual steps left in its weekly routine
~1 hr
Maintenance per month — that's it

All three come from one system I built and run — live and unattended since early 2026.

Sound familiar?

You're running the business.
The business is running you.

Every week there are tasks that eat hours — not because they're complex, but because no one ever automated them. That's fixable.

  • Copying data between apps by hand every day
  • Sending the same follow-up emails manually each week
  • Generating the same reports from the same spreadsheets
  • Manually routing inbound leads or requests to the right person
  • Chasing down documents, signatures, or status updates
What it's actually costing you

See the price tag on
"we've always done it this way."

Rough math, not a quote — but it's usually the number that gets ignored until someone writes it down. Plug in one task your team repeats by hand.

This task is costing your team an estimated

144
hours per year
$5,040
per year

This is a simple time-cost estimate you're providing — not an audit, and not a guarantee of savings. It's meant to make the cost visible, nothing more.

That's the kind of task that's usually worth automating first — repetitive, rule-based, done by hand mostly because nobody's gotten around to it. I can't promise this exact task is automatable without seeing it, but it's worth 20 minutes to find out for sure.

Proof of Work

A real system.
Running in production.

Case Study
The weekly grind that ran itself out of a job

A 200+ member church was burning staff hours every week on the same routine: turning each service's recording into a formatted outline document, updating two websites, organizing videos, assembling announcements, and getting it all in front of the congregation. Twice a week, every week — and when the one person who knew the process was busy, things slipped. I built a system that does the whole routine on its own.

0 hrs Manual work per week
40+ Subscribers in week 1
~1 hr Monthly maintenance
1
The recording becomes a polished outline document automatically — formatted the way the church likes it, scripture quotes corrected to the exact translation they use — and lands in the staff's inboxes the same afternoon. Nobody types a word.
2
Both websites update themselves — each new message posted with cleaned-up, consistent titles, and every video gets chapter markers and a searchable description within hours of going live. No one logs in to do it.
3
Announcements assemble themselves into a ready-to-send bulletin — a staff member reviews it and clicks one button. The system handles the sending, and members manage their own subscriptions through a simple portal.

The one place a human still touches the process is the one place a human should: nothing goes out to the congregation without a person approving it. Everything else runs unattended.

What previously consumed hours of staff time each week now runs entirely on its own. It's been in production since early 2026 and hasn't missed a service. It checks itself — I look at it about once a month. The staff stopped thinking about it, which was the whole point.

This wasn't built for a tech company. It was built for a small organization with no IT department, no engineers, and no patience for tools that need babysitting — exactly the situation most small businesses are in.

If a volunteer project I built for free runs this reliably, imagine what I'd build when it's your livelihood on the line and we're aligned on outcomes.

Read the full case study — with the system diagram →
See it work Illustrative demo

Don't take my word for it.
Watch a manual task run itself.

Here's the kind of messy, human input a business handles by hand every day. Hit the button and watch what an automation does with it — the same capture → understand → act → done shape I build for real (see the church system for a live one).

The messy input
📩 Voicemail transcript · 0:14

"Hey it's Dave over at Dave's HVAC — need to push Thursday's install to next Tuesday if you can. And can you resend the invoice from the last job? I think it was around eight hundred forty bucks. Thanks."

What the automation does
  1. Captures the voicemail and transcribes it
  2. Understands it: a reschedule + an invoice resend
  3. Moves Thursday's job → next Tuesday in the calendar
  4. Re-sends invoice #1042 ($840) to Dave
  5. Logs it all and flags one thing for you to confirm

Illustrative demo of the pattern — not a live system. The real one I built and run follows the same shape.

What I Build

Three types of systems.
One outcome: less manual work.

Document & Content Pipelines
Raw input goes in — formatted, accurate output comes out automatically. No manual transcription, formatting, or distribution.
E.g. meeting notes → structured summaries → auto-emailed to your team. Or: audio/video → transcription → formatted report.
Client Communication Automation
Follow-ups, onboarding sequences, status updates, and reminders — triggered automatically based on what's happening in your business.
E.g. new lead fills form → CRM updated → personalized follow-up sent → you're notified only if they reply.
Internal Ops & Reporting
Data that lives in multiple places gets pulled together, processed, and delivered as a clean report — on schedule, every time.
E.g. weekly ops dashboard built automatically from your existing tools, delivered to your inbox every Monday morning.
Start here

The First Automation

Not ready for a full project? Start smaller. We use the free call to find one manual, repetitive task worth automating — then I build just that, for a fixed price agreed up front before any work starts. If it doesn’t work out, that’s on me to fix, not you to absorb.

  • One working automation, live in your systems — not a platform, not “phase one.”
  • Scope written down and agreed before I start, so “done” is defined up front.
  • Me, directly, the whole way — I scope it, build it, and hand it off with a short doc.
Book the free call Scope & price agreed in writing before any work starts.
9 Years of Production Systems

I don't just know automation tools.
I know how businesses actually break.

For nine years I've built the systems businesses can't afford to have fail — and the numbers are the point.

At a healthcare-technology company, I built data services handling roughly a million API requests a day under GDPR — the kind of system where a bug doesn't just look bad, it breaks federal healthcare law. As lead architect at a fintech company, I built an integration platform that automated customer file-mapping — work that had been burning weeks of engineering time on every new customer — for an estimated $10 million a year in recovered velocity and labor.

I built an internal AI tool that turns raw specs into working configuration, collapsing days of manual setup into a single afternoon. And I cut a core test suite's runtime by 80% and query times by 60% — not by throwing hardware at the problem, but by fixing how the systems were built. Not demos. Systems people relied on every day.

That's the bar I build to: production systems that handle real volume and run unattended. It's exactly what your busywork deserves — built right the first time, and designed to run without you.

What This Means For You
  • I understand the operational pain behind the automation request — not just the technical implementation.
  • I've built systems that handle millions of real transactions without falling over — that's the standard I hold your automation to.
  • I know how to scope and deliver fast. The same AI-augmented approach I use professionally is what I bring to your project.
  • I've spent years translating between business stakeholders and the systems underneath. I speak business, not just code.
How It Works

From problem to
running system in days.

01
You describe the pain
Tell me what you're doing manually and how often. A short conversation — no tech jargon required. I ask the questions.
02
I scope the solution
I map the automation, estimate build time, and give you a clear scope and price before anything is built. No surprises.
03
I build and test it
Most systems are built and running within a week. I test against real data and walk you through it before handoff.
04
It runs. You forget it exists.
That's the goal. The system works in the background. I'm available if something ever needs adjusting.
About

I build for outcomes,
not for show.

I've spent nearly a decade building systems that keep real businesses running — fintech platforms, healthcare operations, and, most recently, an automation system that runs a 200-member organization's weekly operations without anyone touching it. The through-line isn't the technology. It's that every system had to work reliably, day after day, because real people depended on it.

I started using AI tools early because they let me deliver faster without cutting corners. A project that used to take weeks now takes days. That means you get a working system in your hands sooner, and we can refine it together based on how you actually use it.

I'm not an agency. I'm one person who does the work. When you hire me, you talk to the builder. No handoffs, no junior developers, no surprises.

Production systems that run for months without babysitting
An integration platform I built — estimated to save ~$10M a year in manual work
You work directly with the person building it
Kansas City-based · Available for remote projects
What working with me looks like
A working system in days
Most automations are built and running within a week. You'll see progress immediately, not after a month of meetings.
Built to run without you
I design systems that don't need daily attention. Set it up, let it run, and check in when you want to — not because you have to.
Clear communication, always
No jargon, no status reports that obscure reality. I'll tell you what's working, what's not, and what it takes to fix it.
No long-term contracts
You pay for the system, not a retainer. If something needs adjusting later, we'll handle it when it comes up.
Questions

The honest answers.

You don’t have client reviews. Why should I be your first?

Fair question, and you deserve the honest answer instead of a dodge: I’m 9 years into a software engineering career, independent since 2022, and you’d be an early consulting client. Here’s what that actually gets you — you talk directly to the person building it, not an account manager or a junior dev passed your project. And I’m backing it with a real guarantee: I’ll find you at least 5 hours a week back, or I’ll tell you straight there’s nothing here worth building. If that trade-off isn’t for you, I understand.

My business is small and I’m not techy. Is this even for me?

This is built for that. If you can describe the annoying task you keep doing by hand, that’s all you need to bring. I handle the technical side and explain everything in plain language — no jargon test to pass.

Will I need to babysit this thing once it’s running?

No — that’s the point. My clearest example so far is a content pipeline I built as a volunteer for my church, running unattended since early 2026 at about an hour of my time a month. That’s the same “set it up right, then leave it alone” outcome I aim for with paid work.

What if it breaks, or you disappear?

If something breaks, you call me and I fix it — that’s part of the deal. I also build things to hand off: clear docs, no secret black box. If you ever wanted to walk away from me, you could.

How much does it cost?

I don’t quote a price until I understand what you actually need. We start with a free 20-minute call, and if it makes sense to move forward, you get a fixed price for the defined scope before any work starts — no open-ended hourly bill, no surprises.

How long does it take?

Depends on scope, but most of these run days to a couple weeks, not months. The call is where we nail down the real timeline for your case.

Find your easiest
automation win.

The whole first step is a free 20-minute call. I'll find at least 5 hours a week your team could get back — or tell you straight there's nothing here. No pitch, no obligation.