Website, portal or custom software: what do you actually need?

Describe the job before the format

Teams often arrive with a solution noun: website, app, portal, platform. Start instead with the user, the decision they need to make and the information or action that moves them forward.

If most people need to understand, compare and make contact, a well-structured website is usually enough. If they return to see private information, manage a process or collaborate over time, a portal or product may be justified.

Choose a website when communication is the product

A website is the right tool when the experience is primarily public, content-led and conversion-focused. Forms, calculators and guided journeys can add useful interaction without creating a full software product.

Do not mistake a simple technical form for a simple design problem. A strong service website still needs clear information architecture, persuasive content, accessible interaction, measurement and an editing model the team can maintain.

Choose a portal when the relationship persists

A portal earns its cost when users return, authenticate and expect the system to remember their state. Common signals include document exchange, approvals, account-specific information, repeated orders or a workflow that spans days rather than minutes.

Before building, test whether an existing platform can handle the core job. Custom software also creates an ongoing obligation: security updates, support, monitoring, data governance and product decisions after launch.

Use the smallest test that can change the decision

A prototype can test whether people understand a workflow. A manual concierge process can test whether they value the outcome. A website can test demand before accounts, dashboards and integrations are built.

The cheapest first step is not always the smallest screen. It is the smallest piece of work that reduces the uncertainty blocking a responsible decision.

• Public information and one-off enquiry: website
• Private, repeated account activity: portal
• A new operational workflow or product: custom software
• Unproven demand: prototype or manual test first