Work
Systems that are
running right now.
Clients are described by industry and situation, never by name. The numbers below are the ones the businesses themselves confirmed — where a number would have to be invented, there isn't one.
In production
Built, shipped, still running.
RFP response automation
Every incoming RFP arrived written around competitor part numbers, and someone on the sales team had to translate it line by line — two to four hours for a large one. A knowledge base maps the competitor catalog to their own products; the system does the substitution and flags anything it is not sure about.
Intelligent expense management
A retiring CFO was the only person who knew how to code the company’s transactions, and the sales team spent company money with almost no visibility. The system encodes the coding logic, flags outliers, parses receipts, and captures state sales tax — which turned out to matter more than anyone expected.
In the field now
Three more systems with real users behind them. Full write-ups follow once there are results worth reporting rather than guesses worth hedging.
A Twin Cities restaurant group
Reviews across every location, aggregated and pushed out as briefings the operators actually read: a weekly pulse across the group, a monthly deep dive on individual locations, and a quarterly competitor analysis. Nobody pulls a report, and nobody has to remember to look.
Misen and TenetA concrete-leveling contractor in Minnesota
A phone-first business losing jobs to voicemail and slow estimates. The build is a capture surface for incoming leads plus agent-drafted estimates that wait for the owner’s approval before anything goes out — running on ForgeField, with the owner’s own pricing behind it.
ForgeFieldAn event-services provider
The booking lifecycle for event work — inquiry, quote, confirmation, schedule, day-of prep — held in one system instead of a notebook and a good memory. It is now moving onto the same agent runtime behind ForgeField, so each step advances on its own and stops for a human where a decision matters.
SimplyEngagingHow these get built
Every one of these started with the same conversation and the same discipline: requirements interrogated until the ambiguity is gone, work decomposed into tasks with binary success criteria, and nothing merging until it passes both an automated gate and an independent reviewer whose job is to refute it.
This website was rebuilt the same way — including a verification gate that has gone red on my own work and blocked it. That ledger is public →
Have a problem worth solving?
The best way to find out whether this applies to your situation is a straight conversation about it.
Get in touch