Feel Pro Club Docs

Appearance

0003. Manager Onboarding, Team Creation, and Branding ​

Status: Approved Author: Codex Created: 2026-03-09

Overview ​

This PRD defines the organizer journey from team-creation entry into a created, branded team with a shareable invitation link. It covers team identity setup, ownership bootstrapping, deferred recovery from My team, and the immediate next step of optionally inviting the first members.

Problem Statement ​

An organizer cannot run the rest of Feel Pro Club without first establishing a team identity. Team setup must be lightweight enough to complete during onboarding, but also recoverable later if the organizer defers creation and reaches the product without a team.

Goals ​

  • Let organizers create a team in a few focused steps.
  • Ensure the team feels owned and recognizable through name, abbreviation, colors, and logo.
  • Let organizers recover cleanly from deferring team creation.
  • Transition directly from creation into optional sharing of the first invitation link.

Success Metrics ​

  • High completion rate from team-creation entry to a created team.
  • High share rate from the post-creation invite screen.
  • Low abandonment during the branding wizard.

Scope ​

In Scope ​

  • Team creation intro screen.
  • Empty-state recovery from My team when no team exists yet.
  • Team name, abbreviation, color, and logo setup.
  • Automatic organizer ownership and current-team selection.
  • Immediate post-create invite sharing.

Out of Scope ​

  • Advanced team settings such as league metadata, venue defaults, or privacy controls.
  • Ongoing in-team invite management after onboarding.
  • Invite acceptance and join-role assignment for recipients.

Personas and Roles ​

  • Organizer/manager: Wants to create a team and start inviting players immediately.
  • Newly created team: Needs a complete identity so it can appear consistently across the app.
  • Invite recipient: Is a downstream persona for the shared link.

User Journey ​

  1. The product explains the value of creating a team and offers either start-now or create-later.
  2. If the organizer deferred creation earlier, the My team area shows an empty state with a primary action to create the team.
  3. The organizer enters a team name and short abbreviation.
  4. The organizer selects a preset color combination and either keeps a generated shield or uploads a custom logo.
  5. The organizer reaches a success/share screen and may distribute the invite link to teammates or skip sharing for now.
  6. The organizer enters the team workspace with a prompt to organize the first match.

Functional Requirements ​

Team Creation Entry ​

  1. The team-intro screen shall explain that the user is creating a club identity for their group.
  2. The user shall be able to begin team creation immediately or defer it.
  3. If team creation is deferred, the My team destination in the main navigation shall remain accessible.
  4. When the organizer opens My team without an existing team, the screen shall show an empty state that explains no team exists yet and prompts the organizer to create one.
  5. The empty-state primary action shall launch the team creation flow.

Team Identity Wizard ​

  1. The team wizard shall collect the team name before any other team-specific attribute.
  2. Team name shall support free text with a visible character limit of 18 characters.
  3. Team abbreviation shall be uppercase and capped at 3 characters.
  4. The primary action shall remain disabled until the current step has enough data to continue.
  5. The color step shall offer preset pairings of primary and secondary brand colors.
  6. The logo step shall support either a generated shield based on abbreviation/colors or an uploaded custom image.
  7. Custom logo uploads shall accept JPG, PNG, and SVG files up to 5 MB.
  8. The user shall be able to move backward through the wizard without losing already entered values.

Team Creation Outcome ​

  1. Completing the wizard shall create a current team and assign the creator as its primary administrator.
  2. The created team shall start with a single organizer.
  3. The newly created team shall become selectable as the current team and the default team if no default exists yet.
  4. Team creation shall initialize the team without an active match.

Post-Create Share Flow ​

  1. The final onboarding screen shall confirm that the team is ready.
  2. The organizer shall be able to share the team invitation through WhatsApp, Telegram, email, or copy-to-clipboard.
  3. Team invitation links shall embed a token tied to the created team and valid for 24 hours.
  4. A valid team invitation token shall support unlimited registrations during its 24-hour validity period.
  5. The organizer shall be able to skip the invitation step and continue directly into the team workspace.
  6. Leaving the post-create screen, whether by sharing or skipping, shall create a push and in-app notification prompting the organizer to organize the first match. This notification shall persist until the first match is organized.
  7. Leaving the post-create screen shall route the organizer into the team workspace rather than a neutral dashboard.

Business Rules and Permissions ​

  • Team creation implies organizer ownership of the created team.
  • Team name is required; abbreviation is required before leaving the abbreviation step.
  • Team abbreviation is cosmetic in MVP and does not need to be unique.
  • Colors and logo are identity choices; a generated default is allowed if no custom logo is uploaded.

UX Considerations ​

  • The team setup flow should feel celebratory and brand-forward, not like a dense admin form.
  • The team abbreviation should be previewed against the selected colors so the user sees the identity emerge before the final step.
  • Share actions should feel native to how amateur groups actually coordinate, with messaging apps prioritized over generic link handling.
  • The My team empty state should make the missing-team condition obvious while keeping the next action singular and high-confidence.

Error States ​

  • The team wizard shall preserve all entered identity data until creation succeeds. If the final create call fails, the organizer remains in the wizard with retry and no success state is shown.
  • If a custom logo upload fails after file validation passes, the user shall see an inline error and may retry the upload or continue with the generated shield without losing the rest of the team draft.
  • Team creation shall be atomic from the user's point of view: the success/share screen appears only after the team, organizer ownership, and current-team selection are all committed.
  • If the native share target is unavailable or share-sheet launch fails, the invite screen shall still expose copy-to-clipboard and the same invite link shall remain retrievable from the team workspace without minting a new token.
  • Repeated taps or concurrent create attempts shall not produce duplicate teams. Additional submits while creation is already in flight must be ignored or merged into the same request.