Platform development · customers, dealers, members and partners
Let customers and partners act within the agreements you share.
A dealer wants to prepare an enquiry. A customer needs to change an order. A partner wants to see what has been approved and which commission applies. A portal gives them access to your service, with information and actions that reflect their relationship with your business.
From our work · application and partner platform
The same product, not the same permissions.
Administrator
Overview and authority to record commission batches.
Partner
Applications and terms associated with their relationship.
Subpartner
A distinct role within the commercial relationships.
More than documents behind a sign-in
Consider a manufacturer whose dealers have different product ranges and pricing agreements. Product information may be shared, while ordering, proposing changes and viewing prices require specific arrangements for each relationship and role.
We design what people can do independently and where a colleague remains involved. Asking a question or getting help belongs in that experience. Self-service should give customers and employees more options, not make personal contact inaccessible.
What you receive
A design for each relationship and role
User journeys specifying information, actions and decision points. We review them with the people who understand the customer or partner relationship. Acting for an organisation, colleague or family member also requires explicit choices.
Portal and business logic together
The interface, backend and necessary integrations. Pricing rules, approvals and access permissions apply beyond individual screens. We separate information belonging to different relationships and test who can access each record and action.
A rollout with clear follow-up
A first complete user journey, support arrangements and the means to administer the service. We also design how an employee picks up a question from the portal, connecting digital and personal service.
The agreements behind the interface matter
For an application and partner platform, we delivered analysis, design and development of the portal and API. Partner relationships, application statuses and commission tiers became part of the administration.
For an employers association, we developed applications and cloud architecture from an external partner's designs. On a digital healthcare platform, we worked on the patient journey and communications integration alongside the project lead and DevOps.
From the outside, portals can appear similar: sign in, read information, submit a request. Their value lies in the business rules and responsibilities underneath. We design those around your service.
Begin with one action that makes a difference
For example, a dealer submits a complete enquiry with the specifications sales needs to respond. Rather than twenty disconnected features, the first release supports a usable part of the service, from request to response.
We agree which users and systems it involves and how readiness for rollout will be judged. Explore systems integration and security and privacy for the underlying engineering decisions.
Discuss who your portal should serve and what they should be able to do independently.
Your next step
An idea, or a detailed brief?
We start from where you are. Discuss the application, any existing requirements and the team we would work alongside.