Lukas Andersen
Since August 2026 a California pest-control company has filed its termite inspection reports through a system I built and run. The inspector talks through the property on an iPad and taps submit. The state report, its findings and the diagram are in the office's Salesforce under a minute later. Before, the report reached the office a median of one day after the inspection, and four days at the ninetieth percentile.
All four of the company's inspectors use it every day. The office still reviews every report before it goes out, and every correction they make becomes a test. They pay for it.
One fixed-scope build at a time, four to eight weeks, priced by the week. The shape I know: a messy input, spoken, on paper, in a form or an inbox, that has to become a document somebody signs or files, written into the system the business already runs.
How it is built: narrow typed steps rather than a chatty agent. The model can only choose from the business's own vocabulary. Every output is stamped with the model and prompt that made it. A test suite built from real cases gates every change. The system never deletes anything, and one setting turns it off.
I work directly with the owner and the people who do the work. No account manager, no team to brief.
Twelve years of full-stack engineering in San Francisco. Seven at HouseCanary, where I led the team behind a data platform that drove 40% of the company's revenue. Engineering lead at Airbyte. Intel before that.
Anvil, the company I run, is the vehicle for this work.
If you have a workflow of that shape, write and describe it in a few lines. I'll tell you within a day whether it is a fit and what it would cost.
lukas@lukasandersen.com (510) 621-6620