Your MAS licence type decides how strict the platform requirements are
Most Singapore external asset managers (EAMs) shopping for wealth management software start with features: multi-custody aggregation, rebalancing, client reporting. That's the wrong order. The first filter is regulatory. What MAS expects of a platform depends on the licence you hold, and that expectation knocks out more vendors than any feature gap does.
Singapore firms usually fall into one of three positions:
- Licensed fund management company (LFMC) serving accredited and institutional investors only. This is the most common EAM setup. You hold a Capital Markets Services licence, you're subject to MAS's cyber hygiene requirements for CMS licensees, and MAS expects you to apply the Technology Risk Management (TRM) Guidelines and the Guidelines on Outsourcing in proportion to your size and risk.
- Retail LFMC or licensed financial adviser. You face heavier conduct obligations, and supervisors tend to look harder at client data handling, suitability records and complaint trails. Your portfolio management system has to produce evidence, not just valuations.
- Bank or merchant bank with a private banking arm. You're under the Banking Act's confidentiality provisions and MAS's bank-specific outsourcing requirements, which were updated in late 2024. You'll probably classify the core wealth platform as a critical system. That's a different procurement entirely.
A lightweight SaaS portfolio tool that works for a five-person EAM can't simply be scaled up for a private bank. An enterprise wealth suite built for banks is usually too expensive and too slow for a boutique. Before you invite anyone to demo, write one paragraph covering your licence, your client segment (accredited only or retail), the custodian banks you book with, and where your clients live. Many Singapore EAMs serve families in Indonesia, India, mainland China, the Middle East and Europe, and each adds data-protection and reporting obligations of its own. That paragraph becomes page one of your RFP and the first question on every vendor call.
For EAMs with 5 to 30 staff, the realistic shortlist is a purpose-built EAM platform: custodian feeds already built, delivered as managed SaaS. Expersoft, Masttro and Addepar are names that come up in this tier, alongside EAM-focused offerings from Swiss vendors. Private banks generally choose among Avaloq, Temenos, InvestCloud and orchestration layers such as additiv sitting on a core system. Confirm what each vendor actually supports in Singapore before you count it. Coverage and local support teams change.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
What the MAS Technology Risk Management Guidelines mean for hosting, access and recovery
The TRM Guidelines, revised in 2021, are principles rather than a checklist. In practice, supervisors and internal auditors turn them into concrete questions, and your vendor has to answer them in writing. Institutions covered by MAS's technology risk notices and running systems classified as critical face firmer expectations on top: tight limits on unscheduled downtime, a short recovery time objective, and prompt notification to MAS of relevant incidents, measured in hours, not days. Confirm the exact thresholds that apply to your licence with your compliance team. Most EAMs won't classify an outsourced portfolio management system as critical. Most private banks will classify their core wealth platform that way.
Map these points to vendor evidence before you go further:
- Access control. Multi-factor authentication for every user, privileged-access management for the vendor's own engineers, and logs you can retrieve. MAS's cyber hygiene requirements already expect MFA on systems holding customer information, so a vendor without it is out.
- Resilience. A documented RTO and RPO, recovery tests at least annually, and your right to see the results. Ask whether failover goes to a second region and where that region is.
- Security testing. Independent penetration tests at least annually, with a summary of findings and remediation dates. A SOC 2 Type II or ISO 27001 certificate helps, but neither replaces TRM-specific answers.
- Change management. Release notes, notice periods before major changes, and a test environment you can use before upgrades reach production.
- Incident notification to you. If MAS expects fast notice from you, the vendor has to tell you faster. A contract that commits to "24 hours" doesn't work.
Here's a hypothetical. Say a 12-person EAM is choosing between two platforms. Vendor A hosts on a major public cloud in Singapore, supplies a TRM mapping document and agrees to 30-minute incident notification. Vendor B has better reporting templates, hosts in a single European data centre and offers "best efforts" notification. Vendor B might still be workable for a small LFMC, but the firm would have to document compensating controls and accept the residual risk at board level. For most firms, that's reason enough to choose Vendor A.
Outsourcing and PDPA clauses that rule vendors out
Under the MAS outsourcing guidelines, a SaaS platform that holds client positions and personal data will almost always count as a material outsourcing arrangement. For non-bank institutions, that means documented due diligence, board or senior management oversight, a current outsourcing register you can hand to MAS on request, and contract terms that preserve MAS's ability to supervise you. Banks must also work through MAS's bank-specific outsourcing notice and guidelines, and their compliance teams should confirm which arrangements count as material and what must be recorded or reported.
These contract terms are where vendors most often fail:
- Audit and access rights for you, your auditors and MAS, covering the vendor's premises, systems and relevant sub-contractors.
- Sub-contracting controls. The vendor names its sub-processors, notifies you before changing them, and passes your obligations down.
- Data location and retrieval. Singapore doesn't impose blanket data localization, but MAS expects you to know where data sits and to retrieve it quickly, including if the vendor fails.
- Termination and exit. A defined exit period, data returned in a usable format, and migration help at pre-agreed rates.
- Confidentiality that matches your obligations under the Securities and Futures Act or, for banks, the Banking Act.
The PDPA adds two hard requirements. First, the Transfer Limitation Obligation: personal data sent outside Singapore must receive protection comparable to the PDPA's, usually through contractual clauses, binding corporate rules or recognized certifications such as APEC CBPR. Second, mandatory breach notification. Once you've assessed a breach as notifiable, you have three calendar days to tell the PDPC, and affected individuals must also be told where significant harm is likely. Financial penalties can reach 10% of Singapore annual turnover for larger organizations. Your vendor contract needs breach-notification timelines that let you meet those deadlines.
Clients outside Singapore add more layers. EU residents bring GDPR into scope, Indian clients may trigger India's Digital Personal Data Protection Act, and a Swiss affiliate brings FINMA and Swiss data-protection rules. Have a Singapore-qualified lawyer review the outsourcing and data terms. This is the one part of the project where general guidance isn't enough.
Typical 2026 cost ranges for EAMs and private banks
These are typical 2026 market ranges in USD. They vary widely by contract, number of custodians, AUM-based pricing and modules. Vendors often quote in SGD or CHF, and Singapore pricing can run higher than other Asian markets because of local support and hosting. Use the table as a budgeting baseline and confirm every line with vendors.
| Cost item | Boutique EAM (5–15 staff, US$300m–1bn AUM) | Larger EAM / multi-family office (15–50 staff, US$1–5bn) | Private bank wealth platform |
|---|---|---|---|
| Annual SaaS or licence fee | US$40k–120k | US$120k–400k | US$0.8m–3m+ |
| Implementation and configuration | US$30k–100k | US$100k–350k | US$2m–12m+ |
| Custodian bank feeds (setup per custodian) | US$3k–15k each, sometimes bundled | US$3k–15k each | Usually part of integration budget |
| Data migration from legacy system or spreadsheets | US$10k–50k | US$40k–150k | US$300k–1.5m |
| Independent TRM and outsourcing review, penetration test | US$15k–50k | US$30k–80k | US$100k–400k |
| Legal review of outsourcing and data terms | US$10k–30k | US$15k–50k | US$50k–200k |
Three cost drivers catch buyers out. The first is AUM-linked pricing: the fee rises with your growth and can double in a few years without anyone renegotiating. Put a cap or tiered bands in the contract. The second is custodian count. An EAM booking with eight private banks pays for eight feeds and handles eight times the reconciliation exceptions. The third is compliance evidence. A vendor that charges for every due-diligence questionnaire, audit visit or TRM report adds a recurring cost most buyers never model.
A realistic selection-to-go-live timeline and the red flags to watch
Vendors often promise an EAM go-live in eight to 12 weeks. That's achievable for the technical setup. It rarely covers due diligence, contract negotiation, custodian onboarding and parallel running. Plan on something closer to this:
| Phase | Boutique EAM | Private bank |
|---|---|---|
| Requirements, longlist and regulatory filter | 3–5 weeks | 2–4 months |
| Demos, scripted proof of concept, reference calls | 4–6 weeks | 3–5 months |
| Outsourcing due diligence, TRM review, contract negotiation | 4–8 weeks | 3–6 months |
| Configuration, custodian feeds, data migration | 8–16 weeks | 9–18 months |
| Parallel run and reconciliation sign-off | 4–8 weeks | 2–4 months |
| Total | roughly 6–10 months | roughly 18–36 months |
These are planning ranges, not benchmarks. Custodian feeds are the usual critical path. Each private bank runs its own onboarding queue for data-sharing agreements and SWIFT or file-based feeds, and some won't start until you've signed with the vendor. Send custodian requests the week the contract is signed, not when configuration begins.
Red flags during selection:
- The vendor won't name its hosting region or sub-processors until after signature.
- There's no written mapping to the TRM Guidelines, or the vendor treats a SOC 2 report as a full answer.
- Audit-access clauses leave out MAS or limit access to "remote review only."
- No Singapore or APAC references at a firm with a licence like yours.
- Exit terms that charge for your data or return it only as PDFs.
- Reconciliation demos that use clean sample data rather than a real custodian file you supply.
Here's a decision rule for most EAMs: don't book a scripted demo with any vendor that can't deliver, within two weeks, a TRM mapping, a named list of hosting regions and sub-processors, and draft outsourcing clauses covering MAS audit access. Asking for those three documents first usually cuts the shortlist to three or four vendors. You then spend proof-of-concept time on the ones you could actually sign with.