Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire UI/UX Designer for Plumbing
Senior, direct, no layers

Hire a ui/ux designer for plumbing: practical ui/ux designer work for plumbing companies — booking, systems, and follow-up built around how the trade actually runs, not a generic package.

Plumbing — UI/UX Designer

A senior ui/ux designer for plumbing

Plumbing is a phone-first business, and the phone is busiest exactly when the company is least able to answer it: a burst pipe at night, a backed-up sewer on a holiday weekend, a water heater that quit on a Monday morning. Calls get missed, dispatch becomes a whiteboard and a group chat, and the day's schedule is rebuilt by hand every time an emergency jumps the queue. Flat-rate pricing lives in a printed book, truck stock is guesswork, and the review request that should follow every completed job is forgotten more often than it is sent. The work itself is excellent; the system around it is held together by memory and overtime.

That is where a UI/UX designer earns their keep for a plumbing company. Trade customers are usually booking under stress, on a phone, with a problem in front of them. Every extra field, every confusing step, every page that hides the phone number costs booked jobs. Good design here is unglamorous: one clear path to booking, approvals a customer can complete in a minute, and a portal that shows status without a call. Book a free discovery call and we will test the fit before any scope is agreed. Browse the full hire hub for related engagements.

What you get

What this engagement covers for plumbing

  • Research with real homeowners and property managers — Short interviews and observation with the plumbing company own homeowners and property managers and staff: how they find the business, choose a service from the leak repair, drain clearing, boiler installation, and emergency callouts range, and book a callout. Findings are reported as observed behaviour, not as personas invented in a workshop.
  • Journey maps for booking and rebooking — A map of the full journey — discovery, choice, booking, visit, rebooking — marking where homeowners and property managers hesitate, drop off, or call instead of booking online. Each friction point gets a design response, not just a note.
  • Wireframes and prototypes — Screen layouts and clickable prototypes for the website or booking flow, tested before any code is written. A prototype that confuses test users is redesigned cheaply, instead of discovering the confusion after a build.
  • Usability testing with tasks — Test sessions where real users complete real tasks — book a callout, find a price, reschedule — while the designer observes. Results are reported as task success and observed problems, with severity ranked.
  • Visual design and a design system — A visual direction and a small design system: colours, type, buttons, and form patterns, documented so future pages stay consistent without the designer. The system is sized to the plumbing company, not a corporate pattern library.
  • Handover specifications for builders — Annotated designs, interaction notes, and content guidance that a developer can build from without guessing. The handover includes the research findings, so builders understand why each screen is shaped as it is.
The systems plumbing actually run

Built around the tools already in the office

Design work happens in Figma, with prototypes linked for testing and research notes kept alongside the designs. Analytics from the current site and booking data from Housecall Pro, Jobber, or ServiceTitan inform the journey map: where visitors drop off, which pages lead to bookings, and which steps in the booking flow lose people.

Testing uses the prototype and a small set of real users, recruited from the plumbing company own homeowners and property managers where possible, because testing with strangers who would never book tells little about booking behaviour. Findings are recorded as clips and notes the team can watch, not only as a summary report.

How it works

From kickoff to delivery for plumbing

  1. Research the journey first

    We start with interviews, observation, and analytics: how homeowners and property managers find, choose, and book, and where staff see confusion. The journey map is drawn from that evidence, not from assumptions about the homeowners and property managers.

  2. Sketch, prototype, test early

    Early screens are sketched and prototyped quickly, then tested with real tasks. The first prototype is expected to fail in places, and those failures are the most valuable output of the stage.

  3. Refine from test evidence

    Designs are revised from observed test problems, ranked by severity, and retested where the fix changes the flow. A change made on opinion alone is marked as such and tested before it is final.

  4. Hand over designs and findings

    Handover includes final designs, the design system, interaction notes, and the research findings, so the builder and the team understand the reasoning, not just the screens.

Realistic outcomes

What changes when it works

Done well, the booking path gets easier to complete: fewer abandoned bookings, fewer calls asking what the website should have answered, and a design the team can extend consistently. The measure is task success in testing and booking completion after build, not how modern the screens look.

The limit is that design is not build. A beautiful prototype that nobody builds changes nothing, and a design that ignores technical limits in Housecall Pro, Jobber, or ServiceTitan or the website platform will be rebuilt in compromise. The handover therefore includes the constraints, and the designer stays available during build to resolve them.

The common failure is a design handed over without its reasoning, so builders compromise it screen by screen until the tested flow is gone. Keep the research findings with the designs, and stay involved during build, because the decisions that matter most are made when constraints appear.

Why Omer

Why hire Omer

  • Research before screens: Design starts from observed homeowners and property managers and staff behaviour, so screens solve real friction instead of restyling a flow that was already confusing.
  • Tested with real tasks: Usability is judged by whether real users can book, find a price, and reschedule, not by whether stakeholders like the look. Task failure is treated as design evidence.
  • Prototypes fail cheaply: Confusion found in a prototype costs a redesign; confusion found after build costs a rebuild. Early testing is the cheapest quality step in the whole project.
  • Handover builders can use: Annotated designs and interaction notes mean the builder does not guess. The reasoning travels with the screens, so compromises during build stay informed.
  • Design system sized to you: The system covers what the plumbing company actually publishes, not a library of patterns nobody will use. Consistency comes from a small system that is actually followed.
FAQ

Questions, answered

Do you also build the website or app?
No. This engagement delivers research, designs, prototypes, and handover specifications. Building is a separate engagement, and the handover is written so a builder can work from it without the designer in the room.
How is this different from a web developer?
A web developer builds the site in code. This engagement designs how it should work and look, based on research and testing, before code is written. The two fit together, but they are different skills.
Who are the test users?
Real homeowners and property managers and staff where possible, completing real tasks like booking a callout or finding a price. Testing with people who would never use the service tells little, so recruitment aims at the actual audience.
What do we get at handover?
Final designs, a design system, interaction notes, and the research findings, all in Figma and documents the team keeps. The reasoning behind each screen is included, not just the screens themselves.
What if we disagree with a design?
Design decisions are discussed against test evidence and journey findings. Where evidence is thin, that is stated, and the design is tested before it is finalised, rather than settled by taste alone.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.