Software & Cloud Development

UI and UX design

People judge software by whether it helps them get their work done. We research how your users actually work, on the shop floor, in the field or at a desk, and design interfaces that are clear, accessible and consistent across your web, mobile and business systems.

Who this service is for

A good fit if

  • Staff avoid a system, keep side spreadsheets or make repeated errors because the screens are confusing.
  • You are building a new application, portal or app and want it designed around real users before development starts.
  • Your products or internal tools look and behave differently from one another and need a shared design system.
  • You need interfaces that meet WCAG 2.2 AA and work in English and French.
  • Your ERP or line-of-business screens slow down people who use them all day.

Another approach may suit you better if

  • You need a new logo or brand identity. That is brand design, which we do not offer.
  • You want visual polish only, with no access to users and no willingness to change workflows.

What this service is

UI and UX design shapes how software works for the people who use it. UX (user experience) covers research, structure and workflow: whether someone can complete a task quickly and without mistakes. UI (user interface) covers the visual and interactive layer: layout, typography, colour, controls and feedback. We design both, for web platforms, web applications, mobile apps and business systems such as ERP and CRM screens.

Our focus is software that people use to get work done. Your staff have orders to fill, shipments to make, patients or clients to look after. They should be spending that time on their work, not fighting their tools.

Designing for real working conditions

Good design starts with understanding the unique demands of the environment. A warehouse supervisor on a rugged tablet, a technician in a vehicle, a nurse between patients and a finance clerk at two monitors need very different interfaces, even when they use the same system. We research users where they work, whether on the shop floor, in the field or in the office, and design for their conditions: large touch targets and high contrast where gloves and glare are a factor, keyboard shortcuts for heavy data entry, and clear offline states where connectivity is unreliable.

This matters especially for ERP and other core systems that people use all day. Small changes to layouts, defaults and workflows in Prometheus ERP or ERPNext can save a great deal of time, and our ERPNext and Prometheus customization service can build them.

UX audits and gap analysis

For existing systems, a UX audit is the practical first step. We review key tasks against usability principles and accessibility criteria, watch real users complete them, and compare what the system does with what people need, a gap analysis for the user experience. The result is a prioritized list of improvements, from quick fixes to larger redesigns, so you can plan and manage the work in sensible stages.

Accessible, bilingual design systems

We design to WCAG 2.2 AA from the first wireframe, covering contrast, keyboard use, focus, screen reader support and target sizes, and we annotate designs so developers implement them correctly. Layouts are tested with French text, which usually runs longer than English, so bilingual interfaces do not break.

A design system collects your components, patterns and rules in one place, so every web application, portal and app looks and behaves consistently and new screens are faster to build. We create design systems in Figma with documented states and usage guidance, and align them with the code components developers use.

Throughout a project we manage design work in clear stages with agreed outputs, so you always know what has been decided, what is being tested and what comes next.

Design work pairs naturally with web application development and mobile app development, and can also be delivered on its own for your internal team or another development partner. Either way, you receive research findings, prototypes and a documented design system that stay useful long after the project ends.

What is included

The exact list is agreed in writing for each project. These are the usual deliverables and the usual boundaries.

Typical deliverables

  • A UX audit and gap analysis of an existing system, with prioritized findings.
  • User research such as interviews, observation in the workplace and task analysis.
  • User journeys and information architecture.
  • Wireframes and clickable prototypes in Figma.
  • Usability testing with representative users, with findings and recommended changes.
  • Visual design applied to your brand, for web, mobile or business system screens.
  • A design system with reusable components, accessibility notes and usage guidance.
  • Accessibility annotations and checks against WCAG 2.2 AA.
  • Developer-ready specifications and support during the build.

Not included unless agreed separately

  • Logo, brand identity and marketing campaign design.
  • Development, unless combined with one of our software development services.
  • Paid research panels or participant incentives, billed to you with your approval.
  • Formal accessibility conformance audits for legal purposes by an independent assessor.

What we will need from you

Most delays in this kind of work come from access and decisions, not from the technical build. Knowing these early keeps the project predictable.

  • Access to real users, or people who closely match them, for research and testing.
  • Access to the existing system or a test environment, if one exists.
  • Brand guidelines, logos, fonts and colour palettes.
  • A decision-maker who can approve designs and changes to workflows.
Delivery

How the work is delivered

Each stage ends with something you can review before the next one starts.

  1. Understand

    Review the current system, business goals and data, then research users through interviews, observation and task analysis, in person by arrangement or remotely.

    Output: Research findings and UX audit.

  2. Define

    Map user journeys and information architecture, and agree which problems to solve first.

    Output: Journeys, structure and priorities.

  3. Prototype

    Sketch, wireframe and build clickable prototypes of the key tasks.

    Output: Clickable prototype.

  4. Test and refine

    Test prototypes with representative users, measure where they struggle and refine the design.

    Output: Usability findings and revised designs.

  5. Specify and support the build

    Finalize visual design and the design system, annotate accessibility requirements and support developers through implementation.

    Output: Design system and developer specifications.

Testing and handover

  • Designs are tested with representative users before development, and the findings are recorded.
  • Every component in the design system has documented states, including focus, error, disabled and loading.
  • Colour contrast, text size, target size and keyboard order are checked against WCAG 2.2 AA.
  • Layouts are checked with French text, which usually runs longer than English.
  • Figma files, components and specifications are handed over in your organization's account.

What affects the cost

We do not publish package prices. Each estimate is based on an agreed scope, in Canadian dollars, with taxes shown separately. These are the things that move the number most:

  • The number of user groups and tasks to research and design.
  • Access to users and whether research happens on site or remotely.
  • The number of screens and platforms.
  • Whether a design system is created from scratch or extended.
  • Accessibility and bilingual requirements.

Questions buyers usually ask

What is the difference between UI and UX?

UX (user experience) is about whether the software helps people complete their tasks, which covers research, structure and workflow. UI (user interface) is the visual and interactive layer, such as layout, typography, colour and controls. Good results need both, and we deliver both.

Can you improve an existing system without rebuilding it?

Often, yes. A UX audit usually finds changes to layout, labels, defaults and workflow that make a large difference within the existing platform, including ERP screens and forms. We prioritize those before recommending anything bigger.

Do you design for accessibility?

Yes. We design and check against WCAG 2.2 AA, covering contrast, keyboard use, screen readers, focus and target sizes, and we annotate designs so developers build them correctly. Ontario's AODA sets website accessibility requirements for many organizations; this is general information, not legal advice.

How do you research users who are not at a desk?

We observe them where they work, on the shop floor, in vehicles, in clinics or on site, by arrangement, and supplement with remote interviews. Designs for these users account for gloves, glare, noise, interruptions and poor connectivity.

What tools do you use?

Figma for design, prototyping and design systems, and remote testing tools for usability sessions. Files are kept in your organization's account so you keep them.

Software your people struggle to use?

Tell us which system or product you want to improve, and who uses it. We will reply to arrange a conversation about a UX audit or research before anything is priced.