I BUILD FOR ONE OPERATOR AT A TIME / DISCOVERY, PILOT, PRODUCTION
Ian Bearss. I embed with an operator, find where the work leaks hours, and build the system that stops it. Remote, from Fort Collins, Colorado.
/ WHAT I BUILD
Give me the problem. I build the thing.
Most of what gets sold as AI is a demo with nobody behind it. I work the other way: time inside the operation first, a written finding second, software only if the finding calls for it. When it does, I build the whole thing, data, interface, and deployment, and hand over something your team can run without me.
Tooling I built for my own process. It runs the mechanical parts, research passes, scaffolding, regression suites, so the hours go into judgment instead of typing.
01
Answers from your own documents
The question that gets answered by digging through a binder of standards, or by asking the one person who has read them. Every answer points at the clause it came from, or says it does not know.
02
Operations tooling and automation
The spreadsheet somebody maintains at night, replaced with something that does not depend on that person still working here.
03
Web apps and products
Full applications with real state, data, and auth. Next.js and Vite, shipped to production.
04
Sites and motion
Scroll-driven marketing sites and title sequences rendered in code. Usually the front door for the systems above.
I design and build digital products, websites, apps, and the systems that run them.
Fort Collins, Colorado. I started behind a bar and taught myself to build. Client websites, web apps, automations, and the tools behind them, all designed, built, and deployed by me. I built my own tooling to run the mechanical parts, so the hours go into judgment instead of typing.
Nothing ships that I can't explain. Nothing gets claimed without a number behind it.
4 SHIPPED THIS YEAR / 1 IN PROGRESS / EVERY LINE MINE TO EXPLAIN
/ WORK WITH ME
Three stages. You can stop after any of them.
Most of "AI" is noise. I find the parts that pay off and build those. Each stage is priced on its own and produces something you keep whether or not we continue.
01
Discovery
Fixed fee, fixed scope. Time inside the operation with the people doing the job, not with the org chart.
A written finding: where the hours go and roughly what that costs
A straight answer on whether software is the right fix
A fixed quote for whatever is worth building
Sometimes the answer is that you don't need software. That's still the deliverable, and you still keep it.
Want me on call after we ship? A monthly plan keeps your systems, automations, and apps running, with updates and changes from the person who built them. Cancel anytime.
/ WHO OWNS WHAT
01
Your sources, your data, and the questions your team writes stay yours.
02
You keep the system and run it without me. The underlying code, methods, and evaluation framework stay mine.
03
That split goes in the agreement in plain language, not in a definitions section.
04
Clients appear on this page only with permission. Some never will.
/ CONTACT
Let's talk
Tell me what you're working on. If something in your operation eats a day a week and nobody can quite say why, that's the conversation.