Back to the Drawing Board

After the beta, we asked ourselves another hundred questions.

The system was working. Players were coming back. The core loop was solid. But something was still off. The vision we had was good — and yet, somehow, too narrow. Too niche. We were building for a specific audience without fully realizing it, and the feedback we kept getting from the people we consulted made that crystal clear.

We talked to a lot of people during that period. Mentors, advisors, support groups, people who believed in the project enough to challenge it honestly. And the challenge kept coming back in the same form:

"It's good. But it's not open enough yet."

That sentence stuck with us.

The price

From day one, we had assumed FlyQuest would be a paid app. We hadn't even fixed the amount yet, but the idea of a one-time purchase felt natural. With everything we were hearing, that assumption started to crack. If we wanted FlyQuest to actually be the Duolingo of aviation — accessible to literally anyone curious about flight — then putting a paywall at the front door made no sense.

So we made the call: FlyQuest will be free. For everyone.

Which immediately opened a much harder question: how do we sustain the project? We didn't want to go down the pay-to-win route. No mechanic that gives paying players an unfair learning advantage. That principle was non-negotiable.

We spent a lot of time turning the problem over. The answer we landed on is a freemium model, with one strong rule baked in: any player can access roughly 99% of the content without ever paying a cent. Paid options exist for those who want to support the project or unlock convenience, but they never gatekeep the actual learning. That distinction matters to us.

The content

We launched the beta with around twenty activities, and we had roughly double that in stock, waiting to be plugged in. The problem wasn't the volume — it was the pipeline. Setting up a single activity, configuring it, parametrizing it, integrating it into the app, was eating an absurd amount of time.

That pipeline is not scalable. Not even close. If we want FlyQuest to cover every domain of aviation — from absolute beginner stuff to advanced material — we need a content engine, not a content factory built one piece at a time.

The realization

By the end of the debrief, the picture was clear. What we had was a beautiful MVP. Genuinely. We were proud of it. But an MVP is a proof, not a destination. To go where we actually want to go, we needed to think bigger, invest more, and accept that some parts of FlyQuest would need to be rebuilt almost from scratch.

That's when the rebuild started.

A full redesign of the foundations — not the vision, the foundations. The vision stayed exactly where it was. What changed was our willingness to build the long-term version of it, instead of stretching the short-term one until it broke.

In a way, it felt like ending one chapter of FlyQuest. The MVP chapter. The "let's see if this works" chapter.

The next chapter is bigger.