wip
This commit is contained in:
283
docs/concept/COMPETITION.md
Normal file
283
docs/concept/COMPETITION.md
Normal file
@@ -0,0 +1,283 @@
|
||||
# GridPilot Competition & Unique Selling Points
|
||||
*Why GridPilot matters — and why it fills the biggest gap in iRacing league racing.*
|
||||
|
||||
---
|
||||
|
||||
# 1. What iRacing Leagues Are Missing
|
||||
|
||||
iRacing does many things extremely well:
|
||||
- great cars
|
||||
- great physics
|
||||
- huge official participation
|
||||
- excellent netcode
|
||||
|
||||
But iRacing does **not** provide:
|
||||
- long-term driver identity
|
||||
- league structure
|
||||
- team championships
|
||||
- personalized stats
|
||||
- season history
|
||||
- league discovery
|
||||
- automated standings
|
||||
- protest/penalty workflows
|
||||
- a centralized competition ecosystem
|
||||
|
||||
Everything around league racing is **outsourced to Discord chaos**.
|
||||
|
||||
GridPilot fixes the layer iRacing ignores.
|
||||
|
||||
---
|
||||
|
||||
# 2. The Competition Layer iRacing Never Built
|
||||
|
||||
GridPilot becomes the competition universe for league racing:
|
||||
|
||||
### **Drivers get**
|
||||
- a racing identity
|
||||
- a real profile that spans leagues
|
||||
- season standings that matter
|
||||
- team championships
|
||||
- points that persist
|
||||
- stats that make progress visible
|
||||
|
||||
### **Admins get**
|
||||
- reliable standings
|
||||
- structured schedules
|
||||
- automated results
|
||||
- clean sign-up flows
|
||||
- real competition formats
|
||||
|
||||
### **Leagues get**
|
||||
- a professional home
|
||||
- discoverability
|
||||
- branding
|
||||
- stable structure
|
||||
|
||||
This is something **no existing tool** provides in a unified way.
|
||||
|
||||
---
|
||||
|
||||
# 3. What Others Do (and Why It’s Not Enough)
|
||||
|
||||
### **SimRacerHub**
|
||||
- ancient UI
|
||||
- manual CSV uploads
|
||||
- no identity
|
||||
- no automation
|
||||
- no team competition
|
||||
- no discovery
|
||||
- no long-term profiles
|
||||
|
||||
### **Discord + Google Sheets**
|
||||
- disorganized
|
||||
- non-scalable
|
||||
- everything is manual
|
||||
- error-prone
|
||||
- no identity
|
||||
- no automation
|
||||
- no trust system
|
||||
- no visibility
|
||||
|
||||
### **iRacing Official Series**
|
||||
- random grids
|
||||
- no personal connection
|
||||
- no ladder
|
||||
- no league-style competition
|
||||
- no teams (beyond 1-car teams)
|
||||
- no season identity
|
||||
|
||||
### **SimGrid (ACC)**
|
||||
- not for iRacing
|
||||
- no automation
|
||||
- not deeply connected to semiprofessional league structures
|
||||
|
||||
### **LFM**
|
||||
- matchmaking, not league management
|
||||
- no season identity
|
||||
- not for iRacing
|
||||
- no team championship
|
||||
- no admin tooling
|
||||
|
||||
**Conclusion:**
|
||||
There is *no* product that unifies the league racing ecosystem for iRacing.
|
||||
|
||||
GridPilot is literally the **first** to do this properly.
|
||||
|
||||
---
|
||||
|
||||
# 4. What GridPilot Does That Nobody Else Can
|
||||
|
||||
## **1. Clean, automatic league infrastructure**
|
||||
- standings
|
||||
- results
|
||||
- rosters
|
||||
- seasons
|
||||
- scoring
|
||||
- team formats
|
||||
|
||||
Nobody else automates this end-to-end.
|
||||
|
||||
---
|
||||
|
||||
## **2. Real Constructors-Style Team Championships**
|
||||
iRacing has:
|
||||
- only one driver per car
|
||||
- no parallel team scoring
|
||||
- no true team competition
|
||||
|
||||
GridPilot:
|
||||
- multiple drivers race for one team
|
||||
- all points count
|
||||
- teams gain prestige across seasons
|
||||
|
||||
This completely changes how league racing feels.
|
||||
|
||||
---
|
||||
|
||||
## **3. Unified Driver Identity Across Leagues**
|
||||
Drivers currently:
|
||||
- disappear between seasons
|
||||
- have no home
|
||||
- no stats
|
||||
- no history
|
||||
|
||||
GridPilot gives them:
|
||||
- permanent stats
|
||||
- history
|
||||
- standings
|
||||
- cross-league progression
|
||||
- consistent profile
|
||||
|
||||
This becomes the **center of their virtual racing career**.
|
||||
|
||||
---
|
||||
|
||||
## **4. Structured Complaints & Penalties**
|
||||
Other platforms:
|
||||
- use DMs
|
||||
- use Discord
|
||||
- lose messages
|
||||
- inconsistent punishment
|
||||
- emotional chaos
|
||||
|
||||
GridPilot:
|
||||
- structured forms
|
||||
- timestamps
|
||||
- clear penalty tools
|
||||
- automatic standings update
|
||||
|
||||
This makes leagues feel *fair* — a huge USP.
|
||||
|
||||
---
|
||||
|
||||
## **5. Season creation without busywork**
|
||||
Admins normally spend hours on:
|
||||
- session creation
|
||||
- spreadsheets
|
||||
- messaging
|
||||
|
||||
GridPilot:
|
||||
- automates results
|
||||
- simplifies sessions
|
||||
- cleans up registration
|
||||
- centralizes everything
|
||||
|
||||
It’s the **ultimate league admin QoL platform**.
|
||||
|
||||
---
|
||||
|
||||
# 5. Why Drivers Should Sign Up
|
||||
|
||||
**Because racing finally means something.**
|
||||
|
||||
GridPilot gives drivers:
|
||||
- season standings
|
||||
- long-term stats
|
||||
- team championships
|
||||
- identity
|
||||
- clarity
|
||||
- professionalism
|
||||
- an organized home for their racing
|
||||
|
||||
No more guessing, no more chaos — a place to grow and compete.
|
||||
|
||||
---
|
||||
|
||||
# 6. Why Admins Should Use GridPilot
|
||||
|
||||
**Because running a league shouldn’t be a full-time job.**
|
||||
|
||||
GridPilot:
|
||||
- removes the boring work
|
||||
- automates the repetitive tasks
|
||||
- enforces structure
|
||||
- keeps standings clean
|
||||
- removes spreadsheet pain
|
||||
- prevents drama
|
||||
- makes their league look professional
|
||||
|
||||
Admins feel supported instead of overwhelmed.
|
||||
|
||||
---
|
||||
|
||||
# 7. Why GridPilot Will Become THE Platform
|
||||
|
||||
GridPilot combines:
|
||||
|
||||
- **admin tools**
|
||||
- **driver identity**
|
||||
- **team championships**
|
||||
- **competition structure**
|
||||
- **automated results**
|
||||
- **clear season organization**
|
||||
- **discovery & visibility**
|
||||
|
||||
This creates a **complete ecosystem**, not just a tool.
|
||||
|
||||
When multiple leagues use it → drivers collect universal stats.
|
||||
When drivers collect stats → teams form around them.
|
||||
When teams form → prestige and competition grow.
|
||||
When prestige grows → more leagues join.
|
||||
|
||||
This creates a **network effect** no other platform has.
|
||||
|
||||
---
|
||||
|
||||
# 8. Simple Value Summary (ideal for landing page)
|
||||
|
||||
### For Drivers:
|
||||
- real competition
|
||||
- season identity
|
||||
- long-term stats
|
||||
- team championships
|
||||
- one place for all leagues
|
||||
|
||||
### For Admins:
|
||||
- less work
|
||||
- no spreadsheets
|
||||
- clean sign-ups
|
||||
- automatic standings
|
||||
- proper penalty tools
|
||||
- professional league branding
|
||||
|
||||
### For the Community:
|
||||
- a central home
|
||||
- simple discovery
|
||||
- fair competition
|
||||
- consistent rules
|
||||
- real history
|
||||
|
||||
---
|
||||
|
||||
# 9. Why You Should Sign Up Early
|
||||
|
||||
Because:
|
||||
- early leagues define the meta
|
||||
- early drivers get full season history
|
||||
- early admins help shape the platform
|
||||
- you get modern tools for free during beta
|
||||
- you’re part of the first proper iRacing league ecosystem
|
||||
- you want league racing with meaning, structure, and clarity
|
||||
|
||||
GridPilot is the **competition layer iRacing never built —
|
||||
and the league ecosystem drivers always wanted.**
|
||||
Reference in New Issue
Block a user