A business website gets built once every few years, but you work with it every day. That's why picking the wrong vendor is expensive: missed deadlines, rework, a site no one but its author can develop further, and a lost year. Choosing a web development agency is also hard because from the outside a digital agency, an IT agency and a web studio all look the same: a beautiful portfolio, big-name clients, a promise of "end-to-end."
We are an agency ourselves, and we often talk to companies that have already been burned by a previous vendor. Below is how to tell a reliable team from a good-looking storefront: who actually needs an agency, how to read case studies, what to ask at the first meeting, how to compare proposals and what to check in the contract.
Agency, web studio, freelancer or in-house
Don't start by searching for "the best web development agency." Start by asking which type of vendor your task needs. A web studio or a freelancer is a common choice for small projects, and that's perfectly fine.
| Best for | Main risk | |
|---|---|---|
| Freelancer | Landing page, brochure site, changes to an existing design | The project depends on one person |
| Web studio | Standard sites and stores on a builder or CMS | Template solutions, little analysis |
| Agency | A site that drives sales, integrations, an app or a service | Higher budget, needs an owner on the client side |
| In-house | A product under constant development | Slow hiring and team costs |
An agency makes sense when the site is more than just a page on the internet. For example, it brings in leads from search and ads, connects to a CRM and an accounting system, has a customer account or a catalog with thousands of items. Then you need an analyst, a designer, developers, a QA engineer and a project manager working as one team.
An in-house development team pays off if the product evolves every week for years. But building one from scratch takes time. Companies often start with an agency and hire in-house once the product is running and the volume of ongoing work is clear.
What to look for in the portfolio and case studies
A portfolio answers the question "do I like how they work?" Case studies answer a more important one: can the team solve problems like yours. Look at both, but decide based on the second.
- There are projects of similar scale and type: an online store, a corporate site, a service with a customer account.
- The case study describes a business problem, not just "we made a beautiful site."
- It's clear what this particular team did: the whole project, or only design or front-end.
- The work is live: the sites open, work on a phone and load fast.
- The design varies from project to project instead of being one template in different colors.
- There are projects the agency supports and develops after launch.
The client's industry matters less than it seems. Experience in your niche speeds up onboarding, but the ability to understand someone else's business matters more. Our projects include online stores, corporate sites, CRMs and mobile apps for very different industries, and each one started with figuring out how the client's business works.
Questions to ask a vendor at the first meeting
The first meeting is your main selection tool. In an hour you can learn how a vendor thinks, how they communicate and how honestly they talk about risks. Prepare questions in advance and ask every candidate the same ones.
- Who exactly will work on the project, and who is accountable for the result?
- How does the process work: what are the stages, and what do we get at the end of each?
- How does discovery work: will you analyze the market, competitors and audience?
- Will there be a prototype before design, and how many design options do you propose?
- Which stack or CMS will you use, and why that one for this task?
- How often do you show work in progress, and how are revisions handled?
- What does testing include, and who checks the site on phones?
- Do you include SEO groundwork and analytics setup before launch?
- What happens after launch: support, warranty, further development?
- Which projects of similar scale did you deliver on time, and what made that possible?
Listen not only to the answers but also to the questions you get back. A strong vendor will ask why you need the site, where your customers come from, who will produce the content and what isn't working now. A vendor who asks nothing about your business will build blind.
At the first meeting, a strong vendor asks more about your business than you ask about their portfolio.
Our projects start with analysis, structure and messaging: market, audience, competitors. So in the first meetings we mostly ask questions, and design and development come later.
Red flags
None of the points below means a vendor is bad. But if several of them add up, it's better to keep looking.
- A price before discussing the task. You can't give an accurate estimate without understanding the scope. A figure "off the bat" almost always means a template or extra charges later.
- A promise to do everything very fast. Fast is good if the vendor explains how. If not, analysis and testing are what will get cut.
- No discovery or prototype stage. Straight to design, with structure and copy "later," means rework is inevitable.
- A vague scope of work. "End-to-end website development" in one line, with no list of pages, features or stage deliverables.
- Everything registered to the vendor. The domain, hosting and analytics accounts are registered to the agency, and you can't change anything without them.
- A proprietary closed CMS. The site will only run with that vendor, and moving it elsewhere will be hard and expensive.
- No answers about support. Life after launch gets a "we'll discuss it later."
How to compare proposals
Send the same brief to five vendors and the totals can differ several times over. That doesn't necessarily mean someone is overcharging. More often, vendors are simply proposing different scopes of work, and your job is to bring the proposals to a common denominator.
- Send everyone the same brief. The goal of the site, the audience, a rough structure, required features, integrations, the desired timeline. Otherwise you'll be comparing answers to different questions.
- Break proposals down by stage. Discovery, prototype, design, copy, development, integrations, testing, SEO groundwork, analytics, launch, support. Mark what each one includes and what it doesn't.
- Check the deliverable of each stage. Not "design," but "design of all page templates for desktop and mobile, two concept options, a UI kit."
- Compare timelines by stage. A single end date hides risks. Stage-by-stage timelines show whether the vendor understands how the work will go.
- Clarify what's excluded. Licenses, hosting, copy, photos, content migration, revisions beyond the agreed number.
After this exercise you usually have two or three proposals describing a similar scope. Between those you can choose on price, timeline and how the meetings went.
The contract, code ownership and support
A contract protects both sides only if it spells out exactly what is being done and how the work is accepted. A boilerplate "website development services" agreement with no appendices guarantees almost nothing.
- A specification or list of work as an appendix to the contract.
- Stages, deadlines and payment by stage, not 100% upfront.
- An acceptance procedure: what counts as a completed stage and how many days you have to review it.
- The number of revision rounds for design and development.
- Transfer of exclusive rights to the code, design and copy after payment.
- Access to the domain, hosting, repository, CMS and analytics registered to your company.
- A warranty period: which bugs are fixed free of charge and how quickly.
- Terms for support and further development after the warranty.
Discuss code ownership separately. The site should belong to you, not the vendor: with the source code, documentation and access, you can keep developing it with the same team, your own developers or a new agency.
Support is also worth discussing before you start. After launch the site needs updates, bug fixes, new pages and analysis of analytics data. Find out how the vendor takes on tasks, how quickly they respond to urgent issues and how the cost of improvements is calculated.
How to make the decision
Once you're down to two or three candidates, compare more than the numbers. Think about who was easier to talk to, who understood the task better and who was more honest about risks. You'll be working on the site together for several months and then possibly developing it for years.
A good sign is when a vendor brings their own ideas instead of just writing down your wishes, and can explain why they think those ideas will help your business. You can see how we approach projects and the principles we work by on the about Sphere page.
FAQ
Which should I choose for a website: an agency, a web studio or a freelancer?
Go by the complexity of the task. A reliable freelancer or a small studio will build a landing page or a brochure site without integrations faster and cheaper. If you need analysis, UX design, visual design, development, integrations and support from one place, an agency is more convenient: it has a team and a process, and the project doesn't depend on one person.
How many vendors should I consider?
Three to five is usually enough. First shortlist candidates by portfolio and experience with similar tasks, then hold meetings and request proposals based on the same brief. More options rarely add clarity, and they get harder to compare.
Do I need a finished specification before contacting an agency?
No. It's enough to describe the goal, the audience, the rough scope and your timeline and budget constraints. Good vendors write the detailed specification with the client during the discovery stage. What matters is that this stage is clearly listed in the proposal and has a defined deliverable.
Why do proposals differ so much in price?
Most often, vendors have priced different scopes of work: one includes discovery, a prototype, copy, SEO groundwork and testing, while another covers only front-end development from an existing design. That's why you should compare the stages, the deliverable of each and the support terms, not the totals.
Who should own the rights to the website's code and design?
That is settled by the contract. The client usually needs exclusive rights to the code, design and copy after payment, plus access to the repository, hosting, domain and admin panel registered to the company. Then the site can be developed further with any vendor.




