Choosing the right partner starts with asking the right questions. Before signing with any vendor, these 22 questions to ask a software development company will help you evaluate far more than technical capability alone. From delivery process and pricing transparency to IP ownership, QA standards, and post-launch support, the answers you get will reveal how that company actually operates when projects become complex. Whether you’re building an MVP, scaling an existing product, or outsourcing development for the first time, this guide is designed to help you reduce risk, compare vendors objectively, and avoid expensive mistakes that only surface after development begins.
TL;DR — 60-Second Summary
-
- Most software projects fail not because of bad code — but because the wrong company was chosen.
- The questions in this guide cover: team structure, process & delivery, pricing models, IP ownership, QA, post-launch support, and culture fit.
- Each question includes what a good answer looks like, so you can score vendors objectively.
- Jump to the Quick-Reference Checklist at the end to print and use in discovery calls.
Why These Questions Matter More Than Price
Price is what you pay. Poor vendor selection is what you regret for 18 months.
According to the Standish Group’s CHAOS Report, only around 31% of software projects are considered fully successful. The report consistently identifies non-technical factors — including unclear requirements, poor stakeholder communication, unrealistic expectations, and lack of user involvement — among the leading causes of project failure.
Asking the right questions before you commit does three things:
-
- It reveals how a company actually works, not how it sells.
- It surfaces risk early — before money changes hands.
- It signals to the vendor that you’re a serious, informed buyer.
This guide is structured around six categories of questions — matching the six stages where projects typically break down.
Category 1: Team & Expertise (Questions 1–5)
These questions tell you whether the team that pitches you will actually build your product.
Q1. Can you show me case studies or past work in our industry?
What you’re really asking: Have they solved problems like mine before?
What a strong answer looks like: Specific examples with measurable outcomes — ‘We reduced onboarding time by 40% for a UK fintech client’ — not generic portfolio links.
Q2. Who specifically will work on our project — and what are their seniority levels?
Many agencies win business with senior staff and deliver with juniors. Ask explicitly.
What a strong answer looks like: Named individuals (or at minimum, defined roles), clear seniority breakdown (e.g. 1 senior, 2 mid-level engineers, 1 QA), and confirmation that this team won’t be reassigned mid-project without notice.
Q3. Will any work be subcontracted or outsourced to third parties?
This directly affects quality control, IP risk, and accountability. Some companies subcontract without disclosure.
What a strong answer looks like: A clear yes or no, and if yes — who those parties are, whether they’re under NDA, and how quality is managed across the chain.
Q4. What is your team’s time zone, and how does that affect delivery?
For UK businesses, a 5–8 hour offset (India, Eastern Europe) is manageable. A 12+ hour gap requires formal async processes.
What a strong answer looks like: Specific overlap hours, tools used for async handoffs, and a named client success contact in your time zone.
Related: Staff Augmentation vs Hiring Developers vs Agencies — which model suits your team?
Q5. How do you handle team scaling or unexpected attrition mid-project?
Developer turnover is normal. What matters is the company’s response plan.
What a strong answer looks like: A documented onboarding process for replacement developers, knowledge transfer protocols, and an SLA for how quickly gaps are filled.
Category 2: Process & Project Management (Questions 6–10)
Q6. What development methodology do you use, and how does it work in practice?
Agile is almost universally claimed. What matters is how it’s implemented, not the label.
What a strong answer looks like: Sprint length, how sprint reviews work, how backlog prioritisation happens, and what role you (the client) play in each cycle.
Q7. What project management tools will I have access to?
You should have real-time visibility into progress — not just weekly email updates.
What a strong answer looks like: Direct access to Jira, ClickUp, Linear, or equivalent. You should be able to see ticket status, blockers, and sprint velocity without asking.
Related: Best Tools for Project Planning & Discovery Phase
Q8. How do you handle requirement changes mid-project?
Changes will happen. The question is whether there’s a structured process or just friction.
What a strong answer looks like: A formal change request process that documents scope impact, timeline adjustment, and cost implications before work begins. No surprises.
Q9. How do you run the discovery phase, and is it separate from development?
A company that skips discovery and jumps straight to coding almost always underestimates the project. Discovery is where requirements are validated, risks identified, and architecture planned.
What a strong answer looks like: A defined discovery phase (typically 2–4 weeks) with clear deliverables: technical spec, wireframes, risk register, and revised estimate.
Q10. What does your typical project reporting structure look like?
Who reports to you, how often, and in what format? You want to understand the escalation path when something goes wrong.
What a strong answer looks like: Named project manager, scheduled sprint demos (not just email), and a clear escalation route above the PM level.
Related: Managing Scope Creep & Goal Shifts in Software Development
Category 3: Pricing, Contracts & Transparency (Questions 11–14)
Q11. How was this estimate calculated, and what does it include?
Don’t just ask for a quote — ask how they got there. A credible estimate reflects real planning; a low quote often reflects wishful thinking.
What a strong answer looks like: A breakdown by phase and deliverable, clear assumptions documented, and explicit exclusions listed. If they can’t explain how they got to the number, the number is likely wrong.
Related: Software Development Cost: UK Pricing Guide | Hidden Costs in Software Projects
Q12. What pricing model do you use — fixed price, time-and-materials, or retainer?
What a strong answer looks like: A recommended model with a clear rationale based on your project type. Be wary of companies that only offer one model regardless of context.
Related: Software Development Outsourcing: Pricing Models Explained
Q13. What are the payment milestones and what triggers each one?
Milestone-based payments protect both parties. Upfront-heavy structures favour the vendor; output-linked milestones favour the client.
What a strong answer looks like: Payments tied to specific, verifiable deliverables — working sprint demos, passing test suites, or accepted UAT — not arbitrary calendar dates.
Q14. What are the contract exit clauses if the relationship isn’t working?
This question separates confident partners from companies that rely on lock-in. A healthy vendor welcomes this question.
What a strong answer looks like: A clear termination clause (typically 30 days’ notice), handover obligations, and what happens to in-progress work.
Category 4: IP, Security & Legal (Questions 15–17)
Why this category is non-negotiable:
IP disputes are one of the most common and expensive post-project problems. If your contract doesn’t explicitly assign ownership, the developer may retain rights over code they wrote — even code you paid for. This has happened to UK startups.
Q15. Who owns the code, designs, and data after the project ends?
Full IP assignment should be written into the contract. Not implied. Not verbal. Written.
What a strong answer looks like: ‘All IP transfers to you upon final payment’ — confirmed in the contract. Ask to see the relevant clause before you sign.
Related: How to Protect Your IP with a Dev Agency
Q16. What security practices do you follow during development?
GDPR, OWASP Top 10, secure code reviews, penetration testing — these shouldn’t be afterthoughts or expensive add-ons.
What a strong answer looks like: OWASP-aligned development standards, dependency scanning baked into the CI/CD pipeline, and at minimum a penetration test before launch.
Q17. Are your developers under NDA, and do you have data handling policies?
Especially important if your project involves customer data, healthcare records, or financial information.
What a strong answer looks like: All staff under standard NDA, documented data handling procedures, and GDPR compliance for any UK/EU data processing.
Category 5: Quality Assurance (Questions 18–20)
Q18. What does your QA process look like, and is testing a separate team?
Development and QA should be separated responsibilities. When the same person writes and tests code, bugs get missed.
What a strong answer looks like: Dedicated QA engineers, a mix of manual and automated testing, and clear test coverage requirements per sprint.
Related: QA Automation with Playwright
Q19. How do you handle performance and security testing before launch?
Load testing, vulnerability scanning, and browser/device testing should all happen before go-live — not as a response to a live incident.
What a strong answer looks like: A pre-launch checklist that includes load testing thresholds, OWASP security scan results, and cross-browser/device test reports.
Related: Performance Testing: Tools & Practices for App Resilience
Q20. What is your definition of ‘done’ for a feature or sprint?
‘Done’ should mean: coded, tested, reviewed, and accepted — not just ‘the code is written.’
What a strong answer looks like: A written Definition of Done (DoD) that includes unit tests passing, code review approved, QA sign-off, and staged deployment verified.
Category 6: Post-Launch & Long-Term Partnership (Questions 21–22)
Q21. What does post-launch support look like, and is it included in the project cost?
Most defects surface in the first 30–90 days after launch. You need to know who handles them and how quickly.
What a strong answer looks like: A defined warranty period (typically 30–90 days) for fixing bugs at no extra cost, followed by a clear support retainer option with defined response SLAs.
Q22. How do you approach technical documentation and knowledge transfer?
If you ever switch vendors or hire an in-house team, you need to own the knowledge, not just the code.
What a strong answer looks like: Architecture decision records, API documentation, deployment runbooks, and a structured handover session at project end. Not a ZIP file of source code.
How to Score Vendors: A Simple Framework
Use this scoring framework across multiple vendors after your discovery calls.
Score each vendor 1–5 per question. Multiply by category weight. Any vendor scoring below 60/100 carries significant delivery risk.
Quick-Reference Checklist: 22 Questions to Ask
8 Red Flags That Should Stop You Signing
Why These Questions Are Easy to Answer — If You’re Working With the Right Partner
At Emvigo, we welcome every question in this list. Our process is built to give you full visibility: named team members before day one, IP assigned on project completion, structured discovery, milestone-linked payments, and dedicated post-launch support.
We work with UK startups, scale-ups, and enterprises across healthcare, fintech, eCommerce, and SaaS.
One example: when a UK asset management firm needed to reduce a 96-hour manual reporting process, Emvigo delivered a solution that cut processing time to 2 hours — a 98% reduction. The platform went on to generate a 40% revenue increase and helped secure £37.5M in investment funding, with 200,000 installations to date. Read the full case study →
-
- UK-based project management with global delivery capability
- Flexible engagement models: fixed-price MVP, T&M, or dedicated team
- Proven experience in AI tools, mobile apps, eCommerce, and enterprise systems
- Transparent pricing: no hidden costs, no lock-in, full IP transfer
- ISO 9001:2015 certified for quality management
See how we work: MVP in 4 Weeks | Smarter Software Development: The Gap Analysis Impact | Software Development Outsourcing Guide 2026
Frequently Asked Questions
How many questions should I actually ask in a vendor call?
Focus on the highest-risk areas for your project. For first calls, use the six category questions (Q1, Q2, Q6, Q11, Q15, Q18). Go deeper in a second call once you’ve shortlisted two or three vendors.
What’s the single most important question to ask a software development company?
If you could only ask one: ‘Who specifically will work on our project, and what are their seniority levels?’ (Q2). The answer reveals how the company operates far more than any sales presentation.
What’s the difference between these questions and the ones to ask before outsourcing?
Questions before outsourcing focus on whether to outsource and which model to use (see our dedicated guide). The questions here assume you’ve decided to work with a development company and focus on evaluating specific vendors.
Related: 10 Questions to Ask Before Outsourcing Software
Should I ask for a technical interview with the lead developer?
Yes, for any engagement over £20,000 or three months. Ask the project manager to arrange a 30-minute technical Q&A with the engineer who will be leading your project. Any hesitation to arrange this is itself a red flag.
How do I evaluate a vendor if I’m not technical?
Focus on process, communication, and transparency rather than technical depth. Ask for references and call them. A vendor that has happy, repeat clients is usually a better signal than impressive tech jargon.
What happens if I don’t ask about IP upfront?
If IP ownership isn’t explicitly addressed in the contract before work begins, you may face a situation where the developer retains rights over code they wrote. This can limit your ability to modify, sell, or migrate your product. Always get it in writing before you start.
Why are questions important before hiring a software development company?
Asking the right questions helps uncover risks related to delivery process, pricing, communication, IP ownership, and support. It allows businesses to compare vendors objectively and avoid costly project failures caused by poor alignment or unclear expectations.
The Bottom Line
A software development company that’s the right fit will welcome every question on this list. They’ll answer clearly, in writing, without defensiveness. The companies that deflect, generalise, or rush you past these questions are showing you exactly how they’ll behave when the project gets difficult.
Take the time now. It costs a 30-minute call. Skipping it can cost months.
