Why hiring a web agency is harder than it looks
The web development industry is easy to enter and hard to evaluate from the outside. Portfolios can be misleading, pricing varies wildly for similar work, and the difference between a good and bad agency often only becomes clear after the project has started.
This guide is for small business owners who want to make a smart, informed decision — not get sold something they don't need.
What to look for in a portfolio
A portfolio shows what an agency has built — but the most important thing isn't how it looks, it's whether the work is relevant to you.
Look for projects similar in scope to yours. An agency that builds complex SaaS platforms may not be the best fit for a 5-page service business site. And vice versa.
- Are the portfolio sites live and working? (Check them yourself)
- Do the projects look similar in scope to what you need?
- Is there a mix of industries or do they specialise in yours?
- Can they explain what problem each project solved, not just what it looks like?
- Are there any case studies with real outcomes, not just screenshots?
Questions to ask before you hire
These are the questions that separate serious agencies from ones that will disappear after launch. Ask them before signing anything.
- Who will actually be working on my project — you, or a subcontractor?
- What's included after launch? Hosting, maintenance, bug fixes?
- How do you handle revisions? Is there a limit?
- What do you need from me before the project starts?
- What happens if the project runs over timeline?
- Do I own the code and assets when the project is done?
- How will I update the website after delivery?
Red flags to watch out for
These aren't dealbreakers on their own — but any combination of them should give you pause before committing.
- No clear process or timeline from the first conversation
- Reluctant to share references or real client examples
- Extremely low pricing with no explanation of what's included
- Pressure to sign quickly or 'lock in' a special rate
- No contract or vague contract with no scope definition
- They can't explain what tech they'll use or why
- No mention of what happens after launch
Good agency behaviour
- •Clear process with defined stages
- •Fixed scope and deliverables in the contract
- •You own the code and assets on delivery
- •Post-launch support is clearly defined
- •They ask questions before quoting
Red flags
- •Vague timeline and shifting deliverables
- •No written contract or extremely loose scope
- •Agency retains code ownership
- •No mention of what happens after launch
- •Quote within 5 minutes of the first message
