Software & Cloud Development

UI and UX design

People judge software by whether it helps them work. We research how users work, on shop floors, in the field or at desks, and design clear, accessible interfaces for web, mobile and business systems.

Who this service is for

A good fit if

  • Confusing screens drive staff to side spreadsheets, workarounds or repeated errors.
  • A new application, portal or app should be designed around real users first.
  • Your tools look and behave differently and need a shared design system.
  • You need WCAG 2.2 AA, phones and slow connections, or faster all-day ERP screens.

What is included

  • UX audit and gap analysis with prioritised findings
  • User research: interviews, workplace observation, task analysis
  • Journeys, information architecture, Figma wireframes and clickable prototypes
  • Usability testing with representative users, findings and changes
  • Visual design to your brand, and a documented design system
  • WCAG 2.2 AA annotations, developer-ready specifications, build support

What this service is

UX (user experience) is research, structure and workflow: can someone finish a task quickly, without mistakes? UI (user interface) is the visual layer: layout, type, colour, controls, feedback. We design both, for web, mobile, ERP and CRM screens, so staff work instead of fighting tools.

Designing for real working conditions

The same system needs different interfaces for different people:

Warehouse supervisor

Rugged tablet, gloves and glare: large touch targets and high contrast.

Field technician

Working from a vehicle with poor connectivity: clear offline states.

Nurse

Between patients, with noise and interruptions to design for.

Finance clerk

Two monitors and heavy data entry: keyboard shortcuts.

All-day ERP screens gain most: small changes in Prometheus ERP or ERPNext save a great deal of time, built through ERPNext and Prometheus customisation.

Audits, accessibility and design systems

For existing systems, a UX audit (a user-experience gap analysis) comes first:

  1. ReviewKey tasks against usability and accessibility criteria.
  2. ObserveReal users completing them.
  3. CompareWhat the system does with what people need.
  4. PrioritiseQuick fixes to larger redesigns, planned in stages.

We design to WCAG 2.2 AA (contrast, keyboard, screen readers, focus, target size) from the first wireframe and test layouts with longer text and on small screens, so they hold up on the phones many users rely on. A Figma design system holds components, patterns, states (focus, error, disabled, loading) and usage guidance, aligned with developers' code, so apps stay consistent and new screens come faster.

How design work is managed

Design work runs in clear stages with agreed outputs, so you always know what is decided, what is being tested and what comes next. Research findings, prototypes and the design system stay useful long after the project ends.

Design pairs with web application and mobile app development, or stands alone for your internal team or another development partner.

Delivery

How the work is delivered

  1. Understand and define

    Review system, goals and data; research users on site or remotely; map journeys and priorities.

    Output: Findings, UX audit, journeys, priorities.

  2. Prototype

    Sketch, wireframe and prototype the key tasks.

    Output: Clickable prototype.

  3. Test and refine

    Test with representative users, find where they struggle, refine.

    Output: Usability findings, revised designs.

  4. Specify and support

    Finalise visuals and design system, annotate accessibility, support developers.

    Output: Design system, developer specifications.

Scope at a glance

Not included unless agreed

  • Logo, brand identity and marketing campaign design
  • Development (unless combined with ours); formal legal accessibility audits
  • Paid research panels or incentives, billed on approval

What we need from you

  • Real users, or close matches, for research and testing
  • Access to the existing system or a test environment
  • Brand assets, and a decision-maker for designs and workflows

Before handover

  • Designs tested with representative users before development; findings recorded
  • Contrast, text size, targets, keyboard order checked; longer text, small screens tested
  • Documented component states; Figma files and specifications in your account

What affects the cost

  • User groups and tasks to research
  • Access to users; on-site or remote research
  • Number of screens and platforms
  • New or extended design system; accessibility, language, devices

No package prices: estimates in naira from an agreed scope, taxes shown separately.

Questions buyers usually ask

Can you improve an existing system without rebuilding it?

Often, yes. An audit usually finds layout, label, default and workflow changes that make a large difference within the existing platform, including ERP screens and forms. We prioritise those before anything bigger.

Do you design for accessibility?

Yes, to WCAG 2.2 AA, annotated so developers build it correctly. Nigeria's Discrimination Against Persons with Disabilities (Prohibition) Act 2018 sets a general accessibility duty without a web standard, so we treat WCAG 2.2 AA as good practice (general information, not legal advice).

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

We observe them where they work, by arrangement, and add remote interviews. Usability sessions use Figma prototypes and remote testing tools.

Software your people struggle to use?

Tell us which system to improve and who uses it. We will discuss a UX audit or research before anything is priced.