Start with the operating reality
Banks do not buy AML software the way startups buy SaaS. The first useful conversation is operational: entities, jurisdictions, alert volumes, where work stalls, and which capability removes the most friction first.
A quote discussion that stays in feature language usually ends in ambiguity. A discussion that produces a scoped path ends in a decision.
Questions that matter early
- How many legal entities and jurisdictions are in scope for phase one?
- Where do alerts currently stall — detection, triage, or investigation?
- Do you need screening, case management, or scenario detection first?
- Which source systems must integrate before value appears?
- Who owns dispositions today, and what does “done” mean for a case?
- What audit artifacts do supervisors already expect?
These questions sound simple. They prevent months of “we assumed.”
Custom does not mean vague
Custom scoping should increase precision, not widen the story. Banks buy clarity: data sources, roles, SLAs, environments, and a phased path. Feature checklists without operating constraints are marketing, not delivery.
Write the phase-one boundary down. If everything is phase one, nothing is.
A practical phase-one shape
Most banks start with the capability that removes the most friction — often case investigation plus screening search — then expand into scoring and richer detection scenarios. That sequence is not universal, but it is common for a reason: it improves daily work while the data model hardens.
Phase two can deepen detection and scoring once investigation quality is visible. Phase three can expose decisions through APIs once the loop is trusted.
What a good quote response looks like
A strong response is not a brochure. It names assumptions, integrations, roles, and the first measurable outcomes — time-to-disposition, reopen rates, match quality, analyst confidence. Fatcon engagements are scoped that way on purpose: regulated institutions need a conversation, not a public self-serve signup.