How an engagement runs.

One audit, then one build. Both end in software a team can use Monday morning.

First: the audit.

Two to three weeks. I sit beside the workflow or the product surface and rank what’s worth shipping first, against the same honest criteria — fit, integration depth, last-mile owner, hours saved. The audit ends with a working prototype, a ranked list, and a recommendation.

Working prototypes beat decks. The audit ends with one.

Right phase when AI energy is high and clarity is low.

Then: one of two builds.

The audit ends with a recommendation. From there the engagement goes one of two ways — not both, not sequentially.

Operations Build

6–12 weeks

Inside the business.

A scoped agent on the workflow the audit ranked highest. Two weeks paired with the team that owns it, then a production agent shipped against the hours-saved baseline. Ships as a production agent with monitoring and handoff docs. Right phase when there’s obvious waste and an owner who’ll keep it.

Product Build

8–16 weeks

Inside the product.

Embedded with the product and engineering team. I shape the first feature, instrument it, ship behind a flag, and measure what changed. Ships as a launched feature with an outcome dashboard your team owns and a written brief on what to build next. Right phase when a real customer job needs a real AI feature.

How I work.

I ship software, not decks. The deliverable is working code in production. I sit beside the work for the first two weeks — the team doing the workflow knows where it breaks. I do fewer things, very well; a scoped agent shipped beats a platform vision shipped never. Every build has a baseline metric set in the audit and a target measured at 30, 60, and 90 days. The person scoping the work is the person close to the build. On launch day, your team owns the software — documentation, monitoring, and a written brief on what to build next, delivered with it.

How I scope and price.

I price by engagement, not by hour. The audit is fixed-fee, quoted after the first call. Builds carry a fixed weekly burn against a written scope and outcome — the weeks are the variable, not the price. Biweekly invoicing, Net 15.

Included is all my time and the working software at the end. Tools and infrastructure run on your accounts. Travel, third-party software licenses, and any subcontracted specialist work get flagged and quoted before they’re incurred.

Start a conversation.

If that’s the shape of what you need, the next move is a call to talk through your specifics.

Based in Houston, TX · working US-wide