Commercial delivery
We Discipline club management application
A reception-focused management application for members, subscriptions, attendance, payments, schedules and controlled staff access.
Visit We Discipline
- Classification
- Commercial delivery
- Status
- Commercial application delivered and deployed for a single-club operation.
- Scope
- Member registration and records · Sports, coaches, groups and schedules
Context
Why the work existed
We Discipline needed one operational application for daily club reception and administration, with a deliberately bounded single-club first release.
Challenge
What had to be controlled
Bring registration, subscription, payment and attendance workflows into one responsive application while preserving role boundaries and a recoverable production deployment.
Scope
- Member registration and records
- Sports, coaches, groups and schedules
- Subscriptions, payments and outstanding balances
- Session attendance and reception check-in
- Staff roles, permissions and audit history
- Club identity, branding and theme settings
Constraints
- The delivered release is single-club rather than multi-tenant SaaS.
- Public staff registration is disabled; administrators provision staff access.
- Production data is persisted on a dedicated VPS and requires an explicit backup procedure.
CS Soft contribution
The implementation responsibility.
The items below describe work performed or documented for this project.
- Application architecture and responsive reception workflows
- Next.js implementation and Prisma data model
- Business-rule validation and database migrations
- Docker packaging, Linux deployment and Nginx integration
- Production backup, release and handover documentation
Architecture
The principal components and deployment boundaries documented for the project.
- Reception interface
- Next.js application
- Prisma data layer
- Persistent SQLite volume
- Docker and Nginx
Delivery and QA
- Automated API and business-rule scenarios
- Production build gate
- Manual mobile and reception-workflow QA matrix
- Database migration and backup verification
Technical outcomes
- Authenticated production application deployed for the club.
- Core reception workflows implemented across desktop and mobile layouts.
- Persistent application data and branding separated into retained volumes.
- Deployment, backup and operational handover procedures documented.
Technologies
- Next.js
- React
- TypeScript
- Prisma
- SQLite
- Docker
- Nginx
- Linux
Team responsibilities
- Product engineering
- Frontend and backend implementation
- Data modelling
- Production deployment
- Technical handover
Discuss a comparable assignment
Share the business workflow, technical constraint and expected deliverable. We will state whether it fits our current scope.
Discuss the requirement