How to Choose a Web Development Agency and Spot Red Flags

By Grocito12 October 2026

To choose a web development agency, first write down what you need and how you will measure success. Then shortlist a few agencies, review relevant work and speak to past clients, compare how they communicate and plan the project, check who will own the code, hosting and domain, and compare quotes on scope rather than price alone. Walk away from vague answers and pressure tactics.

Key takeaways

Define your goals, users, must-have features and budget range before you contact anyone. Vague briefs produce vague quotes.
Judge portfolios for relevance and substance, and speak to people the agency has worked with.
Good agencies explain their process, who works on your project and how you will communicate.
Insist on clear ownership of your code, content, domain and accounts.
Quotes are only comparable when they describe the same scope. The cheapest quote is often the one that leaves things out.
Red flags include guarantees, pressure to sign, no questions about your business and refusal to put terms in writing.

Start with your own needs

Agencies cannot give a useful answer if you cannot describe the problem. Spend a few hours on a short brief before you start conversations. Our guide to writing a software project brief goes into detail, but the essentials are:

Goals: what should the site or app achieve for the business, such as generating enquiries, selling products or reducing support requests?
Audience: who will use it and on what devices?
Scope: pages, features, integrations and content you must have at launch, and what can wait.
Constraints: deadline, budget range, existing systems and any compliance needs.
Success measures: how you will know it worked.

It also helps to know whether you need a website, a web application or a mobile app. Our posts on website versus web app and mobile app versus mobile-friendly website can help with that decision.

Evaluate the agency's work

Portfolio

Look for projects similar in type, complexity or industry to yours. A beautiful brochure site does not prove an agency can build a booking system. Open the live sites on your phone, check their speed and see whether they work well. Ask what the agency's role was, since some portfolios include work done by partners or freelancers.

References

Ask for two or three past clients you can speak to, ideally including one whose project had difficulties. Useful questions: Was the project delivered as agreed? How were surprises handled? Did the team respond quickly after launch? Would you hire them again? Treat a refusal to share any references as a signal.

Team and capability

Find out who will actually do the work: employees or subcontractors, which roles are involved and how experienced they are. Check that they cover the skills you need, such as design, development, testing, SEO basics and hosting, or that they explain which partners fill the gaps.

Technology choices

Ask why they recommend a particular platform or framework, and what the trade-offs are. A good agency explains in plain language and can discuss alternatives. Our guides to choosing a web development framework and Next.js versus WordPress show the kind of reasoning to expect.

Process and communication

A project goes smoothly when expectations are clear. Look for answers to these questions:

How does the project start: discovery, a written scope, designs for approval?
Who is my single point of contact, and how quickly do they usually reply?
How often will we meet, and how will progress be shown, for example working demos on a staging site?
How are changes requested, estimated and approved?
How is testing handled, including on real phones and different browsers?
What do you need from me, and by when?

Delays often come from the client side too, such as late content or slow approvals, so a good agency will also tell you what they need from you.

Pricing models: fixed price or time and materials

Fixed price

You agree a scope and price up front. This works when requirements are clear and stable. The risk is that changes become disputes, and a very low fixed price may mean corners are cut. Make sure the written scope lists deliverables and what happens when you request changes.

Time and materials

You pay for the effort used, usually with estimates and regular reports. This suits evolving products where you expect to learn as you go. The risk is open-ended cost, so ask for a budget cap or milestone reviews.

Hybrid approaches

Many projects start with a paid discovery phase at a fixed price, then move to fixed or capped phases for the build. This is a sensible way to reduce uncertainty for both sides. See also our overview of what drives the cost of a business website.

Ownership, access and handover

These questions are easy to forget and painful to discover later.

Code: will you own the source code on final payment, or only license it? Is any third-party or open-source code involved, and under what licences?
Domain and hosting: the domain should be registered in your name or your company's. Hosting accounts should be in your control, or you should have clear admin access.
Content and design files: who owns images, designs and written content once the project is paid for?
Documentation and handover: will you receive deployment notes, credentials in a secure way and a walkthrough?
Exit: if the relationship ends, can another team take over without difficulty?

Maintenance and support after launch

Launch is the start of ownership, not the end. Ask what warranty or bug-fix period follows launch, what ongoing support is available, how quickly urgent problems are handled and how updates and backups are managed. Our website maintenance plan shows what ongoing care typically involves.

Red flags to watch for

Guarantees of rankings, traffic or sales. No honest agency controls those outcomes.
A quote delivered without asking meaningful questions about your business.
Pressure to sign quickly because of a limited-time discount.
Refusal to provide references, a contract or a written scope.
Retaining ownership of your domain, code or accounts as leverage.
A portfolio that cannot be verified or that shows no live work.
Vague answers about who will do the work or how it will be tested.
Dismissing your concerns about security, accessibility or performance.
A price far below the others without an explanation of what is excluded.

None of these alone proves bad faith, but several together are reason enough to walk away.

Compare quotes fairly

Put quotes side by side in a simple table with these rows: scope and deliverables, pages or features included, design and revisions, testing, content migration, integrations, hosting and domain handling, support after launch, timeline, payment milestones and ownership terms. Ask each agency to clarify anything that is missing. You will often find that the lowest price omits items another quote includes.

A worked example

Imagine a local training company needing a new website with online course enquiries. It invites three agencies and shares the same one-page brief. One returns a quote within an hour with no questions, another asks about their audience, existing content and goals, and the third proposes a short paid discovery phase before fixing a price. The company compares the written scopes, speaks to a past client of each of the last two, confirms it will own the code and domain, and chooses the one whose process and communication it trusts most, not simply the lowest price.

FAQ

How many agencies should I get quotes from?

Three is usually enough to compare approaches without drowning in detail. Give each the same brief so the quotes can be compared fairly.

Should I hire a freelancer or an agency?

A freelancer can suit small, well-defined projects and offers direct contact. An agency offers a wider mix of skills and continuity if one person is unavailable. Choose based on the project's complexity, risk and how much ongoing support you need.

Who should own my website code?

Normally you should, once the project is paid for, apart from third-party and open-source components that carry their own licences. Confirm this in the contract before work starts.

What should a web development contract include?

At least the scope and deliverables, timeline, payment schedule, change process, ownership of code and content, confidentiality, support terms and how either party can end the agreement. A qualified legal professional can review it for your situation.

Next steps

Write a one-page brief, shortlist three agencies and send each the same questions from this guide. Ask for references and a written scope, then compare them side by side. If you would like to include Grocito in that conversation, our website development team is happy to answer the same questions, and you can contact us whenever you are ready. Even if you choose someone else, a clear brief will improve the outcome.