About
I run Stackcraft's engagements directly — every build, every audit, every coaching session. Here's what that actually means and how I work.
I design, build, and ship the software behind Stackcraft — and I run the consultancy, coaching, and training engagements the same way: directly, without layers between you and the person actually doing the work.
My background is operational, not academic. Before writing a line of code for a client, I've usually spent time understanding how the business actually runs — where the manual work piles up, where a "quick fix" would just move the problem somewhere else. That's the part most software people skip, and it's the part that decides whether what gets built actually gets used.
I use AI tools deliberately, throughout the process — not as a shortcut, but as a genuine multiplier on speed without lowering the bar. The same judgment, considerably faster delivery.
Not theory
~3×
Faster per-item processing on a purchase-order automation build — cut down to minutes and a handful of clicks, built to replace the manual role entirely.
50%
Time saved on a referral-matching tool — a process that used to take roughly three hours cut to under ninety minutes.
6
Distinct pathways handled by a single onboarding system built for Your Focus, an ACC-funded healthcare supplier — gated, sequential, and self-documenting.
How I work
Automating a broken process just makes it fail faster. I look at how work actually happens before deciding what to build or change.
Healthcare and other regulated environments come with real constraints on what AI and automation can and can't do. I work inside those constraints properly, not around them.
You talk to me, every time — not because it's scrappy, but because that's genuinely how senior work should be delivered.
Clean documentation and architecture your team can actually pick up, whether that's in a month or three years.
Tell me about it and I'll get back to you within 24 hours.
Start a project