Insight

Picking an agency mostly comes down to trust before you have any real proof. The questions below will not remove all the risk, but they will surface a lot of it before you have signed anything or spent a dollar.

• What would you actually do if you have not solved this exact problem before? Every agency runs into things they have not built before, that is normal. What matters is whether they have a real process for figuring it out, discovery, prototyping, technical testing, or whether they just reach for whatever they already know regardless of fit.
• What technology are you actually using, and does it match what you are being quoted for? We once had a client come to us with a quote from another agency for a native iOS and Android app. When we looked into it, the technology behind the quote was actually a cross-platform framework, not native. The client was being charged native app pricing for a lower-tier build. Ask directly, and ask them to explain the tradeoffs of their recommendation in plain language, not just the name of the technology. If you want a deeper read on this, we cover it in how to evaluate the technology your agency recommends.
• Who will actually be doing the work? Senior staff in the pitch meeting, then a junior or outsourced team on delivery, is a common pattern. Ask who is actually assigned before you sign anything.
• Where is the delivery team actually based? This affects response times, working-hour overlap, potential language barriers, and whether the team is familiar with local technical or regulatory requirements, things like Australian accessibility standards or local payment providers. Off-shoring is not automatically a problem, we have written about when it works, but it is something you should know upfront rather than discover later.
• Who owns the IP? The code, the designs, the content, all of it. Some agencies build in a way that quietly keeps you dependent on them rather than in full ownership of what you paid for.
• Is there anything in the solution that comes with a recurring fee, and who does it go to? A hosting fee is normal. A recurring fee that goes straight to the agency for something you could otherwise own outright is worth asking more about. It might be entirely justified. It might also be a way of keeping you locked in.
• Can they show you references from something a similar size and complexity to your project? A portfolio full of small brochure sites tells you very little about how an agency handles a complex build.
• How fast did the quote come, and how many real questions came before it? A number that arrives before anyone has asked about your actual requirements is not a considered estimate.

None of these questions guarantee a good outcome on their own, but an agency that answers them clearly and without getting defensive is telling you something useful. If you would rather have a second opinion on a quote or proposal before you commit to it, that is exactly the kind of thing a consulting engagement can help with.

Still have questions? Give us a call, book a quick meeting, or send us a message to understand more without any pushy sales tactics.