Hiring a web studio is a high-trust purchase made by people who often can't fully evaluate the work — which is exactly why it goes wrong so often. You're judging something technical, paying real money, and hoping the polished portfolio reflects how the project will actually go. The good news: you don't need to be technical to hire well. You need to ask the right questions and watch the right signals. Here are the 14 questions, the green and red flags, and how to verify a studio before you sign anything.
The 14 questions to ask
Ask these before signing. It's not about catching them out — it's that the way a studio answers tells you almost everything about how the project will run.
- What exactly is included? Strategy, copy, design, development, SEO, training — or just "a website"?
- What's the all-in first-year cost? Build plus hosting, plugins, and maintenance.
- Who owns the site, code, and accounts when we're done?
- What's your process and timeline? What are the phases?
- What do you need from me, and when? (Reveals whether they understand the real bottleneck.)
- Can I see live links to recent work — ideally in my industry?
- Who specifically will work on this project?
- How are revisions handled? How many rounds, and what counts as a change?
- What platform will you build on, and why that one?
- What happens after launch? Support, maintenance, handover?
- How do you handle SEO and performance?
- What's the payment schedule? Tied to milestones?
- Can you share a client reference I can call?
- What happens if we part ways mid-project?
Confident, specific, written answers are reassuring. Vague, defensive, or "don't worry about that" answers are the warning.
Green flags vs red flags
As you go through those questions, you're really sorting the studio into two columns. Here's what each looks like:
Green flags vs red flags
What to look for in a studio — and what should make you walk.
Green flags
Transparent, itemized pricing
They tell you what's included and what it costs up front, including ongoing costs — no vague 'it depends' that becomes change-orders later.
Clear process & timeline
They can explain the phases, what they need from you, and roughly how long it takes. A real process, not 'a few months'.
Relevant, verifiable work
Live links to recent projects you can actually visit, ideally in your space — not just polished mockups.
You own everything
Clear answer that you own the site, code, and accounts afterward. No hostage situations.
Red flags
Vague pricing & scope
A suspiciously low number with no detail. The gaps reappear as change-orders once you've signed and it's too late to compare.
No clear process
Can't explain how the project runs week to week, or what they need from you. Chaos incoming.
Only mockups, no live sites
Pretty images but no links to real, working sites. Anyone can design a picture; shipping a fast live site is the hard part.
You don't own it
They keep the code, host on their locked platform, or hold your domain. You're renting, and switching means rebuilding.
If you're seeing the right-hand column — vague pricing, no process, only mockups, no clear ownership — walk away, no matter how nice the work looks. Those are the exact conditions that produce the horror stories.
How to verify a portfolio (don't take it at face value)
A portfolio of beautiful images proves a studio can design a picture. It does not prove they can ship a fast, working website — which is the actual hard part. So verify:
- Visit the live sites. Not the case-study mockups — the real URLs. Do they exist, load fast, work on mobile?
- Check recency and relevance. Recent work, ideally in your space or of similar complexity.
- Ask for a reference call. Five minutes with a past client about communication, timeline, and what they'd change beats any case study.
Studios proud of their work connect you to clients happily. Evasiveness here is one of the most telling red flags there is. (You can see our own live work and client showcase sites — real links, not mockups.)
Contract clauses to watch
You don't need a lawyer to spot the basics that protect you:
- Ownership: you own the site, code, and content on completion.
- Domain & hosting: in your accounts, not held hostage on their platform.
- Payment: tied to milestones, not all upfront.
- Scope: what's included vs billed extra, in writing.
- Exit terms: what happens if you part ways — and no nasty auto-renewals or lock-in clauses.
The time to discover a lock-in clause is before you sign, not when you try to leave. (And judge the price against what's included and the all-in cost — our website cost breakdown shows what's fair by tier, while build timelines set realistic expectations on schedule.)
How we answer these (a mini self-audit)
Since we're telling you to ask these questions, here's where HiKit stands, openly: we quote transparent, itemized pricing with the all-in cost up front; you own your site, code, and accounts; we run a clear phased process and tell you exactly what we need from you and when; our portfolio is live links you can visit; and we're happy to arrange a reference call. We'd rather you ask every one of the 14 questions than not — a studio that answers them confidently is the one you want, whether it's us or someone else.
Choosing a web studio? Read how we work, browse the work we've shipped, or book a discovery call and put us through all 14 questions yourself. The right studio will welcome them — that willingness is the biggest green flag of all.
FAQ
Questions, answered.
What to ask — and watch for — before you hire.
The essentials: What exactly is included (strategy, copy, design, dev, SEO, training)? What's the all-in first-year cost including hosting and maintenance? Who owns the site, code, and accounts afterward? What's the timeline and what do you need from me? How are revisions handled? Can I see live links to recent work (ideally in my industry)? Who specifically will work on it? What happens after launch? Clear, confident answers are a green flag; vague or defensive ones are a red flag. How they answer matters as much as what they answer.
Three safeguards. First, demand transparency before signing — itemized scope, all-in cost, ownership, and process in writing. Second, verify their work: visit live links, check the sites are fast and real (not just mockups), and ask for a reference call. Third, read the contract for ownership, who holds the domain and accounts, and what happens if you part ways. Most horror stories trace back to skipping one of these — a vague scope, an unverified portfolio, or a contract that quietly keeps you locked in.
Visit the live sites, not just the case-study images. A mockup proves they can design a picture; a fast, working live site proves they can actually ship. Check that the sites load quickly on mobile, that they're recent, and ideally that a couple are in your industry or of similar complexity. Then ask for a reference — a quick call with a past client about communication, timeline, and what they'd change is worth more than any case study. Real studios are happy to connect you; evasiveness here is telling.
Ownership (you should own the site, code, and content on completion), domain and hosting control (these should be in your accounts, not held hostage), payment schedule tied to milestones, what's included vs billed extra, and exit terms (what happens if you part ways mid-project). Also check for automatic renewals on retainers and any clause that makes leaving expensive. You're not looking for an adversarial contract — you're making sure the basics protect you, because the time to discover a lock-in clause is before you sign, not when you try to leave.
It depends on scope and risk tolerance. A freelancer is cheaper and fine for a small, well-defined project, but you carry the management and there's a single point of failure. A studio costs more but brings a team, a process, and accountability — no project stalls because one person got sick or busy. For a business-critical site you're relying on for leads or sales, a studio's reliability usually justifies the premium. We break this build-vs-buy decision down in detail in our agency-vs-in-house guide.
The cheapest quote isn't automatically bad, but a cheap quote with vague scope usually is — the low number is achievable precisely because things you'll need aren't included, and they reappear as change-orders. Judge quotes on what's included and the all-in cost over the first year, not the headline figure. A clear, itemized quote at a fair price beats a mysteriously cheap one every time. We cover realistic budgets by tier in our website cost breakdown.
Choosing on price and portfolio aesthetics alone, while skipping process, ownership, and verification. A beautiful portfolio and a low price feel reassuring, but they don't tell you whether the studio communicates well, ships on time, hands over ownership, or maintains the site afterward. The biggest regrets come from the unglamorous things people didn't ask about — who owns the code, how revisions work, what happens after launch. Ask the boring questions; they're where the burns happen.
Yes, and a good one will offer them readily. A short reference call with a past client — about communication, whether the timeline held, how problems were handled, and what they'd change — reveals more than any case study. Reluctance to provide references is a meaningful red flag; studios proud of their relationships connect you happily. Prepare a few specific questions rather than asking 'were they good?', and you'll learn what working with them is actually like.