Customer portals
Customer portals and self-service solutions
We build secure, fast customer portals on top of the systems you already use — ERP, CRM, billing, case management — so your customers can find answers themselves instead of emailing support.
What you're left with
What a customer portal solves
- Daily support emails about status and invoices
- Fewer
- Self-service for customers across time zones
- 24/7
- Hosting and data — Vercel EU or AWS Frankfurt
- EU
- Rollout from the first usable version
- Iterative
How we think about portals
A portal replaces the email firehose.
A good customer portal replaces the daily stream of emails, phone calls and PDF attachments. Your customers log in, see exactly what they've ordered, what's on its way and what's missing — and your support team can focus on the hard questions instead of digging up the same document 40 times a week.
We build portals in Next.js on the edge, with role-based access, audit logs and integrations to the systems you already have. The customer sees one clear interface — behind it, we pull data from Economic, Dynamics, Salesforce, your own API, or a mix. No long re-platforming, no forced migration.
We take the portal end to end: from the first user conversations and wireframes through to operations, monitoring and ongoing development. You don't need an internal dev team or an escalation contract with three different vendors — we're one number to call.
What we deliver
This is what we actually build.
A complete portal with login, integrations, cases and operations — built on the edge.
Login, roles and SSO
Email/password, Microsoft Entra (Azure AD), Google Workspace or your own identity provider. Per-organisation roles, multi-account switching, and audit logging on sensitive actions.
Integration with your core systems
We pull orders, invoices, deliveries and cases from ERP, CRM and case-management systems via their APIs — or via a cache if the source is slow or flaky.
Cases, documents and files
Customers can open cases, upload attachments, download contracts and see history per user and per company. With versioning and access control built in from day one.
Notifications and emails
Transactional emails (order updated, invoice ready, case answered) delivered reliably via Resend or Postmark. Web push and in-app notifications for the customers who want them.
Usable, branded UI
We design the portal to look like your brand — not a SaaS template. Accessible from day one (WCAG 2.2 AA), responsive on mobile, and fast enough to feel like a native app.
Operations, observability and support
We set up monitoring, alert on errors and keep the portal alive. You get an SLA, dashboards on operations and a clear number to call when something's on fire.
Before we start
What you should consider first.
Timeline and complexity
A portal with login, order overview and invoice download can be in production in 6–10 weeks. Add deep integration with several systems, case management, billing and notifications, and you're typically looking at 3–5 months. We never ship everything in one go — we roll out incrementally and learn while customers actually use it.
Security and compliance
We treat portal data as the production data it is. Hosting in the EU (Vercel EU or AWS Frankfurt), encryption in transit and at rest, access logging and minimal data sharing. If the portal needs to handle GDPR-relevant personal data or ISAE 3402 controls, we design for it from the start — not as an afterthought.
Integration: API vs. caching
If your ERP/CRM has a fast and reliable API, we read directly. If not, we build a small cache (typically Postgres on Supabase) that syncs on a cadence you can trust — so the portal doesn't go down just because the finance system is down on a Sunday evening.
Maintenance after go-live
A portal is never finished — there are always new requirements from users, new integrations from your team and new versions of the systems it talks to. We offer a fixed monthly operations and development agreement so you know exactly what it costs to keep it sharp.
FAQ
What people usually ask.
Can we connect the portal to our existing ERP?
Yes — that's the normal case. We've integrated with Economic, Business Central, Dynamics 365, Salesforce, NetSuite and a long list of industry-specific systems. If the ERP has a REST or GraphQL API, we read directly. If not, we build a synchronised cache. We review your current setup in discovery and propose the easiest path.
How long does it take to build a portal?
An MVP with login, organisation switching, order list and invoice download is typically in production in 6–10 weeks. A full portal with cases, notifications, file upload and deeper integrations is typically 3–5 months. We roll out incrementally — the first version goes live early, and we build on top based on what customers actually use.
How do you handle security and GDPR?
We host in the EU (Vercel EU or AWS Frankfurt), encrypt everything in transit and at rest, audit-log sensitive actions and set up role-based access from day one. We sign a data processing agreement with you and document the data flow. If the portal needs to handle personal data for your end customers, we design for data minimisation and right-to-erasure from the start.
Can our internal IT team take over later?
Yes. The code lives in your GitHub from day one, documentation comes with it, and we run a formal handover when you're ready. We can also continue with operations and ongoing development on a fixed agreement — or a mix where your team handles new features and we handle ops and security updates.
How do we get started?
We start with a 1–2 week discovery phase where we walk through your systems, user profiles and integration needs. You leave with a concrete plan, an open budget based on scope, and a risk register — before we touch code. We always discuss scope and price privately in the conversation, not on a website.
Related services
- Marketing sitesFast, SEO-strong marketing sites built to convert — without a heavy CMS in the way.
- E-commerceCustom storefronts and headless commerce built on top of Shopify, Stripe or your own commerce API.
- Headless CMSSanity, Contentful or Payload — set up so content folks can work without waiting on a developer.
Ready to get started?
Let's have a no-pressure conversation.
We'll get back within one business day with concrete input — not a stock proposal.