Lawrence Huibuilds AI · writes in public
01Home02Work03Projects04Writings05About06Resume07Email
01Work with methree ways in

AI agents that run in your infrastructure.

I build coding and ops agents that live inside your own cloud account, on your own model subscription, behind your own credential boundary. Teams call me when handing their infrastructure to a SaaS is not an option, and when the agent bill stopped making sense.

$600 → $125daily agent spend, after one audit
1.48Btokens audited in a single week
99.6%of that spend was input, not output
02Engagementsprices shown
01

AI-spend audit

Find out where your agent budget actually goes, and what it costs to stop.

You send a week of agent transcripts and the billing that goes with them. I send back a written report: where the tokens go, which sessions are responsible, what to cut, and what the cut is worth per month.

I ran this on my own usage first. 1.48 billion tokens in seven days, 99.6 percent of it input. One session was reading four novels' worth of context to write a single reply, every turn, for five days. Fixing it took the daily cost from $600 to $125 on the same workload.

The tooling I built for it is open source, so you can check the method before you pay for it.

Book an audit
£950fixed price, one week
02

Agent install

A working coding agent in your Slack, running inside your own cloud account.

Deployed to your AWS, on your own Claude or Codex subscription. Nothing routes through me and nothing routes through a vendor.

Credentials sit behind the tool layer. The model holds a tool name and never a key, so a prompt injection cannot turn into a breach.

Work comes back as a pull request. You review a diff instead of discovering an action that already happened.

This is Citio. It is open source, it is running in production, and you can read the whole design before you hire anyone.

Scope an install
from £3,500fixed scope
03

Fractional

Keep the agents running once they are in, without hiring for it.

Capped days each month. I maintain the deployment, audit the spend, and add capabilities as the models change underneath you.

Model releases break assumptions every few months. Someone has to own that, and for most teams it is not worth a headcount yet.

Talk about a retainer
from £400/mocapped days, rolling
03How it is builtthree decisions

Credentials never reach the model

Tokens live behind the tool layer. The agent asks for an action by name. It never sees the key that performs it.

The unit of delegation is a pull request

An agent that acts directly is an agent you have to trust blindly. A diff is something a human can approve in thirty seconds.

It runs on your subscription, in your account

No metered API in the middle. The worst case of a runaway loop is a rate limit, not an invoice you find out about later.

Start with the audit if you are not sure.

It is one week, it is priced, and it tells you whether the rest is worth doing. Tell me what you are running and I will tell you if I am the wrong person for it.

hello@lawrenceh.xyz