What customer portal software does

Customer portal software gives your customers a private login where they can check orders, change bookings, pay balances and download documents without contacting your team. For a marketing manager, this means moving repetitive tasks away from an overflowing inbox and into a self-service environment. Instead of staff spending hours answering the same questions about order status or invoice copies, customers use the software to find answers themselves. This shift allows your team to focus on more complex tasks rather than manual data entry or routine queries. The software provides a structured way for users to interact with your business through a secure interface.

  • Sign in: Every customer gets a secure login with access levels set by your team.
  • See what's happening: Customers can view order status, upcoming bookings and points on one screen.
  • Change things: Users can update their own details, change a booking or add to an order.
  • Pay or download: Customers use this to pay a balance or download invoices and contracts.
  • Get help: Users can send a message to your team with their complete history included.

Common uses for a customer portal include loyalty and membership accounts, managing bookings and balances, trade and wholesale orders, and client reports and documents. In a loyalty or membership account, users access their specific profile and benefits. For managing bookings and balances, customers can view or update their scheduled appointments and current account totals. Trade and wholesale orders allow clients to place orders or manage bulk purchases through the portal. For client reports and documents, users can access important files or data summaries they need from your business.

The term "portal" can mean different things depending on which vendor you choose. Software functionality varies based on the specific tool and its intended purpose.

  • Support portal, HubSpot: A web page behind a login where customers view, open and reply to support tickets and access a knowledge base.
  • Support portal, Zendesk: A space where customers submit support requests, track open and solved tickets, add comments, or reopen a solved request.
  • Support portal, Freshdesk: A place for customers to submit tickets and find information themselves using a knowledge base.
  • Billing portal, Stripe: A tool for updating billing information and payment methods, managing subscriptions or paying and downloading invoices.

Three of these focus on support tickets, while the fourth focuses on billing, so you should check which job you are buying for. Different vendors make different claims about the impact of these tools on business operations. Salesforce says self-service gives customers 24/7 access to resources and lets businesses reduce costs because agents can focus on complex cases. HubSpot's own product page states that organisations typically see a 67% reduction in support calls with its portal. This is the vendor's own figure and their page provides no study to support it.

Customer portal software examples and what they cost

Portal software is priced per agent, per customer login or as a flat fee, so the cheapest option depends on how many staff and customers you have. These prices were read in November 2026 and change often. You might see costs listed in pounds or US dollars depending on the vendor.

  • Zendesk, per agent: Support Team is £15 monthly or £20 monthly; Suite Team is £45 monthly or £59 monthly; Suite Professional is £89 monthly or £115 monthly.
  • HubSpot Service Hub, per seat: Professional is $90 a month plus a $1,500 one-time onboarding fee; Enterprise is $150 a month plus a $3,500 one-time onboarding fee.
  • Freshdesk, per agent: Growth is $19; Pro is $55; Enterprise is $89.
  • Softr, by plan and users: Pro is $99 a month billed yearly or $119 monthly; Business is $329 a month billed yearly or $395 monthly.
  • Power Pages, per 100 logged-in users: £153.80.
  • SuiteDash, flat plan: $19, $49 or $99 a month; or $180, $480 or $960 a year.
  • Client Portal, yearly fee: $199 for one website or $399 for unlimited websites.

A per-agent cost grows with your support team. If you hire more people to manage tickets, the bill increases accordingly. For example, if you have 10 Zendesk agents on Suite Professional at £89 an agent a month paid yearly, the cost comes to £890 a month or £10,680 a year before any add-ons. This model means you pay for the staff members using the tool to manage customer requests. If your marketing team expands and more people need access to handle incoming queries, you will pay more per month. It is a direct link between your headcount and your software spend.

Per-user cost grows with your customers. This model is common for tools where you provide access to external people like clients or members. Softr includes a set number of client users in its plans, such as 50 for Pro or 100 for Business. If you exceed that allowance, you are billed separately each month for the extra users. For instance, if you need 1,000 logged-in users on Power Pages, you would need 10 packs of 100. At £153.80 a pack, this costs £1,538 a month or £18,456 a year, excluding VAT. Scaling your customer base means you must plan for these rising costs as more people log in to use the service.

Flat fees stay level as you add people. These plans offer a predictable cost because they do not change based on how many staff or clients you have. SuiteDash offers three plans at $19, $49 or $99 a month, which equals $180, $480 or $960 a year. These plans include unlimited clients and staff. Similarly, the Client Portal WordPress plugin provides unlimited portals and clients for a yearly fee of $199 or $399. These options allow you to scale your internal team or your client list without seeing immediate changes in your software budget. You pay one price and use the features as needed.

A low list price is not a like-for-like comparison. These tools do different jobs. Some focus on support tickets, while others handle billing or custom app building. You should consider the specific tasks your team needs to automate before choosing a plan.

Portal software vs a custom portal

Portal software is quicker to launch, and a custom portal earns its cost only when your customers and data do not fit a standard product. Choosing between these two paths requires understanding how each affects your daily operations and long-term budget.

  • Time to launch: Software takes days or weeks; a custom portal takes a few months, launched in stages.
  • Fit: With portal software your workflow adapts to it; a custom portal is created around your process.
  • Branding: Portal software offers limited theming; a custom portal matches your brand, on your own domain.
  • Integrations: Portal software is a standalone ecosystem; a custom portal connects to any system with an API.
  • Per-user fees: Portal software usually charges per seat; a custom portal has none.
  • Best for: Software suits standard support portals; a custom portal suits accounts, bookings, loyalty and trade orders.

These points represent the Big Rocket view, so you should weigh them against your specific business goals. For a marketing manager, the comparison highlights different operational realities.

Standard products have specific constraints that define their "standard shape." For example, HubSpot requires you to use tickets to activate its customer portal. In that system, only tickets associated with conversations appear on the ticket listing page. This means your team must work within their specific structure to see relevant data. Another example is Stripe. In a Stripe customer portal, a customer can cancel but not update a subscription that uses multiple products, usage-based billing or a trial offer. These are normal product limits and not faults in the software, but they are worth checking against your own business processes. You might find that a subscription model or a specific way you handle data requires more flexibility than these tools provide. For instance, Client Portal requires you to use WordPress. These constraints are part of using a pre-built tool.

The honest point for software is that it is built for the masses. It provides a set of features designed to work for many different types of businesses at once. This can lead to limitations when your needs are unique.

Consider these signs that a custom build might be worth the investment:

  • Platform limits: If your business requirements fall outside what a standard tool allows, you may need something bespoke.
  • Too many tools: If you find yourself paying for multiple subscriptions that do not work together, a single custom system might be better.
  • Your workflow is your edge: If your competitive advantage comes from a unique way of handling custom booking systems or specific client interactions, you may need a tool built around that process.
  • Ownership: If you want to own your code and your data, a custom build offers that control.

A marketing manager should also consider the impact of usage limits. For example, if a Softr workspace hits its monthly workflow limit, those workflows pause until the limit renews or the workspace is upgraded. This could interrupt your customer service if you are not prepared for it. A custom portal requires a budget up front, so it is not the cheaper option initially. However, it avoids the per-user fees that can make software expensive as you grow.

When to buy software, and how to choose it

Buy software if your portal is mainly support tickets and help articles, because a custom build will cost more for the same job. Bespoke builds cost more, so we only suggest them when they offer a clear return. "If an off-the-shelf tool works, we'll tell you, even if it means a smaller project."

  • A website is enough: A standard Webflow site might handle your needs without extra software. If your tasks are simple, a basic website often provides the necessary interface for customers to find information or contact you.
  • You need it within a month: Software is ready much faster than custom code. If you require a working product in less than a month, choosing an off-the-shelf tool is the practical path.
  • Lowest cost comes first: If you want the cheapest build possible, standard software is usually the answer. Custom development requires a higher initial investment to cover the design and build process.
  • No owner after launch: If no one will own the product after launch, a custom build is not suitable. You need someone to manage and maintain a bespoke system once it goes live.

When you evaluate different software options, use these four tests from Zapier to compare them.

  • User experience: This test looks at how easy the tool is to use for both the person managing the portal and the clients using it. A difficult interface can lead to more support requests rather than fewer.
  • Functionality: You must check if the tool has enough features for your specific use. This includes things like ticketing, communication channels, analytics, and file storage.
  • Security: Evaluate the tools for secure file sharing, password protection, data encryption, and access control. These features protect your business and your customers' information.
  • Integrations: Check how well the portal connects with your other apps. This includes tools like CRMs, email marketing software, Microsoft 365, and Google Workspace.

To run a practical comparison, start by writing down the exact tasks customers must finish in the portal. For example, list every step needed to submit a ticket or download an invoice. Next, count your current staff members and the number of customer logins you expect to have. This helps you understand how pricing models like per-agent or per-user will affect your budget. Finally, perform a trial of those specific tasks. Open the software and try to complete every task on your list from both an admin and a customer perspective. This shows you how the software behaves in real-world scenarios before you commit to a subscription.

You should also check which plan includes your branding and domain. For example, Softr offers a custom domain from its Basic plan, while the Pro plan allows for the removal of Softr branding. If you need extra custom domains, these can cost $15 a month or $13 if billed annually. Checking these details prevents unexpected costs when you try to make the tool look professional.

Whichever route you take, agree a written scope before you compare prices. Defining exactly what the system must do allows for an accurate comparison between different vendors and builds.

UK GDPR checks before you choose a portal

A portal holds personal data, so you stay responsible for that data whether you subscribe to software or build your own. You act as the controller, while the vendor or developer acts as a processor, which is an organisation that processes personal information on your behalf. You remain responsible for UK GDPR compliance regardless of who manages the technical side. This means you must only use processors that can demonstrate their processing meets legal requirements. Because every business has different needs, you should check your specific situation with a legal adviser.

In practice, the security principle requires that you process personal data securely using appropriate technical and organisational measures. This includes setting up appropriate access controls to protect the information you store. You must make sure only those who need to access certain data can do so. A marketing manager might see this as managing permissions for different staff roles or customer levels to keep data private. If you use a tool, the responsibility for how that data is handled remains with your business.

When you evaluate a vendor or developer, use these checks to understand how they handle your data and responsibilities.

  • Contract: Ask if there is a written contract between the controller and processor. This document should cover what is processed, why it is being processed, and how long it stays in the system. It must also state that processing only happens on your documented instructions. You should also ask how the contract covers security measures, the use of sub-processors, and the process for deleting or returning data when the contract ends.
  • Breaches: Ask how a breach is handled. A processor must tell the controller about a breach without undue delay. You then decide whether to report it to the ICO. A notifiable personal data breach must be reported to the ICO without undue delay and no later than 72 hours after you become aware of it.
  • Access requests: Ask how the system handles subject access requests. Under the UK GDPR, you must respond to these without undue delay and within one month of receipt. This time limit can be extended by up to two further months for complex requests or multiple requests from one person. A portal can help meet these requirements by providing remote access on a secure system where a person can download a copy in an accessible format.
  • Data outside the UK: Ask where the data is stored and if it is accessible to organisations outside the UK. Transfer rules apply when you send personal information or make it accessible to a separate organisation outside the country. You should ask if these transfers are covered by UK adequacy regulations, appropriate safeguards like an International Data Transfer Agreement, or an exception.
  • Logins: Ask about account security to prevent unauthorised access. The NCSC recommends using multi-factor authentication for all important accounts and internet-facing systems so a stolen password alone does not open the account. You should also ask if the system uses throttling, which is a growing delay between login attempts, or account lockout to limit guesses from an attacker.
  • Baseline security: Ask what technical controls are in place. The NCSC describes Cyber Essentials as a minimum standard of cyber security with five technical controls, including user access control. While the ICO considers Cyber Essentials a good starting point, it only provides a base set of controls and you may have to go beyond it.

Testing the portal with disabled users in mind is another practical step. All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010, or the Disability Discrimination Act 1995 in Northern Ireland. Testing how the interface works for everyone helps you understand if the tool meets these accessibility requirements.

How a custom portal works and what sets its cost

A custom portal runs on its own back end while customers sign in through your existing website, and its price depends on the user types, screens and systems involved. The back end refers to the systems behind the site that store data and run the logic. Big Rocket classes a customer portal as a web app, which is a site that lets people finish a task where your clients or employees log in. This is built using Webflow and a custom back end.

  • Access: Users sign in through your current website while the portal runs on its own back end.
  • Privacy: Accounts, roles and permissions control visibility down to individual records so users only see their own data.
  • Consent, data requests and deletion are built in from the start.
  • Hosting: The back end is hosted on Cloudflare, with the Webflow site in front.
  • Mobile: Big Rocket designs portals mobile first, so they can be saved to a phone's home screen like an app.

The price of a customer portal depends on the number of user types, the screens they need and the systems involved. Because custom portals depend on scope and have a huge price range, Big Rocket publishes no range. We cost each project from the brief, covering what it needs to do, what it connects to and what your team will manage. After a first call and a short discovery, you get a written proposal.

  • Users: This relates to how many user types exist and what each can do.
  • Data: This involves the information you own and the systems that house it.
  • Rules: This covers the rules and automation the system must follow.
  • Security: This includes security, access rights and compliance requirements.

A marketing manager can manage these costs by refining the project scope before asking for a quote. You can reduce user type costs by limiting how many different roles exist in the system. For data and rules, you can lower the price by deciding exactly which information is necessary to store or automate. To manage security costs, you can define the specific access rights and compliance requirements needed for your business before starting the build. This planning helps you understand the investment required for your specific needs. A first release covers the core task. Big Rocket then adds to it in stages, and the proposal sets out every stage with dates. Once a project is live, Big Rocket can maintain a bespoke build, or hand over to your developers with documentation. This differs from standard software because there are no per-seat fees, but there is a build cost up front.

Bring your list of user types, screens and systems to a discussion. You can read how we work to learn more.

Sources

Researched and fact-checked with the help of AI tools and Ahrefs data.