Every studio’s portfolio page looks good. That’s the problem. A polished case study tells you what a team can screenshot — not what they can deliver, how they communicate under pressure, or what happens six months after launch when something breaks. If you’re evaluating who to hire for a website or product build, here’s what actually predicts a good outcome.
Ask who will actually do the work
Many studios sell you on a senior designer or lead developer in the pitch call, then hand the project to whoever’s available once the contract is signed. Ask directly: “Who on your team will be doing the design and development, day to day?” A studio that’s confident in its own team will answer with a name, not a department.
Small studios and solo-to-small teams have a real advantage here — there’s no bait-and-switch possible when the person pitching you is the person building your site.
Look at what they shipped, not just what they designed
A Dribbble-worthy mockup is not a website. Click through to the actual live case studies. Is the site fast? Does it work on a real phone, not just in a browser resize? Does the navigation make sense, or is it clever at the expense of usable? A studio’s own portfolio site is also a data point — if their own site is slow or confusing, that’s not a great sign for what they’ll build you.
Get a real discovery process, not a template pitch
If a studio can quote you a fixed price and timeline before understanding your business, your users, or your constraints, they’re pattern-matching you to a template — which might be fine for a simple brochure site, but not for anything where the details matter. A good process starts with questions, not a proposal. Watch for whether they ask about your actual goals (“what does success look like in six months?”) versus jumping straight to “do you want 5 pages or 10?”
Understand the handoff before you sign
This is the one people skip and regret. Ask: What happens after launch? Do you own the code, the CMS, the domain, the hosting? Can you take it to another developer if the relationship ends? Studios that build on proprietary page builders or keep you locked into their hosting are optimizing for recurring revenue, not for your independence. A studio confident in its own value doesn’t need to lock you in — a fair contract typically gives you full ownership of what you paid for.
Check how they handle “no”
Somewhere in the process, you’ll ask for something that’s a bad idea — a feature that will hurt conversion, a design trend that will look dated in a year, a timeline that isn’t realistic. How a studio responds tells you everything. A team that just says “sure, we can do that” to keep you happy isn’t actually protecting your investment. A good studio will push back, explain why, and offer an alternative. That friction, done respectfully, is a sign you’re working with people who care about the outcome, not just the invoice.
Red flags worth walking away from
- Pressure to sign before you’ve seen a detailed scope or timeline
- No clear answer on who owns the code and content after launch
- A portfolio full of screenshots with no links to live, working sites
- Pricing that’s dramatically cheaper than every other quote you’ve gotten, with no explanation of what’s different
- Communication that goes quiet for days once the deposit clears
What good actually looks like
A studio worth hiring will ask more questions than it answers in the first call, show you real, live examples of work — not just mockups, give you a scope and timeline in writing before asking for money, and be straightforward about what they don’t do well. None of that is exotic. It’s just what a normal, trustworthy business relationship looks like — it’s just rare enough in this industry that it’s worth spelling out.
If you’re at the stage of comparing studios, the questions above will tell you more in twenty minutes than another hour of scrolling portfolios.
