The firm we wished existed when we were inside the controller's office.
Firmcraft was started by a CPA who became an ERP consultant who became an AI builder — in that order. The differentiator isn't the technology. It's the path through the technology that someone who's been on the other side of the table can see.
Process fluency, not technology novelty.
The reason AI projects fail at SMBs isn't the model. It's that the person scoping the work has never closed a month, never sat in a fit-gap, and doesn't know what a chart of accounts smells like when it's been mishandled for four years.
Firmcraft is a firm built around the inverse. The principal is a CPA who spent the last seven years inside Microsoft Business Central engagements at one of the larger Dynamics partners — and the last two building eval harnesses, Monte Carlo simulations, and Bayesian models on his own time.
That's the shape of the engagement. We sit across from your controller, debate revenue-recognition treatment, then go build the LLM eval harness. Same person, same day. That's not a slogan — it's the operating constraint.
Four pivots. One throughline.
CPA · Big-4 audit
Audit and assurance. Where the obsession with reconciled numbers and process traceability got installed.
Industry controller
Mid-market manufacturing. Owned the close, the audit, the ERP rollout. Where the empathy got installed.
ERP Consulting
Microsoft Business Central implementations across field service, manufacturing, and operations. Day job. Where the process-first reflex got sharpened on real engagements.
Builder · Hermes / Firmcraft
Claude Code, eval harnesses, Monte Carlo, Bayesian inference. Built Hermes. Then built the firm around it.
Four things we won't trade.
These aren't values for the careers page. They're decisions that come up in every Build engagement, and they have to be defensible in front of a CFO, an auditor, or a procurement team. So we publish them.
Process before tool.
We map the workflow before we pick the vendor. Half our Assessments end with us telling the buyer they don't need an AI — they need three Power Automate flows and a clean COA. That answer is part of the deliverable.
Sovereign by default.
The default is Hermes, in your walls. We'll route to a frontier model when it's the right tool and the data-handling terms are clean. We won't quietly route there because it's faster for us to build.
Fixed-fee where it matters.
Build engagements are fixed-fee with dated delivery. The hourly work is reserved for genuine out-of-scope and change requests, logged and approved before it's billed. No buffer-burn at the end of a sprint.
One engineer, one engagement.
The person who scoped your Assessment is the one who runs your Build, who shows up on the standup six months in. We don't do account-handoffs. The whole firm is sized around that constraint.
Hermes. The open-source LLM foundation Firmcraft is built on.
Hermes is the open-source LLM, retrieval pipeline, and observability layer we deploy in every Build engagement. It runs in your VPC or on-prem. We maintain it, you own it. If we disappear tomorrow, your operator keeps running.
The vendors in our standard kit.
The Assessment ends with a vendor matrix tuned to your engagement. These are the partners we know best — where we have working integrations, eval harnesses, and a phone number we can call if something breaks at 11pm.
ERP & Platform
AI & Workflow
Finance Automation
Voice & Support
Productivity
Data & Infra
The workforce training arm: SkillCalibrate.
Where Firmcraft installs AI into the operating layer of an SMB, SkillCalibrate trains the people working alongside it. Same shop, same standards. If your engagement needs people-side enablement, that's where it goes.