What to Ask a Web Development Agency Before You Sign Anything

We've inherited enough projects from other agencies to know exactly how badly this process can go. The pattern is usually the same: a founder or business owner chose a development partner based on a polished pitch and an attractive price, and six months later they have a half-built product, a strained relationship, and a codebase that needs significant work before anyone else will touch it.

The agencies that deliver well tend to sound like good agencies in a sales call too. Filtering for quality before you commit is harder than it sounds. These questions help.

About Their Process

How do you scope a project, and what happens when scope changes?

A good answer explains their discovery process (how they get to a detailed spec), how they price scope changes, and what protections exist for both sides. A bad answer is vague about the process and dismissive about scope changes ("we'll figure it out").

Every significant project has scope changes. How an agency handles them is not an afterthought — it's one of the most important factors in whether your project comes in on budget.

How often will I see working software during the project?

You want to see demos of working software — not slide decks, not mockups, actual running code — at least every two weeks. Agencies that go dark for months and deliver a "finished" product at the end are a red flag. The longer the feedback gap, the more expensive corrections become.

Who is my point of contact and how responsive will they be?

Some agencies sell projects, then hand them to a junior PM and an offshore team you never meet. Ask explicitly: who writes the code? Who reviews it? Who will I be communicating with day-to-day?

About Their Technical Approach

What technology do you use, and why?

You don't need to evaluate the technical answer deeply — but you should listen for whether the answer is thoughtful or reflexive. A team that has genuinely thought about technology choices can explain the tradeoffs. A team that always uses the same stack regardless of the project may not be making deliberate choices.

Also listen for honesty. "We default to X but have used Y for specific use cases" is more reassuring than "we only do X" or an exhaustive list of every technology they've ever touched.

How do you handle testing and quality assurance?

Any serious development agency writes automated tests. If they don't, your software will be manually tested (which means not tested thoroughly) and every change risks breaking things that were previously working. Ask about their testing approach specifically: unit tests, integration tests, end-to-end tests, and whether QA is integrated into the development process or bolted on at the end.

How will you hand off the code when the project is done?

The code should be yours. You should have full access to a version control repository (GitHub or similar), clear documentation, and ideally a knowledge transfer session. If an agency hedges on code ownership or makes handoff sound complicated, that's a serious warning sign.

What does your deployment process look like?

Good teams have staging environments where changes are tested before they go to production. They use automated deployment pipelines. They have monitoring in place. They can explain what happens when something breaks in production and how fast they can fix it.

About Their Track Record

Can you show me examples of similar work?

Portfolio projects are worth examining carefully. Ask about the scope of their involvement — did they build the whole thing or one section? Ask whether the client would talk to you. Ask what technologies were used and why.

Can I speak with a previous client whose project was similar to mine?

References that agencies proactively offer are references they've pre-screened. Ask for a reference that's specifically relevant to your project type — similar industry, similar scale, similar technical requirements. Then actually call them. Ask whether the project came in on time and on budget, whether there were surprises, and whether they'd hire the agency again.

Have you done projects that failed or went significantly over budget? What happened?

Every experienced agency has had projects that didn't go as planned. How they talk about this tells you a lot. Agencies that take some responsibility, explain what they learned, and can describe process changes they made are more trustworthy than agencies that either claim a perfect record or blame everything on the client.

About Money

How do you structure your contracts — fixed price or time and materials?

Both models are legitimate, but they have different risk profiles.

Fixed price works well when the scope is very clearly defined and unlikely to change. You know what you'll pay. The risk is that "unforeseen" issues can become the agency's justification for change orders, or that a fixed-price agency cuts corners to protect their margin.

Time and materials gives you more flexibility and transparency — you pay for actual hours worked. The risk is that without a clear scope, costs can escalate. Good time-and-materials engagements have detailed estimates, regular check-ins on burn rate, and agreed-upon mechanisms to course-correct.

What's included in your price, and what typically generates additional costs?

Revisions, hosting setup, third-party service integration, post-launch support — these are all common sources of unexpected costs. Get specifics about what's in and out of scope, and what triggers an additional charge.

What does ongoing maintenance cost after launch?

Software needs maintenance. Security updates, bug fixes, dependency updates, performance monitoring — these don't stop at launch. Ask what post-launch support looks like and what it costs. An agency that doesn't have a clear answer to this question may not plan to stick around.

The Questions to Ask Yourself

After the calls, ask yourself:

Did they ask as many questions as they answered? A development agency that doesn't understand your business, your users, and your goals can't build software that serves them. The best agencies ask a lot of questions before they can quote.

Did they push back on anything? The best development partners tell you when your idea has problems, when your scope is too large, or when your timeline is unrealistic. Agencies that agree with everything you say either don't have opinions or are afraid to share them — neither is reassuring.

Were they honest about their limitations? Every agency has things they're not great at. An agency that claims expertise in everything should be viewed skeptically. One that says "we're not the best fit for X, but we're very strong at Y" is telling you something honest.

How did they handle your questions? Patience, directness, and specificity in answers are good signs. Vagueness, defensiveness, or overselling in answers to reasonable due-diligence questions is a warning.

---

If you want to ask us these questions, we're ready for them. Schedule a call and we'll answer everything here — including the parts where the honest answer isn't the most flattering one.