Membership Management — Design Document Index
Master table of contents for all 17 design document chapters plus supplementary documents. Each chapter is a standalone document covering a specific aspect of the Membership Management Software.
Overview
| # | Chapter | Description | Key Topics |
|---|---|---|---|
| 01 | Executive Summary | Product vision and market positioning | Vision, USPs, roadmap, current state |
| 02 | Vision and Goals | Business objectives and technical goals | Revenue model (Starter/Team/Professional/Enterprise, Trial Studio), I18N (32 languages incl. RTL), compliance, Effortless UX philosophy |
| 03 | Target Groups | Market segments, organizational levels, and user personas | 7 segments, 3 org levels, ~30 personas, franchise support |
| 04 | Competitive Analysis | 50-competitor landscape and positioning | Tier rankings, gap analysis, pricing strategy, deep analysis (Magicline/Virtuagym/FitnessNation), franchise chains, municipal software |
| 05 | Feature Catalog | Complete feature inventory by package | 11 packages, v1.0/v2.0/v3.0/v4.0 roadmap (no MVP), Cash360 parity, simple shop, self-service add-ons |
| 06 | Module Architecture | C4 diagrams and module decomposition | System context, containers, tech stack, Cash360 reuse |
| 07 | User Roles and Permissions | Role hierarchy and permission matrix | ~16 roles (6 hierarchical + 3 vendor + 5 lateral + 2 special), RBAC, frontend strategy |
| 08 | User Journeys | End-to-end workflow diagrams | 13 journeys with Mermaid flowcharts |
| 09 | Frontend Strategy | UI/UX approach and design system | "Effortless UX", 10 UX/UI Design Principles (Gestalt Laws & Cognitive Psychology), Flutter, MEMBERSHIP branding, i18n, RTL support, performance targets |
| 10 | API Design | API-first architecture and endpoint catalog | 25 current + 7 missing + new areas, JWT, versioning |
| 11 | Data Model | Entity definitions and ER diagram | 30 entities, migration mapping, multi-tenancy, JSONB |
| 12 | Integration and Payment | External system connections, My Factura API, and access control hardware | Cash360/My Factura billing, SEPA, Gantner/OSDP/BLE access control, DATEV, CRM patterns, IoT, financial separation (Fremdbeträge vs. Eigenrechnungen), SAF-T, comgate |
| 13 | Security and Compliance | GDPR, authentication, and security | Zero-trust, JWT RS256, eIDAS, audit logging, ADR-AUTH-001 (Custom Auth v1.0 + Keycloak v2.0+), Vaultwarden |
| 14 | Infrastructure and Deployment | Cloud-native deployment strategy | Kubernetes, GitLab CI/CD, Icinga monitoring, Dehydrated ACME/TLS, Vaultwarden, environments |
| 15 | Migration Strategy | Cash360 migration and rollout plan | Entity mapping, CSV import, phased rollout |
| 16 | Startup Operations | Membership One GmbH formation, Hetzner infrastructure, dogfooding | Legal setup, service providers (My-Factura, CashControl, Hetzner), cloud infra ~EUR 100/mo, business automation, personnel scaling, GTM |
| 17 | Customer Onboarding | B2B customer lifecycle, 3 onboarding scenarios, tenant provisioning | 3 scenarios (Founder/Expansion/Migration), integrated contract bundle, self-onboarding <60s, wizard, health scoring, churn prevention |
Supplementary Documents
| Document | Description | Key Topics |
|---|---|---|
| My Factura API Review | Current API specification and redesign proposals | Consumer/Transaction/Payment/Webhook APIs, 9 improvement areas, v2 design |
Chapter Groups
Business & Strategy (Chapters 01–05)
These chapters define what the product is, who it is for, how it competes, and what it does.
- 01 Executive Summary — The elevator pitch: vision, USPs, roadmap, and current state
- 02 Vision and Goals — Business model (4-tier SaaS, Trial Studio, no free tier), technical ambitions (32 languages incl. RTL, GDPR/eIDAS), and the "Effortless UX" design philosophy
- 03 Target Groups — 7 primary segments, 5 secondary sectors, 3 organizational levels (Manufacturer/Franchise/Club), and ~24 personas
- 04 Competitive Analysis — 50 competitors ranked across 6 dimensions, feature gap analysis, and positioning strategy
- 05 Feature Catalog — All features across 11 software packages (incl. Executive Dashboards, CRM, Support, expanded Accounting and Access Control), version roadmap, and Cash360 parity
Architecture & Technical (Chapters 06–10)
These chapters define how the product is built, navigated, and consumed via APIs.
- 06 Module Architecture — C4 Level 1/2 diagrams, 11 backend packages (incl. CRM, Support, Accounting), tech stack decisions, Cash360 reuse patterns
- 07 User Roles and Permissions — ~16 roles (6 hierarchical + 3 vendor + 5 lateral + 2 special) with expanded permission matrix covering CRM, support, accounting, dashboards, access control
- 08 User Journeys — 13 end-to-end flows (original 8 + Executive KPI Review, DATEV Monthly Close, Sales Pipeline, Support Ticket, QR Door Access)
- 09 Frontend Strategy — Flutter architecture, MEMBERSHIP design system (colors, typography, components), responsive/offline/accessibility strategy
- 10 API Design — 25 existing + 7 missing + new admin/resource/event/communication endpoints, JWT auth, pagination, rate limiting, error format
Data & Operations (Chapters 11–15)
These chapters define the data model, external integrations, security posture, infrastructure, and migration path.
- 11 Data Model — 30 core entities with field definitions, Mermaid ER diagram, Cash360 migration mapping, multi-tenancy design
- 12 Integration and Payment — My Factura/Cash360 billing API, SEPA mandates, physical access control (Gantner Essecca, OSDP, BLE, QR door), DATEV integration, CRM patterns, IoT/building automation
- 13 Security and Compliance — GDPR implementation, eIDAS signatures, zero-trust architecture, JWT RS256, brute-force protection, Cash360 audit lessons
- 14 Infrastructure and Deployment — Hetzner Cloud (Nuremberg), Kubernetes, GitLab CI/CD pipeline, Docker Compose, Prometheus/Grafana monitoring, multi-region readiness
- 15 Migration Strategy — Field-level entity mapping, CSV import system, 3-phase rollout plan, parallel operation timeline, rollback strategy
Business Operations (Chapters 16–17)
These chapters define how Membership One GmbH operates as a business and how customers are onboarded to the platform.
- 16 Startup Operations — Membership One GmbH formation (EUR 25,000 Stammkapital), service provider contracts (My-Factura, CashControl, Hetzner, DATEV), Hetzner Cloud infrastructure (~EUR 100/month), dogfooding (own CRM, Support, Accounting), personnel scaling (5→11 over 36 months), go-to-market playbook (Starter/Team/Professional/Enterprise), break-even incl. 4-person dev team, risk assessment
- 17 Customer Onboarding — 3 onboarding scenarios (Founder/Expansion/Migration), integrated contract bundle (Membership One + My-Factura + CashControl), self-onboarding with automated tenant provisioning (<60 seconds), 6-step configuration wizard with industry templates, automated data enrichment (Impressum/Handelsregister/OpenStreetMap/libphonenumber), data migration playbook, customer health scoring (0–100), lifecycle automation, churn prevention
Related Documents
| Document | Path | Description |
|---|---|---|
| MASTERPLAN | ../../MASTERPLAN.md | Autonomous execution guide (14 phases, 0–13) |
| CLAUDE.md | ../../CLAUDE.md | Project context for Claude Code |
| Membership Brief | ../../Membership.txt | Original project brief |
| Planning Documents | ../../planning/ | Source PDFs, HTML specs, competitor Excel |
| My Factura Public API | ../../planning/My Factura Public API.docx | Original API specification (DOCX) |
Statistics
- 17 design chapters + 1 supplementary document
- ~600 KB total documentation
- ~10,100 lines of markdown
- 40+ Mermaid diagrams
- 50 competitors analyzed
- 30 core entities defined
- ~30 user personas across 3 organizational levels
- ~16 user roles (6 hierarchical + 3 vendor + 5 lateral + 2 special)
- 13 user journeys documented
- 11 software packages cataloged
- 31 languages supported (24 EU official + 8 non-EU priority incl. RTL)