Questions to ask before signing with an app agency

A sales meeting with an app agency is just as much about what you ask as what they tell you. The right questions quickly reveal whether the agency is a long-term partner or a risk. Here’s a set of questions sorted by theme, with a guide for reading the answers. Bring it to the meeting and listen at least as closely to how something is answered as to what is said.

Team, process, and code quality

Start with how the work actually happens. You’re not buying an off-the-shelf product but a way of working, and it’s worth understanding before you commit.

• Who on the team will actually work on our app, and what are their roles?
• Are they the same people throughout the project, or do they rotate?
• What does your development process look like from idea to launch?
• How often do we get to see working parts of the app along the way?
• How do you ensure code quality: code review, testing, handling of technical debt?
• How is the app tested before release, and what’s tested automatically?
• How is the code documented so someone else can take it over?

Good answers are concrete and ideally come with examples. An agency that describes its process in plain terms and can show how it tests almost certainly has its house in order. Vague answers along the lines of “we’re very agile” with no substance, on the other hand, say nothing.

Ownership, operations, and further development

These are the questions that often get forgotten in the excitement of the build, but that decide what the app is worth to you long term.

• Who owns the code once the project is done, and is that regulated in writing?
• Are the developer accounts with Apple and Google under our name or yours?
• What’s included in maintenance, and what does it cost on an ongoing basis?
• How quickly are critical bugs handled after launch?
• What happens if we want to switch vendors down the line?
• How do you handle updates when the operating systems change?
• What does a setup for further feature development look like?

Here you want to hear that you own the code, that the accounts are under your name, and that maintenance is clearly described. If the agency is vague about ownership or what’s included after launch, it’s worth becoming suspicious, because that’s exactly where lock-in arises.

How to read evasive answers

An evasive answer is rarely random. When an agency gets vague on a concrete question, it often hides a weakness it doesn’t want to put into words. A few common patterns:

• “We’ll figure that out later.” On questions about ownership or maintenance, this often means it hasn’t been thought through. Ask for an answer now.
• “That’s technically complicated to explain.” A good agency can explain its way of working in plain terms. If they can’t, ask who can.
• A big smile instead of an answer. Charm doesn’t substitute for substance. Repeat the question and ask for a concrete example.

The rule of thumb is simple: always ask for an example or a written clarification when an answer feels vague. Vagueness before signing almost never becomes clearer afterward.

A concrete scenario

Say an agency gives great answers about process and design but gets evasive on the question of who owns the code. That’s a signal, not a detail. Follow up by asking for it in writing in the contract. If they refuse, or the answer stays vague, factor that in: an agency unwilling to clarify ownership before signing gives you a weaker position in every future negotiation.

A good way to sharpen the questions is to have a clear set of requirements behind you, so the answers can be measured against something concrete. Read more about our services to see how we approach process and handover, or get in touch and we’ll walk through your situation.