What Should You Ask in the First Discovery Call?
A 2025 Standish Group study found that 68% of outsourced software projects are either late, over budget, or deliver less than the originally agreed scope. Most of those failures were preventable at the evaluation stage. The first call with an agency tells you more than their website ever will — if you ask the right questions.
1. "Show me a case study that matches my industry." Generic portfolios are easy to build. You want proof they've solved problems similar to yours. If you're building a fintech app, a food delivery case study doesn't prove they can handle PCI compliance or real-time transaction flows.
2. "What's your developer retention rate?" High turnover is the silent project killer. If their senior Flutter developers leave every 8 months, you'll get a mid-project handoff that costs you 3-4 weeks of lost velocity. Good agencies retain developers for 2+ years.
3. "Who will actually work on my project?" Some agencies show their A-team during sales, then assign junior developers once the contract is signed. Ask for names. Ask to interview them. If they hesitate, that tells you something.
4. "Walk me through your code review process." Every PR should go through at least one review before merging. Ask who reviews, what they check for, and how they handle disagreements. No code review process = no quality control.
5. "What happens when a developer leaves mid-project?" This will happen eventually. The answer you want: documented knowledge transfer, a replacement within 1-2 weeks, and overlapping time between the outgoing and incoming developer. The answer you don't want: silence, or "that doesn't happen here."
How Do You Evaluate Their Flutter Code Quality?
According to a 2024 Veracode State of Software Security report, 74% of applications have at least one security flaw, and third-party code is a primary vector. You can't evaluate an agency by their pitch deck. You need to see their code.
Request an anonymized code sample from a recent project. Any serious agency will share one. If they refuse entirely (not just redact client info), that's a red flag. Here's what to look for:
State management pattern: Are they using BLoC, Riverpod, or Provider consistently? Mixing patterns across a single project signals architectural chaos. Pick one pattern and enforce it everywhere — that's what good teams do.
Test coverage: Ask for their test coverage percentage. Below 60% on a production app means bugs ship to users. Look for unit tests on business logic, widget tests on key UI flows, and at least a few integration tests. Zero tests? Walk away.
Linting and null safety: Check if they enforce strict linting rules (analysis_options.yaml should exist and be configured). Full null safety should be enabled — any agency still using legacy nullable code in 2026 hasn't kept up with Flutter's evolution.
Red flags in code: Deprecated packages in pubspec.yaml. Business logic inside UI widgets. No separation between data, domain, and presentation layers. Hardcoded strings instead of localization. Platform channel usage without proper error handling. Any of these suggest the team ships fast but doesn't ship clean.
What Does Their Development Process Reveal?
A 2025 Digital.ai State of Agile report found that teams using CI/CD deploy 208x more frequently than those without it. Process separates professional agencies from freelancer collectives pretending to be agencies.
Sprint length and demo cadence. Two-week Agile sprints with end-of-sprint demos are the baseline — tracked in Jira, Linear, or ClickUp with clear story points and velocity metrics. Anything longer than 3 weeks between demos means you're flying blind. You want to see working software regularly, not status reports.
How they handle scope changes. Scope will change — that's reality. Good agencies have a change request process: document the change, estimate impact, get approval, adjust the sprint. Bad agencies either resist all changes or absorb them silently and miss the deadline.
CI/CD pipeline. Ask: does every merge to main trigger automated tests and a build in GitHub Actions, Codemagic, or Bitrise? Can they deploy to TestFlight and Google Play Console from their pipeline? If developers are building APKs on their local machines and uploading manually, the process is fragile. A proper pipeline also runs Dart analyzer and flutter test on every push.
Hotfix protocol. Production bugs don't wait for sprint planning. Ask how they handle P0 issues. The answer should involve a dedicated process — branch from main, fix, test, deploy, then backport to the development branch. If they don't have a hotfix process, they haven't shipped enough apps to need one.
Want to see our process before you evaluate? Here's exactly how a Geminate engagement works — from discovery call to production deployment.
How Do You Verify Their Track Record?
According to Clutch's 2025 B2B Buying Behavior Survey, 89% of buyers check online reviews before selecting a service provider. But reviews are just one signal. You need multiple verification layers.
Check Clutch and G2 reviews — but read critically. Look for detailed reviews that mention specific project types, not just generic praise. A review saying "great communication" is worth less than one describing how the agency handled a production outage at 2 AM.
Contact their references directly. Ask for 3 references, then call them. The questions that reveal the truth: "What went wrong during the project?" and "Would you hire them again?" If the reference can't name a single challenge, the reference was coached.
Check their Upwork or freelancing platform history. If they have profiles, look at job success rate, long-term contracts, and whether clients came back for repeat work. A 95%+ job success score with 20+ contracts is a strong signal.
Examine their published case studies. Do they include specific metrics — "reduced load time by 40%" or "scaled to 250K daily active users" — or just vague claims like "improved performance"? Specific numbers indicate teams that measure their work. Vague claims indicate teams that don't.
Our portfolio includes apps serving 250K+ daily users. See the case study — with architecture decisions, challenges, and measurable outcomes.
What Contract Terms Protect You?
A 2024 Gartner survey found that 53% of IT outsourcing disputes stem from ambiguous contract terms, not technical failures. The contract protects you when things go sideways — and things will go sideways at some point.
IP ownership must be explicit. The contract should state clearly: all code, designs, and documentation produced during the engagement are your property. Not "upon final payment" — from the moment it's created. If the agency retains any rights to reuse your code, you need to know upfront.
Code escrow for fixed-price projects. If you're paying milestones, the code should be accessible to you throughout — not held hostage until the final payment. A shared Git repository solves this. If the agency insists on delivering code only at project completion, you have zero visibility into progress.
Payment milestones tied to deliverables, not dates. "Pay 30% on signing, 30% at beta, 40% at launch" is better than "pay monthly regardless of progress." Tying payment to working software gives both sides the right incentives.
Developer replacement guarantee. The contract should specify: if a developer leaves or underperforms, the agency provides a replacement within a defined window (typically 1-2 weeks) at no additional cost during the transition.
Right to audit and exit clause. You should be able to review code quality at any point. And the exit clause should have a reasonable notice period (30-60 days) — not a 6-month lock-in with penalties. Your development partner should earn your continued business, not trap you into it.
What Are the Red Flags That Should Make You Walk Away?
Not every agency that looks good on paper delivers good work. After reviewing hundreds of agency engagements across our mobile development practice, these are the patterns that predict failure:
No portfolio or a vague one. "We've built apps for various industries" with no screenshots, no metrics, and no client names (even anonymized) means they either haven't done meaningful work or can't show it. Both are problems.
They won't share code samples. Legitimate agencies anonymize and share code to demonstrate quality. Refusal usually means the code wouldn't survive scrutiny. Some agencies cite NDAs — fair enough, but they should still be able to show personal projects, open-source contributions, or architecture diagrams.
Pricing well below market rate. If senior Flutter developers cost $3,000-7,000/month globally and an agency quotes $1,200, they're either using junior developers or planning to bait-and-switch after signing. Cheap development costs more in the long run.
No process documentation. Ask for their development workflow document. If they don't have one, their process is ad hoc — it changes with every project and every developer. That's a recipe for inconsistency.
The founder can't explain their tech stack choices. Why Flutter over React Native? Why Riverpod over BLoC? Why Firebase over Supabase? Technical leadership should have clear, opinionated answers. "We use whatever the client wants" isn't a technical strategy — it's a sign they don't have one.
Unrealistic delivery promises. If they promise your complex app in 4 weeks when everyone else says 12, they're either lying or planning to cut corners you haven't discussed. Fast is good. Unrealistically fast is a warning sign.
A 30-minute discovery call reveals more than a 30-page proposal. Book one — bring your checklist. We'll answer every question on it.
