Development plan based on market research, forums and user pain points. Priorities are set by problem frequency and potential impact.
Overall progress
10%
Done
2
of 21 features
✓ Core
2/2
Phase 1
0/5
What the market confirmed
🏃
Running to the laptop
The need for operators to leave their post and go to the PC by the controller — the most common pain point in forums.
🔒
Vendor lock-in
Users can't extract data from controllers; a technician must come on-site.
🔧
DIY explosion
Mass building of custom solutions (Arduino, RPi, WLED) — a clear signal of unmet demand.
💸
Subscription fatigue
Competitors charge per sport separately with USB dongles. "Subscription free" is the main competitor selling point.
📊
Proof of display for sponsors
Brands spend large amounts and receive vague estimates. The biggest untapped opportunity.
Feature plan
✓
✓ Core
2/2
1
Operator must physically access the PC by the controllerRemote control from mobile/tablet
✓ CoreHigh
2
Brand controller lock-in (vendor lock-in)Universal LED controller compatibility
✓ CoreHigh
1
Phase 1
0/5
3
Wrong information on screen is publicly visibleQuick undo + confirmation for critical changes
Phase 1High
4
Operators are non-technical volunteers who change every seasonMaximally simple UI + demo/practice mode
Phase 1High
5
Lag when updating liveLow-latency display optimization
Phase 1High
6
Connection loss = loss of control / black screenLocal fallback + clear connection status indicator
Phase 1High
7
What the screen shows when there is no matchIdle/standby states and default display
Phase 1Medium
2
Phase 2
0/9
8
One person does everything; tournaments need multiple operatorsRoles and permissions for multiple simultaneous operators
Phase 2High
9
Different sports have different scoreboardsSport templates (football, basketball, handball…)
Phase 2High
10
Clubs want their own visual identityTemplate and theme editor (logo, colors, layout)
Phase 2Medium
11
Outdated, hard-to-read graphicsSet of modern, readable templates
Phase 2Medium
12
Buyer doesn't know if the system works with their hardwareCatalog of tested controllers and screens
Phase 2Medium
13
The screen is more than just scoresContent type library (players, messages, announcements)
Phase 2Medium
14
Emergency and safety messages must be instantQuick button for emergency and safety messages
Phase 2Medium
15
New operators need training every seasonBuilt-in guide / interactive onboarding
Phase 2Low
16
Manual ad switching distracts the operatorAd scheduling and automatic rotation
Phase 2High
3
Phase 3
0/5
17
Sponsors have no proof the ad was shownDisplay reports (rotations, duration, QR engagement)
Phase 3High
18
Large stadiums: multiple screens, fragmented controllersMulti-screen management from one application
Phase 3Medium
19
Streaming: manual sync, OCR workaroundsScore data export for stream overlay (API)
Phase 3Medium
20
Manual time/score entry lags behind the gameIntegration with league systems / referee devices
Phase 3Low
21
Screen faults (dead pixels, brightness)Diagnostics: test-pattern, status, brightness control
Phase 3Low
Development phases
Phase 1
Consolidate the core
Remote control and hardware independence work flawlessly, and the app is simple enough for anyone to operate. Focus on reliability and error prevention.
Phase 2
Differentiation
Outperform competitors on their weaknesses. Roles, sport templates, modern design and branding. StadiumBoard stops being "just another scoreboard".
Phase 3
Growth and monetization
Sponsor display reports turn StadiumBoard from a cost into a revenue tool for clubs. Multi-screen management and streaming integration open new markets.
Pricing note
Research shows two strong aversions: per-sport licensing and subscription fatigue. The goal is one license for all sports, with an optional subscription add-on only for advanced features (e.g. sponsor reports).