UI / UX
Design.

What you actually get.

UI/UX is where I push hardest. UCT-certified, ten years of shipping with engineers across enterprise software means I've stress-tested this work in production — fleet management dashboards, warehouse management systems, customer portals. Real software, real users, real edge cases.

What you're paying for here isn't just pretty screens. It's the thinking — research, user flows, edge-case states (empty, loading, error), and the documentation that makes engineering handoff smooth.

A typical UI/UX engagement from me includes:

• UX research — stakeholder interviews, competitor scan, basic user research where applicable
• User flows — diagrammed journeys for the core tasks, before any visual design
• Wireframes — low-fidelity layouts to lock structure before pixels
• High-fidelity UI — final screens at production quality, mobile + desktop where relevant
• Component library — reusable Figma components so engineering builds consistent UI
• Interactive prototype — clickable Figma prototype showing the core flow
• Edge states — empty states, loading states, error states (the bits people forget)
• Engineering handoff — annotated specs, design system tokens, asset exports

How we get there.

UI/UX takes longer than other services because the early thinking matters more.

• Discover — stakeholder interviews, existing-product audit if any, competitor research
• Define — user flows, screen inventory, prioritisation
• Wireframe — low-fidelity, all key screens. One round of structural feedback
• Design — high-fidelity UI, components, edge states. Two more rounds of feedback
• Prototype — interactive Figma prototype for the main flow
• Handoff — design system documentation, engineering walkthrough, 30 days of iteration support

What it doesn't include.

Things I don't include but can quote separately:

• Front-end development — I do design and handoff; building the actual code is a separate engagement
• User testing sessions — I can recommend research partners if formal usability testing is needed
• Brand identity — if you don't have a brand yet, that's a separate Brand Identity engagement
• Content writing — I design around your copy. UX writing is a separate skill

Who this is for.

This works best for real software products — apps, dashboards, SaaS tools, complex web products. If you just need a website with a few pages, that's Web Design, not UI/UX.

Honest read: if your project is a brochure site with a contact form, paying for a UI/UX engagement (from R4,500) is overkill. Save it for when you need the depth.

Examples.

See Selected Work — the UOL Tech living style guide is a working system you can click through right now — tokens, components, states and motion, all functional.