The best way to judge a software builder when you are not technical is to listen to their questions. A builder who hears your idea and immediately says "yes, we can do that, here is a price" has not understood it yet. A builder who asks awkward questions is already protecting your budget.
One of the biggest fears non-technical owners have is paying a lot for the wrong thing. The builders who prevent that are the ones who push back.
Key Takeaways
- Good questions come before the price. A quote with no questions is a guess.
- The questions should be about your business, not about technology.
- A builder who tells you "you do not need that yet" is on your side.
- Use the list below to check any developer or agency in the first call.
Twelve Questions, and What They Reveal
About the problem
1. "What do you do today without this?" They want to know what the software replaces. If they skip this, they are designing in a vacuum.
2. "What happens when it goes wrong today?" The mistakes you make now are the real specification.
3. "Who are all the people who will use it?" Each kind of user adds screens, permissions, and testing. A builder who does not count them cannot price the work.
About what matters
4. "What is the one thing it must do on day one?" This separates version one from the wish list.
5. "What can wait?" A builder who asks this is trying to lower your bill.
6. "How will you know it worked?" More bookings, fewer mistakes, fewer hours. It gives the project a finish line.
About the hard parts
7. "Does money move through it?" Payments bring fees, refunds, failed cards, and security work.
8. "What does it need to connect to?" Your calendar, accounting tool, or website. Integrations are often where timelines slip.
9. "What data can you never lose?" This decides how carefully the storage and backups are built.
About after launch
10. "Who will look after it once it is live?" Software needs updates, fixes, and hosting. A builder who never mentions this is selling a one-off. See what happens after your app is built.
11. "Whose name should the accounts be in?" The right answer is yours. See accounts you should own before a developer builds your app.
12. "What is your budget and deadline, and why that deadline?" The point is to design something that fits your budget. A good builder will tell you if the budget buys a smaller first version rather than pretending it covers everything.
Pushback Is the Sign You Want
The questions are half of it. The other half is what the builder says after hearing your answers. Listen for:
- "You could do this part with a tool you already pay for."
- "I would leave the mobile app out of version one."
- "This one feature is most of the cost. Is it worth it?"
- "Honestly, you might not need a developer yet."
Each of those loses the builder money in the short run. That is why they are trustworthy. Builders paid by the hour have less reason to say them. Builders working to a fixed price, like our software factory, have every reason to, because a bloated scope is a risk they carry.
A Concrete Version
An owner describes a referral app for real estate agents: agents refer clients to each other and get a fee when a deal closes.
Builder A replies the same day: "We can build that. $38,000, ten weeks."
Builder B asks: What do agents do today? (A group chat and a spreadsheet.) Who logs in? (Referring agents, receiving agents, and an admin.) Does money move? (Yes, a referral fee at closing.) How do you know a deal closed? (The receiving agent says so.)
Then B says: the hard part is the fee. Paying agents means handling payouts, tax forms, and state rules about who can be paid a referral fee. B suggests version one tracks referrals and closings, and the fees are paid outside the app by the brokerage for the first months. B's price is lower, and B has already flagged a legal question the owner had not considered.
B asked the right questions. A priced a guess.
The Honest Counterpoint
Too many questions can also be a problem. Some agencies turn every first call into an interrogation to justify a paid discovery phase before they will give any price. A good builder asks enough to give you a ballpark in the first conversation, and saves the detail for the scoping stage. If you cannot get even a rough range after an hour, that is its own warning sign. See what is a discovery phase in software development.
Frequently Asked Questions
What if I do not know the answers?
That is normal and useful. The questions you cannot answer are the ones to think about before you spend money. The honest read asks many of them for free and turns your answers into a short written plan.
Should I prepare answers before the first call?
Yes. A one-page note answering the questions above will get you a more accurate quote from anyone. See how to write a spec for a developer.
What questions should I ask the developer?
Who will do the work, how you will see progress, and how changes are priced. Our guide on how to vet a development agency has a full list.
Is it a red flag if they agree with everything?
Usually. Read red flags when hiring a software developer for others.
The Bottom Line
Judge builders by their questions and their pushback, not by how fast they say yes. If you want to practice the answers first, the honest read walks you through the same questions and gives you a written read you can hand to any developer.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
