How to Choose the Right Web Agency
Choose a web agency by matching its profile to your project's nature: a marketing agency suits campaign sites, a technical development agency suits web applications and integration-heavy platforms. Review reference projects of the same type as yours, ask about performance, accessibility, and maintenance before signing, and compare candidates in a weighted evaluation matrix instead of on price alone.
There are hundreds of web agencies in Sweden, and most of them are good – at their thing. The problem is that the word “web agency” covers everything from campaign sites to advanced web applications. The most common mistake in choosing an agency, then, isn’t picking a bad agency, but picking the wrong kind of agency for the project.
Start with the project type, not the agency list
Before you google a single agency: define what you’re actually building. A brand site with public content is a design-intensive communications project. A customer portal, e-commerce site, or web application is a software project with login, integrations, and performance requirements under load.
An agency that produces brilliant campaign sites is rarely right for a system with thousands of logged-in users – and vice versa. Always ask for reference projects of the same type as yours, not just attractive examples in general.
Marketing agency or technical development agency?
The two most common agency types are recognized by where their emphasis lies:
- The marketing agency is led by communication and design. Its strength is brand, content, and campaigns; the technology is often template-based CMS solutions produced quickly.
- The technical development agency is led by development. It has dedicated teams for frontend, backend, and architecture, and the conversations are about integrations, testing, scalability, and maintenance.
Neither is wrong – the question is what your project requires. A new brand site with a lot of content: marketing agency or hybrid. Customer portal, advanced e-commerce, or web app: technical agency. If the project is both, let the technical foundation weigh heaviest – design can be strengthened afterward, a weak technical foundation can rarely be rescued after the fact.
Questions to ask before you sign
Three areas separate the wheat from the chaff, and all three are cheap to ask about but expensive to discover too late:
- Performance. How do you work with Core Web Vitals? What were your latest deliveries’ scores at launch? What do you do when the site grows and slows down?
- Accessibility. Do you work to WCAG? How do you test – automated and manual? What’s included in the delivery, and what does it cost to fix gaps discovered later?
- Maintenance. What happens after launch – response times, further development, who owns the code and the environments? What does a typical maintenance agreement look like in kronor per month?
An agency that answers concretely and with examples on all three has done it before. Vague answers here become vague deliveries later.
An evaluation matrix with weighted criteria
Once the candidates are narrowed down: compare them systematically instead of on gut feeling. Score each agency 1–5 per criterion, multiply by the weight, and sum it up.
| Criterion | Weight | What you're assessing |
|---|---|---|
| Technical expertise for your project type | 25% | Architecture reasoning, technology choices, how they handle your toughest requirements |
| Relevant reference projects | 20% | Similar type and scope – call the references |
| Team and continuity | 15% | Which people you get, seniority, risk of substitutions |
| Working method and transparency | 15% | Demo cadence, how changes and deviations are handled |
| Maintenance offering | 15% | SLA, post-launch costs, ownership of code and environments |
| Price | 10% | Total cost and what's included – not just the hourly rate |
The weights above are a starting point – adjust them to your project. If you’re building something business-critical, maintenance should weigh more; if the project is a time-limited campaign, price and speed can weigh more.
Scenario: two quotes at the same price
Two agencies quote SEK 600,000 for your new customer portal. Agency A shows three portal projects with login and integrations, answers the maintenance questions concretely, and states which senior developers you’ll get. Agency B has a nicer portfolio and a better pitch, but no logged-in solutions among its references and a vague answer about what happens after launch.
In the matrix, A wins clearly – even though gut feeling after the pitches said B. That’s exactly what the matrix is for: it makes gut feeling auditable and forces the questions before the contract instead of after.
Before you sign
Check that the contract gives you ownership of the code, access to all accounts, and a clear exit. Ask for a delivery plan with demo checkpoints, not just an end date. And trust the pattern from the evaluation – an agency that’s meticulous in the sales phase tends to be meticulous in delivery.
Want to test your requirements against a technical development agency? At Weapp we’re happy to run a no-strings-attached review – get in touch.
Frequently asked questions
How many agencies should we request quotes from?
Two to four is about right. Fewer gives you no point of comparison, more costs more in evaluation time than it saves in price. Screen first on reference projects and agency type, and spend the evaluation time on the ones that actually match your project.
How much should price weigh in the decision?
Less than most people let it – 10–20% of the total assessment is a reasonable weight. The difference between quotes is often small compared with the cost of a project that fails or a delivery that can't be maintained. Also compare total cost over time, not just the project price.
Does it matter if the agency uses subcontractors?
What matters is knowing who's doing the work. Ask which people are on your team, how long they've been at the agency, and what happens if someone is swapped out. An agency with its own in-house team usually finds it easier to guarantee continuity over the project's lifetime.
Who should own the code and environments?
You should. Make sure the contract gives you ownership or unlimited usage rights to the code, and that you have your own accounts for domain, hosting, and code repository from day one. That way you can switch providers without starting over – a fair requirement that serious agencies accept.
How do we spot an agency that overpromises?
Warning signs are guaranteed results, a fixed price before requirements have been reviewed, and no follow-up questions about your business. A serious agency challenges your brief, states its assumptions, and would rather talk about what to deprioritize than promise everything at once.