Implement one finance AI use case.

Yes. These are defined workflow variants of the Pilot. We agree on the source systems, entities, users, refresh cadence and approval boundaries before building. You can enter directly if the use case is already clear.

Access and security approvals, source reconciliation, agreed evaluation cases and reviewer acceptance determine readiness. We define incident ownership, support hours and escalation before launch. Additional workflows and major data remediation need separate scope. Financial benefits that require repeated cycles are measured after initial acceptance.

Either complete a Sprint first (which produces a directional recommendation), or bring a use case you've already aligned on internally. The Pilot kickoff converts your candidate into a charter with locked success criteria. If we don't think the use case will hit ROI, we'll say so during scoping rather than after.

Two questions decide it. First, will more than one team adopt the system in this engagement? If yes, you're in Standard. Second, are you in a SOX-regulated environment, banking, insurance, or a context with audit-trail, model-documentation, or examiner-review requirements? If yes, you're in Standard regardless of team size.

We document honestly. The readout shows what was built, what was measured, and what the result was. Some pilots over-deliver on ROI and become flagship references. Some hit production but miss the projected ROI for reasons that surface during the engagement (data quality worse than expected, adoption slower than expected, market shift, etc.). In every case, you have a working production system, a documented baseline, and a clear next-step recommendation. We do not bill more if outcomes miss.

Not in a Pilot. Two or more concurrent production use cases is a Transformation. The Pilot exists to ship one capability well. If you need parallel workstreams, the right shape is the Transformation, which has the program structure to coordinate across them.

The embedded implementation team. Finance technologists, data engineers, and AI specialists who deliver production code in your environment. Glenn leads architecture and product decisions, the team handles execution. You can meet the team during scoping if useful.

The Pilot scope can include data infrastructure work, or the engagement can scope around what exists. Most Pilots involve some data engineering as part of the build phase. If your data is genuinely fragmented and undocumented, we'll surface that during scoping and decide whether to include foundation work in the Pilot or defer it to a separate engagement.

We work with your finance and technology owners throughout the engagement. Their involvement helps with system access, review, adoption, and a practical handoff. An Operations Retainer can provide support after the Pilot when ongoing monitoring or improvements are needed.

That's a feature. The Pilot's first two weeks include charter validation. If we surface that the use case is wrong (better candidate found, market shift, internal priority change), we'll recommend re-charter or pause and document the finding. The cost of changing direction in week 2 is much lower than the cost of shipping the wrong thing in week 12.