Skip to content
Evaluation guide

A structured way to evaluate AMIN.

Four tracks, clear questions and explicit outputs — so compliance, technical and business reviewers reach a decision on evidence, not on promises.

See the four tracks
Enterprise evaluation

Evaluate AMIN
with evidence.

Review the product, controls, architecture and operating model before you decide.

Get the information your technical, compliance and business teams need to evaluate AMIN with confidence.

  1. 01ProductSee workflows and product surfaces for staff, clients and governance.
  2. 02ControlsReview security, governance and control boundaries.
  3. 03ArchitectureUnderstand platform architecture, integrations and deployment options.
  4. 04Use casesEvaluate AMIN against your operating requirements and real-world scenarios.
Evaluation Product overviewEvaluation environmentSynthetic demo data
Product evaluation

Explore AMIN in a guided tour.

See key workflows, sample data and real-world scenarios across staff, client and governance experiences.

Start product walkthrough
Client Onboarding
  1. 1Submit
  2. 2Review
  3. 3Verify
  4. 4Approve
Client information
Sanctions screeningUN listClearOFACClearEUClearUK HMTClearUAE LocalClear
  • Client OnboardingEnd-to-end flow
  • Risk ScreeningSanctions alerts
  • Case ManagementInvestigation & approval
  • ReportingAudit packages

Guided evaluation

Structured content for technical and business teams.

Realistic examples

Synthetic sample data and use cases relevant to your work.

Decision-ready evaluation

Give technical, compliance and business teams the context they need.

The four tracks

What to ask in each track.

  • 01 · Product

    Walk through the staff, client and governance surfaces with synthetic data.

    • Does the Staff Workspace match how our team works?
    • What will our clients see and do in the portal?
    • How are decisions and approvals recorded?
    Platform overview
  • 02 · Controls

    Review security, governance and control boundaries with your security and compliance teams.

    • How are tenants and roles separated?
    • What is in place today, and what is agreed in scoping?
    • What evidence can be exported for review?
    Enterprise trust
  • 03 · Architecture

    Understand the platform, its integration surface and the deployment model.

    • Which systems need to integrate, and how?
    • Where will data be hosted and kept?
    • How do the 12 capability areas map to our needs?
    Capability architecture
  • 04 · Use cases

    Test AMIN against your operating requirements and real scenarios.

    • Which programme do we start with?
    • What does a complete decision record look like for us?
    • Who owns each step after go-live?
    Solutions by use case
RFP checklist

Questions to put to any compliance platform.

Use them in your RFP or vendor evaluation, for AMIN or any other platform. Ask for evidence, not assurances.

  • Governance

    How the platform enforces your operating model.

    • Can workflows, roles and queues follow our policy?
    • Who can change configuration, and is every change recorded?
    • How is each decision linked to the policy that applied?
  • Decision authority

    Who can decide what, and how that is enforced.

    • Can approvals be scoped by role and decision type?
    • Can any decision be made without a named person?
    • What does AI do, and what is it never allowed to do?
  • Evidence

    What is kept for every decision.

    • Is the rationale stored with the evidence it relies on?
    • Are documents and screening results kept in the version used?
    • Can evidence be exported in a verifiable form?
  • Auditability

    Reconstructing what happened, later.

    • Are human and system actions on one audit timeline?
    • Can a decision be reconstructed without the people involved?
    • How long are audit records kept, and can they be altered?
  • Data boundaries

    Where data lives and who can reach it.

    • How are tenants, clients and roles separated?
    • Where is data hosted, and who decides?
    • What is in place today, and what is agreed in scoping?
  • Multi-client operations

    For firms that run compliance for many clients.

    • Does each client have its own record and portal?
    • Can the team work across all clients from one queue?
    • How are clients prevented from seeing each other’s data?
  • Evaluation questions

    How the evaluation itself will produce evidence.

    • Will we see the product with data shaped like ours?
    • Which capabilities are current, and which are confirmed in scoping?
    • Which integrations exist today, and which would be built?
    Point solutions vs a Compliance OS
  • Take it into your RFP

    Every question in one spreadsheet, with columns for vendor responses, evidence and scoring. Free, no form.

    Download the checklist (Excel)
How an evaluation runs

From first call to a scoped decision.

  1. 1. DiscoveryShare your operating model and priority use cases.
  2. 2. WalkthroughA focused product walkthrough with synthetic data.
  3. 3. Controls reviewSecurity, governance and deployment review.
  4. 4. Scoped outputsExplicit scope, evidence, ownership and architecture outputs.
Get started

Start your evaluation with the team.

Tell us which track matters most to your reviewers. We will prepare the walkthrough and material around it.

  • Tailored to your organisation
  • Focused on your use cases
  • Synthetic data — no client data needed