About
Built by someone who had to run the operation, not just advise on it.

Michael Cox runs QuickFix Real Estate, his own company, and has spent years building the systems behind it: the intake, the handoffs, the exceptions, the reconciliation between systems that disagreed about the same number. Not as a consultant producing a deck, but as the person who got the call when it broke at nine on a Friday night.
He still does. The systems on this site are the ones running that business today, which is why they are shown working rather than described, and why the ones that are still broken get shown too. The ones worth having are packaged so another operator can install them without him.
That is where the method comes from. Every part of it is a reaction to something that went wrong. Diagnose before prescribing, because a confident recommendation built on a misunderstood process is expensive. Standardize before automating, because automating a disputed process only makes the dispute faster. Keep human authority explicit, because the consequential decisions are the ones you will be asked to explain.
Why this is not an AI agency
An agency is paid to deploy the thing it sells. That is a bad incentive structure for a decision about whether to deploy anything. Separating the diagnosis from the implementation is what makes it possible to say the answer is simplification, or a rule, or leaving the work with a person, without it costing the engagement.
AI is genuinely useful in a narrow band: language, judgment on unstructured input, drafting under review. Most of what a workflow needs is not in that band. Saying so out loud is the job.
What you can expect
Bounded scope with explicit stop conditions. Conclusions that cite the evidence they rest on. Claims labeled as hypotheses until there is paid evidence behind them, including on this website. And a recommendation you own, whether or not it leads to more work for us.
Speaking and podcasts
Happy to do this in front of a room.
I build in public, so the material is already on screen: what an operator can run without a developer, what it costs to keep running, and the honest version of what breaks. Conferences, local groups, and shows for people who run something real.
Start with one workflow.
Thirty minutes, no deck. Bring a process that costs more than it should and we will tell you honestly whether there is something here worth paying for.