A

Running Crew Operations Manager

3.70

Derivation Chain

Step 1 Marathon running boom
→
Step 2 Surge in running crew organizations
→
Step 3 Administrative burden on crew operators

Problem

As running crews (clubs) surge nationwide, crew leaders and managers handle member management (attendance checks, fee collection, group race applications, group running course sharing) through a mix of KakaoTalk group chats, Excel, and Naver Cafes. For crews with 50+ members, attendance tracking alone takes 3-4 hours per month, unpaid fee tracking 2 hours per month, and coordinating group race registrations 5-8 hours per race, leading to manager burnout as a major cause of crew disbandment.

Solution

A crew-specific mini app (Kakao Mini App or PWA) that integrates QR attendance check-in, automatic fee payment and unpaid alerts, group race registration forms, GPS-based group running course sharing with real-time location tracking, and monthly crew activity reports (total distance, participation rate, personal records).

Target: Crew leaders and managers of running crews with 20-200 members, located in the Seoul metropolitan area and major cities, holding regular runs 1-3 times per week.
Revenue Model: Premium at 19,000 KRW per crew per month (approx. $14) (free basic plan for up to 30 members; paid includes unlimited members, fee management, race registration, and reports). Group race registration service fee: 1,000 KRW per person (approx. $0.75).
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (72%)

Tech Complexity
29.3/40
Data Availability
23.1/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (57/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
16.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
12.0/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Frontend [medium] Backend [medium] Infrastructure [low]
Dashboard