TL;DR. Every agency website says the same three things — senior team, proven process, quality first — so the words are worthless as a filter. What works is verification: shipped apps you can install, engineering thinking you can read, prices published before the sales call, and references you actually phone. This post is the checklist we would use if we were the ones buying, and yes — we are a Flutter agency, so at the end we run it on ourselves and show you where to check our claims.

Why the usual research path misleads

Search "best Flutter development company" and you will find listicles and directories. Both are useful and both need decoding. Many listicles are pay-to-play or affiliate-driven — inclusion is marketing, not merit. Directories like Clutch are more useful because verified client reviews are hard to fake at volume, but read the reviews, not the badges: one detailed review describing a real project tells you more than a dozen five-star ratings with two sentences each.

Neither replaces the twenty minutes of direct verification below. Every criterion here is checkable from your desk before you ever book a call.

Six things to verify, not ask about

1. Shipped Flutter apps you can hold

Not screenshots — store listings. Open the portfolio, find the App Store and Google Play links, install two apps, and use them for ten minutes. Scroll fast, rotate, go offline, come back. A team that ships polished production Flutter cannot hide it, and a team that has not cannot fake it. Be suspicious of a portfolio that is all mockups and no links; be understanding about NDA work, but expect at least some named, installable proof.

2. Engineering thinking in public

An agency that has genuinely wrestled a real-time feed or a payment flow can write three concrete pages about it; one that has not writes "we deliver scalable innovative solutions." Read the blog. Look for specifics: named trade-offs, numbers, things that went wrong. Open-source is the same signal, stronger — packages on pub.dev with real users mean the team's code survives public scrutiny, and you can read it yourself before you pay for more of it.

3. Who will actually build your app

The people on the sales call and the people in your repo are often different people. Ask for names and profiles of the engineers assigned to your project, check that team pages show real humans with verifiable histories, and treat a refusal as an answer. Seniority matters more in Flutter than the pool's youth suggests: the framework is easy to start and unforgiving at production edges — rebuild scoping, platform channels, store review — where a senior has scars and a junior has tutorials.

4. Prices and timelines they will commit to in writing

An agency that publishes ranges has decided its numbers can survive comparison; one that will only quote after a discovery call is keeping room to size the quote to the client. Same logic on the calendar: "How long is an ?" deserves a concrete range with conditions, not "it depends." It always depends — professionals tell you on what, and their conditions teach you how they think.

5. What a week of working with them looks like

Demos on a cadence, a channel where you see progress daily, and honest reporting when something slips — ask each reference one question above all: "When something went wrong, how did you find out?" If the client discovered problems themselves, walk away. If the agency raised the flag first with a plan attached, that is the vendor you want, and no proposal deck reveals it.

6. What happens after launch

Shipping is the midpoint of an app's cost, not the end — maintenance has its own economics. Verify there is a real post-launch offering: monitoring, store-policy updates, a named response path. And check code ownership in the draft contract, not the conversation: your repository from day one, your stores, your accounts. Any friction on this point is a rehearsal for a hostage negotiation.

Five red flags that end the conversation

  1. Certifications as the sales pitch. "HIPAA-certified developers" is a tell — HIPAA has no such certification, and an agency that leads with badges is betting you do not know that. Compliance-literate teams describe how they build instead.
  2. Yes to everything. No pushback on scope, timeline, or feasibility during the sales process means the pushback arrives after the deposit, as change orders.
  3. A quote without questions. Anyone who prices your app without interrogating scope, integrations, and the invisible 40% — auth flows, account deletion, store submission — is quoting a number designed to start a relationship, not finish a project.
  4. No engineers in the room. If you cannot get a technical person into a pre-sales conversation, you are buying from a sales layer that will translate your product through a ticket queue.
  5. A portfolio without dates or store links. Undated work can be a decade old; unlinkable work can be anyone's.

Ten questions for the shortlist call

  1. Which of your shipped Flutter apps is most similar to ours — and can we speak to that client?
  2. Who exactly will work on our project, and what else are they on?
  3. What would you cut from our scope, and why?
  4. What is your estimate range for our MVP, and what moves it up or down?
  5. How do you handle a payment flow / real-time feature / offline sync like ours? (Pick your hardest feature; listen for specifics.)
  6. What does a normal week look like for us — demos, channels, reporting?
  7. Tell us about a project that went wrong and what you did.
  8. What do you not do, and where would you send us instead?
  9. What does post-launch support cost and cover?
  10. When can we see the repository, and whose name is on it? (Right answer: yours, from day one.)

Question 8 is the quiet killer. A shop with no honest answer to "what don't you do" has never thought about what it is actually good at.

Comparing quotes without fooling yourself

Quotes for "the same app" legitimately vary 3–5× — mostly because they are not for the same app. Before comparing numbers, normalize the scope: which features, which platforms, whose backend, whose design, what testing, what store-submission work, what post-launch period. A structured breakdown of what actually drives Flutter cost makes that normalization tractable. Then discard the cheapest bid unless you can explain why it is cheap — the usual answers are juniors, offshore leverage that vanishes in communication overhead, or scope that quietly excludes the invisible 40%. Cheap engineering that must be rebuilt is the most expensive kind; paying twice is the standard outcome of buying on price alone.

Geography, while we are here: nearshore and offshore teams can be excellent — the variable that predicts outcomes is not the map, it is timezone overlap with your working day and the seniority of the people actually committing code. Insist on three-plus hours of overlap and named seniors, and the location question mostly answers itself.

The same checklist, run on us

We are Nerdy Production, a Flutter agency, and it would be strange to publish a vetting guide and exempt ourselves. So, line by line: our shipped work is in the portfolio with store links where NDAs allow — install ExtraETF or Jepta and judge the scroll performance yourself. The engineering thinking is on this blog and in open-source packages on pub.dev you can read tonight. The people are on the team page, and the person on your call is an engineer, usually the one who will architect your build. Prices and timelines are published, with the conditions that move them. For references, ask us — we will connect you with named clients, the same ones quoted on this site.

And question 8, answered in public: we do not do native-only builds, we talk clients out of migrations their product does not need, and when Kotlin Multiplatform or Expo fits your team better, we say so in the comparison posts themselves.

Run the checklist on us and on our competitors. If someone beats us on it, hire them.

Frequently Asked Questions

Published agency tiers for a full build typically run from around fifteen thousand dollars for a lean MVP to ninety thousand and up for enterprise work — ours are public on our services pages, from MVP through e-commerce tiers, precisely so they can be compared. Hourly models for embedded senior engineers commonly land in the fifty-to-hundred-dollar range depending on geography and seniority. Treat any quote given without scope questions as a marketing number, and normalize scope before comparing bids — quotes for what sounds like the same app legitimately vary several-fold because the scopes differ.
A strong freelancer is the right call for a small, well-defined build with one hard skill at its center, and the wrong one the moment your product needs design, backend, and mobile work moving in parallel with continuity insurance. An agency's real product is redundancy and process: someone reviews the code, someone can take over mid-project, and delivery does not depend on one person's calendar or health. The honest cost comparison is not day rates — it is what a three-week stall in month four costs your launch.
Install the apps. Real portfolio entries link to App Store and Google Play listings; open two, use them for ten minutes, and check the store reviews and update history while you are there — a listing abandoned since 2023 tells its own story. For NDA work, ask what specifically the agency built versus inherited. Cross-check the agency's name against client testimonials with real names and roles, and ask to speak to one of those clients directly; a confident shop treats that request as routine rather than an imposition.
Sometimes, and the failure mode is predictable enough to test for. Location does not write bad code — junior teams, thin review processes, and zero timezone overlap do, wherever they sit. Excellent teams exist across every geography and rate band; what you must verify is the same list as anywhere: named senior engineers on your project, installable shipped work, and at least three hours of overlap with your working day. What makes cheap expensive is the rebuild — code that must be rewritten at production quality costs more than building it right once.
Fixed price fits a well-scoped first build: the agency carries estimation risk, you get a committed number, and the discipline of writing the cut list down benefits both sides — it is how we run MVP engagements. Time and materials fits ongoing evolution after launch, or genuinely exploratory work where fixing scope would be fiction. The arrangement to refuse is fixed price with vague scope, which converts every conversation into a change-order negotiation. A capable agency will tell you which model fits your situation rather than defaulting to the one that suits them.
Yes, and it happens more often than the industry admits — inherited codebases are a meaningful share of serious agencies' intake. The mechanics depend on two things you should secure on day one of the original engagement: repository ownership in your name and store accounts under your control. A competent successor will start with a paid audit of the existing code rather than a promise, and the audit report doubles as your negotiating position. Sometimes the verdict is two weeks of fixes, not a rewrite — a takeover should begin with evidence either way.

Shortlisting agencies right now? Book a 30-minute call and bring this checklist — we'll answer all ten questions, including the ones that don't flatter us.