Client portals
Give customers a place to submit information, share documents and follow progress. Design the experience around the tasks they return to.
Product design + developmentWeb
Web
applications.
Made for doing.
Give people a place to get things done. Custom portals, dashboards and digital products built around the way your service works.
From an early idea to an existing product that needs a better experience. We connect the product thinking, interface and build.
Discuss your application01 / A product with a purposeBuilt around
Built around
the job to be done.
When people need to sign in, complete tasks, manage information or work together, the experience needs more than a set of pages. It needs a clear structure behind every action.
Workflow products
Turn a service or process into a working digital product, with clear stages, decisions and responsibility.
Useful dashboards
Bring relevant information and actions together. Decide what each person needs to see before choosing what to display.
Accounts & permissions
Define how people sign in and what they can access. Connect the visible interface to permissions enforced by the application.
Connected systems
Connect the agreed services and data sources. Plan how information is exchanged and what happens when a connection is unavailable.
Tools for your team
Give the people operating the product practical ways to review information, resolve issues and manage the work.
02 / Explore the product thinkingOne application.
One application.
Different perspectives.
A customer, a team member and an administrator need different things from the same product. Switch roles to see how the experience changes.
PROJECT SPACECustomer view / Example
Workspace setup / Example request
In reviewYour request, in one place.
Your request
- Project briefReceived
- Supporting filesReceived
- Team reviewIn progress
You’re up to date.
The team is reviewing your request. The next update will appear here.
A shared history
- 01Request submitted
- 02Files attached
- 03Review started
One place to understand where things stand.
A clear view for the person waiting.
A customer sees their request, what they have supplied and what happens next. Internal assignments and review notes stay with your team.
Interactive service illustration with fictional data. Select a role to explore how the same product serves different people.
The craft behind the screenEvery click belongs
Every click belongs
to a bigger picture.
A polished interface is one part of a useful product. We connect what people see to the information, rules and responsibilities that make the experience work.
Who is using it?
Roles, needs and the tasks that matter.
What can they do?
Screens, actions and clear feedback.
What happens next?
Rules, permissions and state changes.
What must be kept?
Records, history and connected data.
Built by AMUI / Product thinking in practice
Inquos.
Inquos brings candidates, employers and recruitment partners into a coordinated hiring platform. AMUI’s work connects onboarding, evidence and operational interfaces to the application logic behind them.
Explore the Inquos case study Product design & application development · Ongoing engagementInquos / One product. Different responsibilities.A clear next step.
For each person.
For each person.
Candidate→Shared process→Operator
Case-study illustration / Explore the project for context04 / From idea to working productStart with a journey.
Start with a journey.
Build something useful.
You do not need a finished specification. We help define a focused first release, with decisions and review points you can understand.
Map the people and the work
We identify who uses the product, the tasks they need to complete and the information involved. You bring domain knowledge and examples; we turn them into flows and a clear initial scope.
Make the experience reviewable
We design key screens, navigation and interactions around representative tasks. You can review the experience before development fills in the details, including less obvious states such as missing information and pending review.
Build a complete first journey
We develop the agreed interface, data model, permissions and integrations as a connected product. The first release follows a useful journey from beginning to end, with acceptance criteria that make progress concrete.
Test, launch and hand over
We check the agreed workflows, access boundaries and responsive behaviour. Deployment, operating guidance and responsibilities are covered in the handover. Further improvements and ongoing support can be scoped from there.
05 / Before we beginGood questions.
Good questions.
Clear answers.
Can we start with an MVP?
Yes. We define a first release around the most valuable user journey. That means deciding which people, tasks and integrations it must support, and which capabilities can follow later.
Can you improve an existing application?
Yes. We first review the current experience, code and constraints. That helps establish what can be retained, where changes are needed and how to introduce improvements without an unnecessary rebuild.
Will the application work on mobile?
Responsive application design is part of the planning. We agree which tasks need to work on smaller screens and test those journeys. A native iOS or Android application is a separate scope.
What determines the budget and timeline?
The number of user roles, workflows, integrations and data requirements shapes the work. We agree milestones and a price after defining the initial scope. Share any deadline or budget constraint at the start.
What happens after launch?
The handover covers the agreed setup and operating responsibilities. Hosting, third-party services, maintenance and further development are discussed explicitly so you know what is included and what is ongoing.
Your next productMake the work
Make the work
flow.
Tell us who the application is for, what they need to accomplish and what you have already. We’ll start with a free 15-minute conversation.
Book a free 15-min call