Customer portal development: what it involves and what it costs

What is a customer portal?

A customer portal (or client portal) is a secure, logged in area of your website or app where each customer sees their own information and completes tasks with you without calling or emailing. Typical tasks are downloading documents, checking the status of a job or order, paying an invoice, approving a quote, uploading files and sending a message to the right person.

The business case is nearly always the same: fewer “where is my…” calls and emails, faster payment, fewer documents lost in inboxes, and a better impression on customers who expect to self serve. It’s worth stating that case in numbers before you scope anything, because it decides how much portal you should build.

What does a portal need?

Every portal needs secure access, a clear view of the customer’s own data, and a way to act on it; everything else should earn its place. This table separates the core from the common additions and the features that usually add significant cost.

Area	Core	Common additions	Adds significant cost
Access	Email login, multi factor authentication, password reset	Magic links, social login	Single sign on with customers’ own identity providers; delegated access for agents or advisers
Roles	Customer and staff admin	Several users per customer account with different permissions	Complex hierarchies, such as head office, branches and sites
Data	Dashboard of current items; status tracking	Search, filters, history	Real time updates from several back office systems
Documents	Download statements, reports, contracts	Uploads from customers; e-signing	Version control, approvals workflows, document generation
Payments	Links to pay invoices	Card payments in the portal, saved cards	Subscriptions, payment plans, direct debit, multi currency
Communication	Contact form or message thread	Email and SMS notifications	Live chat, in app messaging with attachments, AI assistant
Integrations	One system feeding the portal	Two or three systems, such as accounting and CRM	Two way sync with several systems; legacy systems without an API
Admin	Staff manage users and content	Reporting on portal use	Configurable workflows and forms without developer help
Channels	Responsive web	Installable web app	Native iOS and Android apps (see publishing to the App Store and Google Play)

The most common scoping mistake is putting everything in the middle and right columns into version one. Launch with the core plus the two or three additions that remove the most manual work, measure use, then extend.

Should you use an off the shelf portal or build a custom one?

Use an off the shelf portal when your process fits a product and your customer numbers keep licensing affordable; build custom when the portal must present data from your own systems, is part of your offer, or outgrows per user pricing. Prices below are as published at the time of writing (November 2026).

Option	Typical published pricing	Good for	Watch for
All in one client portal products (for example SuiteDash)	From US$19 a month on the entry plan, with US$49 and US$99 plans, unlimited users	Small service businesses wanting CRM, projects, invoices and a portal in one	Fixed data model; limited integration depth; data stored on the vendor’s servers
Low code portal platforms (for example Microsoft Power Pages)	AU$299.30 a month per website for a pack of 100 authenticated users, paid yearly, ex GST	Organisations already on Microsoft 365 and Dataverse	Licensing scales with users; specialised skills still needed for anything complex
Portals built into your CRM, practice or job management system	Often included in a higher plan tier	Businesses whose data already lives in that system	Locked to that vendor’s features and branding
Custom portal	Build cost, then hosting and maintenance	Portals that combine several systems, are customer facing products, or need unusual workflows	Higher upfront cost; you own maintenance

There is no shame in buying. If a practice management product already has a portal your customers can use, configuring it is almost always the right first step. Our build vs buy guide sets out how to decide.

How much does a custom portal cost?

A custom customer portal in Australia typically costs $22k to $120k for most small and mid sized businesses, with complex B2B and multi tenant portals costing more. These are typical market ranges in AUD, ex GST, covering design, build, testing and launch. They are ranges, not quotes.

Portal type	Typical scope	Typical effort	Cost range
Configured off the shelf portal	Setup, branding, user import, one integration	3 to 15 days	$3k to $20k plus subscription
Simple custom portal	Login with MFA, dashboard, documents, status tracking, messages; data from one system	20 to 40 days	$22k to $60k
Mid range custom portal	Several roles, payments, notifications, uploads, admin area, two or three integrations	40 to 80 days	$45k to $120k
Complex portal	B2B ordering and approvals, account hierarchies, single sign on, many integrations, or a native app	80 to 180+ days	$90k to $270k+

How the ranges are worked out. Effort is converted at an assumed blended agency rate of $1,100 to $1,500 a day. For context, Re:Sourced’s July 2026 guide puts senior software engineer contractor rates in Sydney at $800 to $1,100 a day ex GST; agencies charge more to cover design, project management, testing and support.

Running costs to budget for

• Hosting, database and file storage in an Australian region: typically tens to a few hundred dollars a month for a small to mid sized portal.
• Email and SMS notifications: usage based.
• Payment fees: for example, Stripe’s Australian pricing lists 1.65% + A$0.30 for domestic cards and 3.5% + A$0.30 for international cards, including GST, at the time of writing.
• Platform API fees where a connected system charges for API access.
• Maintenance: roughly 15 to 20% of build cost a year for security updates, fixes and small changes.

A custom portal you own is generally treated by the ATO as in-house software rather than an expense; see software development tax deductions and ask your accountant.

A worked example: a portal for an accounting practice

This is a hypothetical scope to show how the effort adds up, not a real project. An accounting practice with about 400 client entities wants clients to stop emailing documents and asking for status updates.

Work package	Effort
Discovery, user flows and design of core screens	6 days
Login with MFA, client accounts with several users each, staff admin	6 days
Secure document exchange: uploads from clients, downloads of returns and reports, virus scanning	7 days
Job status tracking from the practice management system (one way, scheduled)	8 days
Message threads per job with email notifications	5 days
Invoice list with card payment	5 days
Audit logging, security testing and fixes	5 days
Testing, launch, staff training and handover	6 days
Total	48 days

At $1,100 a day that’s $52,800; at $1,500 a day, $72,000, ex GST. Adding e-signing through a third party service, or a two way sync with the practice management system, would move it toward the top of the mid range band. For AI features that suit practices, such as document classification, see AI for accounting firms.

What security and privacy duties come with a portal?

A portal puts many customers’ personal and financial information behind one login, so treat access control and logging as the core of the build. If your business is covered by the Privacy Act 1988, APP 11 requires you to take reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure. The OAIC’s guidelines say reasonable steps include technical and organisational measures, and APP 11 also requires you to destroy or de-identify personal information once it is no longer needed, subject to legal retention requirements.

A practical security checklist for any portal:

1. Multi factor authentication for all staff and offered to all customers, required for high risk actions.
2. Authorisation checks on every request, so a customer can never reach another customer’s record by changing an ID in the address bar. It is one of the most common serious flaws in portals and web apps.
3. Least privilege for staff: roles that limit who can see which customers.
4. Encryption in transit and at rest, with keys managed in your cloud account.
5. Audit logs of logins, document downloads, changes and admin actions, kept long enough to investigate an incident.
6. Secure file handling: type and size limits, malware scanning, and private storage with expiring links.
7. Retention rules that delete or de-identify old documents and closed accounts.
8. Independent security testing before launch and after major changes.

If something goes wrong, the Notifiable Data Breaches scheme may require you to notify affected customers and the OAIC. Our guide to Notifiable Data Breaches and your software explains what a portal must be able to answer in an investigation.

How do you plan a portal so customers actually use it?

Portals succeed when they are the easiest way for a customer to get something done, and fail when they are an extra login for information customers can get faster by email. Plan with that test in mind.

1. Count the requests. For a month, tally the calls and emails a portal could answer: document requests, status checks, invoice copies, address changes. The biggest categories are your version one scope.
2. Decide the source of truth for each item. If job status lives in your job management system, the portal reads it from there. Don’t create a second copy staff must update by hand, or it will be out of date within a week.
3. Design the first login. Invitations, account activation and multi factor setup are where most customers give up. Keep them short and test them with real customers, including less confident ones. Accessibility matters here too; see our accessibility guide.
4. Change staff habits. If staff keep emailing documents, customers keep expecting email. Agree that new documents go to the portal, with an email notification that links to it.
5. Launch in stages. Start with a group of friendly customers, fix what confuses them, then roll out.
6. Measure. Track activated accounts, monthly active customers, documents exchanged through the portal and the drop in the request categories you counted in step 1.

If adoption stalls, the cause is usually one of three things: the information customers want isn’t there, it isn’t current, or logging in is harder than asking.

Examples of portals by industry

These are hypothetical examples of what a portal typically does in each industry, to help you scope your own.

• Accounting and bookkeeping: document requests and exchange, tax return approvals, e-signing, job status, invoice payment.
• Real estate and property management: owner statements, maintenance requests with photos, inspection reports, tenant applications. See real estate software.
• Construction and trades: project progress with photos, variations to approve, progress claims and payments, defect reporting. See construction software and AI.
• Healthcare and allied health: appointment history, forms before visits, documents and invoices. Health service providers are covered by the Privacy Act regardless of turnover, according to the OAIC, and health information needs particular care. See healthcare.
• Wholesale and B2B suppliers: reorders from account specific price lists, order tracking, invoices and statements, credit applications.
• Professional services: matter or project updates, secure document sharing, approvals, time and billing summaries.

How AWLabs approaches portal projects

We start with a Development Consult, then a paid Discovery Audit, credited in full against the build, that identifies the customer tasks worth moving online, the systems the portal must draw on, and whether an off the shelf product would do the job. If one would, we’ll tell you. If custom is the better fit, the work is priced as a fixed price Schedule of Work with three options, The Minimum, The Recommended and The Complete, so you can choose how much to launch with. Portals are built with multi factor authentication, per request authorisation checks and audit logging as standard, hosted in an Australian cloud region wherever the services you need are offered onshore. Senior engineers lead every build. See our web and mobile app development and custom app development services, and our API integration cost guide for the integration side.