# How to Evaluate a Software Development Agency Before Hiring — Hunchbite > A practical guide to evaluating software development agencies and outsourcing partners — what portfolio signals actually mean, how to assess technical depth, red flags in proposals and contracts, and how to structure the engagement to protect yourself. Source: https://hunchbite.com/guides/evaluating-software-development-agency [Home](https://hunchbite.com/)/[Guides](https://hunchbite.com/guides)/[Rescuing Software](https://hunchbite.com/guides/topic/fix-my-software)/How to Evaluate a Software Development Agency Before Hiring [Rescuing Software](https://hunchbite.com/guides/topic/fix-my-software) # How to Evaluate a Software Development Agency Before Hiring A practical guide to evaluating software development agencies and outsourcing partners — what portfolio signals actually mean, how to assess technical depth, red flags in proposals and contracts, and how to structure the engagement to protect yourself. By HunchbiteMarch 12, 202611 min read software agencyoutsourcingvendor assessment > **Hiring a software agency is a high-stakes decision** that most companies make with insufficient information. The consequences of the wrong choice — lost time, wasted money, code you can't maintain, and the need to rebuild — are severe. Most of the signals that actually matter are not in the portfolio or the proposal. This guide covers how to evaluate a software development agency before committing — what to look for, what to ask, and how to structure the engagement to protect yourself. ## The agency evaluation problem Most companies evaluate agencies on the wrong things: * **Portfolio case studies** are curated marketing. They show the best work, often built by the best people the agency has, who may no longer be there. * **Awards and certifications** (Google Premier Partner, AWS Partner, etc.) indicate marketing investment, not engineering quality. * **Proposal quality** tells you about sales skill, not engineering skill. * **Pricing** is not correlated with quality in the way most people assume. The signals that actually predict outcome are harder to surface — but not impossible. ## What actually predicts a good engagement ### Client retention and repeat work * What percentage of their revenue comes from repeat clients? * How long do client relationships typically last? * Can they name clients they've worked with for 3+ years? An agency that retains clients has demonstrated ongoing value delivery. An agency whose clients consistently complete one project and move on is a signal. ### Code ownership after the engagement Ask explicitly: after the engagement ends, who owns the code? Who can read it? Who can maintain it? Agencies with strong client outcomes produce codebases that: * The client team can extend and maintain without the agency * Have documentation sufficient for a new developer to onboard * Don't require calling the agency for every production issue Agencies that optimise for dependency produce the opposite: bespoke, undocumented code that only they can maintain. ### The team that actually works on your project The team presented in the pitch is often not the team that will build your product: * Ask to meet the specific engineers who will work on your project, not the CTO or senior partner * Assess those engineers directly — a technical phone screen is not unreasonable * Ask about their experience with your specific technical requirements (e.g., if you need Kafka experience, ask the developer who will work on your project about their Kafka work) * What is the agency's turnover? If engineers leave frequently, the team you evaluate today may not be the team working on your project in month 3. ## Technical depth assessment ### The technical interview Before signing, run a technical evaluation of the people who will work on your project: * A system design discussion relevant to your product (how would you design this feature or system?) * Code review: give them a piece of code with deliberate problems and ask for feedback * Past project deep dive: ask them to explain the technical architecture of a past project, including the trade-offs they made You're not looking for perfect answers. You're looking for engineering judgement — do they think clearly about trade-offs, do they know what they don't know, and are they honest about limitations? ### Stack fluency vs. stack familiarity There is a significant difference between an engineer who has used a technology for 3 years in production at scale and one who has done a tutorial. Ask specifically: * What is the largest production system you've built using \[technology\]? * What problems did you encounter at scale? * What would you do differently? Surface-level answers indicate surface-level familiarity. If you're hiring an agency to take over or extend an existing system rather than build from scratch, apply the same scrutiny to the codebase itself — our guide on [technical due diligence for enterprise software](https://hunchbite.com/guides/technical-due-diligence-enterprise-software) covers how to evaluate legacy deployments, data migrations, and integration dependencies before you commit. ### Security and quality practices * How do they handle security? What is their process for securing user data, preventing common vulnerabilities (OWASP Top 10), and managing secrets? * What is their testing approach? What percentage of code is covered by tests? * What does their code review process look like? * How do they handle production incidents? Agencies that don't have clear, process-level answers to these questions are telling you something. For a complete list of what to ask in evaluation calls, use our [questions to ask a development team](https://hunchbite.com/guides/questions-to-ask-development-team) guide alongside this one. And to know what patterns to watch for, read our [red flags when hiring a developer](https://hunchbite.com/guides/red-flags-hiring-developer) guide. Hunchbite Service #### Free Technical Audit We review your codebase and send back a written report with findings and recommendations — whether you hire us or not. [Get a free audit](https://hunchbite.com/audit) ## Red flags in proposals and pitches ### Scope that isn't specific A proposal that describes deliverables in vague terms ("user authentication system," "admin dashboard") without specific functionality definitions is a contract for future disputes. Every ambiguous requirement will be resolved in the agency's favour. Before signing, every feature should have: * A specific description of functionality * Acceptance criteria (how you'll know it's done correctly) * What's explicitly not included ### Unrealistic timelines Most agencies underestimate project duration by 40–60% to win deals. Ask: * What projects have you delivered that are similar in scope to this one? * How long did those take vs. the initial estimate? * What caused the variance? An agency that claims all projects come in on time has either very simple projects or selective memory. ### Fixed-price for undefined scope Fixed-price contracts on software with unclear requirements create a structural conflict of interest. The agency will interpret ambiguity narrowly (to protect margin); you will interpret it broadly (to get what you expected). This conflict, repeated across dozens of features, typically results in either a budget overrun or a product that doesn't match expectations. Before sending your brief, read our guide on [how to write a software development brief](https://hunchbite.com/guides/how-to-write-software-development-brief) to ensure your requirements are clear enough to get accurate quotes. And when you're comparing pricing models, our [fixed price vs. hourly development](https://hunchbite.com/guides/fixed-price-vs-hourly-development) guide covers the trade-offs in depth. ### No warranty period Any reputable agency should offer a warranty period — typically 30–90 days post-delivery during which they fix bugs (not new features, not scope changes) at no additional charge. The absence of a warranty period is a signal about confidence in their own work quality. ## Contract protections ### IP assignment, not licence The default in many agency contracts is that the agency retains copyright and licences the code to you. You want an IP assignment — you own the copyright. This matters if you ever raise funding, are acquired, or need to enforce your rights. Review the contract carefully for language like "licence to use" vs. "assigns all right, title, and interest." ### Source code access throughout the engagement You should have access to the code repository throughout the engagement — not just at completion. This allows you to: * Monitor progress (is code actually being written?) * Review code quality as the project proceeds, not at the end when it's too late * Reduce your risk if the relationship breaks down Agencies reluctant to grant repository access are reluctant for a reason. ### Milestone-based payments Never pay 100% upfront. Structure payments around verifiable milestones: * 20–30% upfront * 30–40% at mid-project milestone with demo * Remaining on delivery and acceptance Define "acceptance" explicitly — it should be based on agreed acceptance criteria, not on the agency's declaration that they're done. If you've got a shortlist and want to pressure-test it against a team that's transparent about who builds your product and how it's priced, you can. [have a no-pressure conversation with us →](https://cal.com/hunchbite/discovery) ## Structuring the engagement for success ### Start with a paid discovery Before committing to a full build, commission a discovery phase (2–4 weeks, fixed scope): * Technical architecture design * Detailed specifications and user stories * Technology decisions with rationale * Revised timeline and cost estimate based on actual scope clarity This costs money but surfaces problems before they're expensive. An agency that refuses a structured discovery is optimising for their speed-to-contract, not your project success. ### Internal technical ownership The single biggest predictor of a successful agency engagement is having technical leadership on your side: * Someone who can review code and assess quality * Someone who can push back on technical decisions * Someone who understands when the agency is padding scope and when they're genuinely flagging complexity Without internal technical context, you're dependent entirely on the agency's self-reporting. That's a structural risk. If an engagement is already in progress and things aren't going well, see our guides on [signs your agency isn't delivering](https://hunchbite.com/guides/signs-to-switch-software-agency) and [how to end an agency contract](https://hunchbite.com/guides/how-to-end-agency-contract). ## Working with Hunchbite We're a small, senior team that's transparent about pricing, process, and who will actually build your product. We do a structured discovery before every engagement, give milestone-based quotes, and you own the code from day one. If we're not the right fit, we'll tell you that too. **[→ Work with Hunchbite](https://hunchbite.com/software-development-agency)** Call [+91 90358 61690](tel:+919035861690) · [Book a free call](https://cal.com/hunchbite/discovery) · [Contact form](https://hunchbite.com/contact) Ask an AI assistant about this guide: [ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.&hints=search) · [Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.) · [Perplexity](https://www.perplexity.ai/search?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.) On this page * [The agency evaluation problem](#the-agency-evaluation-problem) * [What actually predicts a good engagement](#what-actually-predicts-a-good-engagement) * [Client retention and repeat work](#client-retention-and-repeat-work) * [Code ownership after the engagement](#code-ownership-after-the-engagement) * [The team that actually works on your project](#the-team-that-actually-works-on-your-project) * [Technical depth assessment](#technical-depth-assessment) * [The technical interview](#the-technical-interview) * [Stack fluency vs. stack familiarity](#stack-fluency-vs-stack-familiarity) * [Security and quality practices](#security-and-quality-practices) * [Red flags in proposals and pitches](#red-flags-in-proposals-and-pitches) * [Scope that isn't specific](#scope-that-isnt-specific) * [Unrealistic timelines](#unrealistic-timelines) * [Fixed-price for undefined scope](#fixed-price-for-undefined-scope) * [No warranty period](#no-warranty-period) * [Contract protections](#contract-protections) * [IP assignment, not licence](#ip-assignment-not-licence) * [Source code access throughout the engagement](#source-code-access-throughout-the-engagement) * [Milestone-based payments](#milestone-based-payments) * [Structuring the engagement for success](#structuring-the-engagement-for-success) * [Start with a paid discovery](#start-with-a-paid-discovery) * [Internal technical ownership](#internal-technical-ownership) * [Working with Hunchbite](#working-with-hunchbite) Ask AI about this guide * [Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.&hints=search) * [Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.) * [Open in Perplexity](https://www.perplexity.ai/search?q=Read%20https%3A%2F%2Fhunchbite.com%2Fguides%2Fevaluating-software-development-agency%20and%20help%20me%20apply%20it%20to%20my%20situation.%20Answer%20my%20questions%20about%20it.) FAQ What is the most reliable signal of a good software agency? Speaking directly with two or three of their past clients — not the references they provide, but clients you find independently. Ask: did they deliver on time and on budget? Did the code quality hold up after the engagement ended? Would you hire them again? A single honest conversation with a past client is worth more than a polished portfolio and a dozen case studies. How should I structure a contract with a software agency to protect myself? The most important protections are: (1) IP assignment — all code written for you must be explicitly assigned to your company, not merely licensed; (2) source code escrow or regular delivery — you should have access to the code throughout the engagement, not just at the end; (3) milestone-based payments with clear acceptance criteria — never pay 100% upfront; (4) warranty period — a minimum 30–90 day period post-delivery during which the agency fixes bugs at no charge; (5) non-compete or non-solicitation on your team if relevant. What is the difference between a fixed-price and time-and-materials engagement? Fixed-price engagements put the scope risk on the agency. If the work takes longer, they absorb the cost. This sounds good but creates incentives for agencies to: underscope initially to win the deal, then claim scope changes to add cost; and minimise quality to hit the fixed price. Time-and-materials puts the scope risk on you, but creates transparency and aligns incentives toward quality. For anything but well-defined, stable scope work, T&M with a well-structured governance process is usually better. How many agencies should I evaluate before choosing one? Three is the right number. Enough to compare meaningfully, not so many that you're overwhelmed and paralysed. Evaluate all three simultaneously, not sequentially — otherwise your requirements get sharper as you go and the early candidates are judged less fairly. If after three evaluations you're not confident in any of them, the problem is usually your brief, not the agencies. Sharpen what you need first, then re-engage. Should I pay for a discovery phase before committing? Yes, almost always. A paid discovery phase (2–4 weeks, fixed scope) is the best ₹50K–₹1.5L you can spend on a project. It produces a real technical specification, architecture design, technology decisions, and a revised cost estimate based on actual scope clarity. More importantly, it lets you evaluate the agency on real work before committing to the full build. An agency that refuses a structured paid discovery is prioritising speed-to-contract over your project success — that's a red flag. What do agencies hide during the sales process? Three things consistently: (1) who will actually work on your project — the senior partner pitching you is rarely the person building your product; ask to meet the specific engineers assigned before signing; (2) their real timeline track record — ask for projects similar in scope and what the actual delivery date was vs. the estimate; most agencies underestimate by 40–60% to win the deal; (3) their subcontracting practices — some agencies win projects and outsource large portions to cheaper third parties without disclosing it; ask directly 'will any work be done by contractors or third-party teams?' Next step ## Evaluating agencies? Start with a real conversation. Hunchbite is a small, senior team that's transparent about pricing, process, and who will actually build your product. We run a structured discovery before every engagement, quote against milestones, and you own the code from day one — and if we're not the right fit, we'll tell you. [Book a Free Call](https://cal.com/hunchbite/discovery)[How We Work](https://hunchbite.com/process) Trusted by VMAC Industries, TKD Logistics, Astitva Jewellery & more. [See our recent work →](https://hunchbite.com/case-studies) Fixed-price, no hourly billing · No obligation · We tell you upfront if we're not a fit Continue Reading [Rescuing SoftwareHow to End a Contract With Your Software Development AgencyA practical guide to ending a software development contract professionally — protecting your IP, securing your assets, managing the transition, and avoiding the legal and technical traps.9 min read](https://hunchbite.com/guides/how-to-end-agency-contract) [Rescuing Software10 Signs Your Software Agency Isn't Delivering (And What to Do About It)The warning signs that a development agency is costing you more than they're building — and how to evaluate whether to fix the relationship or find someone new.10 min read](https://hunchbite.com/guides/signs-to-switch-software-agency) [All Guides](https://hunchbite.com/guides)