About
One engineer. No account manager in between.
Wildflower Software is a solo consultancy. That's a deliberate constraint, not a stage on the way to an agency — it's what lets me take fewer clients and go deeper on each one.
What I actually do all day
I write Python, mostly Django. Data models that hold up once there's real data in them, queries that don't fall over at 10× traffic, background jobs that fail loudly rather than quietly. These days a lot of that work has an AI piece bolted to it: a retrieval pipeline, an agent loop, a classification step. The model call itself is rarely the hard part. What takes the time is evaluation, keeping the cost predictable, deciding what happens on a timeout, and being able to answer a product manager who wants to know why last week's answer was different.
The other half is deployment. Containers, migrations that run in the right order, secrets kept out of the repo, a rollback someone has actually tested. A lot of teams have a perfectly good application sitting behind a deploy process nobody trusts, and that usually takes weeks to fix rather than quarters.
How I work
Fixed scope where scope can be fixed, hourly where it honestly can't. I'd rather quote you three weeks and be right than quote one week and be wrong. The work happens in your repo and your issue tracker, so you can watch it land instead of waiting for a status call.
I default to boring technology and I document what I build. The last deliverable is usually a walkthrough with your team, and it goes well when nobody has much to ask.
Open source
Django is community-maintained software, and I try to pay rent on the parts I use. That means upstream patches, conference talks, and a standing discount for nonprofits and OSS maintainers who need a hand.