Matt Morrow · Roswell, Georgia
Start with the part everyone hates.
Every job has a part people dread. More often than not, that’s also where a business is losing time, money, or a number it can trust. We figure out what’s happening there, cut the work that shouldn’t exist, and build something the team can keep running.
Selected work
What broke,
what we did about it,
and how it’s going.
A few examples, from the systems a homebuilder runs on every day to a website for a small family business and everything in between.
One workspace for every closing
Cutting time-to-start in half without changing any software
A website for a small family business, with translation built in
How we work
Understand the work before changing it.
We start with how the work really happens. Sit with the people doing it, trace the process and the numbers, cut what adds nothing, then build what’s left. The order matters more than the steps do.
01
Observe
Watch the work where it really happens, which is rarely where the process map puts it.
02
Verify
Trace the process and the numbers back to where they come from.
03
Reduce
Remove the step, field, report, or handoff that isn’t doing anything.
04
Build
Build the smallest thing that solves what’s left.
05
Measure
Check that the change held and the team can own it.
What we do
You have to know what’s
actually wrong first.
A useful system starts with the right diagnosis. We map the work, test the assumptions people have stopped questioning, and build only what the business needs.
Operations & process audit
We map how the work really moves from person to person and find the bottleneck, the double entry, the report nobody reads. Sometimes the number everyone trusts turns out to be wrong.
Find the breakAutomation & internal tools
Python automation, data pipelines, and internal web apps that replace manual work and stay maintainable after launch.
Build the fixTechnology leadership & AI adoption
Technology planning, vendor decisions, and the habits that let a team ship safely, including helping people outside the tech team build with AI.
Own the systemWriting
Drafting.
Notes on technology, operations, and the occasional detour through beer, sports, and a winding career. Published on Substack, collected here.
Start With the Schlep: How We Got Nontechnical Teams Building With AI
Agentic AI is an incredible tool for engineers, certainly, but it is also an incredible tool for everyone. If you’re limiting your most...Empathetic Engineering
You can build the most technically impressive application in the world, but if the person you built it for can’t use it, all you’ve done...Hazy AIPA
As a former craft brewer turned software engineer and now CTO, my mind can’t help but see similarities between the launch of hazy IPAs...Put it on the table
What’s the part
of your week
you dread?
Audits, build work, and ongoing advisory, plus the occasional talk or workshop. Whatever you’d hand off first if you could is usually the best place to start.
Start a conversation