--- title: 6 Questions to Ask When Hiring an Application Development Agency description: Hiring an app development agency? These six questions reveal how they handle scope changes, budgets, disagreements and handovers. image: https://weareaffective.com/hubfs/learning-centre-images/6-questions-to-ask-when-hiring-an-application-development-agency.webp --- [Skip to content](https://weareaffective.com/learning-centre/6-questions-to-ask-when-hiring-an-application-development-agency#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # 6 Questions to Ask When Hiring an Application Development Agency Table of Contents Hiring an [application development agency is one](https://weareaffective.com/app-design-agency) of the more consequential decisions a business makes, and it rarely gets the scrutiny it deserves. Most people ask about timelines and pricing. They look at portfolios. They check references. And then they sign a contract with an agency that had no real understanding of the problem before it quoted. We have seen the results of that kind of engagement more than once, and they are not good. The sports club app project is a useful case in point. We warned the client early that adding features without restraint would exhaust the budget before anything reached the store. That warning went unheeded, and the project ended with the entire budget gone and nothing published. Not a slow failure, an abrupt one. > The right questions reveal whether an agency's process is strong enough to protect you when things get difficult. The questions most clients ask during the hiring process do not surface this kind of risk. They are logistical questions dressed up as due diligence. The questions below are different. They are designed to show you how an agency thinks, how it handles pressure, and whether its process is strong enough to protect you when things get difficult. The answers will tell you more than any portfolio page. There are six worth asking. Ask all of them, and listen carefully to how the answers land. ## What does your discovery process look like? Discovery is where the real work begins, and an agency that treats it as optional is telling you something important about how it operates. We consider discovery non-negotiable. Not because it is a line item to defend, but because without it, there is no reliable way to understand what you are actually building or why. We once walked away from a project involving a fairly standard social product because the client wanted to move straight into redesigns. They were not willing to engage with our user-centred discovery phase, and so we declined the work entirely. That is the recognition that [designing without discovery produces answers](https://weareaffective.com/learning-centre/why-most-business-apps-fail-and-how-your-digital-business-can-avoid-the-same-fat) to questions nobody has checked are the right ones. According to [Nielsen Norman Group](https://www.nngroup.com/articles/discoveries-in-industry-revealed/), investing more time in discovery reduces the risk of project failure by 75%. That figure aligns with what we see in practice. Clients who come to us with a fixed budget and a fixed idea often want to skip this stage to save money. Our response is always the same: do the discovery first, and let it define the scope. Skipping it does not reduce cost, it defers it. Ask the agency to walk you through a recent discovery phase, what it included, how long it took, and what it changed about the brief. A vague answer is a warning sign. A good discovery process typically covers [user research, problem definition, technical constraints](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one), and a structured review of the competitive landscape. If an agency cannot describe what theirs produces as a concrete output, be cautious. ## How do you handle scope changes mid-project? Every project changes. Requirements shift, new information arrives, and priorities move. The question is not whether an agency can accommodate change, but whether it has a process for doing so that does not quietly absorb the cost until something breaks. On the alcohol buying and selling platform we worked on, an unexpected technical constraint forced us to embed web elements rather than build a proper API layer. That single decision added approximately 20% uplift in work across the entire project. Because the client wanted to hold the original budget, we had to drop features towards the end to compensate. The work got done, but the trade-offs were real and they required active management from both sides. Scope change becomes genuinely dangerous when nobody flags it as it accumulates. On the grassroots football club app, the [scope kept expanding with each conversation](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-). We pushed consistently to launch a limited feature set first, test the market, and grow from there. The client kept insisting on combining several different apps into one product. The budget kept rising, the complexity kept growing, and the product never reached market. Ask specifically how scope changes are documented and priced. If the answer is informal, that informality will cost you. | Change type | What a good agency does | What a weak process looks like | | --- | --- | --- | | Small feature addition | Logs it, assesses impact on timeline and budget, gets sign-off | Absorbs it silently, raises it at invoice time | | Technical constraint discovered | Presents options and trade-offs clearly before proceeding | Works around it without telling the client | | Client changes direction | Raises cost and timeline implications before starting rework | Begins rework and reconciles later | ## Start your app project the *right* way We deliver the complete blueprint before a line of code is written. User research, psychology-driven design and full technical specifications. You choose who builds it. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## What happens when you disagree with a client's direction? This is the question most clients never think to ask, and it is one of the most revealing. An agency that simply builds what it is told is a production house. Agreeing with everything a client says is a liability. On the concierge app we worked on, the original brief asked us to give residents in-app access to everything, removing the need to speak to the concierge directly. We pushed back. The concierge relationship had genuine value, and reducing it to a transactional information feed would have damaged the product. Instead, we gave each concierge a profile within the app listing personal conversation topics, inviting residents to speak with them about football, motorsport, and other subjects. The intent was to [model and encourage real human connection](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you), not replace it. The client followed our lead, and it shaped the product in a meaningful way. > An agency that simply builds what it is told is a production house. We have also encountered the opposite situation. We worked with a founder who had deep industry experience and very strong pre-existing views about how their product should work. The [research process became a formality](https://weareaffective.com/learning-centre/what-does-good-ux-research-actually-look-like-at-seed-stage). When we showed compelling evidence that a large portion of the target user base did not want certain features, the founder did not move. We eventually walked away. The product launched about a year later, largely unchanged, and by all accounts did not find traction. The reasons the research had flagged were the same reasons it struggled. Ask any agency how they handle this situation. If the answer is that they always defer to the client, that is a problem. ## How do you structure budgets and flag when they're at risk? Budget management is where the gap between a competent agency and an unreliable one becomes most visible. An agency that quotes low to win the work, then adds charges as the project runs, is a pattern we have seen evidence of directly. We have come across competing quotes that were unrealistically low, and upon closer investigation it became clear those agencies had asked very few questions before quoting. The low number was a way to secure the contract, with the expectation that overruns would follow. A trustworthy agency builds its budget from a thorough understanding of the problem. That takes time upfront, and it shows in a quote. A number produced without questions is a number produced without knowledge. Budget risk should be flagged early and often. On the fitness and wellness product we worked on with two co-founders new to app development, we went through a repeated cycle of gaining design sign-off, beginning to build, and then having the clients walk back their approval. We warned them clearly that [budget was being spent on design iterations](https://weareaffective.com/learning-centre/how-much-does-it-cost-to-build-an-event-management-app-like-eventbrite) that would not materially improve the product. Those warnings did not change the pattern. The project never progressed beyond the design and research stage because the budget ran out. We had raised the risk. It had not been acted on. Ask the agency how it flags budget risk during a project, not just how it structures the initial quote. The process for raising problems matters as much as the process for avoiding them. A good agency will show you, at any point, where the budget stands against progress. That transparency should be built into how they report, not something you have to ask for. ## Who will actually be working on our project? Pitches are often delivered by senior people. The work is often done by someone else entirely. This is not universally problematic, but you deserve to know the arrangement before you sign anything. The relevant question is whether the people working on your project have done this kind of work before. [Moldstud](https://moldstud.com/articles/p-the-future-of-cross-platform-development-vs-native-apps) reports that teams with relevant skills deliver projects 40% faster, and while the methodology behind that figure is not detailed, the direction of travel is intuitive. Relevant experience reduces the time spent working things out, and it reduces the likelihood of [technical decisions that create problems later](https://weareaffective.com/learning-centre/5-user-testing-methods-that-will-save-your-app-from-failure). We worked on a wellness genetics product to improve its emotional layer, helping users engage with what was a very data-heavy product for a premium wellness brand. The product had been built in a functional way that did not match the brand feel. When we handed our designs to the development team, a third-party designer created something visually luxurious in between, and the development team then struggled to understand how to implement it on top of their existing codebase. There was considerable back and forth to resolve it. That kind of friction is far less likely when the people involved understand both the design intent and the technical environment they are working in. When you ask this question, follow it up. Ask to speak to the people who will be on your project day to day, not just the people presenting. ## What does a successful handover look like? The end of a project is where a lot of agencies go quiet. The build is done, the invoice is paid, and the relationship winds down. What that often means in practice is that the client receives a [product they do not fully understand](https://weareaffective.com/learning-centre/4-ways-your-app-development-projects-can-improve-your-companys-customer-service), cannot maintain independently, and struggles to hand to another team if the need arises. A proper handover covers several things. The codebase should be documented clearly. The client should understand what they own and where it lives. Any ongoing dependencies, whether hosting, licences, or third-party services, should be laid out plainly. And someone on the client side should be able to brief a new developer without needing to reach back to the agency for basic context. 1. Documentation of the codebase and architecture 2. Access to all repositories, credentials, and hosting environments 3. A list of third-party dependencies and their renewal dates 4. A walkthrough session with the client's internal team or technical lead 5. A defined period of post-launch support with clear terms Ask the agency to describe a handover they delivered recently. Ask what the client received, how long it took, and whether the client needed to come back with questions. An agency that takes handover seriously will have a clear answer. One that treats it as an afterthought will be vague. The handover is also a good proxy for how the agency thinks about its relationship with you. An agency that wants you to remain dependent on them for basic questions is not structured in your interest. ## Conclusion None of these questions are difficult to ask. What makes them useful is that they require an agency to show its thinking rather than its credentials. A polished portfolio does not tell you what happens when a client wants to add ten features with two weeks left in the build. A case study does not show you how an agency behaves when its advice is ignored. The projects we have described here, the sports club app that burned through its entire budget without reaching the store, the fitness product that never left the design stage, the grassroots football app that grew too complex to ship, share a common thread. They were situations where good advice existed and was not followed, often because nobody had asked the right questions at the start to establish what kind of working relationship this would be. A good agency will welcome these questions. It will have clear answers, and those answers will be grounded in specific experience rather than general reassurance. An agency that struggles with them, or deflects, is showing you something worth knowing before any contract is signed. If you are about to hire a development agency and want to think through your brief first, [let's talk about your project](https://weareaffective.com/get-started). ## Frequently Asked Questions Why is discovery so important before starting an app development project? Discovery allows an agency to properly understand what you are building, who it is for, and why it needs to exist before any design or development begins. Without it, teams end up producing solutions to problems that were never properly defined. Research from Nielsen Norman Group suggests that thorough discovery can reduce the risk of project failure by as much as 75%. What happens if I skip the discovery phase to save money? Skipping discovery does not reduce cost, it simply delays it. You are likely to encounter expensive corrections later in the project when problems that should have been identified early begin to surface. In the worst cases, budgets can be exhausted entirely before anything reaches the market. How should a good agency handle scope changes during a project? A reliable agency will have a clear, documented process for evaluating and agreeing scope changes rather than quietly absorbing them until the budget collapses. You should expect transparency around the cost and time implications of any change before it is approved. Agencies that cannot explain this process clearly are worth treating with caution. What should I look for in an application development agency's portfolio? A portfolio tells you what an agency has built, but it does not tell you how they handled pressure, setbacks, or difficult clients. Ask agencies to explain specific challenges they encountered on past projects and how they resolved them. That kind of answer reveals far more about how they will manage your project. Is it a red flag if an agency gives me a quote before fully understanding my project? Yes, it is a significant concern. Quoting before understanding the problem properly usually means the estimate is based on assumptions rather than evidence. When those assumptions turn out to be wrong, which they often do, the consequences are typically felt in cost overruns, missed timelines, or a product that does not do what it was supposed to. How do I know if an agency truly understands my business problem? Ask them to explain your problem back to you in their own words and to describe how their proposed approach addresses it specifically. An agency that can do this clearly and confidently has engaged with your brief properly. One that responds with generalities about their process or their team is likely pattern-matching your project to something familiar rather than thinking about it fresh. What questions should I actually be asking when hiring an app development agency? Most clients focus on timelines, pricing, and portfolios, which are useful but not sufficient. The more revealing questions are about how an agency runs discovery, how it manages scope changes, and how it has handled projects that went wrong. These questions expose how an agency thinks under pressure, which is when its process matters most. Can an agency legitimately decline to work with me, and what does that signal? Yes, and it can actually be a positive sign. An agency that turns down work because a client is unwilling to follow a process that protects the project is demonstrating that it takes quality seriously. It is far better to hear that early than to discover mid-project that corners are being cut because the foundation was never properly laid. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.