Hyperspectral crop analytics
Hyperspectral imagery pipeline for detecting crop stress and yield prediction across large-acreage farms.
I build vision systems for companies whose work happens outside — farms, job sites, service fleets. Trained in computer vision, ten years shipping. A workflow built around agentic coding lets me carry more scope than one engineer should. I take fewer clients than an agency, and I stay longer.
Every project here puts a camera or a sensor where the work actually happens — a field, a job site, a truck. The industries differ. The problem doesn't.
Consulting goes sideways in the same few places. I've taken each one out of the equation.
Thirty minutes. We talk about the problem, not my resume. If I'm not the right fit, I'll tell you.
A short doc — what I'll do, how I'll measure it, what it costs, what I need from you.
Something tangible every week. Demos, not status updates. You always know where things stand.
I write code your team can own. Stay on as long as it's useful — leave cleanly when it's not.
Engagements typically start at $8,000/month. I hold a mix of cash-only, cash-plus-equity, and pure hourly arrangements — for early-stage teams, equity is a real part of the conversation.
Ongoing fractional engineering — a fixed monthly rate, sometimes paired with equity for early-stage teams I believe in.
Flexible hourly engagements, typically a set block of hours per month. Good for specific workstreams or fractional technical leadership.
Short, high-leverage engagements — architecture reviews, hiring a CTO, unblocking a CV or ML problem.
Two to three weeks. I stand up your team's agentic development workflow and leave you running it: specs the agents can follow, task decomposition, isolated worktrees per task, and the review gates that keep the diffs honest.
I earned my masters in computer vision at BYU, then continued into doctoral research there. The academic training still informs every project I take on.
Today my practice is deliberately narrow: vision systems for companies whose work happens outdoors, a small set of long-running engagements, and a bias toward demos over documents. If your team needs a senior engineer who will actually be there — I'd like to talk.
How the agentic part works, concretely: the spec and the task plan live in the repo, agents run against separate worktrees, and I read every diff before it merges. That's why a week of my time covers more ground than it used to.
Two slots open. References available under NDA.