A customer portal is a password-protected part of your website or app where customers serve themselves. They check an order, download an invoice, move a booking or update their details without emailing you. You need one when your inbox has turned into the portal: if staff spend real hours every week answering the same "where's my order" and "can you resend that" emails, it's time to price out self-service.
What goes inside a portal, and what to leave out
- Status. Where an order, job, project or repair stands. For many businesses it's the question customers email about most.
- Documents. Invoices, receipts, contracts, reports and proofs, ready to download instead of lost in email threads.
- Bookings. Customers book, move or cancel on their own, and your rules apply every time.
- Account & billing. Contact details, payment methods, subscriptions and history.
- Support. Requests tracked in one place instead of scattered across everyone's inbox.
Resist ordering the whole list. Every module adds build cost, integration work and one more thing to support, so start with the one that would save the most email.
You can build one three ways, and the cheapest has a catch
Use what your platform already includes
Stores on Shopify and platforms like it come with customer accounts. Booking tools let people reschedule. Accounting tools have invoice portals. This is the cheapest route by a distance. The catches are rigidity and fragmentation. Three logins for three jobs is homework for your customer, whatever you call it.
Buy a portal product and set it up
Dedicated client-portal software, configured for your business. It launches faster than custom work and hangs together better than a patchwork of platform features. You pay for that with a subscription that lasts as long as you use it, and with a product built around someone else's idea of how your business runs.
Build a custom module into your site or app
It follows your workflow, wears your brand and connects to the systems you already run. Choose it when the portal is the product experience. Go in knowing it's real software engineering: sign-in, permissions, data handling and the security duties below all have to be done properly.
Once customers can log in, you have new duties
A login means you now hold accounts and personal data, and that brings obligations. Sign-in has to be secure, and the password-reset flow must not leak. Permissions have to keep customer A from ever seeing customer B. Your privacy policy has to stay accurate. Do any of it carelessly and you carry the breach exposure. That's the best argument against the cheapest possible build: a portal is a trust surface. In our six lenses it sits in Security and Trust, which is why we treat portal work as systems engineering and put an evaluation gate in front of it.
Customer portal questions owners ask
How do I know my business needs a customer portal?
Count the repeat emails: where's my order, can you resend the invoice, can I move my appointment. If they eat real staff hours every week, you're paying people to be a slow portal, and self-service is worth pricing out. Start with the one module that would save the most email.
How much does a customer portal cost to build?
Platform features are often included in what you already pay. An off-the-shelf portal costs a subscription for as long as you use it. A custom module is a real engineering project, priced by how many systems it connects to, what customers can do inside it and the security work it needs. Those drivers tell you more than the sticker, so ask any builder to walk you through them.
Can a portal hurt my business?
A bad one can. Confusing self-service creates more email, and sloppy security turns a convenience into a breach risk. Keep the first version small, and test it hard before you accept it.
Portals are the kind of work the Studio builds
A portal or customer module is product-systems work. We build it with the security duties planned in from the start and an evaluation gate before launch.
Product innovation at Houtos Getting a site built