[ 01 ]Why this exists
Twenty years watching talented people do work they shouldn't have to do.
I ran technology operations inside service firms for two decades — starting as Deputy CIO at AOL, then leading delivery and operations at five more companies across very different industries. Different sectors, different sizes, same problem in every one: smart people spending half their week on admin work that had nothing to do with why they were hired.
Dispatchers copying job details between systems by hand. Account managers rebuilding the same report every Monday. Estimators retyping specs into three different tools. Office managers chasing field crews for notes that never got logged.
AI finally got good enough to do something about it. Not in theory — in production. So I built PropelAI to design and build the software those organizations can't get built anywhere else: the defense contractor running a capture pipeline out of spreadsheets, the association whose two-person membership team is drowning, the property manager running two hundred units, the contractor whose best estimator spends Thursday afternoon on paperwork instead of job sites.
[ 02 ]How we work
Find the bleed. Ship the fix. Repeat.
The problem is structural, and it compounds as you grow. More volume means more dispatching, more reporting, more invoicing, more follow-up — and more things falling through the cracks. Hiring against it works until it doesn't, because you end up hiring people to feed software.
So we find the single highest-impact workflow — whichever one is bleeding the most hours or losing the most deals — and ship a working system that handles it. Not a pilot. Not a proof of concept. A production system your team uses on Monday morning.
Then we find the next one.
[ 03 ]About Mike
An operator who learned AI, not an AI person who read about operations.
Before PropelAI I spent twenty years running technology delivery inside service firms. I've led teams of 200+, owned delivery and operations across multiple companies, and shipped systems that are still in production today.
The difference between me and most AI vendors is that I've sat in the operator's chair. I know what breaks on Monday morning, what the board asks about on Thursday, and what nobody has time to fix on Friday.
[ 04 ]Current focus
Shipping products that started as client problems.
Three things right now: turning engagements into repeatable products — Frame, Brief and Emblem are available today, WebStudio is in private pilot and Dispatch is in development — taking on more product builds, and building the library of industry-specific systems that makes every new engagement faster and cheaper than the last.
If your team spends more time feeding systems than doing the work, we should talk.