# CBB Project Brief: Match Stage Planner & Shooter Analytics
**Status:** Concept
**Destination:** ScopeDOPE feature (competition-workflow module within the ScopeDOPE product; stays in the `ScopeDOPE/` namespace)
**Tier:** 2 — Strong Candidate
**Classification:** Internal — Confidential
**Version and date:** see Revision Control Block at the end of this document

---

## Summary

A competition-specific module within ScopeDOPE™ that covers the complete match day workflow: pre-stage planning (target distances, engagement sequence, hold planning), in-stage operation (minimized UI for quick hold lookup during a 90-second window), and post-match analytics (hit rate by distance, stage performance, improvement over time). This builds on the "Match Stage Mode" item already identified in SCOPEDOPE_STRATEGIC_OPPORTUNITIES.md and expands it into a complete competition workflow. It is the feature that makes ScopeDOPE the tool for competitive shooters, not just a tool used by competitive shooters.

---

## Problem Statement

The NRL22 and PRS competition workflow has three distinct phases that current ballistic apps address poorly:

**Pre-stage briefing:** A competitor walks a stage and records target distances, positions, and required holds. Today this is done in a notebook or the stock notes app on their phone. There is no tool that lets them record this, compute holds from their DOPE, and organize it for reference at the firing point.

**On the clock:** During a 90-second stage (NRL22) or timed engagement (PRS), a competitor needs to recall holds quickly — often under physical stress, with a timer running. A cluttered ballistic app UI is a liability. Competitors who fumble with their phone during a stage lose time and make errors.

**Post-match review:** At the end of a match, most competitors have no structured way to review their performance — which stages they hit well, which distances they consistently miss, what environmental conditions correlated with their best and worst performances. This analysis is done in memory, if at all.

---

## Product Concept

### Core Features (v1.0)

**Stage Builder (pre-match)**
- Create a match: name, date, location, weather (auto-populated from WeatherFlow if connected)
- Add stages: stage name, target count, distance to each target, par time
- For each target: CBB auto-computes the hold from current DOPE — elevation (MRAD/MOA) and a reference wind hold (per MPH)
- Notes per target: position required, any specific considerations
- Export stage as a printable card or share to ScopeDOPE Stage Mode

**Stage Mode (on the clock)**
- Full-screen, minimal UI: large text, maximum contrast, glanceable
- Swipe between targets
- One tap: "Mark hit" / "Mark miss"
- Hold display: elevation only, with configurable wind hold quick-add
- No navigation, no settings access, no distractions — only the current target's hold and the hit/miss tracker
- Offline-first: stage data pre-loaded, no network required during a stage

**Post-Match Analytics**
- Match summary: total hits, total misses, hit rate by distance, hit rate by target type
- Stage comparison: which stages scored best/worst, where does the shooter lose points
- Trend view: hit rate over time across matches (requires multiple matches entered)
- Environmental correlation: "Your hit rate in wind conditions above 10 MPH is 12% lower — calibrate your wind calls"
- Export: share match result summary as a social card (optional)

### v2.0 Features
- Club Management integration: if the club uses the CBB Club SaaS (Brief #02), stage distances auto-import from the match setup — no manual entry at the stage
- Head-to-head: compare your stage performance against a teammate or training partner (both must opt-in)
- Coach view: a coach with permission sees a student's stage-by-stage analytics
- Shot timer integration (if phone mic-based timer APIs are available)

---

## Target User

**Primary:** Active NRL22 and PRS competitors — the same core demographic as ScopeDOPE. A shooter who uses ScopeDOPE for DOPE management and uses the Stage Planner for match day has a complete competition workflow inside one app.

**Secondary:** Three-gun, USPSA, and other precision-timed shooting sport competitors who have similar "hold list + on-the-clock" workflows.

---

## Revenue Model

**Included in ScopeDOPE** at no additional charge. This is the competition-specific depth feature that justifies the "Ballistic Computer" positioning against competitors who only offer "Ballistic Calculator" functionality. No competitor has a match-day workflow.

**Indirect value:**
- Competition shooters are high-engagement users who drive word-of-mouth
- A user whose complete match day is inside ScopeDOPE is a deeply retained user
- Club Management integration (Brief #02) creates a two-way pipeline: club data flows into ScopeDOPE Stage Mode, ScopeDOPE analytics feed back into club reporting

---

## Strategic Fit with CBB / ScopeDOPE

**The competitive differentiation argument:** ScopeDOPE's tagline is "Ballistic Computer" vs. competitors' "ballistic calculator." The Stage Planner is the feature that proves that claim — a ballistic calculator tells you a number; a ballistic computer runs your match day. No competitor has this. This is the feature that generates the "I couldn't have hit that stage without it" testimonials that drive community word-of-mouth.

**Club Management flywheel:** When the Club Management SaaS (Brief #02) exists, stage distances flow automatically from the club's match setup into a competitor's ScopeDOPE Stage Mode. The two products reinforce each other: club directors who use the SaaS naturally recommend ScopeDOPE to their members, and ScopeDOPE members who use Stage Mode naturally use clubs that have the SaaS.

**Analytics data:** Post-match hit/miss data by distance is a high-quality contribution to the DOPE database. A shooter who marks hits and misses in Stage Mode is generating validated impact data that strengthens the DOPE-Blend™ calibration.

---

## Competitive Landscape

| Product | Pre-stage planning | Match-day UI | Post-match analytics | DOPE integration |
|---|---|---|---|---|
| Applied Ballistics Mobile | ✗ | ✗ | ✗ | Limited |
| Hornady 4DOF | ✗ | ✗ | ✗ | ✗ |
| PractiScore | ✗ | Score entry only | Limited | ✗ |
| Generic notes apps | Manual | Poor | ✗ | ✗ |
| **ScopeDOPE Stage Planner** | **✓** | **✓** | **✓** | **✓** |

No ballistic app has a competition workflow. This is uncontested.

---

## Technical Overview

**Platform:** ScopeDOPE module (iOS + Android)

**Data model:**
- `Match` → has many `Stages`
- `Stage` → has many `Targets` (distance, position notes, hold_computed, hit_miss_result)
- `Hold` → computed from current DOPE session for the rifle+ammo combination active at match time
- `MatchAnalytics` → aggregated hit/miss stats, computed post-match

**Key technical considerations:**
- Stage Mode must work completely offline — no network calls during a stage
- Hold computation at stage briefing time: use the DOPE table as of the moment the stage is built; don't recompute live during the stage
- Analytics: computed locally, optionally synced to web companion
- DOPE database contribution: if user opts in, stage hit/miss data at each distance is contributed to the aggregate DOPE database with the session's environmental data

**Complexity estimate:** Medium. The data model is straightforward. Stage Mode UI requires careful design (glanceability under pressure is a design problem, not an engineering problem). Analytics computation is simple aggregate math.

---

## Go-to-Market

**Feature announcement:** "ScopeDOPE now has a match day mode — build your stage holds from your DOPE, run the stage, review your performance." Post in NRL22 Facebook Group and Sniper's Hide with a video demo of the Stage Mode UI.

**Club integration hook:** "If your club uses CBB Club Management, stage distances import automatically." This gives the Club SaaS a direct product hook into the most active segment of the ScopeDOPE user base.

**Analytics as social proof:** Build a shareable match result card ("Hit 72% overall. Best distance: 200 yards (100%). Worst: 400 yards (44%). — ScopeDOPE"). Competitive shooters share this kind of performance data on social media.

---

## Success Metrics

| Metric | 6-month | 12-month |
|---|---|---|
| ScopeDOPE users who create at least one match | 20% | 40% |
| Stages created per active user per month | 2 | 4 |
| Stage Mode engagement during competition (opens on match day) | Trackable | Trending up |
| Post-match analytics views | 60% of matches created | 75% of matches created |

---

## Risks & Mitigations

| Risk | Likelihood | Mitigation |
|---|---|---|
| Stage Mode UI fails under pressure — too complex during a 90-second stage | High | Extensive UX testing with NRL22 competitors before release; prioritize simplicity over features |
| Hit/miss data entry during a stage is too much cognitive load | Medium | Make hit/miss optional — Stage Mode works fine without it; analytics just don't populate |
| Stage data entry (distances, positions) is tedious without club import | Medium | Build a quick-add flow: distance entry is a single number field with the keyboard auto-open |

---

## Resource Requirements

- 1 developer (Jason) — 4–6 weeks for Stage Builder + Stage Mode
- Additional 2–3 weeks for analytics
- UX design: significant — Stage Mode must be usable under competition stress; test with real users before shipping
- No new infrastructure

---

## Recommended Timing

**ScopeDOPE v1.5 or v2.0.** Not a launch feature but a high-priority first update. The Stage Planner is the feature that transitions ScopeDOPE from "app I use before a match" to "app I use all day at a match." That transition dramatically increases engagement and retention. Design Stage Mode concurrently with ScopeDOPE v1.0; build immediately after launch.

---

## Open Questions

- Should Stage Mode allow the user to adjust holds in real time (update the wind call on the fly)? Recommendation: yes, as an optional overlay — swipe right to show wind adjustment, swipe left to hide. Default view shows only the computed hold.
- Should post-match analytics require the CBB Community Account (for sync and history) or work locally? Recommendation: local only for v1.0; sync to web companion as v2.0 feature.
- How does Stage Mode handle stages where the user doesn't know the distance in advance (unknown distances)? Recommendation: "unknown distance" flag on a target — DOPE is not pre-computed; user enters distance at the firing point.

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/ScopeDOPE/03_-_Confidential/Product_Strategy/CBB_BRIEF_12_MATCH_STAGE_PLANNER.md` |
| **Cross-references** | `CBB_PROJECT_BRIEFS_TOC.md` |
| **Created** | 2026-06-02 |
| **Last updated** | 2026-06-09 |
| **Next full review due** | 2027-06-02 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|-------|
| 0.9 | 2026-06-02 | jschwefel | — | — | Initial release |
| DRAFT | 2026-06-09 | Claude (Opus 4.8) | — | — | Fixed "DOPE-blend"→"DOPE-Blend™" per BRAND_LEGAL_LANGUAGE_GUIDE; applied ™ to first use of ScopeDOPE. Portfolio pass (same date): removed header version number (→ Status/Destination + revision-block pointer); added Destination tag (ScopeDOPE feature). |
