Skip to main content
    Davies Meyer – home

    Digital products that solve a real task.

    Customer portals, self-service and custom applications: we connect research, UX/UI and development, from a testable idea to a usable release and its continued improvement.

    Discuss your product idea

    A good product idea makes something easier.

    A customer wants to see the status of a request. A sales team needs reliable product information. A service task currently moves through several inboxes. These are starting points for a digital product. Together we assess who will use it, what needs to improve and whether a custom application is the right approach.

    Develop the experience and underlying workflows together

    A clear interface needs working handovers. We consider , interaction, data, permissions and operation together. Creative Engineering connects human usefulness with technical delivery. AI can prepare designs, code or tests. We take responsibility for concept and quality.

    Applications we can develop with you

    Customer and partner portals make status, information or documents accessible. Self-service applications guide recurring tasks. Internal tools connect approvals, data and ownership. Product advisers and configurators help people narrow down options.

    These use cases describe possible project tasks. We match the required functions and relevant references to your specific project.

    First engagement: make one user task testable

    In a product pilot we investigate one priority task, design the journey and develop a prototype. Agreed user tests show which assumptions hold and where revision is needed. You receive a reasoned scope for initial delivery, including interfaces, acceptance criteria and open decisions.

    A prototype tests an idea. A production application also needs access checks, error handling, data persistence and agreed operation. These activities are planned before implementation.

    Example: from a phone call to a clear service status

    In a possible customer portal, an authorised person sees their request status and the next step. Missing documents can be requested specifically. The design must also address incomplete data, missing permissions or an unavailable source system.

    This workflow is a concept, not a claimed client reference. Whether it reduces follow-up questions and makes tasks easier is evaluated within the project.

    Improve deliberately after launch

    We agree ownership, observation of key workflows and incident handling. Usage data and feedback inform prioritised improvements. Quality shows in whether people can complete their tasks clearly and reliably.

    How we deliver

    01

    Understand the task

    Understand users, the current workflow and success criteria.

    02

    Test the approach

    Connect a prototype and user tests around the core task.

    03

    Define the release

    Prioritise functions, data, permissions and interfaces.

    04

    Build and review

    Validate implementation against agreed user and failure cases.

    05

    Continue operation

    Agree handover, maintenance and further improvements.

    Questions before starting

    Sources and technical context

      Which task should become easier digitally?

      Tell us the users, workflow and systems involved. The first conversation defines a suitable product pilot.

      Discuss your product idea