Software studio · Est. 2026
Software that fits
how your business
actually works.
Most companies outgrow their spreadsheets long before they can justify a software team. We build the tools, integrations and automations that close that gap — and we build them to be handed over, not held hostage.
Sound familiar
The expensive problems are rarely the obvious ones.
- Your team retypes the same information into two or three different systems.
- The software you bought does about 70% of what you actually need.
- One person understands how the whole process works, and they never take a vacation.
- A report that should take minutes takes someone most of a day, every week.
What we do
Custom software
Internal tools, customer portals, and the systems your business runs on — built for how you actually work, not how a product vendor assumed you would.
Integration
Making the systems you already pay for talk to each other, so information stops being carried between them by a person with a keyboard.
Automation, including AI
Where it genuinely saves hours: reading documents, sorting and routing requests, pulling structured data out of messy inputs. Used where it fits, not because it is fashionable.
Straight talk
We’re new as a studio. We’re not new at this.
Milpa Craft opened in 2026. The engineering behind it is fifteen years of SaaS, healthcare and AI systems — most of it for companies much larger than yours, which is exactly why the smaller ones kept asking.
You should not have to take that on faith, so we structure the work so you don’t:
- Discovery stands alone. You pay a fixed fee, you get a written plan with costs and sequence, and it is yours whether we build it or someone else does.
- You own everything from day one. Repository, cloud accounts, domain — in your name from the first commit. Leaving should be boring.
- Fixed scope per phase. You find out how we work on a small piece, before the budget is committed to a large one.
How we work
Three things planted together.
A milpa is the Mesoamerican practice of growing corn, beans and squash in the same field. Each one makes the others work. It is the oldest systems design we know of, and it is a fair description of how we run a project.
Structure
We map how the work moves through your business today, then design the smallest system that fixes the expensive part. You get the plan, the cost and the sequence before anything is built.
Corn is planted first. Everything else in the field grows on it.
Build
Delivered in working increments you can see and use, not a long silence followed by a launch. You review real software every week and change direction while it is still cheap.
Beans climb the corn and feed the soil that grows it.
Protect
Monitoring, documentation, and a handover your team can actually act on. You own the code and the accounts from day one. If you want us gone, you are not stranded.
Squash spreads low, holding moisture and keeping weeds out.
Start here
Start with the cheap part.
Discovery costs $1,500 and takes one to two weeks. You get a document that says what to build, what it costs and in what order — written plainly enough to hand to your accountant.
If you read it and decide not to build anything, you have still saved yourself the larger mistake.