12 Questions to Ask Software Development Company Finalists
Four questions for the first call, four for the proposal and four to settle before you sign.

The questions to ask software development company finalists change with the stage you are at. On the first call, ask about budget fit, the named team, account ownership and AI tool use. When the proposal lands, ask about scope, acceptance criteria, change pricing and third-party code. Before you sign, ask about warranty, exit, pre-existing code and a written copyright assignment, because commissioned software is not automatically yours.
Most buyers spend the first call on portfolio and process, then sign a contract nobody on their side has read for ownership. The order below moves the expensive questions earlier, while you still have three firms competing for the work.
Updated November 2026. Listing figures were read between 28 and 31 October 2026.
Questions to ask software development company finalists, by stage
Ask a contract question on the first call and you get a reassuring sentence; ask it when the draft master services agreement is on the table and you get a clause.
| Stage | Question | Where the answer should be written down |
|---|---|---|
| First call | 1. Where does our budget sit against your minimum and your typical project? | Your call notes, then the proposal price |
| First call | 2. Which two or three people would you name in the contract? | Key personnel clause in the statement of work |
| First call | 3. Whose accounts will the code, cloud and app stores run under? | Onboarding plan and the statement of work |
| First call | 4. How do your engineers use AI coding tools? | A written AI coding tools policy attached to the contract |
| Proposal | 5. What is out of scope, line by line? | Assumptions and exclusions section of the proposal |
| Proposal | 6. What are the acceptance criteria, and who wrote them? | Acceptance schedule in the statement of work |
| Proposal | 7. How is a change request priced and approved? | Change control clause |
| Proposal | 8. Which open-source and paid components will we depend on? | A component and license list delivered with the code |
| Before signing | 9. What does the warranty period cover, and for how long? | Warranty clause in the master services agreement |
| Before signing | 10. If you stop work tomorrow, what do we already hold? | Repository, escrow and termination clauses |
| Before signing | 11. Which of your existing code stays yours, and on what license? | Background IP clause |
| Before signing | 12. Does the contract assign copyright to us in a signed writing? | IP assignment clause |
This list is about what to ask and when. Checking whether an answer is true is a separate job, and the companion piece on questions to ask a software development agency pairs each claim with the document that proves it.
What to ask a software development company on the first call
The first call is for disqualifying, not selecting.
1. Where does our budget sit against your minimum and your typical project?
Budget fit is the question buyers skip out of politeness, and it is the cheapest one to answer, because most firms publish a floor. As of October 2026, the 2,247 firms listed on Edverise under software development services all state a minimum project size. Only 590 of them, 26.3%, put that floor at $10,000 or more, and just 82, or 3.6%, set it at $50,000 or more.
The spread depends on what you are buying, so compare against the category that matches your build rather than the general one.
| Category on Edverise | Firms listed | State a minimum of $10,000 or more | State a minimum of $50,000 or more |
|---|---|---|---|
| Software development services | 2,247 | 26.3% | 3.6% |
| ERP & CRM development | 2,371 | 28.3% | 4.7% |
| Low-code MVP development | 410 | 20.7% | 2.4% |
| Code review & technical audits | 491 | 46.4% | 9.8% |
A low-code MVP development shop is the least likely of the four to turn a small first release away, while ERP & CRM development firms skew a little higher than general software houses. And independent code reviewers set higher floors than the builders they review: nearly half state $10,000 or more. Budget for that if you plan an outside read of the finished code.
A stated minimum is a filter, not a price. So ask the second half of the question too: what did your last three projects of our kind cost, and how long did they run? For the full spread of floors across categories, the analysis of agency minimum project size covers every band.
2. Which two or three people would you name in the contract?
Ask for roles first, names second: a short list of positions the firm will commit to keeping on your project, written into the statement of work as key personnel. The federal 18F guide to buying development services advises asking vendors to specify two or three positions at most, because the developer market is fluid and a longer list just produces substitution notices.
Name the technical lead, the delivery lead and, for specialist work, the one engineer whose skill you are paying for. A firm that will name nobody before signing is telling you the bench decides who shows up.
3. Whose accounts will the code, cloud and app stores run under?
This is an ownership question disguised as an onboarding one. The repository, the cloud subscription, the domain and the app store listings should be opened in your company's name, with the firm invited in as a user.
The reason is mechanical. On Apple's platform, the membership Account Holder initiates an app transfer and the receiving Account Holder accepts it, so an app published under an agency's account can only move with the agency's cooperation. One CTO described the result on the Apple Developer Forums in January 2025: the agency that built the company's iOS app stopped operating in mid-2024, cancelled its developer enrollment, and the app disappeared from the App Store with emails and calls unanswered.
4. How do your engineers use AI coding tools?
Ask for the written policy: which tools are approved, whether your code and data may be sent to them, and how generated code is reviewed before merging.
There is an ownership angle most question lists miss. The U.S. Copyright Office concluded in its January 2025 report on copyrightability that AI output is protected only where a human author has determined sufficient expressive elements, and that the mere provision of prompts does not qualify. Using AI as an assistive tool does not bar protection for the human work around it. The practical reading: code that engineers direct, edit and arrange is on firmer ground than code accepted unread, so a policy that requires human review protects your asset as well as your quality.
Questions to ask about a software development proposal
A proposal is where vague answers from the call either harden into terms or quietly disappear. Read it for what is missing.
5. What is out of scope, line by line?
Every proposal lists what is included. The useful section is the one that lists exclusions and assumptions: data migration, content entry, third-party license fees, hosting, accessibility work, load testing, app store submission. A one-paragraph exclusions section means you will meet the rest later as change requests.
Proposals priced far apart usually differ here rather than in day rates. The guide to comparing software development quotes shows how to line up three proposals so the exclusions sit side by side.
6. What are the acceptance criteria, and who wrote them?
Acceptance criteria are the tests a delivery must pass before you approve the invoice. Ask who drafted them. 18F's vendor management guidance warns that if you allow the vendor to define its own measures of success, you give up one of your strongest tools.
The same guidance shows what objective criteria look like. Its quality indicators include a minimum of 90% automated test coverage, zero errors from both automated and manual accessibility testing, and code free of medium- and high-level security vulnerabilities. Your thresholds may differ, but each criterion should be a number, not a word such as "stable".
7. How is a change request priced and approved?
Ask who can raise a change, how it is estimated and who on your side signs it off. The pricing model sets the stakes. Under a fixed price, every change is a negotiation; under time and materials, the risk is a budget that drifts without anyone deciding to spend it.
Government buyers cap that drift by rule: 18F notes that every time-and-materials contract requires a dollar ceiling. A private contract has no such default, so write one in. The trade-offs between models are set out in fixed price, time and material, and outcome-based contracts.
8. Which open-source and paid components will we depend on?
Black Duck's 2026 Open Source Security and Risk Analysis found open source in 98% of the 947 commercial codebases it audited, and license conflicts in 68% of them, up from 56% the year before.
A license conflict can restrict how you distribute or sell the product, so ask the firm how it tracks licenses and require a component list, with each license named, as a deliverable at every release. Paid components belong on it too, with renewal costs.
Questions to ask before signing a software development contract
These four are often left to a lawyer who has never seen the project. You need not draft the clauses, but know what each must say before the redline starts.
9. What does the warranty period cover, and for how long?
A warranty period is the window after acceptance in which the firm fixes defects at its own cost. Ask three things: how long it runs, what counts as a defect rather than a new feature, and how quickly a reported defect must be fixed. Measure defects against the acceptance criteria from question six.
Warranty is not maintenance. Security patches, operating system updates and dependency upgrades are ongoing work, and the breakdown of mobile app maintenance cost per year shows what that work involves once launch is over.
10. If you stop work tomorrow, what do we already hold?
Ask it plainly, then check the contract against the answer. In 18F's model, code is delivered to a repository the buyer owns throughout the project, so that even if the work stops, the buyer still owns the software delivered up to that point. That is the standard to hold a private firm to: commits pushed to your repository as they are written, not handed over at the end.
The termination clause should let you end the engagement on notice, pay for work accepted to date and receive everything else: credentials, infrastructure definitions, design files and documentation. Source code escrow, where a third party holds a copy for release if the firm fails, matters mainly when you license the firm's own product; if the repository is already yours, it adds little.
11. Which of your existing code stays yours, and on what license?
Most firms reuse their own libraries and starter kits, which usually helps your budget. The contract should list that background IP, leave it with the firm, and grant you a perpetual, royalty-free license to use and modify it as part of your product. Without that license, a component the firm owns can become the reason you cannot move the product to another team.
12. Does the contract assign copyright to us in a signed writing?
This is the question that decides who owns the code a software development company writes for you, and the answer is not "the client, obviously". Under 17 U.S.C. §101, a commissioned work is a work made for hire only if it falls into one of nine listed uses, among them a contribution to a collective work, a translation, a compilation and an atlas, and only if both parties agree in a signed written instrument. Software built for a client sits outside that list, so a contract that only says the code is "work made for hire" may leave copyright with the firm.
The fix is an express assignment. Section 204(a) says a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights or an authorized agent. The clause to look for does both jobs: it describes the deliverables as work made for hire and, to the extent they are not, assigns all rights in them to you, with the firm promising to sign whatever further documents are needed. It should cover all work product created under the agreement, not a named list of deliverables, and it should bind subcontractors. This is US law; have counsel confirm the assignment works where the firm is based.
Frequently asked questions
What questions should I ask a software development company?
Ask a software development company twelve questions in three rounds. On the first call, cover budget fit, named key personnel, account ownership and AI tool use. At proposal stage, cover exclusions, acceptance criteria, change pricing and third-party components. Before signing, cover warranty, exit rights, background IP and a written copyright assignment.
Is commissioned software a work made for hire?
Commissioned software is usually not a work made for hire under US law. Section 101 of the Copyright Act limits commissioned works made for hire to nine listed uses, such as translations, compilations and atlases, and software built for a client sits outside them. Ownership passes to the client only through an assignment that is in writing and signed by the firm, as Section 204(a) requires.
How do I know who will actually work on my project?
You know who will work on your project only once their roles are named in the statement of work as key personnel. Ask the firm to commit two or three positions, such as the technical lead and delivery lead, and to give written notice before replacing anyone named. A promise made on a sales call does not bind the firm; a key personnel clause does.
What should a software development proposal include?
A software development proposal should include the scope, a written list of exclusions and assumptions, acceptance criteria you can measure, the pricing model and how change requests are priced, the named team, and a list of the open-source and paid components the product will depend on.
What questions should I ask an offshore software development company?
Ask an offshore software development company the same twelve questions, with extra weight on the last four. Confirm that the copyright assignment is enforceable where the firm is based, that the repository and cloud accounts sit in your company's name from the first day, and how many hours of each working day overlap with yours for reviews and decisions.
Take the questions into your next call
Put the first four questions on the agenda for each finalist's next call, and send questions five to eight with your request for proposal so the answers arrive in writing. Hold the last four for the draft contract, and do not sign until question twelve has a clause number. If you are still building the shortlist, start with the firms listed under software development services on Edverise, filter by stated minimum before you book a single call.