How to choose an app agency: 9 questions to ask before you sign

Choosing who builds your app is one of the larger decisions in an early product. Most agencies look similar from the outside: a portfolio, a process diagram, a list of technologies. The differences show up later, in how decisions get made, who does the work and what you own when the project ends.

These are the questions we would ask if we were on the other side of the table. A good agency, including us, should be glad to answer all of them.

1. Who will actually work on my product?

Ask for the names and roles of the people who will design and build it, not only the people in the sales call. Ask how many other projects they work on at the same time. A small senior team that stays on your product usually beats a large team that rotates.

2. How do you decide what goes into the first release?

A strong answer starts with your users and the one thing the first release has to prove, not with a feature list. Be careful with an agency that agrees to build everything you mention. Scoping is part of the work, and a partner who never pushes back is not protecting your budget.

3. When will I see something working?

With AI-assisted development, working versions can arrive much earlier than they used to. Ask when you can click through a real build, on a real phone, and how your feedback flows into the next version. Weeks of static screens before any code is no longer the only option. We wrote about how that changes the order of work in code first, Figma second.

4. How do you use AI, and who checks the result?

Almost every team uses AI now. The useful question is who is responsible for what it produces. Ask how code is reviewed, how it is tested and who decides on architecture, security and data. AI makes building faster. It does not replace judgement about what to build and whether it is safe.

5. Who owns the code, the accounts and the data?

The repository, the app store accounts, the hosting, the domain and the analytics should be in your name from day one, with the agency invited as a collaborator. Ask this before signing. It costs nothing at the start and is painful to untangle later.

6. How do you handle security and data protection?

Ask who can see which data, where it is stored, how access rules are tested and how dependencies are kept up to date. For a product in Germany or the EU, ask how GDPR questions such as data export and deletion are handled. If the answers are vague now, they will not get clearer once real users arrive. Our checklist for taking a prototype to production lists the gaps we see most often.

7. How do design and development work together?

Many problems start at the handover between a design team and a development team. Ask whether the same team is responsible for both, and how changes found during development flow back into the design. One team that owns the product and the software behind it avoids most of those gaps.

8. How are scope and budget managed when things change?

They will change. Ask how new ideas are assessed against the agreed scope and priorities, how often you see progress against the budget and who raises trade-offs. You want to hear about a problem when there are still options, not on the invoice.

9. What happens after launch?

A launch is the start of the real feedback. Ask who fixes bugs, who updates dependencies, how releases to the app stores work and whether the team can stay involved for the next releases. Also ask what a handover to your own developers would look like, even if you never need it.

Signals worth checking yourself

• Live products, not only screenshots. Download an app from their portfolio or open the web product, and see how it feels to use.
• Case studies with context. Look for the problem, the decisions and the result, not just final screens.
• References. Ask to speak to a client whose project was similar in size and stage to yours.
• A first conversation that is about your business. A good partner asks more about your users and goals than about the technology.

The right agency is the one that makes your decisions clearer, not the one that agrees with every idea.

If you are planning an app, our app development page explains how we work, and our page for founders covers taking a first version or an existing prototype to launch.