Founders often ask me how to build an MVP without wasting months or money. Bout Buddy, a platform we designed and built for martial arts fighters and gyms, is one of the clearest answers I can give. It went live on both app stores and the web eight weeks after its specifications were finished, and it passed 1,500 users in its first 45 days.
The short version: to build a minimum viable product that launches fast, finish the specifications before development, cut the feature list hard, build one cross-platform app for iPhone, Android and the web, and launch to a narrow, well-defined audience with a small daily ad budget.
What Bout Buddy is
Bout Buddy is a mobile and web platform for Muay Thai, kickboxing, wrestling, BJJ and MMA fighters, their coaches and gym owners. It brings records that are usually scattered across notebooks, group chats and spreadsheets into one place:
Fighter profiles and bout records. Opponent, event, result, method, rounds and weight for every bout, in a record fighters can export to PDF.
Gym management. Owner, Coach and Fighter roles, join requests that coaches and owners approve, gym member management, and announcements to members.
Events and schedules. Fight nights and tournaments to browse and save, plus training schedules gyms keep up to date.
Documents. Medical records and other documents with expiry dates, so fighters get reminded before something lapses.
Bout Buddy is free for fighters and gyms at launch. Gym subscriptions are the planned revenue model, with advertising from martial arts gear brands and other businesses that serve the same audience as a possible second source. Launch marketing went to fighters first to build reach. A minimum viable product (MVP) exists to answer your riskiest questions with real users, and you cannot answer anything without users.
Lesson 1: Write the specs before MVP development starts
Before MVP development started, Bout Buddy had a complete database design, user stories grouped into epics, and screen designs for the whole first version. That preparation is the reason the build itself took only eight weeks.
When every screen and every piece of data is decided up front, developers build instead of guess, and nobody discovers halfway through that two features contradict each other. Skipping this step is the most common cause of budget overruns I see in MVP development.
Lesson 2: Design for the users you actually have
When you build an MVP, it's tempting to design for the scale you hope to reach. Bout Buddy was built for the gyms that exist. Even the top gyms in Canada and the US usually have fewer than 15 active competitive fighters, so the app is designed around small rosters, not hundreds of athletes.
Knowing the users also showed what to leave out. Fighter profiles stay private. Public event pages were discussed and judged not worth building yet. Every feature cut was one less thing to design, test and maintain, and it got version one in front of fighters sooner.
Lesson 3: Build one cross-platform app for iPhone, Android and the website
Bout Buddy is built with Flutter, a cross-platform framework. Flutter app development lets a single codebase run on both app stores and the web, which meant launching on every platform at once instead of picking one and making half the audience wait.
It also pays off after launch. Every fix and every new feature reaches all users at the same time, which matters most in the early weeks, when feedback arrives fast and you want to act on it quickly.
That is why a cross-platform build is the approach I recommend for most custom mobile app development projects. Native apps still make sense when a product depends on heavy device features, such as advanced camera processing or high-performance graphics. For most business and consumer MVPs, one cross-platform codebase gives users the same experience at a lower cost.
Lesson 4: How to market an app launch on a small budget
When it was time to launch the MVP, the first 20 users came from regular posts on Instagram and Facebook. Everyone after that came from a Meta ads campaign with a budget of only $15 to $20 a day. Over the first 45 days, that is less than $900 in total, or well under a dollar per user.
Two things made that possible. First, the audience was narrow and easy to describe: people who train and compete in martial arts. Second, the campaign targeted a mix of countries, and ad costs vary a lot from one market to another. Reaching the same results only in the most expensive markets, such as the US and Canada, would likely have taken at least $50 a day.
So the lesson isn't that a tiny daily budget always works. It's that a precisely defined audience is cheap to reach, and that your budget should be set by where your users are.
Lesson 5: Plan for app store ratings from the first release
Store ratings are one of the first things a potential user checks before downloading, and your earliest users are often your most enthusiastic ones. Build the in-app prompt that asks users to rate the app into version one, timed for a moment of success, such as right after a fighter saves a new bout. It costs very little to add and pays off with every new download.
Bout Buddy by the numbers
Metric |
Result |
|---|---|
Sports supported |
Muay Thai, kickboxing, wrestling, BJJ and MMA |
Time from finished specs to launch |
8 weeks |
Platforms at launch |
iPhone, Android and web, from one codebase |
Users in the first 45 days |
More than 1,500 |
First 20 users |
Organic Instagram and Facebook posts |
Paid acquisition budget |
$15 to $20 a day on Meta ads, across several countries |
Business model |
Free at launch; gym subscriptions planned |
A checklist for building your first MVP
Finish the specifications, user flows and screen designs before development starts.
Design for the users you have today, and write down what you are deliberately leaving out.
Default to one cross-platform codebase unless a core feature needs native device power.
Describe your first users precisely, and set your ad budget by the markets they live in.
Ship the app store rating prompt in version one.
Frequently asked questions
How long does it take to build an app?
It depends mostly on scope and preparation. A focused MVP can launch in about two months: Bout Buddy took eight weeks from finished specifications to launch on both app stores and the web. Larger apps take longer, but the biggest time saver is the same at any size: deciding the screens, data and features before development starts.
How much does it cost to market an app at launch?
It depends on your niche and where your audience lives, because ad costs differ widely between countries. A narrow, well-defined audience is far cheaper to reach. Bout Buddy passed 1,500 users in 45 days on $15 to $20 a day by targeting a mix of markets. Limiting the campaign to the most expensive markets, such as the US and Canada, would have needed at least $50 a day.
Should an MVP launch on iPhone and Android at the same time?
If you build cross-platform, launching on both costs little extra, and you avoid making half your audience wait. Bout Buddy launched on both app stores and the web from the same codebase.
The bottom line
If you want to build a minimum viable product that reaches real users quickly, what worked here is boring and repeatable: decide everything before coding, cut hard, build once for every platform, and launch your MVP to users where they already spend time, with a budget matched to where they live.
About the author: Khaled Elshaer is the founder and CEO of Paracon Consultants, a Toronto company that has built fixed-price web and mobile apps for startups and small and midsize businesses since 2013.
Entrepreneurship
