Customer Portal Development: Features, Cost, Build vs Buy

Customer portal development means giving your customers a secure, personal environment where they check orders, documents, invoices and status themselves instead of emailing or calling you. The value is not in the portal screens but in the integrations behind them: the portal shows live data from your ERP, accounting or scheduling system. A simple portal on a single data source can be live within weeks; a portal with several integrations, roles and AI features is a project of a few months.

The short version:

• A customer portal pays off when your team spends hours on "where is my order" questions and emailing documents back and forth.
• Cost is driven by integrations, roles and security, not by the number of pages.
• Off-the-shelf portals work if your process is standard. Custom pays off when the portal must follow your own data and workflow.
• AI in a portal is useful for search and answering questions, but customers must always be able to reach a human.

What is a customer portal and when do you need one?

A customer portal is a protected part of your website, or a separate web app, where customers log in. They see their own data and can take action: upload a document, approve a quote, report an issue, download an invoice.

You probably need one if you recognize these signals:

• Your inside sales or support team answers the same status questions by email and phone every day.
• Documents such as drawings, certificates, work orders or reports travel back and forth as attachments.
• Customers need to submit information (data, photos, signatures) and it arrives in scattered emails.
• You want customers to see progress without someone internally writing an update.

An example: an installation company with hundreds of active projects. Customers want to know when the technician is coming, which parts are on order and where the handover documents are. A portal that reads from scheduling and project administration lets them find that themselves. The team keeps its time for questions that actually need a person.

Which features belong in a good customer portal?

Do not start with a list of twenty features. Pick the three that remove the most questions or manual work. These are the building blocks we see most often:

Roles and permissions

A portal only becomes truly useful when it reflects how your customers are organized. A buyer wants to see different things than a finance clerk at the same company. Headquarters wants to see all locations, a branch only itself. Design this upfront: adding permissions later is expensive and error-prone.

Integrations: where a portal gets its value

A portal without integrations is a second administration that someone updates by hand. Nobody keeps that up. The data has to come from the systems you already run:

• ERP and accounting: for invoices, orders, customer data and outstanding balances. Think Exact Online, AFAS, Moneybird, or your own ERP.
• CRM: HubSpot or a custom CRM, for contacts and open deals.
• Document storage: SharePoint, Google Drive or a document management system.
• Scheduling: your planning tool or calendar, for appointments and field visits.

Key integration decisions:

1. Read only, or also write? Showing data is simpler. If a customer changes an address in the portal that must flow back to your ERP, you need rules for conflicts and validation.
2. Live or synced? Reading live through the API is always current but bound to the vendor's rate limits. Syncing periodically into your own database is faster and more robust.
3. What is the source of truth? Decide per data field which system leads.

More on the practical side in ERP integration and automation.

Build or buy a customer portal?

There are ready-made portal products, often as a module of your CRM, help desk or ERP. They go live faster and have predictable monthly costs. Custom costs more upfront but follows your process. An honest comparison:

Choose off-the-shelf if your process is standard and the portal module of your existing software already has the data. Choose custom if you need to combine data from several systems, if customers need to do something no product supports, or if per-customer licenses become too expensive as you grow.

How much does customer portal development cost?

As with other custom software, price depends on integrations, roles and security requirements. As a worked example at roughly 100 euros per hour:

Add hosting, maintenance and usage-based AI costs. The reasoning behind these ranges is covered in custom software development cost. At Airflows, a portal project starts with a fixed-price Discovery from 3,500 euros, followed by a working first version in 4 to 8 weeks.

Security and privacy in a customer portal

A portal with customer data is an attractive target, and mistakes are immediately visible to customers. The basics:

• Access control on the server, not in the browser. Every data request must check on the server whether this user may see it. A known example of what goes wrong: CVE-2025-48757 concerned apps built with Lovable and connected to Supabase without proper access control, which exposed other users' data.
• Strong authentication. Two-factor authentication for users with access to sensitive data.
• Audit logging. Record who viewed or changed what.
• Data processing agreements and data location. Know where your data lives and who can access it, especially under the GDPR.
• File validation. Check uploads server-side for type, size and ownership.

AI in a customer portal

AI adds value in a portal in three places:

• Answering questions from your own documentation. An assistant that searches manuals, terms and project information and cites its sources. The technique is called retrieval augmented generation: see RAG explained.
• Smart intake. A customer describes a problem in plain language, and AI turns it into a structured ticket with the right category and urgency.
• Document processing. Automatically reading submitted documents and checking them for completeness.

Two rules apply in Europe. Dutch regulators AP and ACM state that organizations using chatbots must always offer the option to speak to a human and make clear that you are talking to a bot. And since August 2, 2026, the transparency rules of the EU AI Act apply: an AI system that interacts with people must be recognizable as AI. More in AI chatbots for customer service.

Frequently asked questions

How much does it cost to build a customer portal?

A basic portal showing orders and invoices from one system starts around 10,000 to 25,000 euros. With several integrations, document management and roles per customer you are more likely between 25,000 and 60,000 euros. Hosting and maintenance come on top as monthly costs.

How long does customer portal development take?

A first working version with the key features and one or two integrations can be live in 4 to 8 weeks. After that you expand based on how customers actually use it.

Can a customer portal integrate with my ERP?

Yes, as long as the ERP has an API, which most modern systems do. You can read orders, invoices, customer data and balances and often update them too. Watch the API rate limits and define which system is the source of truth for each field.

Is an off-the-shelf customer portal cheaper?

In the short term, usually yes. But per-user or per-customer licenses add up as you grow, standard connectors are often limited, and you work within what the product allows. Custom pays off when you combine data from several systems or have a workflow of your own.

Next steps

For one week, count the questions and requests customers send by email and phone. Group them and find the three that cost the most time. That is the core of your first portal version and your business case in one.

Want to discuss what a portal could do for your customers? See our services or start with the free AI scan.

Sources

• AP and ACM: chatbot mag mens niet volledig vervangen bij klantenservice (October 2, 2025)
• Dutch Data Protection Authority: Vanaf 2 augustus wordt duidelijker of het AI is of echt (July 31, 2026)
• AI Act Service Desk: Timeline for the Implementation of the EU AI Act (September 25, 2026)
• NVD: CVE-2025-48757 (2025)