The first two articles in this series set out a position and a standard: AI in finance is a responsibility problem before it is a capability problem, and the way to solve it is a system in which the model proposes, deterministic code decides, and a person owns the result. This article is about why we are qualified to hold that position.
We already run the systems the AI has to live in
Intelligent Forge Company is the engineering team behind several core systems in the production stack of Nimbus Payments, a US-based payment processing provider specializing in NetSuite-integrated commerce and a registered MSP/ISO of Elavon, Inc., a U.S. Bancorp subsidiary. Nimbus sells, supports, and owns the customer relationship. We design, ship, and operate the technology.
That work is multi-year and ongoing, and it covers the parts of a payments business where mistakes are expensive:
- NetSuite-integrated processing flows, with NetSuite as the system of record for invoices, customers, and payment events
- Customer-facing payment portals for one-time and recurring payments
- Card-present terminal workflows, orchestrated with compensating steps so a failed flow cleans up on its own
- ACH capture and automation built to NACHA operating rules
- Level II and Level III commercial card processing
- Tokenization, PCI scope reduction, and back-office reconciliation services
We did not learn about idempotency, reversible workflows, and audit trails from an AI project. We learned them from operating a processor's book of business without disruption while replacing the platform underneath it. The rules in the previous article are the rules that stack already runs under. AI is the newest thing that has to fit inside them.
We published the case against careless AI first
Our founder has written publicly and at length about where AI fails: the gap between the hype and what ships, the fiction of the average user that models are trained on, and the way a token bill becomes a measure of how little a company understood its own process before automating it. That writing is on the record, and it predates our AI implementation practice.
We consider that a qualification. A firm that spent two years documenting how AI goes wrong is a firm that knows what to check for. Nobody whose finance operation is at stake should want an AI cheerleader. They should want an engineer who expects the model to be wrong and has built the system so that it does not matter when it is.
What "responsible" means as a commitment
Three things, concretely.
We own outcomes, not deliverables. The engagement is not finished when the model returns an answer. It is finished when the process it sits in runs clean, with a cost that is known and a person who can explain any result.
We say no. The most valuable sentence in an AI engagement is "this part does not need a model." We will say it, and we will say it about work we would otherwise be paid to do.
We measure before and after. Every AI component is evaluated on the client's own history before it ships, and reported on per task after. If it does not clear the bar, it does not go live.
How to start
The lowest-risk first step is the AI spend audit: fixed fee, one week, a written report of where the AI budget is going, what is producing results, and what to cut. It is the same discipline we apply to cloud bills and payment-integration reviews, and it usually pays for itself.
For companies with a specific process in mind, the AI implementation practice starts with the process map described in the previous article and proceeds one edge at a time.
Either way, the conversation starts with the founder and is answered the same business day. That is not a funnel. It is the first instance of the principle this series is about: a named person, responsible for the result, from the first email.