Most "best Flutter agency" lists rank companies on three things: hourly rate, review score and portfolio size. Those are fine filters for a brochure app. For a two-sided marketplace they miss almost everything that makes the project hard: split payments, identity checks, real-time messaging and an architecture that survives growth.
If you're the developer, CTO or technical co-founder asked to vet a Flutter partner, this post gives you a technical interview script instead of a ranking. It's based on the marketplace-specific criteria in Journeyhorizon's guide to choosing a Flutter app development company for marketplaces.
Why Flutter is a reasonable default for marketplaces
Before vetting the partner, sanity-check the stack choice:
- One codebase, three targets. iOS, Android and web from a single Dart codebase, with consistent UX for buyers and sellers across devices.
- Cost. For many apps, Flutter is roughly 30–40% more cost-efficient than building separate native apps, with comparable performance. The real saving depends on how many platform-specific features you need, so ask for both estimates.
- Escape hatches. When you do need native capabilities, plugins and platform channels give you access.
Native still makes sense when the product leans heavily on platform-specific features or performance. For most marketplaces, though, the hard problems sit in the backend and integrations, not the UI layer. That's exactly where generic Flutter shops tend to be weakest.
The shortlist checklist
Use this as a first-pass filter before any calls:
- [ ] Live two-sided platforms you can actually download and test
- [ ] Marketplace payments: split payouts, escrow or delayed capture, refunds, multi-currency
- [ ] Trust and safety: identity verification, reviews, moderation, disputes
- [ ] Scalable architecture: backend, search, caching, a plan for 10x traffic
- [ ] Transparent, phased pricing with milestones and market-rate hourly rates
- [ ] Post-launch support: maintenance, app store updates, growth roadmap
- [ ] Commercial thinking: they ask about your business model before your feature list
Anyone who fails more than one of these isn't a marketplace partner, regardless of their rating.
The technical interview: four areas to probe
1. Payments are a subsystem, not a plugin
"We've integrated Stripe" is not an answer. Marketplace payments mean multiple payment methods, currency conversion, escrow logic and settlement cycles. Many Flutter shops can build a beautiful checkout UI but have never run marketplace payments at scale.
Questions to ask:
- Walk me through how funds move from buyer to seller in your last marketplace.
- How did you handle delayed capture and partial refunds?
- Where does commission get calculated, and what happens on a dispute?
- Which payment providers have you integrated in production?
Vague answers are a red flag.
2. Identity and trust
Two-sided platforms live or die on trust. Expect identity APIs, document verification, background checks and third-party trust services. Ask which identity providers they've wired up and how verification state flows into the app (e.g. what a seller can do before and after verification).
3. Real-time state across both sides
Buyers, sellers and support all need the same view of the world. That means push notifications, in-app messaging and message queuing. Booking apps are the classic stress test: availability and confirmations must agree on every device, or you get double-bookings.
Ask: How do you keep availability consistent when two users book the same slot at the same moment?
4. Scale from day one, without over-building
You don't need a planet-scale backend at launch, but you do need caching, pagination, search optimization and sane database queries from the start. Otherwise the success case triggers a rewrite. Ask how their last marketplace handled a 10x traffic jump, and what they'd change.
Business model drives architecture
This is the part engineers sometimes skip, and it's the most important. The monetization model changes your data model and payment flows:
| Business model | Architectural consequence |
|---|---|
| Commission | Payment splits, payout scheduling, fee reporting |
| Subscription | Recurring billing logic, entitlement checks |
| Multi-region | Tax rules and regulatory variation per market |
A partner that doesn't ask about this before quoting is estimating the wrong system.
Reading the estimate
Benchmarks from the source for 2026:
- Startup MVP (auth, profiles, basic listings, notifications, a few integrations): ~$25,000–$50,000
- Booking or service marketplace (availability, booking, payments, reviews, admin): ~$50,000–$100,000
- Complex marketplace (multiple roles, subscriptions, real-time data, AI or heavy integrations): ~$150,000–$250,000+
- Maintenance: ~15–20% of the initial build per year
Timelines: a focused MVP takes about three to four months; a feature-complete marketplace with payments, identity verification and messaging about six to nine months.
A quote far below these ranges usually means marketplace complexity wasn't priced in, and you'll pay for it later in change requests.
Build vs. platform: don't default to custom
Not every marketplace needs a custom backend. Platforms like Sharetribe already cover payments, seller management, disputes and messaging for common models: service marketplaces, product marketplaces and peer-to-peer rentals. Launch can take weeks instead of months, and a Sharetribe mobile app template starts from $199/month plus a one-time setup fee.
Custom development earns its cost for unusual models: B2B multi-vendor, heavy compliance, real-time marketplaces, proprietary matching or ranking, or marketplace-as-a-service. A sensible path is hybrid: validate on Sharetribe, add native-feeling mobile apps, then invest in custom code once you've proven product-market fit.
As a reference point, the Australian fashion marketplace Kifaayat launched iOS and Android apps on Journeyhorizon's Flutter mobile foundation in roughly one to one and a half months.
Red flags during the sales process
- Leading with visuals and speed while skipping architecture
- Long engagements with no milestones or pause points
- "We'll scale to millions of users" with no talk of databases, caching or infrastructure
- No questions about your business model, users or growth plan
What good post-launch support looks like
Shipping v1 is the start, not the end. Ask what happens in month two and month twelve. A solid partner should cover ongoing maintenance and bug fixes, performance tuning, OS and app store updates, and new features as the business evolves. For a marketplace specifically, that includes improving the seller experience, payment reconciliation, dispute workflows, and adding new payment methods or regions. Ask, too, whether the codebase is structured so marketplace-specific plugins and integrations can be added later without a rewrite. If the answer is "we'll figure that out after launch," budget for a second vendor.
Final test
Ask the agency to walk through their last marketplace project end to end: payments, scalability decisions, onboarding. Strong partners will talk trade-offs and edge cases. Weak ones will show screenshots.
If you're evaluating partners now, Journeyhorizon has shipped more than 200 projects since 2018, and its Flutter mobile app development team focuses specifically on marketplace builds.
Top comments (0)