Hiring a software development agency is one of the most consequential vendor decisions a startup or growth-stage company can make. A great agency accelerates your roadmap, brings expertise your team lacks, and delivers work that compounds in value over time. A bad agency delivers code that looks finished but breaks in production, disappears when you need support, and leaves you with technical debt that takes years to unwind.
The stakes are high - and the market is crowded with agencies making similar promises. How do you tell them apart before you've signed a contract?
At Agentixly, we've worked with companies that came to us after bad agency experiences - and we've learned from those stories. This guide distills the 12 most important questions to ask any software development agency before hiring them.
Why Agency Selection Matters More Than You Think
Most founders and product leaders underestimate the leverage of agency selection. They focus on cost and speed - "who can deliver this fastest for the least money?" - and miss the questions that actually predict project success.
The cost of a failed agency engagement is rarely just the contract value. It includes:
- Lost time - months of development that produce unusable output
- Opportunity cost - the features you could have shipped, the customers you could have acquired
- Technical debt - code that appears to work but can't be maintained or extended without a rewrite
- Team demoralization - engineering teams that have to clean up agency work often lose confidence in leadership's judgment
- Delayed fundraising or launch - if agency delivery is part of your timeline to a funding milestone or launch, delays can be existential
These costs dwarf the contract value many times over. Spend the time to select the right agency.
The 12 Questions to Ask Every Software Development Agency
Question 1: Can I See Examples of Similar Work?
Portfolios are a starting point, but you need specifics. Ask to see:
- Projects in your technology stack (React, Next.js, Node.js, Python, etc.)
- Projects of similar scope and complexity to yours
- Projects in your industry or with similar user types
Then look beyond the screenshots. Ask: "Can I speak with the client on this project?" References that agencies provide are pre-vetted to be positive - but even coached references reveal useful information about how the agency communicates, handles problems, and takes feedback.
Red flag: An agency that only shows you visual mockups or marketing websites but can't demonstrate complex application development experience.
Question 2: Who Will Actually Work on My Project?
Many agencies pitch you their senior team, then assign your project to junior developers or outsourced subcontractors. This bait-and-switch is one of the most common agency disappointments.
Ask explicitly:
- Who will be the lead developer on my project?
- What is their experience level?
- Will any work be done by subcontractors or offshore teams?
- What is the ratio of senior to junior developers on the team?
- Will the same team work on my project for its duration, or does team composition change?
What to look for: Agencies that can name specific people, describe their experience, and commit to team continuity. Agentixly, for example, introduces clients to their specific team before the contract is signed - no surprises.
Question 3: How Do You Handle Project Management and Communication?
Opaque project management is a leading cause of agency disappointments. You need regular, structured visibility into progress - not weekly "things are going well" status emails.
Ask:
- What project management methodology do you use? (Agile, Kanban, etc.)
- How often will we have synchronous meetings?
- What tools do you use for project management and communication? (Jira, Linear, Slack, etc.)
- How are scope changes handled and priced?
- What does a typical sprint review look like?
What to look for: Agencies that invite you into their project management tools so you have real-time visibility, not just periodic updates.
Question 4: What Does Your Code Review Process Look Like?
Code quality isn't visible in demos - it lives in the code itself. An agency's code review process is a strong signal of their quality standards.
Ask:
- Do you require code reviews for every PR before it's merged?
- Who reviews code - a peer developer, a lead, or is there no formal review?
- Do you use static analysis tools? (ESLint, TypeScript strict mode, SonarQube)
- Do you write tests? What's your target code coverage?
- How do you handle technical debt accumulation?
Red flag: An agency that doesn't have a clear answer about code review or dismisses testing as "we'll add it later." Later rarely comes.
Question 5: How Do You Handle Security?
Security vulnerabilities in software produced by agencies are common because security review is easy to skip when the agency's incentive is to ship features fast.
Ask:
- Do you have a security review step in your development process?
- How do you handle secrets management? (API keys, database credentials)
- Do you use dependency vulnerability scanning?
- What's your approach to preventing OWASP Top 10 vulnerabilities in web applications?
- Have you worked on projects with compliance requirements? (SOC 2, HIPAA, GDPR)
What to look for: Agencies that have specific processes for security, not just general reassurances. At Agentixly, every project includes a security checklist review before deployment.
Question 6: What Is Your Testing Strategy?
A working demo doesn't mean production-ready software. Ask about testing:
- Do you write unit tests? Integration tests? End-to-end tests?
- What is your quality assurance process before delivery?
- Do you have a staging environment where features are tested before production?
- How do you handle regression testing when new features are added?
Red flag: Agencies that say "we test manually." Manual testing alone is insufficient for any software intended to scale.
Question 7: How Do You Handle Knowledge Transfer and Documentation?
When an agency engagement ends, you need to be able to maintain and extend what they built - either in-house or with a new agency. Many agencies make this harder than it should be.
Ask:
- Will you document the architecture and key technical decisions?
- How is code commented and self-documented?
- Will you provide a handoff session for our engineering team?
- Do we own all code, credentials, and infrastructure from day one?
- What format does documentation take?
Red flag: Any hesitation around IP ownership. All code produced for you should be unambiguously owned by you, not the agency.
Question 8: What Is Your DevOps and Deployment Approach?
Modern software development is inseparable from DevOps. Ask:
- Do you set up CI/CD pipelines for automated testing and deployment?
- What cloud infrastructure do you use and recommend?
- Do you use Infrastructure as Code (IaC)? (Terraform, Pulumi)
- How do you handle database migrations?
- What monitoring and alerting do you set up?
What to look for: Agencies that treat infrastructure as a first-class part of their deliverable, not an afterthought.
Question 9: How Do You Estimate Projects and Handle Scope Changes?
Estimates are inherently uncertain, and projects change. How an agency handles estimation and scope changes tells you a lot about the health of the relationship you're entering.
Ask:
- How do you generate estimates? (T-shirt sizing, story points, time-based)
- What is your estimate accuracy history? (Have previous projects come in on budget?)
- How are scope changes handled? (Do they require a new SOW, a change order, or are they just absorbed?)
- Do you use fixed-price or time-and-materials contracts?
Fixed-price vs. T&M: Fixed-price contracts give you cost certainty but incentivize agencies to cut corners to protect their margin. T&M contracts give you flexibility but transfer cost risk to you. Most sophisticated clients use T&M with a budget ceiling and milestone-based check-ins.
Question 10: What Is Your Post-Launch Support Policy?
Software requires ongoing support - bugs found in production, performance issues, security patches. Ask:
- What is your warranty period after launch? (What bugs will you fix for free?)
- Do you offer retainer-based ongoing support? At what rate?
- How quickly do you respond to urgent production issues?
- Will the same team that built it be available for support?
Red flag: Agencies with no formal post-launch support policy. Once you're live, you need reliable support access.
Question 11: What Are Your References' Unedited Opinions?
Pre-approved references are always positive. To get unfiltered feedback, try:
- LinkedIn - search for the agency name and look at former employees and clients. Former employee reviews on Glassdoor are revealing.
- Clutch.co - a review platform for agencies with more verified reviews than most
- Cold outreach - find past clients in the agency's portfolio and reach out directly, without going through the agency
- Ask about failures - when speaking with references, ask "what would you do differently?" and "what was the most difficult moment in the engagement?" Their answers to these questions reveal more than their answers to "would you recommend them?"
Question 12: What Makes You Specifically Right for This Project?
This open-ended question invites the agency to articulate their differentiation. Listen for:
- Specific technical expertise relevant to your project (not generic capability claims)
- Domain experience in your industry
- Honest acknowledgment of what they don't do well
- Questions they ask you in return (good agencies are selective - they should be evaluating fit too)
Red flag: An agency that says yes to everything and doesn't ask about your goals, constraints, or technical requirements. The best agencies ask hard questions because they want to succeed, not just win the contract.
Red Flags That Should End the Conversation
Beyond specific questions, watch for these patterns that indicate an agency relationship will end badly:
Pressure to sign quickly - "this rate is only available if you sign this week." Good agencies don't need artificial urgency.
Reluctance to show code - if an agency won't let you review their code (even with NDA protection for client confidentiality) during a technical evaluation, that's telling.
No questions about your business - an agency that jumps directly to cost and timeline without deeply understanding your goals doesn't have the information to succeed.
Offshore-only teams with no domestic project management - offshore development can work, but only with strong project management oversight. An agency that presents overseas teams without experienced PM leadership is a significant risk.
Can't explain their tech stack choices - if they can't articulate why they chose a particular framework, database, or architecture for past projects, they may be making technology decisions arbitrarily.
Why Clients Choose Agentixly
At Agentixly, we've structured our engagement model around the questions in this guide. When a prospective client walks through these questions with us, here's what they find:
- You meet the specific developers who will work on your project before you sign
- We use Linear for project management with client access from day one
- Every PR requires a peer code review before merging; we use TypeScript strict mode on all new projects
- CI/CD, infrastructure as code, and monitoring are standard deliverables, not add-ons
- All IP belongs to you from day one, documented in our standard contract
- We offer a 30-day warranty period for defects and flexible retainer support contracts
- We take on fewer clients than we could to ensure we have the capacity to do excellent work
We're a team of experienced builders who care deeply about the work we produce - not just the contracts we close. If that sounds like the kind of partnership you're looking for, we'd love to talk.
Making the Final Decision
After you've gathered information through these 12 questions, make your decision based on the totality of the evidence:
- Technical competency - can they actually build what you need?
- Communication and process - will you have the visibility and collaboration you need?
- Cultural fit - do they share your values around quality and honesty?
- References - what do past clients actually say?
- Commercial fairness - is the contract structure fair to both parties?
Trust your instincts. If an agency is evasive, over-promises, or makes you feel like a mark rather than a partner - walk away. The right agency should make you feel more confident and informed, not pressured. The right partner is out there, and the 12 questions above will help you find them.