Client portal comparison
Custom client portal vs off-the-shelf portal software
Choose off-the-shelf portal software when your workflow fits a proven product and its operating model. Choose a custom client portal when value depends on business-specific workflow, integrations, permissions or customer experience.
The direct recommendation
Start with portal software when customers need familiar capabilities, such as document exchange, knowledge content, standard requests or account collaboration, and a credible product already supports the required permissions, integrations and customer journey.
Choose custom development when the portal must express your operating model: it combines several systems, uses organisation-specific access rules, handles unusual workflow states, or forms a differentiated part of the customer service.
Do not compare labels. Configure a representative workflow in the shortlisted product and prototype the highest-risk custom assumption. Compare both over the same user volume, scope, support model and planning horizon.
01
Portal software and custom development compared
| Factor | Off-the-shelf portal software | Custom client portal |
|---|---|---|
| Best fit | Common external-user workflows supported by product configuration | Business-specific workflow, data and customer experience |
| Starting point | Existing platform, data model, components and operating rules | Architecture and experience designed around the required outcome |
| Delivery speed | Potentially faster when the product fits with limited extension | More discovery and build effort, with scope controlled through a focused first release |
| Integrations | Connectors and APIs within product capabilities and commercial terms | Integration layer designed around the actual source systems and failure modes |
| Permissions | Roles and sharing structures supported by the platform | Organisation, object, workflow and mandate rules modelled for the domain |
| Experience | Branding and journeys within themes, components and extension points | Greater control over interface, accessibility, performance and behaviour |
| Change | Vendor roadmap plus configuration, extensions and release compatibility | Product roadmap controlled by the owner, with direct maintenance responsibility |
| Cost model | Licences or capacity plus setup, integration, administration and extension | Discovery and development plus hosting, operations, support and ongoing change |
02
Choose portal software when configuration creates leverage
- the main customer journey matches a proven product use case;
- the required organisation and role model is supported cleanly;
- source systems can connect through maintained APIs or supported connectors;
- the standard customer experience is acceptable after realistic configuration;
- business administrators can safely own useful day-to-day changes;
- security, data residency, retention and audit capabilities meet the requirements;
- licensing remains sensible at expected customer, user and usage volumes; and
- the organisation accepts the vendor's roadmap, release process and platform dependency.
Configuration is not free of design. Customer roles, data ownership, integrations, exception handling, migration, testing, support and adoption still determine whether the portal works.
03
Choose custom when workarounds would become the product
- the portal supports a workflow that standard products do not model well;
- customers need a coherent view across several operational and reporting systems;
- access depends on account, branch, contract, product, role, record and workflow state;
- customer actions require domain-specific validation, approvals or exception paths;
- the experience is a meaningful part of the service or competitive position;
- data volumes, latency or availability require a tailored application layer;
- the owner needs direct control of code, architecture, release timing and hosting choices; or
- the licence model becomes expensive or restrictive at the intended scale.
Custom does not require inventing every foundation. A purpose-built portal should still use proven identity, storage, messaging, observability and infrastructure services where they fit.
04
Compare total cost across the same horizon
Product subscriptions, capacity and environments, or custom discovery and architecture.
Data model, permissions, interface, integrations, migration, testing and rollout.
Hosting, vendor plans, monitoring, administration, support, security and incident response.
New workflows, product releases, regression, custom extensions, upgrades and technical ownership.
Include internal time and customer growth. A low entry price can change when external users, records, storage, messages, API calls or premium features increase. A custom estimate can look low when it omits support, monitoring, security maintenance and future product work.
05
Evaluate a product with a difficult, representative workflow
Do not base the decision on a vendor demonstration of ideal features. Configure a proof that includes:
- an external customer organisation with at least two roles;
- one account-specific record, document or report;
- one write action that must reach a business system;
- an approval, rejection or exception path;
- a user who belongs to more than one account, if relevant;
- an integration timeout or unavailable dependency;
- customer and internal administration;
- audit evidence for a sensitive action;
- responsive and accessible use on a realistic device; and
- the licence and service assumptions required at expected scale.
Record each gap as configuration, extension, process change or unacceptable limitation. Price and risk the gap rather than assuming it will be solved later.
06
A practical decision process
- Define the customer outcome. Describe the service improvement before selecting software.
- Map the complete workflow. Include customers, staff, systems, data, decisions and exceptions.
- Separate common from distinctive needs. Identify what a proven product should already solve.
- Shortlist credible options. Include platform fit, governance, licensing and supplier capability.
- Test the highest-risk scenario. Use representative users, data and integrations.
- Compare total ownership. Model implementation, operation, change and exit over the same horizon.
- Choose the operating model. Confirm who will administer, support, secure and improve the portal.
Use the broader build-versus-buy framework, compare specific platform options in custom portal vs Power Pages and client portal vs SharePoint, and assess delivery readiness with the implementation checklist.
Questions
Frequently asked questions
What is off-the-shelf portal software?
Off-the-shelf portal software is a configurable product that provides common external-user capabilities such as accounts, content, documents, forms, requests or collaboration without building the whole application from the beginning.
When should a business buy portal software?
Buy or configure a product when the required workflow is common, the platform supports the important integrations and permissions, the customer experience is acceptable, and the total licence and implementation model fits expected usage.
When is a custom client portal worth considering?
Custom development is worth considering when the portal coordinates business-specific workflows, several existing systems, complex customer roles or a differentiated experience that would require persistent workarounds in a standard product.
Is off-the-shelf portal software always faster?
No. It can be faster when the workflow fits. Data migration, identity, permissions, integration, configuration, testing and customer onboarding still require effort. Extensive extension or process change can remove the speed advantage.
Can a portal combine software and custom development?
Yes. A hybrid may use a product for identity, documents, content or workflow while a custom application or integration layer handles business-specific data and actions. The combined operating and licensing complexity must still be justified.
Compare a real portal scope
Bring the workflow, user model, systems and product shortlist.
LCR can help compare configuration, custom delivery and hybrid options against the same requirements and ownership horizon.