Overview

Role

Project Management

Timeline

2 week

Team

1 PM · 1 Designer · 1 Engineer · Stakeholders

Platform

Grocery Store Credit Management App (MVP)

Company size

11 - 20

Why do we want to do this?

Local grocery and kirana store owners often sell goods on credit to trusted customers as part of their daily business. These shops operate in high-traffic, fast-moving environments where speed, accuracy, and customer relationships are critical to sustaining revenue and trust.

Current work flow

Today, when a customer purchases items on credit, the shop owner pauses the transaction and writes down the customer's name, the items taken, and the amount owed in a physical notebook. This record-keeping is done manually throughout the day, often during peak rush hours when multiple customers are waiting.

outcome

Interactive prototype that allow the organization to validate before even developing an actual product

Product Vision & Problem Framing

Product Vision

Enable small grocery (kirana) store owners to track credit sales effortlessly, recover payments confidently, and maintain trust with customers—without disrupting their daily operations.

A simple, reliable digital ledger that replaces handwritten credit books for kirana stores.

Problem Statement

Kirana store owners frequently sell goods on credit to trusted customers.

Today, these transactions are:

  • Recorded manually in notebooks

  • Difficult to track and reconcile

  • Error-prone and time-consuming

  • Dependent on memory and trust

This leads to:

  • Missed or delayed payments

  • Disputes with customers

  • Poor visibility into outstanding dues

  • Stress and cash-flow uncertainty

Why This Problem Matters (Business Impact)

Credit is core to kirana store economics

Margins are thin and cash flow matters daily

Store owners are time-poor, not tech-poor

Existing apps are too complex or overkill

Credit is core to kirana store economics

Margins are thin and cash flow matters daily

Store owners are time-poor, not tech-poor

Existing apps are too complex or overkill

Credit is core to kirana store economics

Margins are thin and cash flow matters daily

Store owners are time-poor, not tech-poor

Existing apps are too complex or overkill

Product Discovery & Assumptions

Key Assumptions (Explicitly Documented) and validated

I documented assumptions early to reduce risk:

Primary User Persona (Lean)

User: Kirana Store Owner
Age: 35–55
Tech Skill: Basic smartphone usage
Motivation: Recover money without conflict
Fear: Losing records or confusing customers

User: Kirana Store Owner
Age: 35–55
Tech Skill: Basic smartphone usage
Motivation: Recover money without conflict
Fear: Losing records or confusing customers

User: Kirana Store Owner
Age: 35–55
Tech Skill: Basic smartphone usage
Motivation: Recover money without conflict
Fear: Losing records or confusing customers

Product Goals & Success Metrics

MVP Goals

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Success Metrics (First 30–60 Days) After release

The first success metric was applied to the interactive prototype to evaluate the efficiency of the design solution.

Time to record credit sale: < 10 seconds

% of users checking outstanding dues daily

Reduction in missed payments (self-reported)

Weekly active store owners

Time to record credit sale: < 10 seconds

% of users checking outstanding dues daily

Reduction in missed payments (self-reported)

Weekly active store owners

Time to record credit sale: < 10 seconds

% of users checking outstanding dues daily

Reduction in missed payments (self-reported)

Weekly active store owners

MVP Scope Definition

MVP Feature Set (Must-Have Only)

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Replace paper credit ledger

Reduce time spent tracking dues

Increase payment recovery confidence

Explicitly Out of Scope (for MVP)

Inventory management

GST / invoicing

Analytics dashboards

Multi-user roles

Inventory management

GST / invoicing

Analytics dashboards

Multi-user roles

Inventory management

GST / invoicing

Analytics dashboards

Multi-user roles

User Journeys & Flows

01 - Flow: App Launch → Language Selection (Onboarding)

02 - Login / Register → Mobile Number → OTP → Validation → Entry

03 - Add Credit flow

04 - Low pay scenerio

MVP Output - Interactive prototype

What Was Delivered

  • Working clickable prototype / basic build

  • Core credit tracking flows

  • Offline-first behavior

  • Clear visual balance indicators

What Was Validated

  • Speed of entry

  • Clarity of balances

  • Ease of recall vs paper book

What Was Learned

  • Users prefer customer-first view, not transaction-first

  • Less text, more numbers

  • Trust increases when history is visible

After MVP vaidation

Sprint Plan (2-Week MVP)

Sprint 1

  • Core data model

  • Credit entry flow

  • Customer list

  • Core data model

  • Credit entry flow

  • Customer list

  • Core data model

  • Credit entry flow

  • Customer list

Sprint 2

  • Outstanding balance view

  • Transaction history

  • Offline handling

  • Basic QA

  • Outstanding balance view

  • Transaction history

  • Offline handling

  • Basic QA

  • Outstanding balance view

  • Transaction history

  • Offline handling

  • Basic QA

Collaboration Model

  • Daily async check-ins

  • Clear acceptance criteria per feature

  • Designers + engineer aligned on “definition of done”

  • Daily async check-ins

  • Clear acceptance criteria per feature

  • Designers + engineer aligned on “definition of done”

  • Daily async check-ins

  • Clear acceptance criteria per feature

  • Designers + engineer aligned on “definition of done”