Most business owners start the search for a web designer by scrolling through portfolios. Reasonable. It can help determine their style and if it aligns with yours. But it’s not the only thing you should be looking at if you’re about to make a serious investment into a new website.
The problem is a portfolio usually only shows you the designer’s output. It doesn’t tell you much about the process that got them there. And when you’re building your next website — the one that actually matches where your business has evolved to — the process really is everything.
Two designers can have portfolios that both look amazing, but one started with a strategic foundation, and the other started with aesthetics. Those two sites will perform very differently in the real world and it can be hard to tell the difference from a screenshot.
A CEO doesn’t make a major business investment based on how things look. She asks different questions. Here are 6 questions I think you must be asking when looking for a web desiger.
1. What does your strategy process look like?
This is the most important question on the list. A designer who thinks strategically will have a clear, specific answer — it won’t be vague. They’ll talk about understanding your business goals, what your audience cares about, and what the new site needs to really accomplish. Website strategy should be its own defined phase, not something loosely woven into the design process or figured out along the way.
A designer who doesn’t work strategy-first will usually answer this question talking about mood boards, color palettes, the way things LOOK. But a real strategy covers things like objectives, competitors, and user experience. At this stage of your business, website strategy isn’t something you want to skimp on. It lays the foundation for everything that gets built — and it’s what ensures the website can grow with you rather than becoming something you’ve already outgrown two years from now.
2. Who will actually be working on my project?
Some studios route clients through account managers or hand work off to junior designers after your initial conversation. You want to know exactly who’s handling the strategy, who’s doing the design, who’s doing the development, and who you’ll be communicating with along the way.
It’s okay if a studio divides those roles — that’s how a lot of legitimate agencies work. But you want to know it up front. The founders who’ve had a bad experience elsewhere usually describe some version of the same thing: they pitched their vision to the owner, then got handed off to an account manager, then a designer they’d never spoken to had a question about the project — and a response took days, sometimes weeks.
You’re investing real money here. Know who you’re working with, know who you’re actually communicating with day to day, and if you can, talk to everyone on the team before you sign anything.
3. What platform do you build on, and why?
You want a designer or studio with a clear, informed point of view here — someone who can explain what it means for your site’s flexibility and longevity. Whether it’s WordPress, Webflow, Squarespace, or something else, the right answer isn’t “whatever you prefer.” It should be a specific, reasoned recommendation.
It’s also worth knowing that most platforms have real limitations, and those limitations tend to surface right when you need room to grow. What if you want to add a membership or sell products down the line? What if you need the site to work differently on mobile? Can the platform handle that — smoothly, without a hack or a workaround? Ask what the platform can’t do, not just what it can. Your designer should be confident in the platform they’ve chosen and be able to answer that honestly — and tell you why the tradeoffs are worth it for the kind of sites they build.
4. What does the revision process look like, and how do you handle scope changes?
This question tends to predict whether a project stays on budget and on schedule. Before you sign anything, it’s worth understanding exactly how many rounds of revisions are included, how feedback is collected, and what happens if you want to make a change after a phase has already been approved.
It’s also worth asking what happens when something comes up mid-project that wasn’t part of the original scope. A designer with a real process should be able to walk you through that clearly, step by step, rather than improvising an answer. Scope creep and miscommunication around revisions are two of the most common reasons web projects run over budget and past deadline — so a designer who has a defined answer here has likely dealt with it before, and built a process to prevent it.
5. What do I need to have ready before we kick off?
This one flips the dynamic — instead of asking what they do, you’re asking what they expect of you. Which is just as important.
Most projects require real things from you before work can begin: copy, photography, brand assets. Some of those take longer to pull together than you’d think. If you’re hiring a copywriter, that process takes weeks. If you need brand photos, you need to schedule and shoot them. The earlier you know exactly what’s needed of you, the more time you have to get it ready. If your project kicks off before you’re actually prepared, it will probably stall somewhere in the middle — which is worse for everyone than just pushing the start date back a few weeks.
Knowing what’s required up front also helps you gut-check whether you’re actually ready to begin. A designer who can hand you that list clearly has run this process enough times to know what derails it.
6. What does support look like after launch?
Before evaluating what a designer offers here, it helps to know what you actually want. Some founders want to manage their own site day-to-day; others would rather hand that off entirely. Both are reasonable, but they point toward different questions.
Most well-built sites are set up so you can handle the basics yourself — updating copy, swapping images, editing hours or pricing. It’s worth asking directly whether that’s true of the sites this designer builds. If routine edits require a call or an invoice, that’s typically a deliberate build decision, and one worth understanding before you commit.
It’s also worth asking what’s available beyond the basics — a maintenance plan, a retainer, priority access for future updates. Not every designer offers this, so it’s worth knowing upfront whether the option exists at all, particularly if you expect to keep evolving the site after launch through new offers, seasonal campaigns, or a future rebrand.
Finally, ask what the handoff itself looks like: documentation, a walkthrough call, training videos. A structured handoff is generally a sign the designer planned for your independence from the start. An unstructured one often means they didn’t — and expect you’ll need them again.
These questions won’t give you a perfect picture. But they’ll tell you a lot about how someone actually runs a project. When the answers are vague on the sales call, they’ll be vague during the project too.
If you’re thinking through a bigger website investment, Built to Scale is worth a listen. It’s my free, four-episode series for founders who want a site that actually scales with their growth — covering what’s missing from most founder websites, what a capable site should be doing for your business, and how to find someone who can build it right.





