Because every studio''s website looks good, says the same things, and shows work you cannot verify. The industry has no licensing, no standard qualification, and no reliable way for a buyer to check whether the site in a portfolio was actually built by the people showing it to you. You are judging on presentation alone.
We should say plainly that we run a web studio, so we have an obvious interest in how you think about this. Read everything below with that in mind. We have tried to write the version we would want a friend to read, including the parts that are inconvenient for us.
The good news is that a handful of specific questions separate serious partners from confident amateurs very quickly. They are not the questions most buyers ask.
Judgment, mostly. Anyone can move a rectangle in a design tool. What you are paying for is someone who has seen enough projects to know which decisions matter, which ones do not, and what will break in eighteen months. The visual work is the visible part of a much less visible skill.
This is why the field is hard to shop in. It is a genuine profession with no gate on entry. The US Bureau of Labor Statistics counts 220,100 jobs in web development and digital design, split between 87,400 web developers and 132,700 web and digital interface designers, with median pay in May 2025 of $99,520 across the combined occupation. It projects 5 percent growth from 2025 to 2035, faster than the average for all occupations.
A market that size, growing, with no licensing requirement, will contain enormous variation in quality. That is not cynicism, it is arithmetic. Your job as a buyer is to find the signal, and the signal is almost never in the pitch deck.
Ask what happens after launch. Ask who owns the site. Ask what performance and accessibility standards they build to. Ask what a change request costs in six months. The answers to those four questions tell you more about a studio than any amount of portfolio browsing, because they are about the parts nobody enjoys discussing.
The performance question is the most revealing one, because there is a public standard and a good studio will name it without prompting. Google''s Core Web Vitals set the good thresholds at 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift, measured at the 75th percentile of page loads. A studio that cannot tell you where your site will land against those numbers is guessing.
The accessibility question works the same way. WCAG has defined conformance levels, and Level AA is the ordinary commercial target. If a studio treats accessibility as an optional extra rather than a build standard, that tells you how they think about the people using what they make.
Ask about ownership explicitly and get the answer in writing. Who holds the domain, the hosting account, the design files, and the code? The answer should be you, in every case. A studio that holds your domain hostage as a retention strategy exists, and you find out at the worst possible moment.
Open the live sites, not the case study images. A portfolio page is a designed artefact showing a designed artefact, and it can look immaculate while the real site is slow, broken on mobile, or no longer live at all. Two minutes with the actual URL beats twenty minutes of scrolling case studies.
Run the live sites through a performance test yourself. It is free, it takes seconds, and it is the single most efficient filter available to a non-technical buyer. If a studio''s own showcase work loads slowly, that is what they consider acceptable, and yours will be the same.
Then check the sites on your phone properly, not by resizing a browser window. Look for text you can read without zooming, tap targets you can hit, and navigation that works with a thumb. A surprising number of impressive-looking portfolio sites fall apart on a real handset.
Be sceptical of results without context. A case study claiming a large conversion increase should say over what period, against what baseline, and alongside what else changed. Numbers without those three things are decoration. We hold ourselves to that on our own work, and you should ask us for it too.
It depends on how much coordination your project needs. A single skilled freelancer is often the best value for a focused project with a clear scope. A larger agency makes sense when you need many disciplines running in parallel. A small studio sits in between, which is useful for most marketing sites and a poor fit for very large programmes.
The real variable is not size, it is who does the work. In some agencies the people who win the project are not the people who deliver it, and the quality gap between the pitch and the build is where a lot of disappointment comes from. Ask directly who will be doing the work and whether you will speak to them.
Freelancer risk is concentration. One person can be excellent and can also get ill, take another contract, or simply stop replying. That risk is manageable if you own your accounts and your code, and it is severe if you do not. This is another reason the ownership question matters more than it sounds.
Page count, custom design versus template, CMS complexity, integrations, and content. Those five drive nearly all of it. Notice that none of them is "how good the design looks", which is why comparing two quotes on price alone tells you very little about what you are getting.
The biggest hidden variable is content. A project where the client supplies finished copy and images moves at a completely different speed from one where the studio has to write it, and it is the most common reason quotes vary wildly for what sounds like the same site. Get clear on who is writing the words before you compare numbers.
A quote that arrives before anyone has asked you what the site needs to do is a guess dressed as a price. We give a firm number after a scoping conversation, and any studio that gives you one before that is either padding heavily to cover the unknowns or setting up a change-order conversation later. We broke down what actually drives the number in our piece on what a Webflow website costs.
Vague answers about timelines, no written scope, reluctance to name the people doing the work, and pressure to sign quickly. Any one of these is worth a question. Two together is worth walking away, because all four tend to travel in the same company.
Be especially wary of guaranteed rankings. Nobody can guarantee a Google position, and a studio that offers one is either misunderstanding how search works or counting on you to. Google itself says there is "no guarantee that changes you make to your website will result in noticeable impact in search results", which is a useful sentence to have in your pocket during a sales call.
The other one is the promise that a new site alone will fix traffic. It usually will not. Ahrefs studied roughly 14 billion pages for its 2023 research and found that "96.55% of all pages in our index get zero traffic from Google." A beautiful new site with no content strategy joins that 96.55%. A studio that does not raise this is either not thinking about it or not telling you.
Finally, watch for a studio that agrees with everything. You are hiring judgment, and judgment sometimes means being told that the thing you asked for is a bad idea. A partner who never pushes back is not saving you from anything.
Scope in writing, a named timeline, a defined revision process, ownership terms, and what happens after launch. Those five turn a friendly understanding into something both sides can point at when memories diverge, which they always do around week six.
Be specific about revisions. "Unlimited revisions" sounds generous and is usually a trap for both parties, because it removes any structure from feedback and turns the end of the project into an open loop. A defined number of review rounds with a clear process is better for you, not worse.
Get post-launch terms in writing too. Who fixes a bug found in week two? What does ongoing support cost? Is there a handover session and documentation? Projects that end badly usually end badly here, not during the build. It is also worth asking whether accessibility obligations apply to you, since the European Accessibility Act covers e-commerce among other services and member states had to bring it into national law by June 2022.
Pick the studio that asked you the best questions. After the process above has filtered out the obvious problems, you are usually choosing between two or three capable options, and the differentiator is whoever showed the most curiosity about your business rather than the most enthusiasm about their process.
A studio that spent the call asking what your customers actually struggle with is going to build you a better site than one that spent it showing slides. Selling is easy to fake. Genuine interest in a problem you have is much harder to fake for an hour.
It is also worth being honest that a redesign is not always the answer, and a good partner will tell you when it is not. We wrote about the patterns behind that in our piece on why website redesigns fail, and on what separates a site that feels considered from one that merely looks current in our notes on what makes a website feel premium.
If you are working through this decision and want a straight conversation about whether we are the right fit, we are happy to have it, including the version where the answer is no. Reach out through phoenix.studio and tell us what you are trying to do.
Tell us where you want to go. We'll tell you how we'd get you there.