Resolve the parties, assemble the checks and draft the engagement letter from your approved templates — with acceptance, risk rating, screening decisions and signature left to the people authorised to make them.
Ingest new-client and new-service requests from supported intake, CRM or practice-management sources.
02
Normalise the entity, the service actually requested and the jurisdiction it falls under.
Reason
03
Resolve the party list — entity, directors, beneficial owners and connected parties.
04
Assemble identity, ownership, conflict and screening evidence against each named party.
05
Draft the letter by selecting approved clauses for that service, entity and jurisdiction.
Decide
06
Score file completeness and flag every unresolved match, gap and expiring document.
07
Route acceptance, risk rating and screening matches to the people authorised to decide them.
Out
08
Retain the party list, searches run, hits, clause sources and every human decision.
09
Issue letters and open files only inside the approval boundaries agreed during implementation.
→Product statement
The agent drafts, checks and assembles inside the approval boundaries agreed during implementation; acceptance, risk rating, screening decisions and signature stay with authorised people.
Example workflow
One new client, end to end
AgentHuman
1Request receivedReferral, enquiry form, CRM record or a new service for an existing client
2Parties resolvedEntity, directors, beneficial owners, connected parties and the service actually requested
3Checks assembledIdentity and ownership evidence, conflict search, sanctions and PEP screening, adverse media
4Letter drafted and checkedScope, fees and exclusions from the approved template, then conformance, expiry and completeness checks
No human action required
Stages 1 to 4 run without a person in the loop — nothing has been accepted or sent yet, so the lane stays empty until the gate.
5DecisionSplits on the completeness and risk-flag gate
Complete and clear
Goes forward as a pack ready to approve.
Flagged or incomplete
Held for the risk owner or the MLRO.
Acceptance decision
The pack is held with its party list, evidence, screening hits and clause sources.
Accept · Amend · Escalate
Accepted — handed back▼
6Letter issued, then file openedAn authorised approver accepts and the letter goes out; the file opens when the signed copy returns
7Outcome evaluatedTemplate conformance, scope accuracy, screening precision, time to onboard and re-acceptance completeness
Amendments
Clause edits and declined acceptances are counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Accepting the client or the engagement.
The client's money-laundering risk rating.
Clearing or accepting a screening match.
Conflict and independence conclusions.
Automation boundaryAgent acts unaided
✓Resolve the party list and gather ownership evidence.
✓Run conflict, sanctions and PEP searches and present the hits.
✓Draft the letter from approved template clauses.
✓Flag gaps, expiries and unresolved matches for the approver.
Letters are issued and files opened only inside the approval boundaries agreed during implementation.
Any clause outside the approved template set.
Fee terms, caps and liability limits.
Signing or countersigning the letter.
Annual re-acceptance and disengagement.
Example output
One onboarding pack, annotated
Everything the agent drafts is attached to the clause it came from.
Onboarding pack · single clientIllustrative example
Prospect
Service requested
Origin
Drafted from
Completeness
Held for decision
Newly formed holding company
Annual accounts and tax
Referral
Accounts template v4
92%
Sanctions name match
As receivedTaken from the enquiry as it arrived — the agent does not infer an entity or a service.
Evidence usedRegistry ownership filingApproved clause libraryScreening provider hit
Why it is heldA name in the ownership chain matched a list. Only a person may clear or accept it.
ActionAcceptAmendEscalate
What the score decidesBelow the threshold the pack goes back for missing evidence instead of to an approver.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
All new engagementsFrom your intake channels
03Drafting
Apply the firm's own templates
Draft from the approved clause library, the firm's acceptance policy and prior terms.
01Approved path
Shorten the onboarding wait
Routine, lower-risk onboarding arrives assembled instead of built by hand.
02Human review
Put partners on the difficult files
Screening matches, layered ownership and non-standard terms reach a decision-maker instead of every file doing so.
04Build an evidence trail
Retain the party list, searches run, hits, clause sources, evaluator result and the approver's decision — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Practice management & CRMKarbon · Canopy TaxDome · Client and billing records
AML / KYC screeningSmartSearch · Amiqus · First AML Sanctions and PEP lists · Adverse media
Registries & conflictsCompany registries · Ownership filings Your client and party register
Agent
Engagement letter & onboarding
Resolves parties Assembles evidence Drafts from templates
Sole traders on standard terms clear without incident, while layered ownership, non-resident parties and trusts account for most of the clause and screening failures. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Layered ownership structures
5.4%
3.3×
Review
Non-resident clients
4.1%
2.5×
Review
Trusts and partnerships
3.0%
1.8×
Watch
Sole traders, standard terms
1.0%
0.6×
Normal
Bar: lift vs. standard-terms baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
No change ships without the risk owner
A letter's wording is contractual and its thresholds are the firm's own policy, so the loop cannot close inside the agent — every fix is re-approved first.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendments, sent-back packs or dismissed matches rise in a cohort.
02Diagnose
Traced to the party list, a clause mapping, a screening threshold or intake.
03Improve
The clause or threshold is re-approved by the risk owner and version-linked.
04Verify
Re-run over past onboardings, including every pack that was amended.
05Learn
The amended clause becomes the template and a standing check.
Learn → DetectThe return edge. Next year's re-acceptance runs against the clauses this cycle approved.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, clause library, agent workflow, evaluation, integration, then a supervised onboarding and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Acceptance workflow and approval-boundary definition.
02Screening-provider and system assessment.
03Service, entity and jurisdiction scoping.
04Approved template and clause-library mapping.
05Party resolution and evidence assembly.
06Conflict, sanctions and PEP search integration.
07Acceptance and sign-off workflow.
08Document and e-signature integration.
09Evaluation suite and regression cases.
10Guardrails and template-conformance controls.
11Observability and trace instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne service lineProductionProduction integrationAdvancedMultiple offices / entities
Introduced at Pilot
Letters drafted from your templates✓✓✓
Acceptance sign-off✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Conflict and screening assembly—✓✓
Risk-flag routing—✓✓
Approved issue and file opening—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Multi-jurisdiction letters——✓
Multi-stage acceptance——✓
Annual re-acceptance cycles——✓
Enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on services and jurisdictions in scope, screening providers, onboarding volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01The services, entities and jurisdictions in scope→Service, entity and jurisdiction scopingWeek 1
02Your acceptance policy and who approves what→Approval-boundary definition and acceptance controlsWeek 1
03Your approved letter templates and standard terms→Template and clause-library mappingWeek 2
04Access to practice management, registries and screening→Source-system and screening-provider assessment, then integrationWeek 2
05Your client risk-rating criteria and escalation rules→Risk-flag routing, guardrails and the escalation path to your MLROWeek 3
06Past onboardings, including the ones that went wrong→Evaluation suite, regression cases and failure-mode testingWeek 4
07Named approvers and a signing authority→Acceptance and sign-off workflow, then a supervised onboardingWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. No letter reaches a real client before week 6, and an approver clears it before it goes.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Acceptance workflow, approval boundary and who signs whatW2Template and clause library, registry and screening accessW3Party resolution, check assembly and the drafting workflowW4Evaluation suite, conformance guardrails and failure modesW5Packs rebuilt from clients you onboarded last year, nothing issuedW6One live client onboarded under approval, then Agent Care handover
Reading the bandBars cover only the weeks their work is named in. Week 5 rebuilds files you closed last year, not live ones.
At the end of W6One live client is onboarded, accepted and signed by your people, then Agent Care monitors.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Accounting AI agent
Build an onboarding assistant around your acceptance process.
Show us how work arrives, the templates you already approve and who accepts a client. We'll run a past onboarding through it, then agree what a person has to clear before a letter goes out.
