# Interfaces your team will actually use.

Source: https://cruxlabs.com.au/services/ui-ux-design

UI/UX design decides how a screen works for the person using it: what they see first, what they tap next, and what never gets in the way. We research the work, map the flows, prototype and test with your team, then build it from one design system. Built in Melbourne, working Australia-wide.

## The problem: Software your team works around.

- **Built for the demo.** Impressive in a pitch, painful by Friday, so the spreadsheet stays open beside it.
- **Five tools, five looks.** Every system has its own buttons, words and menus.
- **Nobody asked the people who use it.** The screens suit whoever signed off, not the daily user.

## The solution: Designed with the people who use it.

We test the flow on a prototype with your team before any code.

- **Research and flows.** We watch the work and map every path through the job.
- **Prototypes you can click.** Tested with your team before anything is built.
- **One design system.** One set of components for web and mobile.
- **Designed and built by one team.** No handover, so what you approved is what ships.

Set up for: [Professional services](https://cruxlabs.com.au/industries/professional-services), [All industries](https://cruxlabs.com.au/industries).

## The design system: One design system, and this is ours.

A real sheet from the system this site runs on. Yours gets the same.

![The Crux Labs component sheet: a mint Book a call button beside a secondary button, a text link, the focus ring, a numbered section marker with a margin note, and a form field with its error message.](https://cruxlabs.com.au/img/services/ui-ux-design-system-screen-1440.jpg)

## What we have built: Designed and built here.

- **PropyChat, our own startup, designed and built in-house** (Proptech, Victoria, Early access). AI planning answers with the rule cited on each one, property cards, site analysis and a property finder. 4.1M+: Victorian properties, with their planning, that PropyChat answers about. [Read the case](https://cruxlabs.com.au/case-studies/propychat)
- **Screens for every role in a 35-store franchise network** (Food and franchise, 4 cities, Live). Store ordering, warehouses, statements and an offline driver sign-off, each role with its own view. 35 stores: on one Business Operating System across four cities. [Read the case](https://cruxlabs.com.au/case-studies/franchise-network-os)

## After launch: three ways to keep it growing. Nobody holds the keys but you.

The code, the data and the accounts are yours from day one. What changes is who does the next change.

- **We run it for you.** For owners who want results, not another tool to learn. You own everything.
- **You ask, it builds.** For teams with one or two people who like to tinker. You own everything, and the power to change it.
- **We teach your team.** For founders and operations leads who want full control. You own everything, and the skill.

[How each one works](https://cruxlabs.com.au/how-we-work#three-ways)

## Questions

**Do you design without building?**
Yes. You own the source files and the design system either way. Most of the value comes when the same team builds it, but that is your call.

**How long does design take?**
It is sized to the screens and flows your work needs, and agreed in the fixed price before work starts. Design runs ahead of the build in short releases, so your team tests real screens early.

**Do we get the design files?**
Yes. The research notes, the mapped flows, the prototypes, the design system and the source files are yours.

## Show us the screen your team avoids.

[Book a call](https://cruxlabs.com.au/contact)