Questions to Ask a Software Development Company Before You Sign
Preparing the right questions to ask a software development company before you sign a contract is the surest way to separate polished sales pitches from genuine engineering capability. Once a master services agreement is executed and the initial deposit clears, your commercial leverage shifts dramatically. Partnering with an established software development company ensures that every question around architecture, code ownership, sprint velocity, and post-launch support is answered transparently in writing before development begins.
Many UK CEOs, founders, and IT directors walk into vendor interviews focusing solely on headline price and target launch date. This guide sets out the essential questions to ask before hiring software developers, grouped across technical architecture, delivery governance, team structure, legal protection, and commercial terms, along with the exact answers you should expect from a competent supplier.
Why Pre-Contract Questioning Prevents Mid-Project Disputes
Most disputes between UK businesses and external software agencies stem from unstated assumptions. The client assumes that automated testing, cloud deployment scripts, technical documentation, and 90-day bug warranties are automatically included in the build price. Meanwhile, the vendor may have priced only raw feature coding, intending to bill extra for DevOps setup, user acceptance testing support, and security hardening.
Structured software development vendor questions force both parties to align on operational reality before legal commitments are made. If you have already worked through our guide on the 9 factors to consider when choosing a software development company, you can use the targeted interview questions below during your final shortlist workshops to test how each contender thinks under pressure.
Most disputes between UK businesses and external software agencies stem from unstated assumptions. The client assumes that automated testing, cloud deployment scripts, technical documentation, and 90-day bug warranties are automatically included in the build price. Meanwhile, the vendor may have priced only raw feature coding, intending to bill extra for DevOps setup, user acceptance testing support, and security hardening.
Structured software development vendor questions force both parties to align on operational reality before legal commitments are made. If you have already worked through our guide on the 9 factors to consider when choosing a software development company, you can use the targeted interview questions below during your final shortlist workshops to test how each contender thinks under pressure.
Category 1: Technical Architecture and Engineering Standards
Start by interviewing the vendor’s solution architect or principal engineer. Never allow a commercial account manager to answer technical architecture questions on behalf of the build team.
1. Why are you recommending this specific technology stack for our business?
A credible architect will explain their choice in terms of your performance requirements, five-year hiring availability in the UK market, third-party integration ecosystem, and licensing costs. Beware of agencies that recommend a framework simply because their bench developers happen to know it.
2. How do you build security into the software development lifecycle?
Security cannot be treated as an optional final-week checklist. Industry standards such as the Microsoft Security Development Lifecycle (SDL) emphasise threat modelling during design, static and dynamic code analysis during builds, and strict secret management across environments. Ask the vendor how they prevent OWASP Top 10 vulnerabilities, manage role-based access control, and comply with UK GDPR data protection rules.
3. What does your automated testing and CI/CD pipeline look like?
Ask the technical lead to show you an anonymised continuous integration pipeline from a recent project. You want to see automated unit tests, API integration tests, mandatory peer code reviews on every pull request, and automated deployments to staging environments before any code touches production.
4. How will you design the system to handle peak traffic and future growth?
Whether you are launching an internal logistics portal or require regulated financial software development capable of processing thousands of concurrent transactions, the architecture must scale cleanly. Look for practical answers covering database indexing, caching layers like Redis, asynchronous message queues, and horizontal cloud scaling.
Category 2: Team Composition and Delivery Governance
Software is built by individual engineers, not by company logos. These software developer interview questions for agencies verify who will actually write your code and how they will be managed day to day.
5. Can we interview the exact engineers and delivery manager assigned to our project?
Always insist on meeting the lead developers, quality assurance engineer, and scrum master before signing. Ask about their tenure at the company and their direct experience with similar technical integrations.
6. What happens if a key developer on our account falls ill or leaves the company?
Staff turnover happens in every consultancy. A mature vendor mitigates this through pair programming, modular code documentation, standardized onboarding runbooks, and contractual key-person clauses that guarantee a qualified replacement at the vendor’s expense during the handover period.
7. How do you run sprints, track velocity, and report progress each week?
- Sprint Cadence: Two-week sprints ending with a live demonstration of working software in a staging environment you can test yourself.
- Backlog Transparency: Full client access to Jira, Linear, or Azure DevOps showing every user story, acceptance criterion, and bug ticket.
- Budget Burn Tracking: Weekly burn-up or burn-down charts showing story points completed against budget spent.
- Blocker Escalation: Same-day notification whenever a third-party API dependency or requirement ambiguity threatens the release schedule.
Category 3: Scoping, Pricing, and Change Management
Even the best-planned software projects encounter shifting commercial priorities once real users test early prototypes. Your pre-contract questions must clarify how scope adjustments affect your budget.
8. What is explicitly excluded from your proposal price?
This is one of the most revealing questions to ask before hiring software developers. Ask the vendor to list every item not covered by their quote, such as AWS or Azure hosting fees, third-party SMS or mapping API licences, app store developer accounts, legacy data cleansing, or external penetration testing.
9. How do you handle scope changes or new feature requests mid-build?
Look for a disciplined change-control process. For minor adjustments that do not increase total effort, the team should allow swapping an unstarted user story of equal size from the backlog. For larger additions, the vendor should provide a written impact assessment detailing the exact hours, cost, and timeline adjustment before any extra work begins.
10. How did you calculate the time and cost estimates in your proposal?
Reliable estimates are built bottom-up by breaking modules down into granular user stories and having senior engineers estimate optimistic, realistic, and pessimistic effort bands. If the vendor admits their price is a top-down commercial guess, request a structured scoping phase first.
Category 4: Intellectual Property, Contracts, and Post-Launch Support
Before your legal or procurement team signs the contract, ask these governance questions to ensure your business retains full control over its digital assets.
11. When does intellectual property ownership transfer, and who controls the Git repository?
Ensure the contract states that 100 per cent of bespoke source code, database schemas, custom APIs, and UX design files transfer to your UK company upon payment of each milestone invoice. Additionally, code should be pushed daily to a GitHub, GitLab, or Bitbucket account owned by your organisation.
12. Do you use any proprietary agency frameworks that would lock us in?
Some agencies build client applications on top of closed-source internal libraries. If you ever part ways, your internal developers cannot legally or technically maintain the system. Insist that your software is built using widely supported open-source or standard commercial frameworks.
13. What warranty period and post-launch SLA options do you provide?
Clarify the post-launch defect warranty window (typically 30 to 90 days during which bugs in the agreed specification are fixed free of charge) and review the ongoing service level agreement (SLA) for P1 critical outage response times, OS updates, and security patching.
Summary Table: Strong Answers vs Evasive Responses
Bring this reference matrix into your final vendor interviews to score how transparently each supplier answers your questions.
| Question Topic | Strong, Trustworthy Answer | Evasive or High-Risk Answer |
| Named Build Team | Shares CVs and schedules calls with your actual lead engineers | Claims engineers are only assigned after the deposit is paid |
| Estimation Method | Shows bottom-up user story breakdown with clear assumptions | Provides a single lump-sum figure with no task-level detail |
| Code & Git Custody | Commits daily to client-owned repository; full IP assignment | Holds code on private servers until final project sign-off |
| Testing & QA | Demonstrates automated unit tests, CI/CD, and staging pipelines | Says developers test their own code manually before release |
| Scope Changes | Allows backlog priority swaps; clear written impact assessments | Treats every minor clarification as a chargeable variation order |
| Post-Launch SLA | Includes a 30-to-90-day bug warranty and tiered P1-P4 SLAs | Offers only ad-hoc hourly support when developers are free |
Real Business Example: Pre-Contract Engineering Due Diligence at Barclays
Large UK financial institutions offer a clear blueprint for how rigorous pre-contract questioning prevents operational failures during external software procurement.
- Challenge: When Barclays expanded its digital banking APIs, fraud analytics, and merchant onboarding tools across the UK, working with external technology suppliers required strict compliance with Prudential Regulation Authority (PRA) and FCA operational resilience rules. Ambiguous vendor contracts or unverified engineering standards could expose customer data or cause service outages.
- Solution: Rather than relying on high-level vendor pitch decks, Barclays instituted a multi-stage technical and operational due diligence questionnaire prior to onboarding engineering partners. Vendors had to prove automated DevSecOps capabilities, zero-trust encryption standards, clear dependency management, and verifiable disaster recovery protocols.
- Implementation: Prospective suppliers underwent architecture review boards with Barclays principal engineers, demonstrated live CI/CD security gates, agreed to strict source-code escrow and IP ownership terms, and committed to transparent sprint telemetry before full contract awards.
- Business Outcome: By asking uncompromising technical and contractual questions before signature, Barclays reduced third-party integration defects, maintained strict regulatory compliance across UK payment rails, and ensured external engineering squads delivered at enterprise quality from sprint one.
How to Structure a 90-Minute Final Vendor Interview
To get through these questions efficiently without turning the meeting into an interrogation, structure your final 90-minute vendor workshop into three focused 30-minute blocks.
- Minutes 0 to 30 (Technical & Architecture Review): Have the vendor’s solution architect walk through a proposed high-level system diagram for your project, answering questions 1 through 4 around stack selection, security, testing, and scalability.
- Minutes 30 to 60 (Delivery & Team Walkthrough): Meet the delivery manager and lead engineer to cover questions 5 through 7, inspecting a live Jira board and sample weekly sprint report.
- Minutes 60 to 90 (Commercials, IP & SLA Alignment): Review questions 8 through 13 with the account director, confirming proposal exclusions, change control, IP transfer, and post-launch support terms.
Conclusion: Ask Tough Questions Early for a Smoother Build
Knowing the right questions to ask a software development company transforms vendor selection from a leap of faith into an evidence-based commercial decision. Suppliers who take pride in their engineering craft will welcome detailed questions about their testing pipelines, security standards, and contract terms.
If you are preparing to interview software partners or want clear, direct answers on how we architect and deliver bespoke systems for UK businesses, our senior technical team is ready to talk. Speak with IIH Global today to arrange a discovery workshop with our solution architects.
Share On :