Kuotify • Shipped • 2025

A quoting tool

Role

Product designer
Founder

Timeline

May 2025 - Aug 2025

Scope

Product design
User research
UI design

Journey

What went wrong, and how I addressed it, is what this case study covers

Kuotify was a quoting tool I designed for contractors, built to be faster and simpler than the bloated or outdated options already out there. I designed it, got it built, and launched it, all without talking to a single contractor first.

I solved an assumption, not a problem

The trades don’t get much attention from tech, so I saw a gap. But I built around how I assumed contractors quote a job.

I researched with AI first

AI gave me a quick read on the industry and its pain points, enough to feel confident. But I was only finding what supported my idea, not testing whether contractors actually had the problem.

Designing it in Figma

The core idea: creating a quote should be fast. Contractors could make a quote in a few taps, with tax and discounts calculated automatically, and export it straight to PDF.

Building it myself wasn’t working

I kept hitting technical walls, so I hired a developer to build it in Bubble from my designs. That let me focus on launching.

I launched before I validated anything

I priced it at $35/month because it felt reasonable. I hadn’t compared competitors or checked whether contractors would pay. I marketed it on Reddit and Instagram, and reached out to 30+ blue-collar content creators.

The result: no signups, no interest

Finally talked to 6 contractors

They didn’t want a website. They needed an app they could use on the job site. They also said existing tools charge for features they never use, so $35/month for fewer features wasn’t worth it. By then, I’d already spent money building on the wrong platform.

Why it failed

Contractors do need quoting software. It failed because I didn’t do any user research or validation before building.

Outcome

The fix

Two things needed to change: format and price. So I repositioned Kuotify around simplicity, dropped the price to $3/month, and showed an app concept to 4 contractors. All 4 said they’d use it, because it did the job without charging for features they didn’t need.

It’s a small, informal sample, so it’s a signal, not proof. But it showed the packaging was the problem, not the idea. Next, I’d test with a bigger group to see if $3/month holds up.

Reflection

Validate before building

I need to make sure I’m going in the right direction before I build anything.

Don’t rely on AI alone

AI gave me a starting point, but it couldn’t tell me if contractors would use or pay for what I made. Only real users can.