Hiring a web design studio is one of the most consequential decisions a business owner makes for their digital presence. Get it right and you gain a long-term partner who understands your brand, your customers, and your goals. Get it wrong and you can find yourself months down the line with a website that misses the brief, a relationship that has broken down, and a budget that is gone. The difference between those two outcomes often comes down to the questions you ask before you commit.
Most businesses approach the hiring process the wrong way around. They ask for a quote, review some portfolio pieces, and make a decision largely on price. What they should be doing is treating the pre-engagement conversation as a diagnostic: a structured process of questions designed to reveal how a studio actually thinks, works, and communicates, and whether that is compatible with what they need.
At AG Art Studio, we welcome clients who come to conversations with demanding questions. It tells us they are serious about the outcome and that the relationship will be built on mutual clarity rather than assumptions. Here is the complete list of what you should be asking before you sign anything.
Why the pre-engagement conversation matters as much as the portfolio
A portfolio tells you what a studio has produced. It does not tell you how they got there, how they handled difficulties along the way, how they communicate when something goes wrong, or whether the clients involved were satisfied with the experience. Two studios with equally impressive portfolios can deliver wildly different experiences depending on their process, their communication style, their approach to scope, and the structure of their contracts.
The pre-engagement conversation is your opportunity to go beneath the surface of the portfolio and understand the studio as a working partner. The questions below are designed to surface what you genuinely need to know, in the categories that matter most: process, communication, ownership, support, and fit.
The right studio is not just the one with the best portfolio. It is the one whose process, communication style, and values align with how you need to work.
Questions about process and approach
Can you walk me through your process from brief to launch?
A studio that cannot clearly articulate its process does not have one, or does not follow it consistently. A well-run studio should be able to describe its phases in plain language: discovery, strategy, wireframing, design, development, testing, and launch. Listen not just for the phases but for how they describe client involvement at each stage. You should be an active participant in the process, not a passive recipient of deliverables.
Who exactly will be working on my project?
Some studios pitch with their most senior people and then hand the actual work to junior team members or offshore contractors. Ask specifically who will be doing the design, who will be doing the development, and whether any part of the work will be subcontracted. If it will be subcontracted, ask to see examples of that subcontractor's work specifically. The person who presents to you in the pitch should be involved in delivering your project, not just winning it.
How do you handle changes to the brief mid-project?
Scope creep is one of the most common sources of budget overruns and project friction. Ask the studio to explain, specifically, how they handle changes that arise after the project has started. A professional studio will have a clear change request process: a defined mechanism for assessing the impact of a change, communicating any cost or timeline implications, and obtaining written approval before proceeding. If the answer is vague, that ambiguity will become your problem later.
Questions about communication and collaboration
How will we communicate throughout the project?
Establish the communication cadence upfront. How frequently will you receive updates? Through what channel: email, a project management tool, video calls? Who is your primary point of contact, and what is their typical response time? Studios that do not set clear communication expectations at the start tend to go quiet at the worst moments, typically when something is delayed or needs your input urgently. Regular, structured communication is a sign of a professionally run operation.
How many rounds of revisions are included?
Revision rounds are where project budgets quietly inflate and timelines silently extend. A professional studio will include a defined number of revision rounds at each stage, with a clear process for what constitutes a revision versus a new direction. Ask what happens when you exceed the included rounds: is there an hourly rate, a flat fee per additional round, or is it negotiated case by case? Understanding this in advance removes one of the most common sources of surprise costs in a web design project.
Questions about ownership, access, and portability
These are the questions that clients most commonly forget to ask before signing, and most frequently regret not having asked afterwards. Ownership and access questions determine what you actually end up with at the end of the project and what your options are if the relationship ends.
Questions about post-launch support and maintenance
What support do you provide after the site goes live?
Launch day is not the end of the relationship; it is the beginning of the most operationally critical phase. Ask specifically what happens in the weeks after launch: is there a warranty period during which bugs are fixed at no charge? What is the process for reporting issues? Is there a retainer available for ongoing updates and maintenance, and what does it include? The period immediately after launch is when businesses most need their studio to be responsive, and it is worth establishing the terms of that responsiveness before you sign.
Will you train us to manage the site ourselves?
If your site is built on a content management system, you should be able to make routine updates, publish new content, and manage basic settings without needing to call the studio for every small change. Ask whether training is included, what form it takes, and whether documentation is provided. A studio that builds sites its clients cannot operate without ongoing paid support has a structural incentive to keep you dependent. A studio that trains you to be self-sufficient is demonstrating that its long-term relationship with you is based on the quality of its work, not on your inability to manage without them.
Red flags to watch for in the conversation
How to compare proposals once you have asked the right questions
| Evaluation area | What a strong proposal includes | What a weak proposal includes |
|---|---|---|
| Scope definition | Detailed page list, features, and exclusions | A vague description with no defined deliverables |
| Timeline | Phase-by-phase schedule with milestones | A single end date with no interim checkpoints |
| Payment terms | Clear payment schedule tied to milestones | Full payment upfront or vague "on completion" |
| Ownership | Explicit IP and code transfer upon final payment | Silent on ownership or retains rights to source files |
| Revision policy | Defined rounds per phase with clear overage terms | Unlimited revisions (unsustainable) or none included |
| Post-launch | Named warranty period with defined bug-fix terms | No mention of what happens after the site goes live |
- You have received a written proposal with defined scope, timeline, and payment schedule
- The contract explicitly states that you own the code, design files, and all intellectual property upon final payment
- Hosting, domain, and CMS accounts will be registered in your name, not the studio's
- You know exactly who will be working on your project and have seen their specific work
- The revision policy is written into the contract with clear overage terms
- You understand the change request process and what triggers an additional cost
- Post-launch support terms, including a warranty period, are documented in writing
- You have spoken to at least one previous client of the studio, not just read written testimonials
- You understand what CMS platform the site will be built on and are comfortable that you can manage it
- You have asked what happens if the project is not completed to the agreed standard and understand your recourse
The businesses that have the best web design experiences are not the ones that spent the most or hired the most well-known studio. They are the ones that entered the relationship with clear expectations, a thorough contract, and the confidence that came from asking the right questions before committing. That diligence costs nothing but a well-prepared conversation, and it is the single most effective way to protect your investment.
Getting two or three proposals is sensible, not because price is the deciding factor but because comparing proposals from different studios reveals how differently they interpret the same brief. That comparison gives you a much clearer picture of what is and is not included in each proposal, and sharpens your ability to evaluate value rather than just cost.
Entirely reasonable, and any professional studio should welcome the request. Ask to speak with a client whose project was similar in scale or complexity to yours, and ask that client specifically about communication quality, how problems were handled, and whether the final result matched what was promised at the brief stage. Written testimonials are useful but a direct conversation is far more revealing.
Walk away. A written contract is not a sign of distrust; it is the professional standard that protects both parties. Any studio unwilling to put agreed terms in writing is either operating informally in a way that will cause problems later, or has terms they know you would not agree to if you saw them clearly stated. Neither situation is one you want to enter into.
A common and fair structure is a deposit of 30 to 50% at project start, a further payment at a defined midpoint milestone such as design approval, and the remainder upon launch. This structure aligns incentives for both parties: the studio has security that they will be paid for work completed, and the client retains leverage to ensure the project is delivered to the agreed standard before final payment is released.
The right process is one that matches your availability, your decision-making structure, and the complexity of your project. If you need to involve multiple stakeholders in approval decisions, a studio that requires rapid single-point-of-contact responses will frustrate you. If you want to be closely involved in design decisions, a studio that presents only finished work for sign-off will feel opaque. Ask the studio to describe a typical week in the project and assess whether that rhythm fits how your business operates.
This is a risk worth addressing in the contract, particularly for larger projects. Ask whether stage payments are tied to deliverable handovers so that in the event of a studio closing, you retain the work you have already paid for. Ensure that all work in progress is transferred to you at each milestone, that code is stored in a repository you have access to, and that any third-party accounts are in your name so they are not lost if the studio ceases trading.