Selecting entity management software is one of the most consequential technology decisions a CSP can make. The system will hold the firm's core data — every entity, every beneficial owner, every compliance record, every document — and will be relied on by every member of the team for their daily work. A poor selection creates technical debt that compounds over years; a good selection creates an operational foundation that scales with the firm and enables service quality that cannot be achieved manually.
The evaluation process is also the moment where CSPs are most vulnerable to vendor influence. Demonstrations are designed to show the system at its best; pricing is structured to understate total cost; implementation timelines are typically optimistic. This guide helps CSPs structure an evaluation process that reveals genuine capability and surfaces the issues that vendor demonstrations are designed to conceal.
Start with Requirements, Not Demonstrations
The most common mistake in CSP software selection is starting with vendor demonstrations before establishing clear requirements. When you watch a demonstration before you know what you need, you evaluate the software through the lens of what the vendor wants to show you — which is always the most impressive subset of the system. You are not evaluating fitness for purpose; you are evaluating presentation quality.
The requirements definition process should cover: what entity types the system needs to support (companies, trusts, foundations, partnerships, SPVs, and which jurisdictions for each); what compliance workflows are required (CDD, screening, risk assessment, refresh, reporting); what document management capabilities are needed; what client-facing capabilities are required (portal, document sharing, digital signatures); what reporting and analytics the team needs to manage operations; and what integration requirements exist with other systems (accounting, banking, third-party screening tools).
The Right Evaluation Questions
With requirements defined, the evaluation process should include structured demonstrations against your specific use cases — not the vendor's standard script. Key questions to drive behind the demonstration:
- Show me how you would onboard a Cayman exempted limited partnership with 8 corporate limited partners, each with their own UBO structure. How does the system handle the beneficial ownership identification and documentation?
- Show me the compliance calendar for a portfolio of 150 entities across 3 jurisdictions. How does it prioritise? How are tasks assigned? What happens when a deadline is missed?
- Show me how a client accesses their entity documents through the portal. What happens when they need to sign a document? What is the audit trail?
- Show me how you generate a board resolution for a specific entity type and jurisdiction. Where does the data come from? What template library do you maintain?
- Show me what a regulatory inspection data request looks like. If an examiner asks for all CDD records for entities onboarded in 2023, how long does it take to produce that?
"The question I now always ask in a software demo is: show me something going wrong and how the system handles it. I want to see what happens when a document upload fails, when a deadline is missed, when a compliance review is escalated. The vendor will always show you perfect workflows. The real system lives in the edge cases."
— Chief Operating Officer, Channel Islands CSP
Data Migration: The Underestimated Challenge
Data migration — moving your existing entity records, documents, and compliance data from your current system (or spreadsheets and shared drives) into the new platform — is consistently the most underestimated challenge in CSP software implementation. Migration takes longer than vendors estimate, requires significant internal resource to validate migrated data, and often reveals data quality issues in the source system that must be addressed before migration.
Implementation: What Good Looks Like
A well-structured implementation includes: a dedicated project manager from both the vendor and the CSP; a phased rollout starting with a pilot group (typically 20-30% of the team) before full deployment; structured training including role-specific training content, not a generic walk-through of the system; a data migration plan with defined validation criteria and sign-off process; and a stabilisation period of 4-6 weeks after go-live with enhanced vendor support before moving to standard support terms.
The implementation red flags: a vendor that proposes going live across the entire firm simultaneously; a training plan that is a single half-day session; a data migration approach that involves the vendor "loading the data" without a defined validation process; an implementation timeline of less than 6 weeks for a firm with more than 50 entities.
Total Cost of Ownership
Vendor pricing for CSP software typically comprises a combination of: per-user licensing fees; per-entity fees above a base allocation; implementation fees; data migration fees; training fees; and annual maintenance and support fees. The headline price per user per month that appears in initial conversations rarely reflects the true total cost of ownership.
To build an accurate total cost of ownership model: get detailed pricing for your specific user count, entity count, and module requirements; include implementation and migration fees in year-one cost; understand the pricing model as you scale — does per-entity pricing become punitive above certain thresholds?; understand support tiers and what is included vs. additional cost; and model the internal resource cost of implementation (who from your team will work on this, and for how long).
Building the Business Case
Most CSP software investments require approval from senior management or a board that is not close to the operational problem being solved. Building a compelling business case requires translating operational improvements into financial terms: time saved on document production multiplied by average hourly cost; compliance incidents avoided and the regulatory risk reduction value; client attrition prevented by improved service quality; and new clients won due to a stronger technology proposition.
The most persuasive business cases include a current-state analysis (how much time is spent on manual processes that the system automates, with specific data points) and a comparison against a relevant peer firm that has already made the investment. References from peer CSPs — not clients the vendor selects for you, but firms you identify independently — are the strongest validation available.