[02] AI in the loop · Austin, TX · Remote US
I make AI a working part of how your engineering team builds software, not a demo. As a fractional CTO I embed with the org, install the workflows, and measure the result in team-wide proficiency and cycle time. I run the same stack on my own product, PeptIQ, every day.
What gets installed
The goal is not one hero engineer with a fast laptop. It is a whole team that ships faster with the same quality bar.
How it runs
[01]
Discovery of the codebase, delivery process and current tooling. Agree on the metrics we will move.
[02]
Workflows, skill files, review gates and cost controls go in. I pair with the team until it sticks.
[03]
Proficiency and cycle time reported against the baseline. The team runs it without me.
Proof
PeptIQ runs on iOS, Android and web. I built it and run it with an agent stack, and the live telemetry is public on the /now page. Client engagements are confidential; the work below is what I can show.
Founder, product and engineering
Peptide tracking for people running protocols who want data instead of guesswork. Dose logging, phase goals, check-ins, stock and vials, Apple Health and Google Fit sync, calculators, and a moderated community to compare notes against. iOS, Android, and web.
Fractional CTO, AI enablement
Embedded with engineering orgs to make AI a working part of how software gets built, not a demo. Agent workflows, skill files, review gates, and cost controls that the teams own after I leave. The measure is proficiency across the whole team and shorter cycle time, not one hero engineer with a fast laptop.
Fractional CTO
An AI legal platform for law firms in Mexico, Panama, and Colombia: drafts contracts for attorney review, answers client email, writes filings, and researches the law. Fractional CTO on platform, security, and accuracy as the product moves from waitlist to firms.
I embed with the engineering org and make AI a working part of how software gets built, not a demo. That means agent workflows, skill files, review gates, verification loops and spend controls the team owns after I leave. The measure is proficiency across the whole team and shorter cycle time, not one fast engineer. I run the same stack on my own product, PeptIQ, and publish the live telemetry on the /now page.
Daily and hands-on. I build with coding agents, design prompt and retrieval systems, and take pilots to production with guardrails, evals and cost controls. As a fractional CTO I have embedded AI into client workflows for automation, moderation and analytics. PeptIQ, my own product on iOS, Android and web, is built and run with an agent stack.
Most engagements run 1 to 3 days a week. We start with a short discovery of the architecture, team, delivery process and costs, agree on a 90-day plan with owners and checkpoints, then run a weekly operating rhythm with visible metrics. Engagements are scoped by the quarter and renew if the numbers say they should. Advisory can be a few hours a month. Scope, cadence and pricing are written down before we start.
Send a note through the contact page or book a 20-minute intro. Tell me the goal and the constraint. You get a short written proposal with scope, cadence and pricing. Advisory can start right away; larger programs usually start within one to two weeks.
Next move
Tell me where the team is today and what you want cycle time to look like in a quarter. You get a written plan with scope, cadence and pricing.
See also: fractional CTO engagements, resume, how I operate, and contact.