I help small businesses optimize and scale — automating the repetitive work, connecting the tools that don’t talk to each other, and building systems that keep running when you’re not in the room.
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.
Nine years building production software in healthcare, fintech, and government work — now systems for small businesses and local organizations in Kansas City.
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.
Sound familiar?
This task is costing your team an estimated
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.
Not sure which task to start with? Take the 2-minute automation quiz →
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.
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.
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.
More work: Volunteer scheduling systemContractor websiteFintech integration platform All work →
Three kinds of systems, one outcome: less manual work.
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.
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.
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.
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).
"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."
Illustrative demo of the pattern — not a live system. The real one I built and run follows the same shape.
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.
Tell me what you're doing manually and how often. A short conversation — no tech jargon required. I ask the questions.
I map the automation, estimate build time, and give you a clear scope and price before anything is built. No surprises.
I test against real data and walk you through it before handoff.
That's the goal. The system works in the background. I'm available if something ever needs adjusting.
Most automations are built and running within a week. No long-term contracts — you pay for the system, not a retainer.
I've spent nearly a decade building systems that keep real businesses running — fintech platforms, healthcare systems, government health-data work, and, more recently, automations and software for local organizations. 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.
For nine years I've built the systems businesses can't afford to have fail — in healthcare, fintech, and government work, and now for small businesses. The numbers are the point.
At a healthcare-technology company, I helped build and run patient-data services handling roughly a million API requests a day under HIPAA and GDPR — the kind of system where a bug doesn't just look bad, it breaks federal healthcare law. As technical lead on an integration platform at a fintech company, I led the architecture for a system that automated customer file-mapping — slow, manual engineering work on every new customer. The company projected it would save millions of dollars a year in onboarding time.
As an independent consultant, I worked on a government healthcare project — health-data interoperability with FHIR and HL7, and hardening the codebase by fixing a batch of known security vulnerabilities (CVEs).
I built an internal AI tool that turns raw specs into working configuration, collapsing days of manual setup into a single afternoon. And earlier, on the healthcare side, I cut a core test suite's runtime by 80% and a key query's time 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.
Please do. I work alongside the advisors a business owner already trusts, and I stay in my lane — systems and software, never financial, legal, or tax advice. Here’s how a referral works.
Yes. I’ve spent nine years building production software in healthcare and fintech, consulted independently on a government health-data project, and today I build and run automations and software for local organizations — from a church’s weekly content pipeline to a contractor’s lead-capturing website (see the work). You talk directly to the person who built all of it, not an account manager or a junior dev handed your project. And the first call comes with a simple guarantee: I’ll find you at least 5 hours a week back, or tell you straight there’s nothing here worth building.
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.
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.
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.
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.
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.
The first call is free. I'll find at least 5 hours a week your team could get back — or tell you straight there's nothing here.