
The Flowchart
If Opus 4.7 needs instructions that explicit, it needs its own programming language. Because it's no longer interested in inferring what we have to say.
Odyssey Alive
25 years building websites. A cultural anthropology background that explains why your "simple" workaround is actually genius.
Anthropic buried their Opus 4.7 strategy in a single sentence. The model they're not shipping explains the one they are.
A Different Kind of Builder
Most developers ship a tool and hope you'll adapt. I spend time understanding why your team uses that shared Google Doc instead of the expensive CRM. Then I build automations that work with your reality, not against it.
It's like the difference between a GPS that recalculates every time you take a "wrong" turn versus one that learns your preference for the scenic route. Same destination, wildly different experience.
How We Can Work Together
Your business isn't a template, so why would your automation be? I dig into how your team actually works: the workarounds, the shortcuts, the "we've always done it this way." Then I build AI systems that amplify what's working instead of bulldozing it.
Building focused tools for specific industries, starting with real estate agents who need market intelligence that doesn't require a data science degree to interpret.
Join Focus to get early access when we launch.
Latest Thinking

If Opus 4.7 needs instructions that explicit, it needs its own programming language. Because it's no longer interested in inferring what we have to say.

Cloud AI fails. Power grids fail. Your client's deadline doesn't care about either one. So I built Krull AI, a complete offline solution.

Your developer is deciding how much to tell you about AI risk. That's not dishonest. It's rational. But the questions you're not asking are the ones that matter most.