Every studio's site shows its best three projects, finished, polished, framed generously. That tells you what they are capable of on a good day. It tells you almost nothing about how they behave on a bad one — and a bad day is when the relationship actually gets tested.

Ask about the project that went wrong

Anyone who has shipped enough software has had a project slip, a client change scope midway, or a launch that broke something. A team with nothing to say here is either new or not being honest. Listen for whether they explain what changed afterward, not just what happened.

Ask who actually writes the code

  • Is the person in this call the one building it, or is it handed off after signing?
  • If subcontracted, who owns the relationship when something needs fixing at 11pm?
  • How many other projects is that person carrying at the same time?

A senior sales conversation followed by junior, overstretched execution is the single most common bait-and-switch in this industry, and it rarely shows up until week three.

Ask what happens after launch

A site or app that works on launch day and is never touched again is not finished, it is abandoned with a bow on it. Find out what maintenance actually includes — bug fixes, dependency updates, monitoring — and for how long it is covered before you are billed again.

The real product is not the code you receive on delivery day. It is what happens the first time that code breaks in front of a customer.

Ask how they handle scope changes

Every project's scope moves once real usage starts. Studios that quote a fixed price and then treat every change as a renegotiation create friction exactly when you need flexibility. Ask upfront how changes are estimated and communicated, and get it in writing.

Ask for a reference you didn't see on the site

Not the client in the case study — a different one. Anyone can produce a glowing quote for their best outcome. A team confident in its work will happily connect you to someone from a messier, more typical project instead.

None of these questions are adversarial. A team worth hiring will answer them plainly, because they have answered them before — and the answers, more than any portfolio, are what tell you what working together will actually feel like.