Customer portals
people actually use.
Secure self-service portals for your customers, clients, partners and suppliers: documents, orders, applications and account information in one place, connected to the systems behind them. Designed and built in London; free working prototype in 5–10 days.
Self-service that
saves your team time.
A good portal takes routine questions off your team's inbox: customers find their documents, track their orders and send requests themselves, and your staff deal with the exceptions. Magora designs and builds customer, client and partner portals for UK companies, connected to the systems you already run.
Free working prototype
A coded prototype of your portal's core journey in 5–10 working days, before any paid work.
First release in 6–8 weeks
After a two-week Discovery from £3,000, your first users log in within 6–8 weeks.
Your portal, your IP
Code in your repository from day one; source code, designs and IP transferred on payment.
Portals for every
side of your business.
The same building blocks — secure login, roles, documents, workflows, integrations — arranged around who is logging in.
Customer self-service portals
Accounts, orders, invoices, bookings and support requests without a phone call.
Client portals
Secure document exchange, approvals and case progress for accountancy, legal, financial and property clients.
Partner & dealer portals
Dealers, installers and resellers register leads, check eligibility, order and track their own pipeline.
Supplier & contractor portals
Jobs posted, accepted and completed, with documents and invoices in one place.
Member & learning portals
Content, courses, events and payments for members, students or communities.
Employee portals
Policies, requests and the internal tools staff use every day, behind single sign-on.
Portal software
or a bespoke portal?
Off-the-shelf portal products are quick to start and fine for simple needs. A bespoke portal earns its cost when it has to reflect your own rules and data.
| Bespoke portal (Magora) | Off-the-shelf portal product | Your CRM's built-in portal | |
|---|---|---|---|
| Up-front cost | From £10,000 for a first release | Low: subscription | Usually included or an add-on |
| Ongoing cost | Hosting plus support | Per user or per seat | Per seat of the CRM |
| Your rules and workflows | Built in | Within the product's settings | Within the CRM's settings |
| Data from several systems | Yes, through integrations | Limited to supported connectors | Mostly the CRM's own data |
| Best for | A portal that is part of your service | Standard document sharing or ticketing | Customers who only need their CRM records |
Not sure which fits? Discovery ends with a recommendation, including when an existing product is the better answer.
Secure by design,
not by afterthought.
A portal opens your systems to people outside the company, so security is decided in Discovery and tested on every release.
Role-based access
Every user sees only their own records, documents and organisation — tested automatically on each release.
Two-factor authentication
One-time codes or authenticator apps, and single sign-on for staff through Microsoft 365 or Google Workspace.
Encryption & UK or EU hosting
Data encrypted in transit and at rest, hosted in the UK or EU on AWS, Azure or Google Cloud.
Audit trails
A log of who viewed, downloaded or changed what, for your own records and for GDPR requests.
Privacy built in
Data minimisation, retention rules and subject-access exports planned with you up front.
Monitoring & backups
Uptime monitoring, alerts and tested backups in place before the first user logs in.
What a customer
portal costs.
Our 2026 prices in GBP. Our rates start from £49/hour per developer, and £65–£70/hour for a full team with QA and product ownership. Across 12 real 2026 project estimates the median MVP came to about £25,000 (range £11,000–£34,000). For a quick figure, try the cost calculator.
Two weeks: users and roles, journeys, integrations, security and a costed roadmap.
One user type and its core self-service tasks, live in 6–8 weeks. Most MVPs land between £10,000 and £25,000.
Several user roles, integrations and admin tools, delivered in phases.
Hosting, monitoring, security updates and new features.
Five steps to
a live portal.
Weekly demos on a staging portal you can log in to, with real users testing the journeys before launch.
Discovery
2 weeksWho logs in, what they need to do and which systems hold the data — turned into roles, journeys and a costed roadmap.
UX & security design
Within discoveryKey screens tested with real users; access rules, authentication and hosting decided up front.
Build in sprints
6–8 weeksTwo-week sprints with a working release at the end of each, and automated tests on every access rule.
Launch
Go-livePilot group first, then all users, with monitoring, backups and analytics in place.
Support & grow
OngoingNew user types, integrations and features on a retainer, by the team that built it.
Portals we've
built.
From our case studies — more in our work.
Grant Thornton
A self-service platform that automates EMI scheme documentation for the firm's clients, from creation to close-out.
See case study → Energy · Partner portalRetrofit Navigator
A portal for UK retrofit installers to check households against ECO4 and Warm Homes grant rules and run the application from the same screen.
See case study → Logistics · Supplier portalDelivery Management System
A web portal where courier companies register and post jobs, with mobile apps for their couriers.
See case study → IoT · Customer portalOrganic Response
A web portal and iOS and Android apps for configuring and monitoring a smart lighting system.
See case study →What clients
say.
Verified reviews from our Clutch profile — 4.9 out of 5 across 71 client reviews.
“They're accessible, and it doesn't feel like I'm working with a faceless team.”
“Broader than just the code itself, the team strived to understand the entire project.”
“They didn't simply take our requirements and run with them; they truly made an effort to understand everything.”
What makes a
portal work.
Six things we get right before the first line of code.
One clear first job
Launch with the task users need most, not every feature at once.
The right people see the right data
Roles and permissions designed and tested before anything else.
Live data, not copies
Integrations with the systems that own the data, so the portal is never out of date.
Easy sign-in
Two-factor authentication without making every login a chore.
Works on a phone
Most users will open it on a phone at least some of the time.
Measured after launch
Analytics on which journeys are used, and which still end in a phone call.
Customer portal
questions.
A customer portal is a secure website or app where your customers log in to help themselves: see their account, documents and orders, submit requests or applications, and talk to your team. A client portal does the same for professional-services clients, and a partner portal for dealers, installers or suppliers.
A focused first release — one type of user, the core self-service tasks and one or two integrations — starts from £10,000 as an MVP; across 12 real 2026 estimates the median MVP was about £25,000. Larger portals with several user roles and integrations are delivered in phases. Our rates start from £49/hour per developer, and £65–£70/hour for a full team with QA and product ownership.
A free working prototype takes 5–10 working days and Discovery two weeks. A first release typically takes 6–8 weeks after that.
If your customers only need to see invoices or tickets from one system, that system's own portal or an off-the-shelf portal product is usually enough. Build when the portal has to pull from several systems, follow your own rules, or become part of the service you sell.
Role-based access so each user sees only their own data, two-factor authentication, encrypted data in transit and at rest, audit logs of who saw and changed what, and UK or EU hosting. We plan GDPR requirements in Discovery and test access rules automatically on every release.
Yes. Most portals are a front end to systems you already run — CRM, ERP, accounting, document storage — connected through their APIs. See API integration and bespoke CRM development.
Yes. Portals are built responsive by default, and where users need offline access, push notifications or a camera — engineers on site, drivers, installers — we add native or cross-platform apps. See app development.
You do. We sign an NDA on day one, the code lives in your repository as it is written, and source code, designs and IP transfer to you on payment.
Planning a
customer portal?
30-minute call with a senior Solution Architect. Tell us who the portal is for and what they need to do — we will tell you what the first version should be, and what it should cost.