Wecan
Back to blog
Insights12 min read· November 18, 2026

Fenergo Alternative for Swiss Private Banks and EAMs: The Criteria That Matter

Looking for a Fenergo alternative? What Fenergo says it is built for, the criteria that matter to a Swiss private bank or EAM, and the RFP questions to ask.

by Wecan

Searching for a "Fenergo alternative" rarely means that Fenergo is a poor product. It usually means that a Swiss private bank or an External Asset Manager (EAM) has looked at a client lifecycle management (CLM) platform designed for a broad range of financial institutions and asked a narrower question: is this the right scope, cost and operating model for an institution of our size, under Swiss rules, with our counterparties?

This page answers that question without repeating claims we cannot source. On Fenergo, we only use what Fenergo publishes on fenergo.com. On Wecan, we only use what our own site states. Everything else is a criterion or a question you can put to any vendor, including us. If you want a side-by-side of three vendors instead, our Wecan vs Fenergo vs Ondato comparison covers that ground; this page is the shorter, decision-oriented version for Swiss private banks and EAMs.

1. Why Swiss firms look for a Fenergo alternative

The search usually starts from one of four situations:

  • A mid-sized private bank is replacing in-house onboarding tools and has been shown enterprise CLM platforms during a market scan. The question is whether the full scope is needed, or whether onboarding, perpetual KYC and periodic reviews are the actual pain points.
  • An EAM with a compliance team of two to five people needs a structured KYC file, screening and periodic reviews, but cannot staff a multi-workstream implementation project.
  • A bank with a large EAM channel wants to exchange KYC data with the asset managers it works with, rather than receive the same documents by email from each of them.
  • A procurement or IT team has been asked to run a competitive RFP and needs a credible list of criteria and questions, not a vendor's marketing grid.

In each case, the useful exercise is not "which vendor is best" in the abstract. It is "which vendor fits our size, our regulator, our languages and our counterparties", with evidence.

2. What Fenergo says it is built for

Fenergo describes its product as Client Lifecycle Management. On its CLM page, Fenergo states that the platform orchestrates client journeys from initial onboarding and KYC, through transaction monitoring, ongoing due diligence and perpetual KYC reviews, to other regulatory frameworks such as ESG, and finally to client offboarding. The same page states that it supports compliance obligations across 120+ jurisdictions, with KYC, AML and other regulatory rules, and describes the solution as cloud-native.

Fenergo also addresses private banking directly. Its private banking and wealth management page presents the platform as "enabling private banks and wealth managers to digitalize client onboarding", and Fenergo announced its expansion into private banking and wealth management in November 2018.

Read together, Fenergo's own material describes a broad CLM platform, built for financial institutions with multi-jurisdiction obligations, that also serves private banks. That breadth is a real strength for institutions that need it: a group booking clients in many countries, with transaction monitoring, onboarding and regulatory reporting to coordinate on one platform.

What Fenergo's public material does not tell you, and what no vendor's homepage will tell you, is how that breadth translates into implementation effort, cost and day-to-day fit for a firm with a small team and a Swiss-only or Swiss-centred book. Those are the questions to take into an RFP, and they apply to every vendor on your list.

3. Where a Swiss private bank or EAM is different

A Swiss private bank or EAM shares the regulatory foundations of a global bank (identification of the contracting partner, the beneficial owner and the controlling person, risk classification, screening, ongoing monitoring) but differs in four practical respects.

Team size. An EAM authorised by FINMA under the Financial Institutions Act often runs compliance with a handful of people, sometimes one compliance officer plus an external adviser. A private bank may have a larger team, but rarely a dedicated CLM programme office. The software has to be configurable and maintainable by the business, not only by a vendor or integrator.

Concentration of documentation standards. Swiss banks work with the forms appended to the Agreement on the Swiss banks' code of conduct with regard to the exercise of due diligence (CDB 20), in force since 1 January 2020: Form A for the beneficial owner (art. 27 and 28), Form K for the controlling person of operating entities (art. 20 and 21), Form S for foundations (art. 40), Form T for trusts (art. 41) and Form I for insurance wrappers (art. 42). The CDB allows a written declaration with similar content instead of the sample form, but in practice EAMs and their custodian banks exchange these forms constantly.

Languages. A Swiss client file regularly mixes French, German, Italian and English: the client's documents, the relationship manager's notes, the bank's forms and the supervisory organisation's audit requests.

The bank-EAM relationship. An EAM typically works with several custodian banks, each requiring its own KYC package for the same client. The bank, for its part, needs the EAM's own due diligence file. This many-to-many exchange is a Swiss-specific workload that a single-institution CLM does not address on its own.

4. Seven criteria that decide the choice

Team size and who configures the platform

Ask who will change a KYC form, a risk scoring rule or a review workflow after go-live, and how long it takes. If every change requires a vendor ticket or a professional services day, the total cost of ownership for a small team rises quickly and the platform drifts behind regulatory change.

Time to go-live

Ask for a dated project plan for an institution of your size, with the integrations you actually need (core banking, CRM, portfolio management system, screening provider). Ask for the name of a reference client of comparable size that went live with that scope, and call them.

Hosting and data location

For a bank, outsourcing a significant function is governed by FINMA Circular 2018/3 "Outsourcing". It does not prohibit outsourcing abroad, but it requires that the company, its audit firm and FINMA can assert and enforce their right to inspect and audit, and that the information needed to restructure or resolve the company is accessible in Switzerland at all times. For every institution, disclosure of personal data abroad is governed by article 16 of the revised Federal Act on Data Protection. Ask where production data, backups, logs and AI processing are located, and whether on-premise deployment is possible. Our article on KYC pricing and budget shows how hosting choices also change the cost line.

Languages FR / DE / IT / EN

Distinguish three things: the language of the user interface, the language of the client-facing portal, and the languages in which the platform can read and extract data from documents. A platform can be fully localised in one and not the others.

Swiss forms A, K, T, S and I

Ask the vendor to show, in the demo, a Form A and a Form K being produced from the file data, and a Form T for a trust with a protector and several beneficiaries. Ask how the forms will be maintained if the CDB is revised. This is where generic "configurable forms" claims are best tested against reality.

The bank-EAM network

If you are an EAM, ask whether you can maintain a KYC/KYB file once and share it, with consent, with each custodian bank. If you are a bank with an EAM channel, ask how many of your EAMs are already on the platform and how updates propagate. A network only helps if your counterparties are on it.

Total cost of ownership

Ask for a five-year cost including licence, implementation, integrations, hosting, screening data, change requests and internal staff time. Compare like for like: the same scope, the same number of users and client files, the same integrations.

5. The criteria table

Criterion Why it matters for a Swiss private bank or EAM Evidence to request from every vendor
Team size and configuration Small teams cannot depend on vendor tickets for every form or rule change Live demo of a form and a scoring rule changed by a business user
Time to go-live A long project consumes the same small team that runs daily compliance Dated plan for your scope, plus a reference client of comparable size
Hosting and data location FINMA Circular 2018/3 and FADP art. 16 apply to outsourcing and cross-border disclosure Data location for production, backups, logs and AI; on-premise option
Languages Client files mix FR, DE, IT and EN Interface, client portal and document extraction languages, shown separately
CDB forms A, K, T, S, I Daily exchange with custodian banks relies on them Forms generated from file data in the demo; maintenance plan for revisions
Bank-EAM network The same client is documented for several banks Number of counterparties connected; consent and update mechanism
Total cost of ownership Licence is rarely the largest cost over five years Five-year cost broken down by licence, services, hosting, data and change
Security Client data is subject to banking secrecy and data protection Certifications, audit reports, tenant isolation, penetration testing

6. Questions to put in your RFP

  1. Describe your reference implementation for an institution with our number of client relationships and compliance staff. What was the dated plan, and how long did it take?
  2. Which configuration changes (forms, scoring, workflows, review frequencies) can our compliance team make without you? Show three of them live.
  3. Where are production data, backups, logs and any AI processing physically located? Can the platform run on our infrastructure?
  4. How does your contract address FINMA Circular 2018/3, including audit and inspection rights for us, our audit firm and FINMA?
  5. In which languages are the user interface, the client portal and document extraction available?
  6. Show CDB 20 Forms A, K, S and T generated from client data. Who maintains them when the CDB changes?
  7. Can our KYC/KYB file be shared, with consent, with the banks or EAMs we work with? How many of our counterparties already use the platform?
  8. Which screening providers can we keep, and which do you supply?
  9. Provide a five-year total cost of ownership, including services, change requests and data.
  10. Which certifications do you hold, and when was the last independent audit?

For a broader checklist of what onboarding software must do, see our guide on how to choose KYC onboarding software.

7. How Wecan answers these criteria

We apply the same rule to ourselves: only what our site states, and you should test it in a demo.

  • Who it is for. Wecan works with banks and External Asset Managers, from Geneva, where the company was founded in 2015. It is a subsidiary of SEALSQ Corp (Nasdaq: LAES) and is used by more than 100 financial institutions.
  • Configuration. KYC forms, document packs, scoring models, workflows and internal rules in plain language are configured from the admin interface by your team. There are out-of-the-box KYC forms per client type: individuals, legal entities, trusts, foundations and asset managers.
  • Hosting and security. Hosted in Switzerland, Luxembourg or on premise, ISO 27001 certified since 2022, with per-tenant databases and document storage, encryption at rest and in transit. Details are on our security page.
  • Languages. The interface and the white-label client portal are available in French, English, German and Italian.
  • Integrations. CRM, core banking and portfolio management systems through open APIs, with RPA for legacy systems; you can keep your screening provider (World-Check, LexisNexis, ComplyAdvantage and others) or use ours.
  • Network. The shared KYC/KYB network, live since 2021 and designed with a consortium of Swiss banks and asset managers, lets an EAM maintain its file once and share it, with consent, with each bank it works with.
  • Go-live. Our site cites a typical go-live of four to six weeks for API-first deployments. For a bank with core banking integration, ask us for a dated plan like any other vendor.

8. Frequently asked questions

Is Fenergo suitable for private banks?

Fenergo states that it serves private banks and wealth managers and has a dedicated private banking offering since 2018. Whether it suits your institution depends on scope, team size, hosting requirements and budget, which is why the criteria above matter more than any general statement.

What is the main difference between a CLM platform and a KYC platform for EAMs?

Fenergo describes its CLM as covering the client lifecycle from onboarding to offboarding, including transaction monitoring and other regulatory frameworks across 120+ jurisdictions. An EAM usually needs a narrower core: a complete KYC file, screening, risk classification, periodic reviews and exchange with custodian banks. Match the scope to your obligations.

Do Swiss banks have to use the CDB forms A, K, T and S?

The CDB 20 provides sample forms and allows a written declaration with similar content instead. In practice, the forms are the common language between banks and EAMs, so software that produces them from the file data saves rework.

Can a Swiss bank host KYC data outside Switzerland?

FINMA Circular 2018/3 permits outsourcing abroad under conditions, notably enforceable inspection and audit rights for the bank, its audit firm and FINMA, and access in Switzerland to the information needed for restructuring or resolution. Data protection law adds its own conditions for disclosure abroad. Many institutions nonetheless prefer Swiss hosting to simplify both.

How long should a Fenergo alternative take to implement?

There is no honest general answer. Ask each vendor for a dated plan for your exact scope and a reference client of comparable size, and compare those.

Should we include Fenergo in our RFP?

If your scope is broad, multi-jurisdictional or includes transaction monitoring on the same platform, yes. A well-run RFP with the same questions to every vendor is the fairest way to decide.

9. What Wecan Copilot does

Wecan Copilot covers onboarding, perpetual KYC and periodic reviews for Swiss private banks and EAMs, with configurable KYC forms per client type, FR/EN/DE/IT interfaces and hosting in Switzerland, Luxembourg or on premise. Its shared network lets an EAM maintain one file and share it, with consent, with each custodian bank. Bring a sample file to a demo and test it against the criteria above. See Wecan Copilot or book a demo.

See Wecan in action. In 30 minutes.

A live walkthrough on real KYC scenarios — no slides, no commitment. Just see if it fits your context.