02 / Familiar situations
Your team has become the helpdesk.
A portal usually only becomes a topic once the manual work piles up. Do you recognise any of these situations?
Questions that keep coming back
Customers call or email for information that already exists somewhere: the status of a request, an invoice or a document.
Data in too many places
Changes come in by email, forms and phone, and then have to be processed by hand in several systems.
Service that doesn't scale
More customers or members means more work for the same team, while many tasks could easily be handled by people themselves.
03 / What you get from us
A portal that fits the way you serve people.
We don't build an off-the-shelf package with your logo on it, but an environment built around the tasks your customers and employees actually carry out.
What we build
- accounts, roles and permissions per type of user;
- self-service for data, requests and changes;
- sharing, signing and finding documents;
- messages and notifications at the right moment;
- integrations with your CRM, ERP or accounting system.
What you notice
- fewer routine questions for your team;
- data that is entered only once;
- an up-to-date overview per customer or case;
- an environment you extend step by step;
- code and data that remain yours.
04 / Our approach
From first sketch to a portal that gets used.
A portal succeeds when people want to use it. That is why we start with the tasks, not the screens.
- Step 1
Mapping the tasks
We determine which questions and tasks take the most time and what each type of user needs to be able to do.
- Step 2
First version
We build the core: logging in, the most important self-service and the integration with your existing system.
- Step 3
Testing with users
A group of customers or employees uses the first version. Whatever causes friction, we adjust.
- Step 4
Extending
After go-live we add new features step by step, based on usage and feedback.
05 / Good to know
Questions about portals.
Can't find your question? Feel free to send us a message.
Can a portal connect to our existing systems?
Yes. That is usually the core of the work. We connect through the APIs of your CRM, ERP or accounting system, so data isn't entered twice.
How do you handle privacy and access?
We include roles, permissions and logging from the start. Which requirements apply to your organisation, we agree on and record up front.
Who owns the software?
We agree on code, ownership and handover in advance. No knowledge stays stuck with us.