Automation · Process design · AI integration Willamette Valley, Oregon · Taking work

I build the systems that do the work you keep doing twice.

Automation, process design, and AI integration for small operations. You own what gets built — source, keys, and documentation. No subscription keeping it running, and no shortage of help when your process changes.

Start a conversation See how it runs

The Waybound astrolabe mark — a gold compass rose inside concentric rings,
crossed by a sighting arm

Your dataStays in your systems

EngagementScoped, fixed price

Built onTools you already pay for

You keepSource, keys, docs

What I do

Custom tools, shaped around the way you already work.

Every engagement starts with the actual process, not the one in the handbook. The aim is a tool that fits the business as it runs today and can be adjusted as it changes.

01Process design

Built around how you already work

The tool should fit the process, not the other way around. That starts with documenting what actually happens — including the steps that only work because someone remembers them — so what gets built reflects your business rather than a template someone else was sold.

Current-state walkthrough
The real process, written down
Where a tool genuinely helps, and where it doesn't

02Automation

The repetitive work, handled

Scripts, scheduled jobs, and integrations that move information between the systems you already pay for. Built to be readable rather than clever — the version someone can still understand in a year is the version that still works in a year.

Data pulls, reports, and scheduled runs
Integrations across existing systems
A plain-language runbook for each one

03AI integration

AI builds it. Whether it runs it is your call.

AI is how these tools get designed, written, and tested — that's what makes a genuinely custom tool affordable at your size. By default what ships is ordinary software on your own systems, and your data never goes near a model. If you do want AI working inside the business, that's work I take on gladly — built deliberately, with a human check on anything it produces and a data-handling policy agreed in writing before a single thing is connected. Either way it's a decision you make, not one you inherit.

AI accelerates the build, not the running of it
By default, no client data leaves your systems
Want AI in the workflow? Built deliberately, policy first

04Ownership & evolution

Yours to keep, and built to change

You own what gets built — source, credentials, documentation — outright, with no monthly fee keeping it switched on. Owning a tool isn't the same as being left alone with it, though. Processes move: a new vendor, a different approval, another entity to report on. These are built so that those are adjustments rather than rebuilds, and I'm here to make them when they come.

Ownership and credentials transferred outright
Designed to be adjusted, not replaced
Support when the process changes — no retainer required

How it runs

Three phases, and you know the cost before the second one starts.

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.

Phase 01Discovery

Engraving of a steamship working through heavy seas

Chart the water

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.

You getScope & fixed-price proposal

Phase 02Build

Engraving of a sextant and dividers resting on a nautical chart

Plot the course

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.

You getThe working system, plus its runbook

Phase 03Handover

Engraving of a sailing vessel on flat calm water at the horizon

Hand over the helm

Documentation, ownership, and credentials transferred, and my standing access closed. You're able to run it without me — and when the work changes, I'm here to adjust it. Continuing help is available whenever you want it, and never a condition of owning what was built.

You getOwnership, documentation, and an open door

Proof

I'd rather show you my own tools than talk about someone else's numbers.

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.

Tool 01Markets

Dross

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.

Scheduled data collection and scoring
Vision-model enrichment where text fails
Runs unattended, reports when it matters

Tool 02Real estate

Rent Survey Scraper

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.

Weekly manual task → scheduled run
Consistent format, week over week
The kind of thing most offices still do by hand

Contact

Tell me what you're doing twice.

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.

● I answer every one myself

● Usually within a business day

● NDA before anything sensitive