From sandbox to a first live pack —
in weeks, not quarters.
A practical checklist for running an AssureLocker pilot. You keep every credit decision and all custody of funds; we supply the evidence and risk signals that get you there faster.
What you bring
- A ring-fenced set of real deals to evaluate (sandbox first, then production-style)
- A credit/risk owner and a technical contact for integration
- For live privileged signals: your own AA-FIU and CERSAI membership + DSC (used inside your boundary via AssureConnect)
- Your decision criteria — so we can shape the pack to your book, not ours
What we bring
- A verified Risk Signals / Verified Receivables Pack on every deal — as JSON, API or a human-readable PDF
- The assessment room (orchestrator, interrogator, analysis, report) with an AI assistant guiding the borrower
- API, HMAC webhooks, idempotency and an LMS decision-event + disbursement-ready packet endpoint
- AssureConnect lender-side connectors that return signals and discard raw records
A phased plan
1 · Scope & sandbox
Agree the deal set, signals and thresholds. Run the pack in a deterministic sandbox on fictional data — no integration required to see the output.
2 · Connect (lender-side)
Stand up AssureConnect inside your boundary for any privileged rails (AA, CERSAI, CKYC). Sandbox keys first; production credentials only when you're ready.
3 · Shadow run
Generate packs alongside your existing process on real deals. Compare what the pack surfaces against what your team would have caught — and when.
4 · Production-style
Run under your own controls with the LMS packet wired to your system of record. You make every credit decision; we never do.
Indicative timeline; actual pace depends on the deal set and which privileged rails are in scope.
Shadow pilot
Test the pack before it touches production decisions
A shadow pilot lets your team measure evidence coverage, false positives, reviewer effort and time-to-evidence while your existing credit workflow remains the system of record. AssureLocker surfaces signals; your team records whether to accept, challenge, request more evidence or resolve each finding.
Historical cases
Replay closed deals, including clean and stressed files, to compare what the pack would have surfaced and when.
Synthetic edge cases
Use deterministic fictional cases for duplicate-financing, related-party, missing-evidence and source-unavailable scenarios.
Controlled-live cases
Run packs beside the current credit process with no decision automation; the lender reviewer records how each signal was treated.
How we’ll know it worked
- Time-to-evidence: hours, not days, per deal
- Risks surfaced earlier — duplicate-financing, related-party, capacity and shell-company signals before commitment
- Analyst effort saved per deal vs the current manual process
- A clean audit trail and evidence-tier labelling your auditors can rely on
Throughout the pilot, AssureLocker supplies signals and evidence only. It does not lend, hold or move funds, set advance rates or make the credit decision — your system of record does.