TwoMore Market And Revenue Research
Status: Active Last researched: 2026-06-27
This document is the source-backed market brief for TwoMore's roadmap and revenue thinking. It should not be read as a financial forecast. Treat all pricing and revenue lines as hypotheses until pilot clubs, payment rails, legal review, and production usage data validate them.
Use this with:
- App Functionality Map for what the app currently delivers.
- Product Spec Sheet for product boundaries and success metrics.
- Roadmap for sequencing and acceptance gates.
- Roadmap Implementation Plan for concrete slices under each roadmap track.
- Sports Club Administration Opportunity Audit for the app-to-market improvement map and Organizer Operations slice plan.
Research Question
Can a Korean amateur-tennis club operating system become a revenue-producing product, and where should it compete first?
Short answer: yes, but the best wedge is not direct court booking first and not a generic chat replacement. The more defensible wedge is reducing the weekly work of club admins and pickup hosts: sessions, RSVP, fees, attendance, trust, records, guest flow, and shareable growth.
Source Refresh
| Source | Fresh signal | Implication for TwoMore |
|---|---|---|
| MCST 2025 National Sports Participation Survey summary | Korea's latest national sports participation survey reports 62.9% weekly participation, 9,000 surveyed residents, high public-facility use, KRW 62,000 average monthly sports spend, and time/access barriers. | Market exists, but the app must reduce friction instead of assuming users want more content. |
| Kakao IR earnings page and 1Q25 Kakao presentation | Kakao reports roughly 49M domestic KakaoTalk MAU and positions KakaoTalk as the No. 1 messenger in Korea. | TwoMore should integrate with Kakao habits, not try to replace group chat on day one. |
| BAND official site | BAND positions itself as free group communication for sports teams and communities with messages, calendar, polls, attendance, and chats. | Generic group tools already cover communication, so TwoMore must win on tennis operations and records. |
| CourtReserve pricing/features and CourtReserve AI info | Racquet-club SaaS bundles booking, public booking, lessons, memberships, invoicing, POS/payments, mobile app, leagues/ladders, and integrations. | Mature revenue paths are credible, but CourtReserve is facility-first; TwoMore can stay club-community-first. |
| Playtomic Manager and Playtomic pricing | Playtomic has a large racket-sports network and tiered club plans around booking, payments, tournaments, leagues, classes, reporting, memberships, POS, and coach booking. | Direct booking can be valuable later, but it requires venue supply and operational density. |
| TeamSnap pricing | TeamSnap monetizes team management with free, premium, ultra, and quoted business tiers, including scheduling, messaging, RSVP, assignments, payments, and org-wide management. | Team operations are a proven software category; TwoMore should specialize rather than generalize. |
| OpenSports pricing | OpenSports prices recreational group, full-time club, and premium tiers and includes event setup, registration, payments, waivers, waitlists, reports, memberships, leagues, and tournaments. | Event/session operations can carry subscription value before venue marketplace scale. |
| Spond payment costs | Spond documents transaction-cost handling and lets groups decide whether the group or members absorb payment costs. | TwoMore needs transparent fee policy and admin/member cost controls before real payments. |
| PortOne V2 docs | PortOne documents Korean payment integration, server-side data, supported PG/payment methods, and webhook/payment infrastructure. | Real monetization is gated on production payment verification, webhook smoke, refund/support policy, and merchant terms. |
| SMASH Google Play and SMASH App Store | SMASH emphasizes tennis friend finding, matching, lessons, location/time/skill filters, and app chat. | Korean tennis matching is a live category, but matching alone is not the same as club operations. |
| Baceline App Store | Baceline lists tournaments, court booking, friend finding, ranking, payment, AI skill measurement, and video/highlight tools. | Some Korean tennis apps are moving toward broad player platforms; TwoMore should compete on club admin depth. |
| TeChinSo App Store | TeChinSo positions itself as free tennis matching/community with review-based NTRP/trust. | Free matching creates price pressure; paid value must be organizer-side or payment/operations-side. |
| Modo tournament bracket Google Play and KDK bracket Google Play | Korean app-store tools support tennis brackets, doubles/KDK formats, score entry, ranking, player lists, and tournament history. | Bracket/ranking tools are point solutions; TwoMore should integrate match flow into club/session lifecycle. |
Competitor Landscape
| Segment | Examples | Strength | Gap TwoMore can attack |
|---|---|---|---|
| Korean default coordination | KakaoTalk, Kakao Open Chat, BAND, spreadsheets, bank transfer | Habit, free distribution, low adoption friction. | Weak structured RSVP, fee tracking, score/attendance records, trust, admin exception handling, and reusable club data. |
| Korean tennis matching and court apps | SMASH, Baceline, Tennis Friends, TeChinSo | Player discovery, partner matching, court finding/booking, chat, sometimes lessons/ranking. | Usually player-first. Club admin workflows, dues, attendance, fee confirmation, guest approval, and records tied to real club sessions are less central. |
| Tournament/bracket tools | Modo brackets, KDK bracket manager, Winner-style tournament managers | Fast bracket generation, score entry, tournament history, doubles formats. | Point-solution behavior. They do not own onboarding, club membership, payment status, weekly sessions, trust, and recurring retention. |
| Global racquet/facility SaaS | CourtReserve, Playtomic | Booking, facility scheduling, POS/payments, memberships, lessons, leagues, reporting, player app. | Facility-first, often heavier and less Korea/community-specific. Requires venue/operator adoption before player network effects. |
| General team-management apps | TeamSnap, Spond, OpenSports | Scheduling, RSVP, communication, payments, event registration, group/club tiers. | Multi-sport generic. They lack tennis-specific rotations, match board, ratings, TMI/weather context, Korean terminology, and Korean legal/payment assumptions. |
| Rating/competition networks | UTR Sports and similar | Ranking identity, events, competition layer. | Less focused on the day-to-day 총무 workflow and Korean local club operations. |
Strategic Positioning
TwoMore should not position itself as "another tennis matching app."
Better positioning:
The operating layer for Korean amateur tennis clubs and pickup hosts.
This makes the competitive frame narrower and more defensible:
- Kakao/BAND are distribution and communication layers, not operational systems.
- Matching apps are demand/supply discovery layers, not retained club operating records.
- Bracket tools are event utilities, not a weekly club cockpit.
- Facility SaaS is a later expansion, not the v1 wedge.
Revenue Potential
Revenue should follow trust and retained operations. The app already has many capabilities that can support revenue later: club/session management, payment state, dues, guest applications, attendance, records, messaging, share routes, PortOne scaffolding, and subscription shells. The risk is not lack of monetizable surface. The risk is charging before users trust the workflow.
Recommended Revenue Order
| Order | Revenue line | Why it fits | Gate before charging |
|---|---|---|---|
| 1 | Club/admin subscription | Organizer pain is recurring and business-like: sessions, RSVP, fees, attendance, guest apps, reports, dues, and records. | Retained pilot clubs, admin dashboard proof, support process, clear free/paid boundary. |
| 2 | Participation-fee/payment convenience | The app already models manual fees and mock checkout; payment value is close to session operations. | PortOne test channel, webhook/idempotency smoke, refund/support policy, fee disclosure, legal review. |
| 3 | Dues automation | Club dues are recurring and admin-heavy, but higher trust than one-off sessions. | Payment rail, ledger clarity, member notification, refund/correction flow. |
| 4 | Premium organizer analytics/export | Attendance, no-shows, payment exceptions, member reliability, session utilization, and club growth are admin-visible value. | Enough real data volume and admin interviews proving willingness to pay. |
| 5 | Player premium identity/stats | Records, leaderboards, achievements, stat cards, and profile identity can support optional player value. | Avoid splitting the one app-facing rating; prove recurring player retention first. |
| 6 | Venue/court booking handoff or commission | Venue booking can be valuable, but only after venue supply and canonical court data are strong. | Pilot venue partners, booking support workflow, settlement/refund policy. |
| 7 | Coaching/brand marketplace | Player intent and records could generate leads for coaches/equipment/brands. | Retained clubs, payment rails, abuse/report flow, ad disclosure, partner ops. |
Pricing Hypotheses
These are starting points for interviews and pilots, not commitments.
| Package | Hypothesis | Validation question |
|---|---|---|
| Free club | Basic club profile, member list, one or limited active session, manual RSVP, public share. | Does this activate enough clubs without giving away admin value? |
| Organizer Pro | KRW 19,000-49,000/month per active club for unlimited sessions, admin cockpit, payment-state tracking, attendance/no-show tools, guest approvals, and share analytics. | Will 총무 pay personally or collect from members to reduce weekly admin work? |
| Club Operations Plus | KRW 79,000-149,000/month for larger clubs with dues automation, exports, reports, priority support, advanced roles, and richer analytics. | Are bigger clubs materially different from casual clubs in willingness to pay? |
| Payment fee | Pass-through PG costs plus a transparent platform fee or fixed convenience fee only after PortOne production proof. | Who should absorb the fee: club, host, or player? |
| Player premium | KRW 1,900-4,900/month for cosmetic stat/profile/share enhancements only after records retention is proven. | Is player willingness to pay independent of club admin value? |
| Venue/coach lead | Commission or lead fee after manual pilots. | Can TwoMore generate qualified demand without degrading trust? |
External pricing anchors support the shape, not the exact KRW numbers:
- TeamSnap has free, paid team tiers, and custom business tiers for larger organizations.
- OpenSports publishes recreational group, full-time club, and premium monthly tiers, with payments/events/memberships/leagues as paid operational value.
- CourtReserve and Playtomic show racquet-sports operators paying for booking, payments, memberships, events, leagues, POS, and player experience.
- Spond shows that group-payment products need explicit transaction-fee handling and member/group fee responsibility.
Revenue Scenarios
These scenarios are planning instruments. Replace them with real cohorts after pilot data exists.
| Scenario | Assumption | Monthly gross revenue signal |
|---|---|---|
| Pilot proof | 10 paying clubs at KRW 29,000/month. | KRW 290,000/month: not meaningful revenue, but validates willingness to pay. |
| Local traction | 100 paying clubs at KRW 39,000/month plus small payment fees on active sessions. | KRW 3.9M/month before transaction fees: enough to evaluate support and retention load. |
| Regional depth | 500 paying clubs at blended KRW 49,000/month plus dues/session-payment revenue. | KRW 24.5M/month before transaction fees: proves this can become a real SaaS line. |
| Marketplace expansion | Venue/coach/brand revenue layered only after retained club base and payment trust. | Treat as upside, not core v1 revenue. |
The most important number in early revenue is not top-line MRR. It is retained clubs that would be upset if the admin workflow disappeared.
Adversarial Risks
| Risk | Why it matters | Mitigation |
|---|---|---|
| Kakao/BAND inertia | Users already coordinate there for free. | Use Kakao/share as distribution; make TwoMore the structured system of record. |
| Matching apps create free expectations | TeChinSo-style free matching and SMASH-style discovery can depress player-side willingness to pay. | Charge organizer/admin value first, keep player activation low-friction. |
| Venue booking is supply constrained | Booking marketplace needs operator adoption, inventory, settlement, and support. | Start with venue context and booking handoff; only build direct inventory after pilots. |
| Payment trust burden | Money errors create support, refund, and legal exposure. | Keep manual payment until PortOne verification/webhook/refund/support gates are closed. |
| Casual clubs may not pay | Some groups will tolerate spreadsheet/manual work. | Segment by club size, admin workload, paid sessions, dues, and session frequency. |
| Generic team apps can copy primitives | Scheduling, RSVP, and chat are not enough. | Defend with tennis-specific operations: rotations, match board, rating/records, trust, TMI, Korean club terminology. |
| Privacy/safety failures hurt trust | Profiles, payments, reports, and location data are sensitive. | Keep consent, export/delete, purpose catalog, RLS, and PI lint central to monetization work. |
Roadmap Implications
- Keep R0 Launch Readiness first. No revenue experiment matters if legal/auth/store launch gates are unresolved.
- R1 Club Growth should optimize share/deep-link activation and Kakao-native behavior, not paid acquisition.
- R2 Organizer Operations is the strongest monetization bridge. Build the admin cockpit and prove time saved.
- R3 Real Payments should start with participation-fee trust and dues, not a broad marketplace.
- R4 Venue/Court Platform should begin with data quality and booking handoff.
- R6 Coaching/Brand should remain held until retained club usage and transaction rails exist.
Research Backlog
Before committing pricing or marketplace work, collect:
- 10-15 총무 interviews across club size, fee model, venue type, and session cadence.
- 5 pickup-host interviews focused on guest approval, no-shows, and payment confirmation.
- 3 venue/operator interviews about booking handoff, inventory control, settlement, and support expectations.
- A competitor teardown with installed-app screenshots for SMASH, Baceline, TeChinSo, and Korean bracket tools.
- PortOne merchant pricing/contract confirmation, including refund, virtual account, webhook, and settlement implications.
- Pilot willingness-to-pay tests: monthly admin subscription, per-session fee, and dues automation.
- Support load estimate for payment disputes, guest applications, member reports, and account deletion/export.
Maintenance Rule
Refresh this document when:
- A roadmap item adds or removes a revenue line.
- A competitor materially changes pricing or product direction.
- PortOne/payment assumptions change.
- Pilot-club evidence changes willingness-to-pay assumptions.
- The App Functionality Map moves a revenue-relevant capability from scaffolded to production-ready.
When this document changes, run:
bash
yarn docs:generate
yarn docs:check