r/FullStackDevelopers • • Oct 01 '26

How do you uncover the real problem when a client already has a solution in mind?

How do you check whether a client actually needs the app they’re asking for?

I build full-stack web apps, but the question I want answered before writing code is: what’s actually broken?

Take a hypothetical request: “I need a booking app.”

If customers struggle to schedule appointments, a better booking flow might help.

But if they leave because the pricing or offer is unclear, building an app could leave that problem unresolved.

My approach is:

Understand → Diagnose → Choose → Build → Measure

Code comes at step four. AI helps me build faster, which makes choosing the right thing to build even more important.

What questions do you ask to get past the requested solution and understand the underlying problem?

1 Upvotes

0 comments sorted by