Free scorecard
Development vendor scorecard
What to ask a software partner before you sign — including the questions that make weak answers obvious.
Use this on every vendor you are considering, including us. Score each line from 1 to 5 while the conversation is still fresh, and keep the sheets — comparing them side by side later is far more useful than comparing your memory of three separate calls.
The most informative questions here are the ones about failure: what happens when an estimate is wrong, when someone leaves, or when you want to leave. Vendors rehearse the happy path. The answers to the awkward questions are where the differences actually show.
Technical depth
- They asked about your constraints before proposing a stack
- They can explain a past technical trade-off and what it cost A partner with no regrets has not shipped enough.
- They pushed back on something in your brief
- You will meet the engineers who do the work, not just a lead
- They were specific about testing, not just "we do QA"
Delivery process
- You can see working software regularly, not only at milestones
- They described what happens when an estimate turns out to be wrong
- Deployment and environments are their responsibility, not an afterthought
- They have a defined handover process, not just a final invoice
- They asked who on your side makes decisions
Communication
- You know exactly who you speak to day to day
- Time zone overlap is enough for real conversation, not just handoffs
- There is a named escalation path when something goes wrong Ask who you call at 9pm during an incident. Hesitation is the answer.
- They write things down — you have already seen evidence of this
Commercial terms
- The quote is itemised, so you can see what each part costs
- You understand precisely what triggers a change order
- Payment is tied to delivered milestones
- You know the cost of ongoing support before you commit
Ownership and exit
The most important section, and the one most often skipped.
- You own all code, designs and documentation outright
- Work happens in your repositories and your cloud accounts
- The stack is mainstream enough for another team to pick up A proprietary framework is a lock-in disguised as an efficiency.
- You could leave in 30 days and still run the software
- They gave a straight answer to the exit question without flinching
0 of 23 scored · 0 /115 points
Want help working through it?
This is the same ground we cover in a Custom Development engagement — except we do the remediation as well as the assessment.
Have a project in mind?
Tell us what you're building. If it ships software, we can help.