How to Choose a Software Developer: 12 Questions to Ask

Choosing who builds your software is a bigger decision than choosing the software itself. A good partner saves you money for years; a bad one costs you twice — once to build it and again to fix it. Here are the questions we'd ask if we were in your place, including the ones that would rule us out.

Questions about their work

1. Have you built something like this before? Not "can you build it" — everyone says yes. Ask for something similar they've actually delivered.

2. Can I see it working? Screenshots are easy to fake or polish. Ask for a live demo or a video walkthrough of the real thing.

3. Can I speak to a past client? A good developer will happily connect you. Ask that client whether the project was on time and what happened after launch.

Questions about how they'll work with you

4. Who will I actually talk to? With some agencies you speak to a salesperson, and the people building your software never meet you. Find out who makes the decisions.

5. Will I get a written scope? Every screen and feature should be written down before work starts. If it isn't written, it isn't included — for both of you.

6. How will I see progress? Weekly demos of working software beat a long silence followed by a big reveal.

7. What do you recommend I don't build? This is the most revealing question on the list. A good partner will cut features you don't need. One who agrees to everything is building their invoice, not your business.

Questions about money

8. Is the price fixed, and what counts as a change? Agree what happens when you want something new halfway through, before it happens.

9. How are payments split? Milestones tied to delivered work (for example an advance, a payment at a halfway demo, and the balance before launch) protect both sides.

10. What will this cost me every year after launch? Hosting, domain, maintenance and any third-party fees. Get the full picture, not just the build price.

Questions about ownership and the future

11. Who owns the code, domain and hosting? They should be in your name after you pay. If the developer keeps the domain or refuses to hand over the code, you're locked in.

12. What happens if something breaks, or you're not around? Ask about the warranty period, ongoing support, and whether there's documentation another developer could pick up.

Red flags

Walk away, or at least slow down, if you see:

• No written scope, or a vague one-page quote for a complex system.
• Pressure to sign quickly, or "discounts" that expire today.
• A long list of extra features or services you didn't ask for.
• The domain or hosting registered in the developer's name.
• No way to see their previous work running.
• A price far below everyone else's with no explanation of what's left out.

How we answer these

We'd rather you hold us to these questions than take our word for it. Every project we take on comes with a written scope, a fixed price paid in milestones, regular demos, your domain and hosting in your name, and the custom code yours after final payment. If you don't need custom software, we'll tell you. You can read our promise, see every project with a video walkthrough, and ask us anything — even if it never becomes a project.