Every agency demo looks good. Every proposal promises quality, communication, and agile something. The real differences between a reliable partner and an expensive mistake only show up if you ask for them, so here is what to ask. These questions apply to us too. We would rather be examined than assumed.
1. Who exactly will build my project?
The people in the sales meeting are often not the people who write the code. Ask to meet the engineers who will actually work on your project, and ask how long they have been with the agency. High turnover mid-project is one of the quiet killers of software quality, because context leaves with people.
2. Show me something still running after two years
Anyone can show a portfolio of launches. The question that separates agencies is what their systems look like years later, under real load, after real change requests. Ask for one example and permission to speak to that client. Our case studies carry the numbers (uptime, cost, processing times) precisely because launch-day screenshots prove nothing.
3. What happens if we stop at month three?
Projects pause: funding shifts, priorities change, people leave. A fair arrangement means you own the code and can walk away at any paid milestone with something usable. Ask where the repository lives, whose name is on the cloud accounts, and what documentation exists for a new team to pick up. If the answers are vague, the arrangement is designed to keep you, not serve you.
4. What will it cost to run after launch?
A quote that ends at launch is half a quote. Hosting, monitoring, security updates, and fixes are part of the true price, and we have written a full breakdown of what custom software actually costs in Malaysia. Ask every agency whether they maintain what they build. We maintain every system we deliver, and we treat an agency that refuses maintenance on its own work as a signal worth reading.
5. How do you deliver on time?
Not "do you," but "how." On-time delivery is a process property, not a personality trait. Listen for specifics: a discovery phase before the quote is fixed, short sprints with demos you attend, a change process that prices additions instead of absorbing them silently. These mechanics are why our own projects ship on time. Ask any agency to describe theirs.
6. What would make you tell me not to build this?
This is the question most buyers never ask, and the most revealing one. An agency with no answer will build anything you can pay for, including things that should not exist. Good partners can describe projects they turned down or redirected: the blockchain that should have been a database, the custom build that should have been an off-the-shelf product. Judgment is the expensive part of software. Verify the agency has some.
Red flags worth walking away from
- A fixed price quoted in the first meeting, before anyone asked what the system decides
- No named engineers, only "our team"
- Code ownership deferred until final payment
- No answer for post-launch support, or support priced only after you are committed
- Every technology you mention is one they "specialize in"
Make the comparison fair
Finally, the step that improves every outcome: write a one-page brief (who uses the system, what they do in it, what it connects to, what happens after launch) and send the same page to every agency you approach. Identical inputs make the quotes comparable, and the clarifying questions each agency asks will tell you more about them than their proposals will.
If Addvaluez ends up on your shortlist, send us the brief, and bring every question on this page.