From a self-built prototype to a production portal for mobility advice
The prototype came from the director. We turned it into a secure production portal, with a new website alongside.
- Sector
- Mobility
- Solution
- Customer portal and website
- Built on
- .NET, Azure, Next.js (website)
- Collaboration
- Analysis, build, maintenance and development
A prototype that worked, but could not go into production
This advisory firm mediates between employers and providers of business mobility. With an AI building tool, the director had made a working prototype himself of the portal he had in mind: customer profiles, a comparison of providers, requests and agreements.
The prototype showed clearly what the portal had to do. For production the basis was missing: storage, access and integrations were not built to let real customers work on it. The question was to turn this into a secure, maintainable portal and renew the website at the same time.
The calculating heart of the prototype came along. The rest was redesigned.
A production portal, with the website alongside
The analysis of the prototype determined what was reusable and what had to be redone. The comparison logic stayed, the foundation underneath is new.
Substantiated advice
Advisers compare providers on weighted criteria, see immediately where a provider drops out and share a substantiated advice with the customer.
Requests by customers themselves
Drivers and employers submit requests and follow the status. Everyone has their own access and rights.
Agreements and messages with the file
Agreements come from templates. Messages and status changes sit with the file, so nothing disappears into a mailbox.
Integration with the accounts
Invoices and files match up, without retyping.
New website with own management
A site in the branding with a blog the customer maintains themselves.
One environment for advisers and customers
Advice with substantiation
The comparison is traceable for every customer: which criteria, what weight, why a provider drops out.
Customers handle requests themselves
Requests and status questions go through the portal instead of email.
Building on what already worked
The logic from the prototype was carried over. Storage, access and integrations were rebuilt.
Maintenance, monitoring and a shared backlog
Portal and website are in our care, with monitoring and support in a monthly contract. New wishes go on a shared backlog and are picked up in phases.
A process outgrowing its spreadsheets too?
Tell us where it hurts, and we will tell you how we would approach it.
Book an intro callCurious what this means for your business?
A first conversation. You tell us where it hurts, we tell you how we would approach it.