Most founders hire the wrong development agency because they ask the wrong questions. They focus on portfolio and price, but miss the questions that reveal how an agency actually operates when a project gets hard.
Here are the 12 questions to ask every agency you consider — with what good and bad answers look like.
1. “Who exactly will work on our project?”
Good answer: They name specific developers, describe their experience levels, and explain the team structure. You know exactly who’s doing the work.
Bad answer: “Our team,” “our developers,” or vague references to their talent pool. This means your project could be staffed with whoever is available, including juniors or contractors.
At Whipp Studio, we introduce the specific developers assigned to each project before the contract is signed.
2. “Can I speak to three recent clients whose projects are similar to mine?”
Good answer: Yes, immediately. They connect you with clients who give honest feedback.
Bad answer: They offer testimonials from their website, say references are “available upon request” (but make it hard), or only offer introductions to cherry-picked clients.
References are the single most important signal for agency quality. Any agency with a track record of good work will give you them without hesitation.
3. “What does the contract say about code ownership?”
Good answer: All code belongs to you on project completion (or on each milestone payment). They can provide the exact contract clause.
Bad answer: Vague ownership language, clauses that give the agency a license to reuse your code, or withholding code until full payment is received.
You should own everything built for you, with no restrictions, upon completion.
4. “How do you handle scope creep?”
Good answer: They describe a specific process — change requests are documented, scoped, priced, and approved before work begins. They have a change order process.
Bad answer: “We’re flexible” or “we’ll figure it out.” Flexibility without process means your project will either blow the budget or stall when scope grows.
5. “What’s your communication rhythm during a project?”
Good answer: Weekly status updates, a shared project management tool (Linear, Notion, Basecamp), and a named project manager who is your single point of contact.
Bad answer: “We’ll be in touch,” ad-hoc updates, or developers who you email directly without a PM layer.
Communication structure is how projects stay on track. A lack of structure correlates directly with missed deadlines.
6. “What happens if the project runs over deadline?”
Good answer: They explain their process for scope management that prevents this, and describe what happens if it does — is there a cost impact? Do they absorb it if it’s their fault?
Bad answer: Deflection, blame on “it’s always the client’s fault,” or no clear answer. Every agency has had projects run late. How they handle it tells you a lot.
7. “Do you offer post-launch support? What does that cost?”
Good answer: Yes, with a clear offering — a retainer, a support SLA, or an included warranty period (typically 30–90 days) for bugs.
Bad answer: “You’ll need to re-engage us for any issues” without a formal support offering. The first 60 days post-launch are always the most bug-prone.
Whipp Studio includes a 30-day post-launch support period in every project and offers ongoing retainers for clients who need continued development.
8. “What’s your testing process before delivery?”
Good answer: They describe unit tests, integration tests, or end-to-end tests (Playwright, Cypress). Manual QA checklists. Browser/device testing. Staging environment review before production deployment.
Bad answer: “We test as we go” or no structured QA process. Code without tests is technical debt that compounds.
9. “What tech stack will you use and why?”
Good answer: Specific, opinionated answer based on your requirements. “We’ll use Next.js for the frontend because you need SEO, Supabase for auth and database because it eliminates backend boilerplate, and Stripe for payments. We’ve built 20 products on this stack.”
Bad answer: “We can work with anything” or a different framework listed for every project in their portfolio. An agency without strong stack opinions is a team of generalists, not specialists.
10. “How do you handle security — especially auth and data storage?”
Good answer: They mention HTTPS by default, environment variables for secrets, Row-Level Security (or equivalent), parameterized queries to prevent SQL injection, and a policy on not storing sensitive data beyond what’s necessary.
Bad answer: “We follow best practices” without specifics. Security questions should prompt specific, technical answers.
11. “What does your handoff look like?”
Good answer: Full source code on GitHub/GitLab, README with deployment instructions, documented environment variables, a walkthrough call with your team, and access to all third-party accounts (Stripe, Vercel, Supabase, etc.).
Bad answer: A zip file of code with no documentation. You should be able to deploy and modify the product without the agency’s help after handoff.
12. “What projects have you turned down, and why?”
Good answer: They describe projects they declined because they weren’t the right fit — wrong tech domain, unrealistic budget, unclear scope, client wasn’t ready. This shows self-awareness and integrity.
Bad answer: “We take everything” or obvious discomfort with the question. Agencies that take every project optimise for revenue, not for client outcomes.
Frequently Asked Questions
Should I get quotes from multiple agencies? Yes — 3 quotes minimum. This isn’t just about price; it’s about understanding how different agencies scope and approach your project. The variation will be informative.
Is a cheaper agency always worse? No. Eastern European and Latin American agencies often deliver exceptional quality at lower rates due to lower cost of living. Evaluate by portfolio and references, not by price.
How long does an agency proposal/quote process take? A good agency will spend 3–7 days scoping your project properly before providing a quote. Immediate quotes without deep discovery calls are a red flag.
Should I pay a retainer upfront? Milestone-based payments are standard and appropriate — typically 25–50% upfront, then milestones at key delivery points, with the final payment on completion. Avoid agencies requiring 100% upfront.
What should be in the contract? Scope of work, IP ownership, payment schedule, timeline, change order process, post-launch support terms, and confidentiality clause. Get a lawyer to review if the engagement is above $25K.
Evaluating your options? We’re happy to answer all 12 of these questions (and more) on a no-commitment discovery call. At Whipp Studio, transparency is our default. Book a free strategy call →