CricketKhata — Expense & Payment Tracker App

# Project Brief: CricketKhata — Cricket Team Expense & Payment Tracker

## 1. Project Overview

I want to build a simple, mobile-friendly web app that helps corporate cricket teams manage match expenses, collect money from players, and track who has paid or still owes money.

The app should be easy to use on a mobile phone. Initially, I want a web app rather than a separate Android or iOS app.

**Goal:** Build a basic working MVP that real cricket teams can use for their weekend matches.

## 2. The Problem We Are Solving

Corporate cricket teams regularly play matches at rented grounds. The captain or organizer usually pays for the ground, balls, refreshments and other expenses, then collects each player's share through UPI.

This creates several problems:

* The captain must repeatedly calculate how much each player owes.
* It is difficult to track who paid, who paid partially and who has not paid.
* Payment reminders are sent manually through WhatsApp.
* Some players pay in advance, while others pay late.
* The captain may pay the ground fee upfront and collect money from players later.
* Tracking outstanding balances and expenses across multiple matches becomes confusing.
* Previous match balances, refunds and adjustments are easily forgotten.

Currently, teams often rely on spreadsheets, WhatsApp messages and manual calculations.

## 3. Target Users

* Corporate cricket team captains.
* Weekend cricket groups.
* Cricket match organizers.
* Players who need to pay their share of match expenses.

The captain/organizer is the primary user. Players should be able to view their own payment request without being forced to create an account or install an app.

## 4. Features Required in the First Version (MVP)

### Feature 1: Create and Manage a Team

* Captain can create a team and give it a name.
* Captain can add, edit and remove players.
* Each player has a name and optionally a phone number.
* The same team roster can be reused for future matches.

### Feature 2: Create a Match and Add Expenses

* Captain can create a match with a date and optional ground name.
* Captain can enter expenses such as:

* Ground booking.
* Cricket balls and equipment.
* Refreshments.
* Other expenses.
* The app calculates the total match expense automatically.
* Captain can select the participating players for that match.

### Feature 3: Calculate Each Player's Share

* By default, divide the total expense equally among participating players.
* Allow the captain to manually adjust an individual player's share.
* Display the total amount and each player's amount due before saving.

Example: Total expense is ₹3,000 and 12 players participate. Each player owes ₹250.

### Feature 4: Track Payments

For every player in a match, show:

* Total amount due.
* Amount paid.
* Remaining balance.
* Payment status: Pending, Partially Paid or Paid.

The captain should be able to record a payment manually after receiving it through UPI or another payment method.

Example: A player owes ₹250 and pays ₹100. The app should show ₹100 paid and ₹150 remaining.

### Feature 5: UPI and WhatsApp Sharing

* Provide a UPI payment link or QR code if feasible within the budget.
* Allow the captain to share a payment request through WhatsApp.
* The message should include the match name/date, amount due and payment instructions.
* Players should be able to open a simple page showing their own amount due and payment instructions.

**Important:** Payments should go directly to the captain's UPI account. The app should not hold or pool money.

Automatic bank/payment verification is not required in the first version. The captain can update payment statuses manually.

### Feature 6: Match History and Team Ledger

* Display previous matches and their expenses.
* Show the amount collected and outstanding for each match.
* Track advances paid by the captain or players.
* Allow the captain to record refunds and balance adjustments.
* Show any outstanding balance carried forward to the next match.
* Provide a simple summary of each player's balance across matches.

Financial records must remain available for reference. Editing or cancelling a match should not silently erase payments or historical records.

## 5. Basic User Flow

1. Captain signs up and creates a team.
2. Captain adds the players once.
3. Before each match, captain creates a match and selects participating players.
4. Captain enters expenses.
5. App calculates each player's share.
6. Captain shares individual payment requests through WhatsApp.
7. Players pay the captain directly using UPI.
8. Captain records payments in the app.
9. App updates paid, pending and outstanding amounts.
10. After the match, the captain can view the final expense summary and outstanding balances.

## 6. Screens Required

1. Login/sign-up page.
2. Dashboard showing teams and recent matches.
3. Team roster page.
4. Create-match page.
5. Add-expenses and calculate-shares page.
6. Match payment-tracking page.
7. Individual player payment-request page.
8. Match history and team balance summary.

The design can be simple and clean. Priority should be correct calculations, ease of use and mobile responsiveness rather than animations or elaborate design.

## 7. Features NOT Required Initially

To keep the first version affordable, do not include:

* Live cricket scoring.
* Player rankings or statistics.
* Tournament management.
* Ground booking.
* In-app wallet or holding player funds.
* Automatic bank account access.
* Automatic payment verification.
* Separate native Android or iOS applications.
* Complex accounting or tax features.

These can be considered later if users need them.

## 8. Technical and Ownership Requirements

* The web app must work on Android mobile browsers and desktop browsers.
* Use a suitable low-cost technology stack.
* Store financial amounts accurately and prevent duplicate or inconsistent payment records.
* Each team’s financial information must be private to authorized users.
* Players opening a payment link must only see their own relevant payment details.
* The application must have appropriate authentication, access controls, database backups and basic security.
* The app should be deployed to a live URL for testing with real teams.

The client must own and have administrative access to the source-code repository, domain, hosting, database and related accounts.

## 9. Deliverables

The freelancer must provide:

1. A working, deployed web app.
2. Complete source code.
3. Database setup and documentation.
4. Login and access-control functionality.
5. All agreed MVP features.
6. Basic testing and bug fixes before handover.
7. Instructions for managing and maintaining the application.
8. A clear list of any recurring hosting, database or third-party charges.

## 10. Budget and Timeline

I want to keep the first version as affordable as possible.

* **Target budget:** ₹10,000–₹15,000 for a very basic MVP, subject to the final scope.
* **Target timeline:** Approximately 1–3 weeks, depending on the features and development approach.
* I am open to using existing frameworks, templates or low-code tools if they reduce cost without compromising essential functionality.

Please clearly state if any requested feature cannot fit within the proposed budget.

## 11. Please Include These Details in Your Quote

1. Total development cost.
2. Estimated delivery date.
3. Technology stack.
4. Features included and excluded.
5. Any additional hosting, domain or service charges.
6. Whether the full source code will be handed over.
7. Whether the quoted price includes deployment, testing and bug fixes.
8. Any recurring maintenance charges.

Please provide a fixed-price quote based on the agreed scope before starting development.