The handover is the product
Handover should leave your team able to run and change the system without us. That means code, runbooks, decision records and rehearsal.
ReadInsights
Notes from the work itself.
Practical notes on AI-first engineering, software architecture, security and delivery, written for the people who have to decide what gets built and who pays for it when it goes wrong.
Rollback plans for models
You can revert a model quickly. The hard part is deciding what to do with the output it already wrote, sent, or used.
ReadWhat a written definition of done actually contains
A useful definition of done settles delivery arguments. It states behaviours, data, interfaces, numbers, boundaries and acceptance.
ReadFraud detection was the first agent, we just did not call it that
Fraud systems show how to govern agents: use challenge paths, reason codes, expected-loss queues, holdouts and hard limits.
ReadHow to estimate work nobody has done before
Fixed price works when estimates separate known work from real uncertainty and price discovery before commitment.
ReadHIPAA and the model, what you may and may not send
HIPAA model projects need clear data categories, BAAs when PHI leaves, strong de-identification, and an audit trail showing what the model saw.
ReadWhere your data actually goes when you call a model
Most teams know their model provider. Fewer can say what sensitive text crossed the boundary, who could read it, and where copies remain.
ReadThe cost curve nobody models
At AI production scale, pilot pricing breaks. Input tokens, retries, retrieval quality and human review decide whether the unit cost works.
ReadObservability for a system that is sometimes wrong on purpose
A probabilistic system can be confidently wrong while every health metric looks normal. Track movement, inputs, versions and human review.
ReadSecrets, agents, and the blast radius of a leaked token
A leaked agent token lets an attacker act across systems at machine speed, so credentials need narrow scope, short lives, real rotation, and honest…
ReadNext step
Reading because you have a project in mind?
A senior engineer reads every enquiry and replies within one business day with an honest assessment, including when we think you shouldn’t build it. No sales call, no deck.
