7 questions to ask before you hire a developer or agency
Hiring someone to build software for your business? Ask these seven questions first. The answers tell you more than any portfolio.
Ali Hassan
· 4 min read
Quick answer
Before you hire a developer or agency, ask: can I see something similar you've built, who will actually do the work, is the price fixed, what happens when something breaks after launch, who owns the code and accounts, how will you keep me updated, and what would you not build for me. Clear, specific answers are a good sign. Vague ones are a warning.
Hiring someone to build software is stressful, especially if you're not technical. Every portfolio looks impressive. Every proposal sounds confident. And you won't really know if you chose well until you're months in and thousands of dollars deep.
I'm on the other side of this conversation all the time, so let me give you the questions I'd ask if I were in your shoes. Yes, including the ones that make people like me a bit uncomfortable.
The answers tell you far more than any portfolio.
1. "Can I see something similar you've built?"
Not "can I see your portfolio". Something similar to what you need. A beautiful app for someone else doesn't prove they can build your booking system.
A good answer: a real, live example you can click through, ideally with a short story of what the client needed and what changed. Bonus points if they're honest that something wasn't a perfect match.
A warning sign: only mockups and design images, or "we can't show that, it's confidential" for everything.
2. "Who will actually do the work?"
With agencies especially, the person who sells to you is often not the person who builds for you. Sometimes the work is passed to someone you'll never speak to.
A good answer: names and roles. "I'll build it, and you'll talk to me directly" or "Sara builds it, I review every change."
A warning sign: vague answers like "our team" with no names, ever.
3. "Is the price fixed? What's included?"
For a well-defined project, you should know the full price before work starts. Then ask what's included, because two quotes for the "same" project can include very different things.
A good answer: a fixed price for a written list of what will be built, plus clear terms for anything extra. Testing, launch help and a short support period should be in there.
A warning sign: an hourly rate with no estimate and no cap. Or a price that's far lower than everyone else's, with no explanation.
4. "What happens when something breaks after launch?"
Something will. Every piece of software has bugs, and the apps it connects to keep changing.
A good answer: a clear period where they'll fix bugs for free, plus an optional, simple support plan after that. And error alerts, so problems are spotted quickly.
A warning sign: "it won't break" or "we'll sort it out then".
5. "Who owns the code, the accounts and the data?"
This is the one people forget, and it causes the most pain later.
A good answer: you do. The code, the hosting accounts, the domain, the app store accounts and all your data belong to your business once you've paid, and it's in writing.
A warning sign: everything runs on their accounts, and leaving them would mean starting again.
6. "How will you keep me updated?"
Silence is where projects go wrong. Weeks pass, you hear nothing, and then there's a "small problem".
A good answer: a regular rhythm, like a short update every week and something you can actually see and click every week or two.
A warning sign: "we'll show you when it's done".
7. "What would you not build for me?"
This one surprises people. But it might be the best question on the list.
A good developer or agency will tell you what you don't need. Maybe a ready-made tool would do the job. Maybe the big feature you're excited about should wait. Maybe the whole project should be smaller.
A good answer: honest pushback, even if it means a smaller project for them.
A warning sign: they agree with everything and suggest adding more.
Freelancer or agency?
Honestly, it matters less than people think. What matters is the answers above.
| Freelancer | Agency | |
|---|---|---|
| Usually costs | Less | More |
| Who you talk to | The person building it | Often a project manager |
| If someone's away | Work may pause | Someone usually covers |
| Range of skills | One person's skills | Design, development and more |
A small studio, like us, sits in between: you talk directly to the person building it, with a bit more cover and range than a solo freelancer.
Thinking about cost? Read what automation really costs. And if your project is an automation, why automation projects fail is worth five minutes before you hire anyone.
You're welcome to ask me every one of these. Book a free 20-minute call, and you'll get straight answers, even if you end up hiring someone else.