Digital membership
Plan, start and end dates, and a member's own screen showing exactly when it runs out.
CASE STUDY
Example buildMobile AppGym Membership App
Digital membership, quick check-in, class booking and renewal reminders that actually go out.
- Type
- Mobile app + desk web
- Build time
- 9–12 weeks
- Platforms
- iOS, Android, desk browser
- Starts at
- ₹90,000*
This is an example build. Tavzuran is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.
The price follows the feature list. The number above buys everything scoped on this page. Take features out and it comes down — the shortest route to a smaller number is a shorter list, and deciding what to drop is what the free call is for.
THE SITUATION
What's actually broken.
A gym with about four hundred members tracks memberships in a spreadsheet and check-ins in a register. Expiries are noticed late, which means renewals are lost, which is the entire business.
Retention is the whole game here. The features that matter are the ones that put the member back in the building: a renewal nudge before expiry, and a class they have already booked.
Memberships expire quietly and nobody follows up
Check-in is a register nobody fills in properly
Class capacity is managed by shouting
Renewal reminders depend on someone remembering
VERSION ONE
What we'd build first.
Every item here earns its place by being something a real user would miss on day one.
Fast check-in
A QR scan at the desk. Under two seconds, because there is a queue at 7am.
Class booking
Schedule, capacity, and a waitlist that promotes automatically when someone cancels.
Renewal reminders
Seven days out, on the day, and after expiry, with a payment link in the message.
Owner numbers
Active members, expiring this week, and attendance by hour. Enough to staff the floor properly.
DELIBERATELY NOT IN V1
What we'd leave out.
Not because these are bad ideas. Because each one is designed better once the first version has told you something.
- Workout plans and exercise libraries. Members already use apps for that and yours will not beat them.
- Wearable and fitness-tracker integrations.
- Diet plans, which are a licensing question before they are a software one.
UNDER THE HOOD
How it's put together.
- Member app
- React Native, one codebase for both stores
- Desk app
- A web app, since the desk has a browser and a scanner
- Backend
- Node with Postgres
- Check-in
- QR codes that rotate, so a screenshot cannot be passed around the car park
- Payments
- A gateway for renewals, with the link inside the reminder
HOW IT RUNS
Week by week.
-
01
Week 1
Plans, freezes, transfers and the awkward cases the spreadsheet handles informally today.
-
02
Weeks 2–7
Member app, membership and check-in.
-
03
Weeks 8–10
Classes, capacity and waitlist.
-
04
Weeks 11–12
Reminders, payments, owner view, live.
THE HARD PART
Renewals are the product
Every build has one problem that decides whether the rest of it matters. This is that problem, written out.
It is tempting to treat this as a check-in app with membership attached. That has it backwards. A gym's revenue is renewals, and renewals are lost to silence — an expiry nobody noticed, a member who drifted for three weeks and was never asked why.
So the system is built around expiry rather than around entry. Who expires in the next fortnight, who has not attended in twenty days, who cancelled a class twice and did not rebook. Those lists are the product; check-in is the mechanism that keeps them accurate.
The awkward part is everything that makes a membership not a clean date range: freezes for travel or injury, transfers between members, upgrades mid-term, the regular whom the owner informally lets slide for a fortnight. The spreadsheet handles these by a human ignoring the rules. Software cannot ignore rules, so the rules have to be agreed in week one — which is usually the first time anyone has written them down.
BEFORE A PRICE EXISTS
What we'd ask you first.
A quote given without these answers is a guess. These are the questions that actually move the number.
- 01How many active members, and how many lapsed in the last six months?
- 02What plans exist, and can members freeze or transfer them?
- 03Do you run classes with limited capacity?
- 04Who chases renewals today, and how do they know who to chase?
- 05Is there a desk computer, and does it have a scanner?
AFTERWARDS
How we'd know it worked.
Agreed before the build starts, so there is something to judge it against other than whether it looks nice.
- The renewal rate improves against the same period last year.
- Check-in takes under two seconds at the 7am queue.
- The expiring-soon list is worked through every week.
- Classes fill closer to capacity, with the waitlist doing the work.
BEFORE YOU START
Worth knowing.
App-store publishing adds about a week the first time and needs developer accounts in your name, not mine — Apple charges yearly, Google once. You keep ownership of both.
Websites and apps start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.
KEEP LOOKING
Other example builds.
Mobile App
Field Service Job App
Dispatch, on-site checklists, photo proof and an invoice raised before the technician leaves.
Read the case study New BusinessFirst Website for a Social-First Business
You built an audience on Instagram and TikTok. This is the address, the inbox and the page that are actually yours.
Read the case study Code RescueVibe-Coded App, Made Production-Ready
You built it with AI over a weekend and it works. This is what it takes before it can safely carry a business.
Read the case studyWant this built for your business?
Tell us what you're thinking. We'll figure out the next step together.
Free 20-min idea call · No obligation