I live here. An in-person working session is a drive, not a flight and an expense line — and the AI question looks different in this market than it does anywhere else, because of what this city actually does for a living.
Uptown is a banking town, and in a regulated institution "who is accountable for this model's output" isn't a CFO question — it's an examiner question. The answer has to survive a third party reading it cold, months later, without you in the room to explain it.
Smaller teams, the same regulatory weight, a fraction of the governance staff. AI usually arrives through a core provider or a vendor bundle rather than a deliberate purchase — and the accountability arrives with it, whether it was scoped or not.
Charlotte moves freight and makes things. AI shows up in forecasting, routing, quality and maintenance — where the value is genuinely measurable, and therefore genuinely provable. That's the easiest place to build an ROI story that survives scrutiny.
In most industries the AI accountability question is asked by a CFO who wants to know whether the money worked. In a regulated financial institution it's asked by someone with statutory authority, and the standard of proof is different: not "do you have a policy," but "show me the inventory, show me who owns each system, show me the evidence you reviewed it."
That's a documentation problem before it's a technology problem — and it's exactly what a two-week diagnostic produces. The inventory, the ownership map, and the review cadence are the three artifacts an examiner asks for, and most institutions discover they can't produce them on demand.
Community banks and credit unions carry a particular version of this. The regulatory expectation doesn't scale down with headcount, but the governance staff does. AI capability that arrives bundled inside a core banking platform or a vendor product is still your accountability — and it's the hardest kind to inventory, because nobody chose it deliberately.
Why local matters here, and not everywhere.
The Diagnostic runs on interviews — four to six conversations with department leads. Done in a room, those conversations surface the shadow tooling that a video call does not, because someone mentions the thing their team has been using since spring and two other people look up. If you're in the Charlotte region, that's how I'd rather run it. And if you're not: the work runs remotely just as well, and most of it always has. Location changes the logistics, not the work or the price.
Thirty minutes, no deck — what's on your desk, who's asking, and whether this is even the right work.