Design & Product Strategy Proposal 2026 · Submitted to Swish × Under Armour

Swish League Platform

A product design proposal for building Southeast Asia's first centralized youth basketball infrastructure — the right foundation before any code is written.

See the proposal ↓ View full deck →
Prepared by
MK Agency
Discipline
Design & Development Studio
Agency Head
Manish Kumar ↗
For
Swish Basketball
4
Pilot modules, tightly scoped for maximum traction signal
38–44
Pilot screens across Admin and Guest roles
₹2,00,000
Total investment across Phase 0 and Phase 1
The Situation Today

Youth
Basketball
Has No
Record

Results live in spreadsheets. Player progress lives in coaches' heads. Parents chase updates across WhatsApp. Nothing is documented. Nothing compounds. Every season starts from scratch.

What this costs everyone
01
Coaches lose hours they should spend coaching
Manual record-keeping after every match builds friction until coaches stop doing it at all — and every season's data is lost.
02
Players have no proof of their development
A young athlete who played 3 seasons has nothing verifiable to show scouts, schools, or sponsors. Their effort simply disappears.
03
Swish cannot scale without infrastructure
Expanding to Southeast Asia is impossible when the operational foundation is a group chat, a PDF, and a spreadsheet nobody updates.
How it works today

The Current Workflow Is Broken at Every Step

🏀
Match Played
Score written on paper
Photos posted to Instagram
📋
Coach Updates
WhatsApp group
Maybe a spreadsheet
Sometimes nothing
👨‍👩‍👧
Parent Checks
Line app
WhatsApp
Instagram
Asks another parent
🏫
Sponsor Asks
Gets highlight reel
No verified data
Cannot measure ROI
❓
Season Ends
No historical record
No player data
Reset to zero
Result: a league that cannot prove its own value
This is solvable with the right platform
The Opportunity

Every Major Market Solved This. Southeast Asia Is Wide Open.

Market
Europe
Solved

Structured national leagues with centralized player databases, official stats tracking, and digital athlete profiles that follow players for life.

National infra exists
Market
USA
Solved

EYBL, AAU, and GameChanger provide centralized circuits, consistent tracking, and full exposure infrastructure for youth athletes at every level.

Private platforms dominate
Market
Southeast Asia
Gap exists

Explosive basketball growth. Genuine youth talent. No centralized infrastructure. No tracking. No records. The opportunity is entirely open.

Nobody owns this yet
Swish is positioned to own this gap — if it builds the right infrastructure first
That infrastructure starts here
Case Study 01 · Why Design Wins

HomeCourt Won Because of Design Decisions, Not Technology

Launched 2018 · Apple Design Award 2019
170+
Countries within the first year
25M+
Shots tracked before NBA partnership
Outcome
NBA equity stake 2019. Integrated into NBA youth development globally.
Lesson 01 — Design Drives Adoption
They Designed for the Court, Not the Desk
Before writing a line of code, HomeCourt mapped every user interaction. A coach on a basketball court is standing, one-handed, under pressure. That mapping produced a product 170 countries adopted instantly. Without it, it would have been another app nobody used.
Lesson 02 — Data Must Tell a Story
Data Designed as Progress Made Coaches and Players Feel It
The same data another app showed as a table, HomeCourt designed as a progress journey. Coaches saw their players improving. Players felt their effort was building something. Parents saw proof their investment was working. That emotional design is what the NBA paid for.
Lesson 03 — Profiles Create Identity
A Player Profile Designed as an Athlete's Passport
They designed verifiable profiles that coaches could share with scouts and parents could show with pride. This was a design decision, not a feature — and it turned a utility app into something athletes genuinely cared about preserving across seasons.
For Swish
Swish Needs the Same Translation
Technology creates the data. Design creates the meaning. Coaches need stats designed as insights. Parents need progress designed as proof. Every flow must be mapped before Swish's developer writes a single line — or the same data becomes noise.
The Lesson
HomeCourt proved that designing user flows completely before building is what separates a product that scales globally from one that coaches abandon by week two. The design work is what the NBA invested in.
Case Study 02 · Why Design Wins

GameChanger Won Because Parents Could Feel Their Investment

Founded 2009 · Acquired by Dick's Sporting Goods 2016
500K+
Active teams across 20+ sports
$100M+
Annual revenue in 2024
Outcome
Dick's Sporting Goods acquisition. Now their most strategically valuable product.
Lesson 01 — Map Every User Role
They Discovered Parents Were the Real Users Through Mapping
GameChanger built for coaches first, then mapped usage and discovered grandparents were the most engaged users in the entire system. That mapping insight forced a design pivot that made every parent, coach, and fan feel included — and drove 500K teams to adopt it.
Lesson 02 — Design Makes Data Meaningful
Complexity Was Designed Away So Coaches Could Focus on Coaching
Baseball scorekeeping is notoriously complex. The design team's job was to hide that entirely. A volunteer parent could be logging stats in 30 seconds. That simplicity was not accidental — it came from designing every flow before any engineer touched the product.
Lesson 03 — Data Shows Investment Is Working
"Every Kid Is a Star" Was a Design Philosophy, Not a Feature
GameChanger designed player data so a recreational youth player felt as valued as an elite athlete. Parents could see their child's stats growing. They could share it. They felt their investment in youth sports was producing something visible and real. That feeling is what built loyalty at scale.
For Swish
The Guest View Is Swish's Most Powerful Retention Tool
Swish's Guest view — where coaches, parents, and players see team rosters and player data with progress charts — must be designed to make every parent feel their child's progress is visible. That is GameChanger's exact playbook, and it is what turned a youth sports app into a $100M acquisition.
The Lesson
GameChanger's $100M valuation came entirely from design decisions that made coaches' and parents' lives feel easier and their investments feel worthwhile. Mapping user roles completely before building is what created that.
The Solution

One Platform.
One Record.
Every Game.

A centralized system where every match, every team, and every player is part of a permanent, queryable record — not a scheduling tool, not a social feed. Basketball infrastructure.

What the platform does
01
Creates a permanent competition record
Every season, every fixture, every result — tracked, searchable, and historically preserved. No more starting from zero each season.
02
Gives every player a verified identity
Stats that accumulate across seasons. A profile that travels with the athlete as they move through age groups over years.
03
Gives Swish full operational control
One admin panel. All leagues, all teams, all results. Swish staff and coaches operate the entire platform without external tools.
04
Team and player data for coaches and parents
Coaches see roster and match stats to inform training. Parents see their child's progress grow across every match — making their investment in youth basketball visible and meaningful.
The Pilot Model

Two User Roles. Deliberately Simple.

Role 01 — Login Required
Admin

Swish staff, league organisers, and coaches — all in one role. In the pilot, the people running the league and coaching the teams often sit in the same room. This role serves them both without adding unnecessary complexity.

Create and manage all seasons and age groups
Full league setup from scratch — season name, dates, format, bracket style. No external tools needed.
Register teams and manage rosters
Add teams, assign players, lock rosters per season. The foundational data layer every other feature depends on.
Build fixtures and schedule matches
Create match schedules, assign venues, set match dates. Replaces the spreadsheet entirely.
Enter live match stats from courtside
Designed mobile-first for one-handed use during a live game. Under 3 taps to log any stat.
Confirm results and resolve disputes
Approve submitted results, override errors, and maintain data integrity across the season.
One login for everyone running the league. Separating coach and admin roles is a Phase 3 expansion — when the platform is proven and the team is larger.
Role 02 — No Login Required
Guest

Players, parents, fans, scouts, and anyone watching the league. Accessible from any device with a shared link — no account, no barrier. The public face of the entire platform.

Browse league standings and match results
Live standings table. Every match result visible as soon as admin confirms it. Searchable by season and age group.
See any team's page and match performance
Team stats page shows results, standings position, and aggregate performance data. Full player rosters are admin-only and not publicly visible.
Go deep into any player's profile and stats
Per-player stats card: points, assists, rebounds per game. Season totals. Navigable from their team's roster page.
See player radar chart and team bump chart
Radar chart shows player shape across 5 stats. Bump chart shows team rank movement week-by-week. Both show a clear empty state until match data exists.
Share any page as a direct link
Every standings page, team page, and player profile has a shareable URL. This is how parents share and how the platform grows without marketing.
No login friction means parents and players actually use it. Splitting into separate Parent and Player roles is a Phase 2 expansion — once the platform has data worth showing them.
The Pilot Core Loop

From League Creation to First Traction Signal

Part A · Setup — League Creation to First Whistle
Step 01
Admin Creates Season
Step 02
Teams Registered
Step 03
Players Added to Roster
Step 04
Fixtures Scheduled
Step 05
Venues Assigned
Step 06
Admin Confirms Schedule
Outcome A
The league exists. Every team has an official roster. Every player has an identity in the system.
Outcome B
The calendar exists. Every team knows when and where they play. The league is ready to begin.
Part B · Match Day — First Whistle to Traction Signal
Step 07
Match Played
Step 08
Coach Enters Stats Live
Step 09
Result Submitted
Step 10
Admin Confirms Result
Step 11
Season History Builds
Step 12
Charts Populate
Step 13
Guest View Updates
Outcome
Verified match data enters the system. Player stats update automatically. Standings recalculate instantly.
Traction Signal
After 3+ matches with real data, coaches and parents are checking the platform independently. Links are being shared. The expansion conversation begins.
Every feature in the pilot exists to power this loop. If coaches are entering stats and guests are checking rankings — the platform works.
Repeat from Step 07 each match day ↺
Pilot Scope

4 Modules. Enough to Prove Everything.

01
League and Season Management
Create seasons, configure age groups, build fixtures, assign venues, enter match results, and display live standings. The operational core — replaces every spreadsheet and group chat Swish currently depends on.
Core Module
02
Team and Roster Management
Team registration, player registration per team, coach assignment, and roster locking per season. The data foundation every other module depends on — without it, there is no league to manage and no player to track.
Core Module
03
Guest View — Player Stats & Data Visualisation
No-login public access to per-player stats navigable from league standings. Includes radar charts for player performance shape and bump charts for team rank movement — both with a clear empty state when no match data exists yet. Roster details are admin-only.
Do Not Cut — This Is What Coaches & Parents Open
04
Admin and Coach Portal
A unified login for Swish staff and coaches to organise leagues, manage full team rosters, build fixtures, and enter live match stats courtside on mobile. Roster data is visible only here, not publicly. Mobile-first — every stat loggable in under 3 taps, one-handed. The engine that powers everything.
Cannot Be Cut
Deliberately deferred to later phases
Dedicated Parent RolePhase 2
Dedicated Player RolePhase 2
Separate Coach RolePhase 3
Sponsor DashboardPhase 4
Development ProfilesPhase 5
Guest View · Data Visualisation Design

Two Charts. Two Truths. Designed for Both States.

Player Radar Chart
Performance shape across 5 key stats
Per Player
With Match Data
PTS REB AST STL BLK
Player's performance shape, visible after the first match
Empty — Season Just Launched
Chart will appear after this player's first match
Team Bump Chart
League rank movement week by week
Per Team
With Match Data
#1#2#3#4#5 W1W2W3W4W5
Team rank story, visible after 2+ matches played
Empty — Season Just Launched
#1#2#3 W1W2W3
Chart will appear after the first two matches are played
Both charts are designed with empty states from day one. When a season launches and no matches have been played yet, guests see a clear, non-broken message explaining that data will appear here after the first matches. Empty states are not an afterthought — they are the first impression new users get.
Why Design First

The Same Pilot, Two Very Different Outcomes

!
Path A — High Risk
Build Without
Design First
Every developer assumption becomes a build decision
The Guest view navigation, the Admin mobile courtside flow, the empty states — all guessed by a developer. Every wrong guess costs money to reverse.
Stakeholders only see the product once it is built
A change in Figma takes 10 minutes. The same change after a developer has built it takes days — and costs multiples of the design fee.
The courtside stat entry gets built desktop-first
Without explicit mobile-first specs, developers default to desktop thinking. The most critical UX in the project fails on the first match day.
Chart empty states are built as an afterthought
The first thing every user sees at launch is the empty state. If it looks broken, coaches and parents lose trust before a single match is played.
High Probability of Costly Rebuild
✓
Path B — The Right Way
Design First
Then Build
Every user flow is mapped before any code is written
Guest navigation, Admin mobile flow, all permission boundaries — agreed in Figma. The developer builds from a blueprint, not assumptions.
Stakeholders approve every decision before it is built
Two rounds of feedback on wireframes in Phase 0. What gets approved is what gets built. No surprises when the developer delivers.
Courtside stat entry is a first-class mobile feature
One-handed, under-3-taps, large targets, instant undo. Fully specified before a developer sees the project.
Empty states designed alongside the data states
Every chart, list, and screen has an intentional empty state. The platform looks professional from the moment of launch.
The Professional Standard
The Business Argument

Design Is Not a Cost.
It Is Risk Insurance.

Every rupee spent on design before development is protecting multiple rupees of development budget from being wasted on rebuilds. The more precisely every screen, flow, and user role is designed, the faster and cheaper it is to build — and the less likely it needs to be rebuilt after the first review.

For a pilot with a fixed budget and a traction deadline, this is not a philosophical argument. It is a financial one.

10×
Industry-standard cost multiplier to fix a design decision in production code versus the same change in a Figma file.
38–44
Screens in this pilot. Each built without design direction is a screen that may need rebuilding after the first stakeholder review.
2
User roles. Without a mapped permission model, every role boundary is a developer assumption — and assumptions in production code are expensive to fix.
A design engagement is not added cost on top of development. It is the thing that makes development predictable, fast, and finished the first time.
Platform Expansion Plan

The Pilot Is the Foundation. Each Phase Builds on What Was Proven Before It.

02
Parent & Player Separation
After pilot traction is confirmed

The Guest role splits into two dedicated roles — a Parent role with a personalised feed of their child's stats, schedule, and progress, and a Player role with a personal profile they own and can share.

Why this comes next
Once coaches enter data consistently, parents and players want more than the Guest view gives them. This serves that demand directly — and makes the platform sticky for families.
03
Admin & Coach Separation
After Phase 2 is live and adopted

The Admin role splits into a dedicated Coach role focused on match day — quick stat entry, team management, player notes — and a full Admin role for league operations and oversight.

Why after Phase 2
When the platform grows to multiple leagues with many coaches, the combined role becomes a limitation. Separating them at scale gives each side a focused tool.
04
Sponsor Reporting Dashboard
After Phase 3 roles are in place

A sponsor-facing dashboard showing verified participation numbers, season impact reports, age-group reach, and attendance data. Turns Swish from an event brand into a data-backed partnership opportunity.

Why it needs the earlier phases
Sponsors need real verified data to justify investment. That data only becomes credible after two or three full seasons of consistent entry.
05
Development Profiles & SEA Expansion
After Phase 4 establishes credibility

Full multi-season development journeys — skill progression, milestone tracking, scout access, and shareable athlete profiles for schools. SEA expansion beyond Thailand begins here.

Why this is last
This is the product that competes with HomeCourt. It only becomes credible with 2–3 years of multi-season data behind every profile — exactly what the earlier phases build.
The pilot proves the core loop. Every phase that follows is a direct expansion of what the pilot data made possible.
Pilot → Phase 2 → 3 → 4 → 5
Before Phase 0 Begins

Six Questions Phase 0 Exists to Answer

None of these are answered yet. Phase 0 exists specifically to answer each one with documented, stakeholder-approved answers. Tap any question to see why it matters.

These are two completely different mobile UI designs. This single answer determines the entire courtside flow architecture.
One named decision-maker prevents conflicting feedback from multiple people stalling the project mid-design.
This determines whether the current timeline is feasible or whether scope needs further adjustment before Phase 0 starts.
Pilot scale directly determines how complex the Admin fixture-building interface needs to be at launch versus later.
If players are not logging in during the pilot, the Guest view scope is narrower — which affects the Phase 1 screen count and timeline.
If the answer is no — that mapping is the first deliverable of Phase 0. It is the document the developer needs before writing any code.
All six questions are answered in Phase 0. No screen is designed until every answer is documented and approved by all stakeholders in writing.
Phase 0 · Discovery & Wireframes

4 Weeks.
Every Decision Documented.

Phase 0 produces documents and wireframes — not final UI. Its job is to make every design and development decision in Phase 1 a known quantity with stakeholder sign-off, not a guess.

Phase 1 Cannot Start Until
All deliverables are approved in writing by the Swish stakeholder. No exceptions.
Six deliverables — tap to expand
All six Phase 0 questions answered in writing. Confirmed scope, confirmed platform purpose, confirmed success criteria for the pilot season.
Every action each role can and cannot take. Every data field each role can see. This is the document the developer references to build access control correctly.
The complete navigation structure and data model for the platform. Every screen, how it connects to every other screen, and what data lives where.
Lo-fi wireframes for every screen including all empty states, error states, and the mobile courtside stat-entry flow. Layout and logic confirmed — visual design comes in Phase 1.
Client reviews wireframes async — no extra meetings required. One structured revision round. Feedback is collected, addressed, and the revised set submitted for final approval.
A single document containing every approved decision. Signed before Phase 1 begins. This is the contract between design intent and development execution.
What We Need From You

Three Touchpoints. That Is All.

Phase 0 is designed to be light on your time. You are building a basketball platform — not managing a design agency. Everything is structured so your input is focused, decisive, and minimal.

1
Kickoff Call — 60 to 90 minutes
One call at the start of Phase 0. You answer the six initiation questions, share existing documents or context, and we align on scope. The only meeting required in Phase 0.
2
Async Wireframe Review — 48-hour window
You review wireframes in your own time using a shared Figma link and leave comments. No call required. A structured feedback form makes it fast and clear.
3
Sign-Off Approval — Email or message
A single written confirmation that Phase 0 deliverables are approved before Phase 1 begins. No meeting required — just a clear yes from the named decision-maker.
Our commitments to you
Every question asked of you has a documented reason
Nothing in the kickoff call or feedback round is asked without a clear explanation of why the answer matters for the design or the developer.
No surprise scope additions after sign-off
Once Phase 0 is signed off, the scope of Phase 1 is fixed. Any additions are formal change requests — documented, priced, and approved before any work begins.
Your feedback always gets a decision, not more questions
Every round of feedback produces a resolved document, not a new round of open questions. You always know exactly where the project stands.
Deliverables arrive on the agreed date — or you hear in advance
If a deliverable will be late, you hear about it 48 hours ahead — not after the deadline. The project timeline is a commitment, not an estimate.
Project Timeline

4 Months from Kickoff to Developer Handoff

Month 1
Month 2
Month 3
Month 4
Phase 0 · W1–4PH 0
Review·
Phase 1 · W6–14PH 1
HandoffEND
Phase 0 — Discovery & Wireframes (4 weeks)
Phase 1 — UI Design & Handoff (9 weeks)
Review, Handoff & Buffer
End of Week 4
Phase 0 Wireframes Delivered for Review
End of Week 5
Phase 0 Approved. Phase 1 Advance Received.
End of Week 14
Phase 1 Full UI Delivered for Review
End of Week 15–16
Developer Handoff Complete. Project Closed.
Phase 1 · UI Design & Developer Handoff

9 Weeks.
Every Screen Designed.

Phase 1 converts approved Phase 0 wireframes into production-ready, annotated high-fidelity screens. The developer receives a blueprint — not a mood board.

Key Priority
The Admin mobile courtside stat-entry flow is designed first — before any other Phase 1 screen — because every other feature depends on this data being entered correctly.
Six deliverables — tap to expand
The shared visual foundation: colour, typography, spacing, button states, form elements, and data display components. Used consistently across all 38–44 screens.
League setup, team and roster management, fixture builder, courtside stat entry (one-handed, under 3 taps), result confirmation, account management. All error, empty, and loading states included.
Standings, team rosters, player profiles, stat cards, radar charts and bump charts with both data states and empty states. Every page shareable via direct URL.
Every screen has its first-impression state designed — what the platform looks like on day one before any data exists. Not optional — it is what every user sees first.
Every screen annotated with spacing, component behaviour, interaction notes, and permission logic. The developer has no open questions when they begin building.
One call to walk the developer and stakeholder through the complete Figma file. All files delivered in agreed formats. Project closed.
Investment Breakdown

Two Phases. One Fixed Investment of ₹2,00,000.

Kickoff & Discovery
Stakeholder Kickoff Call + Discovery Brief
60–90 min call answering the 6 initiation questions. All context and existing assets reviewed. Brief document produced as output.
4 hrs
₹3,000
User Role Definition — Admin & Guest
Every action each role can take, every data field they can see. Admin combined role fully mapped. Guest navigation paths fully defined.
8 hrs
₹6,000
Permission Matrix & Data Access Map
Tabular reference of every permission for every role across all 4 modules. Developer uses this to build access control.
6 hrs
₹4,500
Architecture & Wireframes
Information Architecture — All 4 Modules
Complete navigation structure and data model. Every screen mapped to its parent, its data source, and its connected screens.
10 hrs
₹8,000
Complete Screen Inventory
Full list of every screen across Admin Portal and Guest View including all empty, error, and loading state variants.
6 hrs
₹4,500
Lo-fi Wireframes — Admin Portal Flows
All Admin screens wireframed including mobile courtside stat entry. Layout logic, navigation, and content hierarchy confirmed.
12 hrs
₹9,500
Lo-fi Wireframes — Guest View & Data Viz Empty States
All Guest screens wireframed including radar and bump chart with both data and empty states fully designed at wireframe level.
10 hrs
₹8,000
Review, Revision & Sign-Off
Async Client Feedback Round
Client reviews wireframes via Figma and leaves comments. All feedback compiled and triaged into a structured response document.
4 hrs
₹3,500
Revision Round — Wireframes Updated
One full revision pass based on approved feedback. Updated wireframes submitted for final approval.
6 hrs
₹5,000
Phase 0 Sign-Off Package & Handover to Phase 1
All approved documents compiled into a single handover file. Stakeholder approves in writing. Phase 1 schedule confirmed.
4 hrs
₹3,000
Phase 0 Total
All deliverables listed above
~70 hrs
₹55,000
50% advance (₹27,500) required before Phase 0 begins. Remaining 50% (₹27,500) due on delivery of the final Phase 0 sign-off package.
Foundation
Design System — Tokens, Components, Patterns
Colour, typography, spacing scale, button states, form elements, data display components. Shared across all screens in both roles.
1 system
₹12,000
Admin Portal
League & Season Management
Season creation, age-group setup, fixture builder, match scheduling, standings dashboard. All states including empty season-launch state.
8–10
₹28,000
Team & Roster Management
Team registration, player registration, coach assignment, roster lock per season. Admin-facing management views with all form states.
6–8
₹20,000
Courtside Stat Entry — Mobile-First Priority
One-handed mobile interface for live match stat logging. Under 3 taps to log any stat. Instant undo. Large tap targets. Designed for a coach watching a live game simultaneously.
5–7
₹18,000
Result Confirmation & Dispute Flow
Result submission, admin confirmation screen, dispute flag and resolution flow. Data integrity protected at every step.
3–4
₹12,000
Account & User Management
Admin-level user creation, role assignment, and account deactivation. Minimal scope for pilot — expanded in Phase 3.
2–3
₹8,000
Guest View
League Hub & Standings Page
Public-facing entry point. League standings table, season selector, age-group filter, match results list. Shareable URL.
3–4
₹12,000
Team Stats Page
Team page navigable from standings. Shows team match results, standings history, and aggregate season performance. No roster data — that is admin-only. Shareable URL.
2–3
₹8,000
Player Profile & Stat Cards
Per-player profile with points, assists, rebounds per game. Season totals. Navigable from team roster. Shareable URL.
2–3
₹8,000
Radar Chart — Data State & Empty State
Player performance shape radar chart. Data state with real stats. Empty state with a clear "first match required" message for new players and new seasons.
2 states
₹6,000
Bump Chart — Data State & Empty State
Team rank movement over weeks. Data state with league history. Empty state with a clear "first match required" message. Both states fully designed and annotated.
2 states
₹6,000
Handoff
Developer Annotations & Specification Document
Every screen annotated with spacing, interaction notes, component behaviour, permission logic. Developer has zero open questions when they start building.
1 doc
₹5,000
Handoff Review Call & Final File Delivery
One walkthrough call with developer and stakeholder. All files delivered. Project closed.
1 call
₹2,000
Phase 1 Total
38–44 screens across both roles
38–44
₹1,45,000
50% advance (₹72,500) required before Phase 1 begins. Remaining 50% (₹72,500) due on final file delivery.
Total Project Investment
₹2,00,000
Engagement Terms

Structured to Protect Both Sides.

Five terms keep the engagement predictable for everyone. Tap any term to read the detail.

Each phase includes exactly 2 structured revision rounds built into the fee. Any additional rounds beyond this are billed at an agreed hourly rate before work begins on them.
Once a phase deliverable is signed off in writing by the client, it is considered final. Any changes to approved work are treated as a formal change request — documented, priced, and approved before execution.
No phase runs in parallel with another. Phase 0 must be fully signed off and the Phase 1 advance payment received before any Phase 1 work begins.
Phase 0 advance: ₹27,500 before kickoff. Phase 1 advance: ₹72,500 before the first Phase 1 deliverable. No advance received — no start date given.
Any feature, screen, or user flow added after Phase 0 is signed off is a change request — documented, priced, and approved before any design work begins on it.
Payment Schedule
Phase 0 Advance — before kickoff call
₹27,500
50% of Phase 0 fee. Project starts after this is received.
Phase 0 Completion — on sign-off delivery
₹27,500
Remaining 50% of Phase 0.
Phase 1 Advance — before Phase 1 begins
₹72,500
50% of Phase 1 fee. Phase 1 starts after this is received.
Phase 1 Completion — on final file delivery
₹72,500
Remaining 50% of Phase 1. Project closed.
Total
₹2,00,000
How We Move Forward

Start with Phase 0.
Prove everything.
Then build.

1
Approve Phase 0 & Transfer Advance
₹27,500 advance. 4 weeks. One kickoff call. Complete wireframes, role maps, and a signed product definition document — before any visual design begins.
2
Review & Sign Off on Every Decision
All stakeholders review the Phase 0 wireframes async. Feedback consolidated. Revisions made. One written approval before Phase 1 begins. No surprises.
3
Full UI Design & Developer Handoff (Phase 1)
9 weeks. 38–44 screens. Annotated Figma handoff. The developer receives a complete blueprint with no open questions. The platform builds from certainty, not assumptions.
View / download the full deck →
Prepared by
MK Agency — Design & Development Studio
Led by
Manish Kumar ↗  ·  Head of Agency
The Final Word
Build the Foundation.
Own Southeast Asia.

The pilot is not the final product. The pilot is proof. Once coaches are entering real data after real matches, the conversation about Phases 2 through 5 changes from a proposal into a roadmap — because the data exists to show the platform is working and the community is ready to grow with it.