Checklist for hiring a software house without regrets
Seven questions to ask before signing a contract with a software house — including what contracts usually hide and what to evaluate beyond the portfolio.
hiringsoftware housechecklistbest practices
Why most hires go wrong
Hiring software development is hard because the client can't evaluate technical quality before delivery — only after. This creates an information imbalance that dishonest vendors exploit.
The 7 questions
- Who will build the project? Ask to meet the person who will write the code. Undisclosed subcontracting is a red flag.
- Is the scope documented in writing? "We understand what you need" is not scope. Require a document listing features, integrations, acceptance criteria, and what's explicitly out of scope.
- What happens if the project is delayed? If there's no penalty for vendor delay, the timeline is an optimistic estimate, not a commitment.
- Does the code belong to you from the start? Require that the repository be yours from the first commit.
- Is there a post-delivery warranty? Require at least 30 days. 90 days is what we consider fair.
- What's the scope change policy? A serious vendor has a clear process: scope changes are documented, quoted separately, and approved before executing.
- Can I speak with a previous client? A portfolio is marketing. A real client conversation is a reference.
Get in touch if you want to talk.