South African pricing guide

How much does a custom client portal cost in South Africa?

Plan on R75,000 to R300,000 excluding VAT for most custom client portal projects. A focused MVP is usually at the lower end. A complex customer platform can cost substantially more.

Get a portal estimate See the cost ranges

Reviewed 17 August 2026 · 12 minute read · Prices in South African rand

The short answer

A focused, production-ready custom client portal in South Africa commonly needs a budget of R75,000 to R180,000 excluding VAT. An integrated B2B portal that connects to existing systems, applies customer-specific permissions and supports several workflows is more likely to fall between R180,000 and R300,000 excluding VAT.

Complex platforms with several integrations, approval workflows, payments, advanced reporting, high user volumes or specialised security requirements usually start from R300,000 and are scoped individually.

The number of screens is a poor way to estimate a portal. The business process behind those screens is what usually determines the effort.

Still deciding whether the need is strong enough? Read the seven signs that show when a business may need a custom client portal.

Typical custom client portal cost ranges

Portal type	Planning budget	Typical scope
Focused custom MVP	R75,000 to R180,000	Secure sign-in, customer-specific data and one core workflow with limited integrations.
Integrated B2B portal	R180,000 to R300,000	Several workflows, business-system integrations, roles, notifications, documents and reporting.
Complex customer platform	R300,000+	Multi-system architecture, advanced permissions, payments, approvals, audit controls or high scale.

These are planning ranges, not a fixed price list. They exclude VAT, hosting, third-party licences and ongoing support unless a proposal states otherwise.

What affects the cost of a custom client portal?

Authentication and user permissions

Most B2B portals need more than a username and password. You may need customer organisations, several users per customer, internal administrators, role-based permissions, single sign-on or multi-factor authentication.

If 200 companies use the same portal, each company must only see its own information. This needs careful application and data architecture. Hiding information in the interface is not enough.

Integrations with existing systems

Integrations are often one of the largest cost drivers. A portal may need to connect to a CRM, ERP, accounting system, warehouse platform, Snowflake, payment provider, document store, internal API or legacy database.

The portal does not necessarily replace those systems. It can become the customer-facing layer while existing systems remain the source of truth.

Customer signs inPortal validates accessBusiness system processes requestPortal shows status

What customers need to do

A read-only reporting portal is generally simpler than one where customers complete business processes. Common functions include:

viewing account information, invoices, statements or reports;
submitting documents, requests, orders or quote enquiries;
tracking services, deliveries or support cases;
approving information or making payments;
updating company details and user access; and
receiving notifications or communicating with a support team.

Security, testing and operational risk

Personal, financial or commercially sensitive data increases the need for threat modelling, audit trails, access testing, secure deployment and recovery planning. These are part of the product, even though customers do not see them as screens.

Three example portal scopes

R75k to R180k

Focused customer portal MVP

Secure sign-in, account information, document downloads, detail updates and support requests, with one data source and simple roles.

R180k to R300k

Integrated B2B portal

Customer-specific data, requests, status tracking, notifications, documents and reporting connected to a CRM, ERP, API or data platform.

R300k+

Complex customer platform

Several integrations, advanced roles, approvals, payments, audit controls, white labelling, AI capabilities, mobile features or specialised industry workflows.

How long does a custom client portal take to build?

A focused MVP often takes 4 to 6 weeks after scope and access to the required systems are confirmed. An integrated portal commonly takes 6 to 12 weeks. Complex platforms are usually delivered in phases over a longer period.

Phase 1Secure access

Customer dashboard, essential data, one request workflow and status tracking.

Phase 2Deeper capability

Reporting, payments, documents, further integrations and additional workflows.

API availability, unclear business rules, data quality, security reviews and delayed stakeholder feedback can extend the timeline. A short discovery stage should identify these risks before the full build is quoted.

Should you build a custom portal or buy existing software?

Do not build custom software automatically. If a well-supported SaaS product covers most of the workflow at a sensible total cost, buying it may be the better decision.

Buy or configure

Choose standard functionality

Common document sharing or ticketing
Few unusual business rules
Limited integration requirements
Speed matters more than ownership

Build custom

Support a specific workflow

Several systems must work together
Customer permissions are unusual
The process is a competitive advantage
Manual work cannot be automated well by SaaS

Use the detailed build-versus-buy client portal guide to compare SaaS, configured platforms, custom development and hybrid approaches.

When does a custom portal pay for itself?

The number of customers is not the only factor. A better starting calculation is:

Customers × interactions × handling time × employee cost

If a business handles 600 customer requests each month and each request takes 15 minutes, that represents 150 hours of administration every month. A portal that automates a meaningful share of that work may also reduce errors, duplicated data entry and time spent answering status enquiries.

A proper business case should include the build cost, hosting, support, third-party licences, process adoption and the portion of work that will still need a person.

What should the first version include?

1
Secure customer access
Customers sign in and only access information for their organisation and role.
2
Customer-specific information
The portal provides information customers currently request from employees.
3
One high-value workflow
Start with a request, order, quote, document, report or tracking process that creates measurable value.

What information is needed to estimate a portal?

A useful estimate starts with the workflow, not a list of screens. We normally need to know:

who will use the portal and how many users are expected;
what each type of user must be able to see and do;
which existing systems contain the required data;
whether suitable APIs and test environments are available;
which manual processes the portal should replace;
whether approvals, payments, reports or document handling are required; and
which security, audit, hosting or data-location constraints apply.

A simple workflow diagram and examples of the current spreadsheets, emails and systems are often more useful than a long requirements document.

How LCR Technologies approaches client portal projects

We build custom B2B client portals and internal business systems for organisations that need to connect customers to existing data, systems and workflows.

Understand the current customer workflow and its bottlenecks.
Identify the highest-value manual process.
Map the systems that already contain the required information.
Decide what remains in those systems and what belongs in the portal.
Build a focused first version, then expand it using real usage evidence.

Our work includes legal, finance, rewards and workflow portals, along with APIs, multi-tenant applications and business-system integrations. See our selected work for public examples.

Frequently asked questions

Can I build a client portal for less than R75,000?

Possibly. A template-assisted portal, prototype or tightly limited tool may cost less. A production portal with custom permissions, security, testing and integrations usually needs a larger budget.

Why can two client portals have such different prices?

The interface is only one part of the work. Integrations, permissions, business rules, workflows, data architecture, testing and security often take more effort than the visible screens.

Can we start with an MVP?

Yes. A useful first version normally includes secure access, the most important customer information and one high-value workflow. Further features can follow once real customers have used it.

Can a custom portal connect to our existing systems?

Yes. A portal can connect through APIs, databases, webhooks, queues or other integration methods, so the business does not necessarily need to replace its existing systems.

Can different customers see different information?

Yes. A multi-tenant portal can restrict each customer organisation to its own data, while roles can control what individual users may view or change.

Get a scoped answer

Show us the workflow your customers use today.

Send us the current process, the systems involved, an approximate user count and the first workflow you want to improve. We will help you decide whether to buy, configure or build.

Discuss your client portal Email hello@lcrtech.co.za