Bringing UX to a product that never had a designer.

The product worked and had real customers, but it had grown without a UX designer — flows were more complicated than they needed to be, shaped by what got built over time rather than what users needed.

Homeowners had to work through a multi-step bid, and service companies needed it clear enough that customers actually finished.

Being the first designer meant earning trust and learning the domain — how home-service pricing works, what info a company needs to quote, and where homeowners dropped off.

I was designing for two audiences at once: the homeowner, who needed a quick, clear path to a bid, and the service company and its technicians, who needed to act on that work.

I simplified many existing processes — fewer steps, a clearer self-serve bid so more homeowners could finish on their own — then started the bigger shift from bid to job.

A bid is the proposal: the home's details and pricing, written for the homeowner. A job is the next step: an actual event on the calendar telling technicians they can go visit — a view built for the tech, not the homeowner. I began designing how jobs would live inside ResponsiBid.

Jobs were in development when I left and are now part of ResponsiBid — I helped lay the groundwork.

This is where my product-UI craft began. Designing for both a homeowner and a technician taught me to hold two very different users in mind at the same time.