Nepal FRAML localization OS for banks to ship local PEP coverage, FIU-ready reports, and unified fraud controls fast.

1. A named Nepal bank has already bought the category, proving budget and urgency are real rather than hypothetical.
2. Nepal-specific PEP coverage and NRB/FIU reporting are explicit buying criteria, so localization is the moat rather than a services afterthought.
3. Buyers are shifting from point compliance tools toward unified FRAML workflows that merge fraud and AML investigation context.
4. Microservices deployment and local Nepali implementation partners lower adoption risk enough for banks to move from pilots to production.

Catalyst. Machhapuchchhre Bank's live selection of a unified, microservices-based, Nepal-localized AML system shows that buyers are moving now from generic compliance tooling to localized FRAML stacks.

The product would sit above a bank's core, channel, and transaction systems and ship a maintained Nepal pack of PEP and entity data, NRB and FIU reporting templates, and local rule libraries for sanctions, AML, and fraud. It would unify alerts into one investigator console so a suspicious account, payment pattern, and fraud signal are worked as one case instead of three queues. A microservices design would let banks adopt modules gradually and deploy them in-country with local implementation partners, matching the rollout model described in the sources. Over time, the company could benchmark false-positive tuning and investigation workflows across similar banks to deepen its moat.

What's different. Most AML vendors ask banks or local SIs to do the hardest last-mile work: translating local regulation, PEP coverage, and reporting formats into usable operations. This company productizes that layer as software, not one-off services, while also joining fraud and compliance cases in one workflow. Its advantage compounds through regulator mappings, local data coverage, and bank-specific tuning that are hard for generic global platforms to maintain market by market.

Jobs to be done

flowchart LR
  Buyer[Head of AML at Nepali bank] --> Pain[Manual local PEP and FIU reporting]
  Pain --> Product[Nepal FRAML localization OS]
  Product --> Outcome[Faster compliant launches and unified investigations]

Executive takeaways

• The demand signal is real but concentrated: Machhapuchchhre Bank already chose ZIGRAM for a Nepal-localized unified AML/fraud stack, proving that a buyer in Nepal will fund this category when localization and workflow unification are packaged together [16][17][20].
• Localization—not raw detection models—is the credible wedge. FIU-Nepal keeps updating STR/SAR and TTR guidance, and APG says commercial banks are relatively more advanced than other FIs while the rest of the market still shows screening and supervision gaps [4][5][6].
• Nepal is digitally large enough to create pain but not large enough to create venture scale on its own: NRB still lists only 20 commercial banks, yet mobile banking users reached 24.65 million and QR payment number grew 117.03% in FY2023/24 [1][2].
• Horizontal incumbents already cover the generic stack. Oracle, NICE Actimize, Tookitaki, and ComplyAdvantage all market monitoring, screening, or case-management modules, so a startup must win as the Nepal-specific orchestration layer rather than as another generic full suite [22][26][29][32].
• Year-3 SOM is reachable at a few logos, but TAM remains modest without regional expansion; the local-market ceiling is real unless Nepal becomes a reusable localization engine for adjacent South Asian markets and payment institutions [1][2][36][37].

Market definition

Defined market: software and data layers that localize financial-crime controls for South Asian financial institutions—combining customer and payment screening, transaction monitoring, fraud-alert unification, case management, and FIU-ready reporting for Nepal-specific obligations rather than generic global AML modules [3][5][6][18][19][22][29][32][35].

Customer and buyer

Day-to-day users are heads of AML/FCC operations, MLRO-equivalent teams, and fraud-operations managers at Nepali commercial banks; the economic buyer is usually the CRO, Head of Compliance, or COO who owns digital-channel risk and regulator-facing controls [1][2][4][16][17].

Buying triggers

• An NRB/FIU review, internal audit, or suspicious-activity reporting remediation effort exposes how much local filing logic still lives in spreadsheets and manual investigator work. [4][5][6]
• Digital-payment growth increases alert volume and makes separate fraud, screening, and AML queues harder to manage with existing staff. [2][14][15]
• A bank modernization or vendor-change program creates an opening for a lighter localization layer or a unified FRAML stack deployed with local partners. [16][17][20][21]

Willingness to pay

Public pricing is scarce, but willingness to pay is credible because a Nepal commercial bank has already bought the category, incumbent vendors position these products as enterprise-wide risk platforms, and case studies from adjacent markets focus on scaling compliance teams rather than on replacing free tools. The budget line already exists inside bank risk/compliance modernization and payment-screening programs. [16][17][22][25][26][38][39]

Category dynamics

Growth signal 17.8% CAGR global AML market, 2025-2030

Validation signals

• Machhapuchchhre Bank chose ZIGRAM in July 2026, proving a live Nepal bank budget for this category.
• ZIGRAM built separate Nepal alliances with AMNIL and Dolma, showing a practical implementation ecosystem exists.
• NRB reports digital-channel adoption at a scale that can create real AML/fraud alert volume and operational pain.
• Tookitaki and ComplyAdvantage both market case studies focused on false-positive reduction and scaling compliance operations, indicating real buyer demand for workflow improvement.

Regulatory & technical constraints

• FIU-Nepal added new categories and predicate-offence indicators in the July 2025 STR/SAR guideline update.
• TTR rules were amended in July 2025 with sector-wise threshold and exemption updates.
• APG found stronger automated screening among commercial banks and larger FIs than among the rest of the market.
• NRB payment oversight found inadequate due diligence and missing AML-CFT program budgeting among some payment institutions.

ZIGRAM is the closest direct threat because it already pairs Nepal localization with a unified stack and local partner model. Tookitaki competes on APAC-focused FRAML operations and false-positive reduction, ComplyAdvantage on API/data-driven screening and monitoring, and NICE Actimize plus Oracle on broad enterprise suites. The true substitute inside Nepal remains incumbent AML modules plus spreadsheets and SI work, not no software at all [16][17][18][19][20][21][22][23][24][26][27][28][29][30][32][33][35].

Why incumbents do not win by default

• Global AML suites. Oracle and NICE Actimize already cover monitoring, screening, fraud, and regulatory reporting, but their public material is horizontal and still leaves Nepal-specific filing content and local rollout complexity to the customer or partner ecosystem.
• APAC anti-financial-crime suites. Tookitaki is closer to the workflow and has strong FRAML/case-management claims, but its public positioning is APAC-generic rather than explicitly Nepal-localized.
• API-led screening and data vendors. ComplyAdvantage is strongest where global screening data, modular monitoring, and case workflow matter, but it is still oriented around API-native risk infrastructure rather than a Nepal-specific regulatory pack.
• Local partner plus full-stack model. ZIGRAM already proves that local implementation alliances help close Nepal deals, yet that same model could leave room for a thinner vendor-neutral overlay if banks want localization without a bigger suite replacement.
• In-house workflows plus system integrators. The fallback remains spreadsheets, manual investigations, and stitched-together incumbent modules; APG and NRB evidence shows this is workable but uneven, especially outside the largest banks.

Nepal FRAML localization OS should start as a vendor-neutral localization overlay for Nepali commercial banks that already run imported AML or fraud tools plus manual local workflows. Research shows live demand because Machhapuchchhre Bank has already bought a Nepal-localized unified stack and FIU-Nepal updated STR/SAR and TTR guidance in 2025, making local rule maintenance and filing accuracy urgent. The first product is not a new generic detection engine; it is Nepal-specific PEP/RCA data, FIU-ready report packs, unified alert triage, and investigator casework deployed on top of incumbent systems with local partners. The first customer is a 25-75 branch Nepali commercial bank with an in-house mobile app, rising digital-payment volume, and an upcoming NRB or FIU review or modernization project. The first sale should be a paid pilot for one bank entity and one reporting workflow that converts only after the platform auto-populates most filing fields, reduces manual case preparation, and shortens investigation cycle time. This wedge is attractive because the buyer set is concentrated, pain is regulator-linked, and an overlay can be proven faster than a full-suite rip-and-replace. The market is real but small: modeled SAM is about $8.0M and year-3 SOM about $1.6M, so the venture case depends on reusing the localization engine in Sri Lanka or adjacent regulated institutions. Research does not yet confirm incumbent penetration, in-country deployment requirements, or credible price points, so overlay win rate, deployment architecture, and ACV must be validated in the first 12 months.

Problem

• Nepali commercial banks still stitch together global AML modules, spreadsheet-based local PEP checks, and manual STR/SAR/TTR preparation even as digital-payment volume raises alert counts.
• Separate fraud and AML queues create duplicate investigations, slower escalations, and weaker audit trails exactly when NRB/FIU scrutiny is rising.
• Generic vendors cover monitoring and screening breadth but leave Nepal-specific filing logic, local data maintenance, and regulator-ready workflows to the bank or SI.

Solution

• Ship a Nepal localization overlay with maintained PEP/RCA and reporting mappings, versioned STR/SAR/TTR packs, and auditable evidence generation for regulator-facing filings.
• Unify fraud, screening, and AML alerts into one investigator queue and case file without forcing the bank to replace its current monitoring stack on day one.
• Deploy through modular connectors and local partners so a bank can start with one entity and one workflow, then add modules after proof.

Why we win

• The startup sells the last-mile product gap incumbents and SIs still treat as custom work: Nepal-specific data, filing templates, and investigator workflow tied to live rule changes.
• A vendor-neutral overlay is easier for banks to buy than a full-suite replacement because it fits existing modernization budgets and lowers core-system switching risk.
• Cross-bank tuning data, filing-template history, and local partner deployment playbooks compound into a moat that generic global suites do not maintain market by market.

Milestones

flowchart LR
  Wedge[Nepal bank localization overlay] --> MVP[PEP plus FIU report pack plus unified casework]
  MVP --> Proof[2 production bank references and faster filings]
  Proof --> Expansion[Sri Lanka or adjacent institution pack]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 6 of Nepal’s 20 commercial banks still run material parts of local PEP review or FIU reporting manually and face a budgeted modernization or audit trigger within 24 months.
• At least 3 of the first 6 serious prospects prefer a vendor-neutral overlay over a full-suite replacement or SI-only project.
• The first 3 pilots can auto-populate 70%+ of required STR/SAR or TTR fields and cut median case-preparation time by at least 30% within 90 days.
• At least 50% of paid pilots convert to $250k+ annual software contracts without services exceeding 30% of first-year revenue.
• A Sri Lanka or adjacent-institution pack can reuse at least 60% of the Nepal content, rules, and workflow model by month 18.

Open diligence questions

• How many of Nepal’s 20 commercial banks already use Oracle, NICE, Tookitaki, ZIGRAM, or homegrown workflows, and which are easiest to sell as overlays?
• Do target banks require in-country or on-prem deployment for suspicious-activity case data, and what does that do to gross margin and rollout speed?
• What percentage of FIU filing fields and case-preparation steps are still manual at the first 2 design partners?
• Can the startup win against ZIGRAM and incumbent suites without owning the full transaction-monitoring engine?
• Which second market reuses the Nepal pack with the least net-new regulatory content: Sri Lanka banks or Nepal payment institutions?

Model sanity

• Revenue engine. Base revenue is driven by converting 2 paid pilots into 4 Nepal production banks by Q4Y2 and then adding 2 adjacent-market paying institutions plus in-logo expansion by Q4Y3.
• Must go right. Local partners must keep deployments near the 90-day target so pilot logos convert before the model adds the second seller and adjacent-market motion.
• Model breaks if. If realized logo value stays near $360K ARR or pilot-to-production stretches toward 120 days, the downside case pushes cash below zero before regional proof exists.
• Next-round proof. A seed round is justified once 4 Nepal production logos, 1 expansion win, and 1 adjacent-market paid pilot exist with services still below the BP 30% threshold for new-logo first-year revenue.

Scenarios

Sensitivity

flowchart LR
  TargetBanks[Target Nepal banks] --> PaidPilots[Paid pilots]
  PaidPilots --> NepalProduction[Nepal production banks]
  NepalProduction --> Expansion[Expansion modules]
  NepalProduction --> Adjacent[Adjacent-market pilot]
  Expansion --> Revenue[Revenue]
  Adjacent --> Revenue
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash]

Flags: The core Nepal bank market has only 20 buyers, so missing one or two target accounts can move Y2 and Y3 materially. · customersEop includes paid pilots and production entities, so recurring-only production count is lower than the headline paying count in mixed pilot quarters. · Q4Y3 turns EBITDA positive only if partner-assisted deployments actually stay under 90 days and localization upkeep does not collapse into services-heavy work. · ZIGRAM already has a live Nepal bank deployment, so the overlay-vs-suite positioning must stay crisp or the 90-day conversion assumption will slip. · Cash is modeled as EBITDA, so enterprise billing milestones, implementation prepayments, or delayed collections can shift the real cash curve by a few months.

• Local-market ceiling. Nepal alone may not support venture outcomes if expansion logic is weak. Mitigation: Use Nepal as the proof point, then productize reusable localization packs for adjacent South Asian banking and money-movement markets.
• Incumbent vendor squeeze. Global AML vendors or local SIs could bundle Nepal localization once demand is proven. Mitigation: Move faster on regulator mappings, partner distribution, and unified fraud-plus-AML workflow data that services firms cannot easily standardize.
• Compliance accuracy liability. Errors in local PEP coverage or FIU reporting templates could damage trust with early bank customers. Mitigation: Ship versioned rule packs with human approval workflows, local compliance SMEs, and reference-bank validation before each release.