Automation, process design, and AI integration for small operations. You get the tools, the documentation, and the keys — not a standing dependency on me.
Every engagement starts by watching the actual process, not the one in the handbook. What gets built after that depends on what's really slowing you down.
Most broken processes aren't broken — they're undocumented, and they live in one person's head. I write down the real one, find the steps that only work because someone remembers, and put a trigger where the memory used to be.
Scripts, scheduled jobs, and integrations that move data between the tools you already use. Small, boring, and reliable beats clever. If it can't be explained to the person who inherits it, it doesn't ship.
AI is good at reading, sorting, drafting, and summarizing. It is bad at being trusted without a check. I build the useful parts and the check that goes with them, and I put the data-handling policy in writing before anything is connected.
Automation leaves things behind: scripts, keys, scheduled jobs, accounts. At close-out you get all of it, documented, with my access revoked and shown to be revoked — plus a straight answer about what to do if it breaks in six months.
Nothing gets built before we've both written down what "done" means. The scope, the price, and what's explicitly not included are settled in phase one.
A call and a walkthrough of how the work happens today, what it costs you in hours, and what "fixed" would look like. Mutual NDA before anything sensitive changes hands. The output is a written scope with a real price on it.
Contract signed first, then the work starts — never the other way around. I build against the written scope, in the open, with one place you can look to see where things stand. Changes get priced as changes, not absorbed quietly.
Documentation, ownership, and credentials transferred. My access closed and shown closed. If you want me around after that it's a new, separate arrangement — the goal is that you don't need one.
Client work stays confidential, which makes for a thin portfolio and a lot of vague claims. So here's what I've built for myself instead — same problems, same methods, and I can show you the inside of any of it.
An options and stock-flow tracker that watches a few dozen accounts, scores what it finds, and reads the charts it can't parse as text. Built because doing it by hand every morning was an hour I wasn't going to keep spending.
A market rent survey for multifamily operators that used to be a weekly manual grind — open the sites, copy the numbers, rebuild the sheet. Now it's a scheduled job and a finished comparison waiting on Monday.
First conversation is a real one, not a pitch — what the process looks like now and whether it's worth automating at all. Sometimes the answer is no, and that's a fine outcome for both of us.
Half an hour, over video, and you'll get the link with the invite. If you'd rather meet in person, say so in the form above — I'm in the Willamette Valley most weeks.