Turning a Fitness App Idea Into a Roadmap - A Real Discovery Session at Olio Apps

At Olio Apps, we believe the success of any new product starts long before the first line of code is written. It starts with discovery. A structured discovery process helps uncover the real problems an application solves, clarifies user needs, and separates “must-have” features from “nice-to-have” ideas. Many founders and innovators come to us with a vision already forming in their minds. But often, those early visions are obscured by assumptions, blind spots, or competing priorities. A discovery session is where we peel back the layers, hold up a mirror, and ask the hard questions that bring clarity and refine the product before valuable development time is spent. Recently, we recorded a discovery session with Josh, who came to us with an idea for a new kind of fitness app. What began as a rough concept quickly evolved into a clearer picture of what the minimum viable product (MVP) could look like and why it might fill an important gap in the market.

---

The Client’s Idea: A Fitness App for Group Workouts, Not Just Individuals

Josh works out regularly with friends, family members, and people of different ages and abilities. Like many fitness enthusiasts, he uses apps to track sets, reps, and weights. But here’s the problem: existing apps are primarily designed for individuals. When Josh is in the gym with others, he ends up juggling data for multiple people, often doing mental math to keep track of different progressions across individualized programs. With two people, he can manage. With three or more, the system (Josh’s brain) breaks down. His idea is simple and compelling: the ability to log workouts for multiple people, side by side, in real time. That single feature would make the app unique. Current solutions like Boostcamp or spreadsheets either overload him with unnecessary features or make logging clunky and time-consuming, which takes away from the focus needed when you’re in the gym sharing equipment. Neither fits the dynamic, variable, and time conscious nature of group workouts. Josh also envisions features that extend beyond logging. Imagine being able to set personal goals, track volume by muscle group over time, and even tally aggregate group performance: “We did 100 sets of legs this week as a team!” This subtle but meaningful insight reframes fitness from a purely individual pursuit into a shared wellness experience.

---

What Makes This Idea Different

During the discovery session, we teased out the unique differentiators:

• Multi user input in one screen: Rather than logging workouts for each person separately, the app would allow easy side-by-side tracking.
• Goal driven tracking: Instead of drowning users in charts, the app would highlight progress toward meaningful benchmarks users could input themselves, such as completing a target number of sets for specific muscle groups in a given month.
• Group Focus: Fitness apps tend to emphasize personal progress. But what happens when multiple people need their unique periodization methods logged at the same time? Josh’s vision turns it into a social experience that makes working out together easier, more fun, and more sustainable.

This combination of ergonomics, streamlined data entry, and group accountability is rare in the crowded fitness app space.

Key Insights From Discovery

As with most discovery sessions, the conversation moved in many directions before settling on the core problem. By listening carefully and asking clarifying questions, we distilled several key insights:

• The core problem isn’t lack of data or workout options, it’s friction. Logging for multiple people is possible today, but it’s cumbersome, especially during a workout. The MVP must make this seamless.
• Ergonomics are critical. No one wants to fumble with tiny spreadsheet cells on a phone while spotting a friend on the bench press. The app has to work fast, in the heat of the workout.
• The MVP can stay lean. Local storage, simple input, and basic progress tracking are enough for version one. Analytics, cloud syncing, and social features belong on the roadmap.
• Opportunities for future features. Aggregate group metrics, customizable progression methodologies, and even influencer-driven marketing strategies could make the app stand out in a competitive market.
• The goal for the prototype is undefined. Frankly, Josh has been so immersed in just trying to find a solution to his problem, he hasn't thought too much about if he wanted to fully go to market with his idea or seek investors. For now, he was just planning to bootstrap the application but would be interested in hearing how the prototype would change if he was planning to use it alongside an investor pitch.
• Need to plan for future dev responsibilities. Currently Josh doesn't have a dev team, so Olio Apps would be responsible for designing, architecting, and developing the prototype. Whether Olio would continue to be Josh's main dev team after the prototype is finished needs to be defined.

The Olio Apps Discovery Process in Action

Our approach to discovery is less about dictating solutions and more about uncovering truths. We start by asking questions like:

• What is the real pain point?
• What’s the smallest useful version of this product?
• Where are the risks, including technical, market, or usability?

What's the MVP, Really?

With Josh, we helped distinguish between “table stakes” (a library of exercises, recording results) and the truly differentiating features (multi-user input, goal-driven metrics). We also surfaced hidden challenges, such as how to design an interface that doesn’t interfere with the physical flow of a workout. Spending time defining a minimum viable application upfront ensures development time is as efficient as possible and Josh's application is on the fast track for release. Ideally, our next call would include getting some feedback from Josh's workout partners, his first users, to help us define multiple user personas and essential user flows. Another key aspect of discovery involves understanding the goal of the prototype and understanding milestones for the project. Whether Josh is deciding to fully bootstrap this application himself, or if he's looking to build a prototype for Venture Capital or angel investors, changes our advice and development recommendations. Whether Josh is bootstrapping this app versus seeking outside investment significantly influences the applications' overall budget, runway, and development timelines. This leads to our next point. A lot of the entrepreneurs we talk to, including Josh, don't have a development team already and are seeking support in this area. But what happens once we build the prototype and the application gets traction? Does our client plan to take development 100% in house so we need to design an offboarding strategy? Or are they planning to still work with us at some capacity after the initial release? Finally, we can begin assisting Josh in developing a monetization strategy for his application. By starting from the pain points experienced by his user personas, we can compare the value they would receive from using the application versus competitor solutions. This analysis would also help us iterate ideas for a go to market strategy. Maybe an influencer based User Generated Content strategy is best for a direct to consumer application? Maybe this app would be best as part of an employer sponsored healthcare offering? Ultimately, a good discovery process is collaborative. It involves not only the founder but also the prospective users. By combining these perspectives, we are able to provide a tailored recommendation on how we think is best to take an application from idea to functioning prototype.

Mapping the Path: From Idea to Prototype

So what happens after this first conversation? We recommend a structured path:

1. Synthesize notes into a clear problem statement. This ensures alignment on the “why” behind the product.
2. Prototype workflows using simple tools like spreadsheets or low-fidelity mockups. The goal is to test usability quickly, not to build prematurely.
3. Validate assumptions by observing real users (Josh’s gym partners) interact with the prototype.
4. Define MVP scope, what features will make it into version one and which ones should wait?
5. Estimate cost and ownership of development and production so Josh can decide how to fund and prioritize.

This iterative process avoids wasted effort, keeps investment focused, and provides confidence before moving into development.

Why Discovery Matters (Beyond This One Idea)

Josh’s story is unique, but the principles apply broadly. Every founder thinks their idea is clear, but talking it through with technical experts often reveals new insight. Discovery sessions often reveal:

• Blind spots: Assumptions about what users want may not hold up under scrutiny.
• Hidden risks: Usability, ergonomics, or market positioning can be just as critical as technical feasibility.
• Prioritization needs: Not every feature belongs in the MVP. Discovery forces trade-offs for the benefit of the project’s lifecycle.
• Opportunities: Sometimes, discovery uncovers unexpected differentiators that make the product more compelling.

By slowing down at the beginning, you speed up later. The cost of misunderstanding your problem space is far higher than the cost of a few structured conversations.

Lessons for Founders and Innovators

Josh's discovery for his fitness app idea illustrates several lessons we'd like to define:

• Solve for simplicity first: Don’t try to compete with feature-heavy incumbents. Focus on the unique pain point you can address best.
• Think in phases: MVPs and roadmaps serve different purposes. Get version one into people’s hands quickly, then expand.
• Respect ergonomics: If the app isn’t usable in the user’s real context, sweaty hands, crowded gyms, limited time, adoption will falter.
• Lean on prototypes: A simple spreadsheet can validate an idea before you spend thousands on development.
• Discovery is a two-way street: It’s not only about whether Olio Apps can help a client, it’s also about whether the idea, founder, and team are a good fit to succeed together.

Ready to Explore Your Idea?

At Olio Apps, we specialize in turning rough concepts into clear roadmaps. Through discovery sessions, prototyping, and iterative design, we help founders and teams find the heart of their product idea, before development begins and even if you have a working prototype. If you have a software idea, the best investment you can make is discovery. It will save you time, reduce risk, and give you confidence in your next steps. Talk to us today to schedule a discovery session and see what your idea could become.