Gym Management System Discovery Form

Alphatech Developers — Tell us about your gym so we can scope membership, attendance, M-Pesa payments, and management software. Required fields are marked *.

← Back

Thank you for your response. ✨

Section 1 — Basic Client Information

We start with who you are and how to reach you. This information is used for proposals, clarification calls, and project updates throughout development.

Primary contact for this project — proposals and clarifications go to this person.

Legal or trading name as it should appear on invoices and the app.

e.g. Owner, Manager, Operations — helps us tailor communication.

Business email for quotes, login invites, and project updates.

Best number for quick questions; include country code if outside Kenya.

Preferred Contact Method

How should Alphatech reach you first? Select all channels you actively use.

City, estate, or branch addresses — important for multi-site setups.

Your member portal and admin dashboard need a web address. Enter your preferred domain as it should appear (e.g. www.gym.co.ke or fitness.yourbrand.co.ke). We’ll register or connect this for you.

Section 2 — Business Overview

Help us understand your gym’s scale and pain points. Your answers here shape which features we prioritize in phase one versus later releases.

What type of gym or fitness business do you run?

Select all that apply if you offer multiple formats.

Only if you chose Other above.

Number of branches

Include planned openings if you expect new branches within 12 months.

Active members

Approximate paying or active members today — helps size infrastructure.

Current challenges

Select everything that slows your gym down today — this helps us prioritize features.

Describe pain points not listed above.

Section 3 — Project Goals

Tell us what success looks like. Clear goals help us recommend the right modules and avoid building features you do not need yet.

Main goals

What should this software achieve in the first 6–12 months?

Only if you chose Other under Main goals.

The one issue you want fixed first after launch.

How will you know the project succeeded? e.g. 90% M-Pesa auto-reconciliation.

Section 4 — Platform Requirements

We build web apps with member portals and admin dashboards. This section confirms which surfaces you need and whether you already have hosting or a domain.

Platforms needed

Web app includes member-facing portal; admin dashboard is for owners and managers.

e.g. kiosk mode, TV display, API for external systems.

Do you have hosting/domain?

Yes if you already own hosting or a domain we should use or migrate.

Section 5 — User Roles & Permissions

Different staff and members need different access. We use your answers to design login roles, permissions, and approval workflows.

Who will use the system?

Every role you select may get its own login and permission set.

e.g. Marketing, Security — only if not listed above.

Different permissions per role?

e.g. receptionist can check in but not see revenue reports.

Describe any unusual access rules or approval steps.

Section 6 — Member Management

Member data drives profiles, check-in, billing, and communications. Select what you collect today or plan to collect in the new system.

What member information should be stored?

Select all fields you collect or want to collect digitally.

Custom fields e.g. employer, referral source.

Digital member profiles?

Online profiles members can view or update themselves.

Profile pictures?

Useful for staff recognition and member apps.

Membership IDs / cards?

Physical or digital member cards linked to QR check-in.

Section 7 — Attendance & QR

How members check in affects hardware, staff workflow, and fraud prevention. Be specific so we can plan QR codes, scanners, and expiry rules.

How should attendance tracking work?

How members check in affects hardware, staff workflow, and fraud prevention.

Describe your current or preferred method.

Who scans the QR code?

Who performs check-in at the door or desk.

Unique QR per member?

Recommended to prevent sharing one code between members.

QR codes expire / refresh?

Rotating codes reduce fraud if screenshots are shared.

What to track

Entry-only vs entry+exit affects reporting and capacity planning.

Attendance notifications

Optional alerts when a member checks in or out.

Block check-in if membership expired?

Stops expired members from entering without manual override.

Section 8 — Membership & Subscriptions

Membership plans and renewals are core to gym revenue. Your choices here guide billing cycles, reminders, pauses, and family plans.

Membership types

All billing periods you sell today or plan to sell.

Auto-expire memberships?

System marks memberships inactive when the period ends.

Auto-remind before expiry?

SMS/email nudges before renewal date.

Days before expiry to remind

Select all reminder windows you want.

e.g. 14 days before expiry.

Pause / freeze memberships?

For travel, injury, or seasonal holds without losing the member.

Family / group memberships?

One payment covering multiple people or a household.

Section 9 — Payment Integration (M-Pesa emphasis)

Kenyan gyms often rely on M-Pesa. Share what payment methods and Safaricom credentials you already have so we can plan Daraja API integration.

Payment methods

All ways members pay you today or should pay in the app.

e.g. Flutterwave, PayPal.

Existing M-Pesa setup

Tell us what payment credentials you already have so we can plan Daraja API integration.

Payment features needed

Automation and billing features beyond simple recording.

Failed payment notifications?

Alert staff or members when STK push or renewal fails.

Section 10 — Booking & Scheduling

If you offer classes, PT sessions, or equipment booking, we need to know who schedules what and whether trainers manage their own calendars.

What can members book?

Online booking reduces front-desk calls.

e.g. Sauna slots, swimming lanes.

Trainers manage their own schedules?

Trainers set availability; admins can still override.

Section 11 — Trainer & Staff

Trainers and staff may need their own profiles, schedules, and attendance tracking separate from members.

Trainer profiles in system?

Public or internal profiles with bio, photo, and specialties.

Trainer features needed

Tools trainers need beyond basic member lists.

Staff attendance tracked?

Clock-in for reception, trainers, or security.

Section 13 — Notifications

Automated SMS, WhatsApp, and email reduce manual follow-ups. Choose channels and triggers you want built into the system.

Notification methods

Channels you are willing to use for automated messages.

Automated notifications

Events that should trigger messages without manual action.

Section 14 — Reports & Analytics

Owners and managers need visibility into revenue, attendance, and retention. Tell us which reports and export formats matter most.

Reports needed

Dashboards and exports you need for daily operations.

Export formats

How managers download data for accounting or analysis.

Section 15 — Multi-Branch

If you operate more than one location, we can separate data by branch or share members and subscriptions across sites.

Multi-branch support needed?

Separate or shared data per location.

Per-branch requirements

How independent each branch should be.

Section 16 — Branding & Design

Your app should feel like your gym. Share brand assets and style preferences so design matches your identity.

Brand assets you have

We can use your logo and colors in UI design.

Preferred design style

Overall look and feel for web and member portal.

Section 17 — Technical & Security

We follow security best practices by default. Select any extra controls you need for admins, audit trails, and data protection.

Security features needed

Extra controls beyond standard HTTPS and access control.

Section 18 — Future Expansion

Optional features for later phases help us architect the system so additions are easier and less expensive down the road.

e.g. mobile app, nutrition tracking, corporate wellness.

Section 19 — Budget & Timeline

Budget and timeline help us propose a realistic scope and delivery plan. Ranges are fine — this is for planning, not a final quote.

Rough range in KES or USD — helps scope phase one realistically.

Timeline

When you ideally want to go live.

Project type

New build vs upgrading an existing system changes migration work.