Most businesses hire the wrong agency not because they chose badly, but because they did not know what to look for before the contract was signed. The right agency will have a defined process, a portfolio that matches your project type, and the communication habits to keep a build on track. This guide covers exactly what to evaluate, what questions to ask, and what early warning signs to walk away from.
What Good Looks Like: At a Glance
Before getting into detail, here is a summary of what separates agencies worth hiring from those worth avoiding.
Green Light | Red Flag |
Defined project phases with named deliverables | Vague scope with no milestone structure |
Portfolio includes projects similar to yours | Portfolio is broad but shallow with no detail |
They ask more questions than you do in discovery | They skip discovery and jump straight to pricing |
References available on request | No references, only anonymous testimonials |
Contract specifies IP ownership and handoff terms | Contract is verbal or a single-page email summary |
Realistic timeline with contingency built in | Timeline matches exactly what you want to hear |
Named team members on your project | Offshore or freelance handoff with no disclosure |
Post-launch support terms defined upfront | Support is 'we will figure it out after launch' |
1. A Defined Process Is Not Optional
A web development agency that cannot explain its project process in concrete steps is one that improvises. That is fine for small tasks. It is expensive on a $20,000 build with a hard launch date.
What a credible process looks like in practice:
1. Discovery: The agency asks about your users, your competitors, your existing tech, and your definition of success before proposing anything.
2. Scoping and estimation: A written scope of work is produced from the discovery findings, with features listed, excluded, and estimated. Not a quote built on assumptions.
3. Design: Wireframes or mockups are reviewed and approved before any development begins. Changes at the design stage cost a fraction of what they cost in code.
4. Development with checkpoints: Builds happen in sprints or phases, with working demos shared at regular intervals rather than a single reveal at the end.
5. Testing and QA: Browser testing, device testing, load testing, and user acceptance testing happen before any launch discussion.
6. Launch and handoff: The agency documents what was built, provides training for your team if needed, and hands over credentials, source code, and assets.
What to ask: 'Walk me through how a typical project moves from brief to launch.' If the answer is vague or skips steps, that is the answer.
2. Portfolio Depth Matters More Than Volume
Any agency can show screenshots. What you are looking for is evidence they have solved the problem you are bringing them. A portfolio with 40 sites tells you very little. A portfolio with 6 detailed case studies, each explaining the brief, the constraints, the decisions made, and the outcome tells you a great deal.
What to look for in portfolio work
• Projects in your industry or with comparable complexity
• Evidence of design decision-making, not just finished visuals
• Technical context: what platform was used, what integrations were built, what the performance constraints were
• Outcome framing: did the project achieve the client's stated goal
If the portfolio shows only finished visuals with no context, ask for a case study on one of the projects. A good agency will have one. If they do not, that is a signal the work was execution-only, with no strategic involvement.
Questions to ask about specific portfolio pieces
• What was the original brief for this project?
• What was the biggest technical or design challenge, and how did you solve it?
• What platform did you build on, and why?
• Is the client still with you, or was this a one-time engagement?
3. Know Who Is Actually Building Your Project
The person who sells you the project is rarely the person building it. That is not inherently a problem, but you need to know who the delivery team is before you commit.
Several things are worth confirming explicitly:
• In-house vs. subcontracted: Some agencies outsource development to freelancers or overseas teams without disclosing it. Ask directly: 'Is all development done by your in-house team, or do you work with subcontractors?'
• Named team members: Ask who will be assigned to your project and whether that changes mid-build. High-turnover shops cycle through developers, and a handoff mid-project can set a build back weeks.
• Point of contact: You need one named person who owns the project from the agency side. If no one can name that person before you sign, project management is likely ad hoc.
• Time zone alignment: For offshore arrangements, find out what the actual overlap hours are. A one-hour window per day for questions slows every decision in the build.
4. Communication Style Predicts How Problems Get Handled
You will not know if an agency communicates well until you have worked with them. But you can get a strong early signal from the sales process itself. Agencies that respond quickly and clearly when they want your business rarely get slower once they have it.
Signals to watch during the pre-contract phase
• Response time to your first inquiry
• Whether discovery questions are asked before pricing is quoted
• Whether proposals are customized to your brief or feel templated
• How they handle a question they cannot immediately answer
Communication terms to clarify before signing
• How often will you receive project updates, and through what channel
• What is the turnaround expectation on feedback you provide
• Who approves scope changes and how are they documented
• What happens if a milestone is missed
A written communication plan in the contract is a strong indicator of a mature agency. A vague 'we will be in touch' approach is not.
5. The Contract Protects You: What It Must Include
A verbal agreement or a short email summary is not a contract. Disputes over web development projects almost always come down to what was and was not written down. Before signing anything, these terms need to be explicit.
Contract Term | Why It Matters | What to Watch For |
Scope of work | Defines exactly what is being built and what is not | Vague descriptions like 'full website' with no feature list |
IP ownership | States who owns the code, design assets, and content on delivery | Language that gives the agency ownership until payment is received in full |
Payment milestones | Ties payments to deliverables, not just calendar dates | 100% upfront or 100% on delivery with nothing in between |
Change order process | Documents how out-of-scope requests are handled and priced | No process for changes means every change becomes a dispute |
Timeline and milestones | Named checkpoints with dates, not just a final launch date | Single delivery date with no intermediate milestones |
Post-launch support | Defines what happens if something breaks after go-live | No warranty or support terms at all |
Termination clause | States what each party is owed if the relationship ends early | One-sided termination terms that favor only the agency |
Credentials and access | Lists what accounts, logins, and assets are handed over at completion | No explicit handoff checklist |
If an agency resists putting any of these terms in writing, treat that resistance as information about how the project will be managed.
6. Red Flags That Warrant Walking Away
Most agencies are legitimate businesses that want to do good work. But some patterns show up consistently in troubled engagements, and recognizing them before you sign saves significant time and money.
Operational red flags
• No discovery process before a proposal is delivered
• Proposal delivered within hours of the first conversation
• Significant pressure to sign before a deadline that exists only in the sales conversation
• Portfolio work that cannot be verified as live or that differs significantly from the finished product
• No named references willing to speak on the phone
Contract red flags
• Agency retains IP ownership after project completion
• No change order process defined
• Payment terms front-loaded beyond 30-40% of total project cost as a deposit
• No post-launch warranty of any kind
• Arbitration clauses that require dispute resolution in a jurisdiction inconvenient to you
Communication red flags
• Slow response times during the sales phase, then promises that 'the project team is much faster'
• Reluctance to name who will actually be building the project
• No clear point of contact once you have signed
The Questions Worth Asking Before You Sign
Use these in any agency conversation. The quality of the answers tells you more than any sales deck.
Question | What the Answer Reveals |
Walk me through a recent project from brief to launch. | Process maturity and ability to communicate clearly about execution |
Who specifically will be assigned to my project? | Whether they have a real team or a reseller model |
Have you built something with this type of integration before? | Technical experience relevant to your specific requirements |
Can you connect me with two references from similar projects? | Confidence in their own track record |
What happens if we disagree on whether something is in scope? | Change management process and conflict resolution approach |
What does post-launch support look like, and is it included? | Whether support is a product or an afterthought |
Who owns the code and assets once the project is complete? | IP terms, which are non-negotiable and should be in writing |
What is your approach if a milestone slips? | Accountability culture and transparency under pressure |
FAQ: Choosing a Web Development Agency
How much should a web development project cost?
It depends heavily on scope. A brochure-style website with a CMS typically runs $5,000 to $20,000. A custom web application or e-commerce platform with complex integrations can run $30,000 to $150,000 or more. Be cautious of quotes significantly below market rate for your project type. Low bids often reflect offshore subcontracting, stripped scope, or a team without relevant experience.
Should I hire a local agency or does location not matter?
Location matters less than it used to for most projects. What matters is communication quality and time zone overlap. An agency three time zones away that responds within an hour and runs structured meetings is a better operational fit than a local agency that is slow to respond. That said, if your project requires in-person workshops or close strategic collaboration, proximity is a genuine advantage.
What is a reasonable deposit to pay upfront?
A deposit of 25-35% of the total project cost is standard practice. Anything above 50% upfront is unusual and shifts most of the financial risk to you. Milestone-based payments are the cleanest structure: a deposit to begin, a payment on design approval, a payment on development completion, and a final payment on launch.
How do I know if an agency actually built the portfolio work they are showing me?
Ask for the live URL and verify it is operational. Ask who the client was and whether they can provide a reference. Ask for their specific role on the project: did they own the build end-to-end, or were they one contributor on a larger team? Agencies that built the work are typically eager to walk through the decisions they made. Those that did not tend to stay at the surface level.
What should be handed over to me when a web project is complete?
At minimum: all source code in a repository you own, all design files (Figma, Adobe XD, or equivalent), all media assets and copy, login credentials for hosting, domain registrar, CMS, and any third-party services. A good agency will also provide documentation for your team and a short onboarding session if the CMS or admin interface needs explanation.
Want to see how we structure a web project before you commit to anything? Our process page walks through every phase, from discovery to handoff, so you know exactly what to expect. See our process at Coded Pulse.
