Kuwait's fitness scene lived in DMs and spreadsheets. We put it in one app.
FitFinds connects fitness enthusiasts with gyms, academies, and product vendors — subscriptions, bookings, and shop, in one bilingual platform. Three separate businesses, one backend, one team. A platform FitFinds owns — not a subscription they rent. Delivered under a verified Upwork contract.
Fitness in Kuwait lived in fragments.
Members discovered gyms on Instagram, booked classes over WhatsApp, paid in person, and bought supplements from a different seller entirely. Gym and academy owners juggled subscriptions in spreadsheets, had no way to run promotions, and had zero visibility into their own revenue.
The client's vision was ambitious: one fitness marketplace app serving three different user types — members, merchants, and administrators — where a user could subscribe to a gym, book a recurring academy class, and order equipment to their door in the same session. That meant solving subscription billing, class scheduling, e-commerce logistics, and marketplace payouts simultaneously, in two languages, with Kuwait's payment rails.
They needed a team that had already built each of those systems — not one that would learn on their budget.
Scope before code.
We started where every NLS build starts: scope before code. Working from the client's brief, we mapped the three products against one shared backend, then made the architecture decisions that kept a complex fitness subscription platform shippable:
One codebase, both stores.
Flutter for iOS and Android — one team, one timeline, no feature drift between platforms. Every future feature launches once, not twice.
One backend, three clients.
Node.js APIs on AWS with MongoDB serving the member app, merchant dashboard, and admin panel — so a booking made in the app appears in the merchant's schedule and the admin's reports in real time.
Gulf-native from day one.
MyFatoorah, KNET, and card payments; full Arabic with RTL layouts; and WhatsApp integration as a first-class feature — because in Gulf commerce, WhatsApp is customer service.
Logistics built for reality.
Pickup and delivery per vendor, with dynamic delivery pricing calculated from distance and location.
Weekly demos kept the client watching the product grow — booking flows one Friday, merchant payouts the next.
Three products, one platform.
3 separate products. One shared backend. One team. One timeline.
Member App
- Gym & academy subscriptions
- One-time and recurring class bookings
- Fitness marketplace — clothing, supplements, equipment
- Cart with pickup or delivery
- MyFatoorah, KNET & card payments
- WhatsApp chat with gyms, trainers, and vendors
- AI-driven recommendations
- Arabic + English with full RTL
- Push notifications
- Profile with full order and booking history
Merchant Dashboard
- Subscription, listing & service management
- Class schedules
- Revenue and analytics
- Promotional campaigns, banners & discounts
- Order and renewal tracking
- Financial reports with payout requests
- WhatsApp customer interaction
Admin Panel
- Vendor approvals & account control
- Subscription and order monitoring
- Product and listing approvals
- Payout and revenue control
- Platform-wide announcements
- Performance, merchant, and engagement reporting
What this means in practice.
One Flutter codebase shipped to both the App Store and Google Play — every future feature launches once, not twice.
Members subscribe, book, and shop in one session — three revenue streams that previously required three separate tools, now on one custom fitness platform.
Gyms and academies replaced spreadsheets with a real dashboard: schedules, promotions, revenue, and payouts in one place.
The marketplace runs itself — vendor onboarding, listing approvals, and payout control sit with the admin, no developer needed for daily operations.
The AWS + MongoDB architecture scales with marketplace growth instead of capping it — adding new vendors or categories costs nothing in infrastructure.
FitFinds owns the platform outright — no per-seat SaaS fees, no vendor lock-in, no ceiling on what they can build next.
The Stack
Every tool below shipped to production — no résumé-ware.
Questions We Get Asked
Building a fitness platform or marketplace?
We've already solved subscriptions, bookings, payments, and payouts.
See exactly how we'd scope yours.
