We shipped our SaaS v1 in ~5 weeks on FlutterFlow instead of ~5 months. Here's where it actually held up and where it didn't.

Posting this because I keep seeing the "FlutterFlow doesn't scale" take repeated without much nuance, and our experience was more mixed than that.

Context: small team, B2B dashboard product, needed something real in front of design partners before a fundraise. Going fully custom was a 4 to 6 month build we couldn't afford to validate an unproven idea. So we did the v1 in FlutterFlow with Firebase on the backend.

What worked:

• Auth, the core CRUD screens, and a working dashboard were live in about three weeks. We had paying-intent users testing it while a custom team would still have been setting up the repo.
• One codebase to iOS, Android, and web mattered more than I expected. We didn't have to pick a platform before we knew where users actually were.
• It exports real Flutter code. That was the dealbreaker for us. We weren't locked into a black box, so the "but you'll have to rebuild" fear didn't really apply.

Where it bit us:

• Anything past basic API logic needs someone who actually understands Flutter and state management. The drag-and-drop ceiling is real, and we hit it around the time we added role-based access and a billing flow. That's the part people underestimate.
• Messy data modeling early on cost us later. FlutterFlow lets you move fast enough to build the wrong thing fast.

The honest summary: it's a validation and speed tool, not a free pass on engineering. The teams I've seen do well with it pair the speed with someone who can take over when it gets complex. When we hit that point we went the Hire FlutterFlow Developer route for the parts that outgrew the visual builder (full disclosure, that's our own company page, so take it for what it is). For broader context, Gartner expects 70% of new apps to use low-code or no-code by 2026, up from under 25% in 2020, so this approach isn't fringe anymore.

Curious where others landed: for those who used FlutterFlow for a real product, at what point did you hit the wall and decide to bring in a dev or move off it? Trying to figure out if our "validate fast, engineer the hard parts" split is the right pattern or if we just got lucky.