Slate71 builds that software, one company at a time, into the system the company already runs, on the one workflow where its office's time goes. Anvil is the platform it is built on.
In production
A California pest-control company has filed its termite inspection reports through Anvil since August 2026, the first system Slate71 built on it. The inspector talks through the property on an iPad, draws the diagram on the same screen, and taps submit. The report, its findings and the diagram are in the office's Salesforce under a minute later. The office reviews it there and sends it, the way it always has.
All four of the company's inspectors use it every day. In September, 164 of 165 reports were filed the same day as the inspection. The office's own handling of a report went from 20 to 30 minutes to 5 to 7, by the office manager's count.
The day counts come from the company's own Salesforce history, 5,383 reports from January 2025 to the cutover. The seconds are measured by the system.
How it is built
A language model turns the spoken walkthrough into the report's typed fields. It can only choose from the company's own list of finding codes, so it cannot invent one. When it is unsure it flags the finding instead of guessing. Every extraction is stamped with the model and the prompt version that produced it, so any line on any report traces back to what made it.
The office keeps the last word. Anvil writes each report once and never overwrites an edit. It writes only the fields an inspection produces and never touches the company's own automation. It cannot delete anything; its permissions do not allow it. One setting turns it off.
Every correction the office makes becomes a test. Before any change ships, the system is run against every case the company's own work has produced, so the same mistake cannot come back.
Working with Slate71
It starts with a week on site, watching how work moves through the company and writing it down. From that comes one workflow to build first: the one where a messy input, spoken, on paper, in a form or an inbox, has to become a document somebody signs or files.
The build is fixed in scope and priced up front, four to eight weeks, and runs alongside the current process until the office signs off. Then a monthly fee to run it, sized to the volume it carries. Lukas works directly with the owner and the people doing the work. There is no account manager and no team to brief.
It is for companies with enough volume that finished work queues up as office work. A company that handles a few of these a month does not need it.
Who
Twelve years of engineering in San Francisco before Anvil. Seven at HouseCanary, leading the team behind a data platform that drove 40% of the company's revenue. Engineering lead at Airbyte. Intel before that. Slate71 was founded in January 2026 and the first system on Anvil went live in August.
Talk
Lukas will say within a day whether it is a fit and what it would cost.