Micro-Savings App for Bharat: Build vs. Service vs. Agent

Who does it:

• Bank Sakhis / Banking Correspondents (BCs): Appointed by small banks (Small Finance Banks, regional rural banks), they collect cash deposits door-to-door in villages. Typically earn 1-2% commission per deposit.
• Self-Help Group (SHG) leaders: Women who manage a group of 10-20 members, collect weekly contributions in cash, maintain a physical passbook, disburse loans from the pool. Work is entirely manual.
• Chit fund agents / nidhi agents: Operate in semi-urban Bharat, manage monthly chit subscriptions in cash.
• Insurance agents (micro-SIPs): Push recurring deposit or micro-insurance products door-to-door using physical premium collection.
• Kirana shop keepers: In many villages, the local shop is the informal savings collection point — people drop ₹10-50 daily and receive a slip.

What they use:

• Basic keypad phones (not smartphones) for calls and WhatsApp text forwards
• Physical passbooks (often hand-written, no digital copy)
• WhatsApp groups for sending daily balance screenshots
• Excel on a basic Windows laptop for SHG accountants who have one
• No digital record for 80%+ of these transactions — the passbook IS the ledger

Where money leaks:

• Float: BCs hold cash for 1-3 days before banking it; interest earned on that float is theirs
• Rounding: Agents often round deposits up — user deposits ₹47, agent enters ₹50, keeps ₹3
• Promised vs. actual returns: Passbooks show one rate; actual payout at maturity is lower due to hidden charges
• Default recovery: Physical passbooks are easy to lose or alter; disputes favor the agent
• Time cost: Users (often women) spend 1-2 hours per month traveling to and queuing at the collection point

Who profits from staying manual:

• BCs and agents — float income, rounding income, and the job security that comes from being irreplaceable
• Small banks — they receive government Jan Suraksha and financial inclusion subsidies for BC networks; digitizing removes the BC and the subsidy claim
• MFI field staff — SHG loans are their bread and butter; a digital app that reduces field visits reduces their headcount value
• Kirana collectors — the informal "savings drop" at the shop creates foot traffic and hence purchase volume

Who is hurt:

• The saver — loses ₹200-800 per year to rounding, float erosion, and opaque charges on a ₹5,000-10,000 annual corpus
• The honest BC — competes against rounding agents and cannot win on price; a digital layer that makes rounding visible would actually help honest agents
• Small banks — they bear the cost of BC fraud and reconciliation errors that digital would eliminate

Who would pay to change it:

• The user — unlikely to pay directly above ₹20/month, and even that is a hard sell for a population that treats every rupee as allocated
• Small Finance Banks — would pay ₹8-15 per active user per month for a digital audit trail and reduced BC fraud, because the cost of BC default/fraud currently runs ₹50-200 per user annually
• Microfinance institutions (MFIs) / NBFCs — would pay for a verified savings history as underwriting data for small loans; currently they rely on manual field verification at ₹100-300 per applicant
• Government schemes — Jan Dhan and postal insurance programs have administrative cost budgets that could co-fund digital onboarding

Day one product: A WhatsApp-native savings tracker and recurring deposit reminder bot for SHG groups. Not an app — a number (a WhatsApp Business API account) that an SHG leader or BC adds, and their members message to record deposits.

What it does on day one:

• Member sends "deposit 50" to a WhatsApp number; the system logs it with timestamp and replies with a running balance
• SHG leader gets a daily summary screenshot (image generated, sent to WhatsApp group) they can print and staple into the passbook
• No KYC required on day one (works on trust; BC or SHG leader is the KYC proxy)
• UPI integration for actual fund movement (optional day-one; can work as a pure recording tool first)

Who pays and how:

• SHAPE: Per active SHG group per month — ₹200-300/month for the SHG leader to have a digital record-keeper and fraud-proof log
• SHAPE: Per transaction via UPI (optional layer) — ₹1-2 per successful deposit recorded; paid by the bank/NBFC partner who gets the float and the audit trail
• SHAPE: Per user per month (B2B) — Small banks and MFIs pay ₹10-15/month per active user for verified savings history as underwriting data
• Do NOT try per-seat from the end user on day one — Bharat does not pay subscription fees to new apps

Verified players:

• Jar — micro-savings app (gold-backed); targets Bharat with small daily deposits; USSD option exists; has raised funding; operates in Hindi and regional languages
• Monomyto — recurring deposit app for small-ticket monthly deposits; targets salaried and self-employed in tier 2-3 cities
• Fi (by PhonePe) — digital savings account; smarter than most but targets smartphone-using urban users, not deep Bharat
• Post Office RD — government-backed recurring deposit; fully physical, no app; used by millions in Bharat as the default micro-savings instrument
• Bank RD products — HDFC, SBI, Kotak all have RD products; entirely physical or net banking for existing customers

Unverified or niche:

• Several unnamed chit fund apps in regional language app stores; do not assume market presence without verification
• WhatsApp-based savings bots used internally by some MFIs (internal tools, not products)

Gap: No WhatsApp-native, BC-first, SHG-focused savings recording tool that works on basic phones with an optional UPI layer. This gap is real and unoccupied.

Fact 1: Target users will not adopt a digital savings tool without physical verification — kills the recording-only product

Check cheaply: In 3 talukas of Gujarat or Maharashtra, approach 30 SHG leaders and show them a WhatsApp Business demo. Ask: "Would you use this instead of your passbook?" Count "yes, immediately" vs. "only if I can show it to my members physically." If fewer than 10 of 30 say yes-immediately, the wedge does not hold.

Fact 2: BC float income is structurally necessary for BC retention — a digital tool that removes float will cause BCs to actively sabo the product

Check cheaply: Interview 15 BCs in one district (not agents, actual BCs who bank with SFBs). Ask: "How much of your monthly income comes from float?" If more than 30% say float is essential income, the agencify model must compensate for float loss or BCs become adversaries, not channel partners.

Fact 3: UPI and bank account penetration in the actual target segment is lower than reported government figures suggest

Check cheaply: In 3 villages with <10,000 population, count how many adults have made a UPI transaction in the last 30 days (not how many have a UPI app installed). Use physical survey, not app store data. If fewer than 40% of women and fewer than 60% of men are active UPI users, a UPI-first product will exclude the bottom quartile of the target segment.

Budget: ₹45,000

• ₹15,000 — WhatsApp Business API setup (Meta has a startup program; otherwise ~₹5,000/month for a small account)
• ₹10,000 — Basic UI for the savings dashboard (a clean React web dashboard showing SHG group balances; can be built in 2 weeks)
• ₹8,000 — Field outreach: travel to 2 talukas, meet SHG leaders, demonstrate the product, onboard 5 groups
• ₹7,000 — Local field partner: pay one local person ₹7,000 for a month to collect daily deposit entries manually and feed them into the system (this IS the product — see below)
• ₹5,000 — Misc: hosting, UPI test account, image generation for passbook screenshots

The actual test is the field partner, not the tech:

The ₹7,000 field partner does the work the app is supposed to do. They visit 5 SHG groups daily, collect cash, record deposits via WhatsApp on behalf of members, send passbook images to the group. This simulates what the app automates. The test is: do members trust the WhatsApp record enough to stop asking for a physical passbook?

Pass mark:

• 5 SHG groups, 15-20 active members per group = 75-100 users
• 60% of members must be checking WhatsApp balance messages weekly (measured by open rate of broadcast messages)
• 80% of groups must have zero disputes at month-end (recorded balance matches what members remember)
• If both met: move to phase 2 (actual app with UPI)
• If either fails: the trust model is broken, and the agencify model must be rebuilt before any product is built

AGENCIFY first, PRODUCTIZE after, AI-FY the backend.

The Bharat micro-savings segment cannot be cracked with an app alone because trust requires human presence and the last mile runs on cash, not UPI. The correct first move is a service layer — a small team of field agents who do the saving collection and record it digitally — that proves demand, earns trust, and generates the data needed to build a product that replaces the human layer over time. Building the product first wastes development money on an unproven trust model; trying to AI-automate before earning trust is backwards. The field agent IS the product hypothesis; the app is the hypothesis validation.

Availability confirmed against the .in registry (RDAP) on 2026-09-24. Prices and ownership read from our own intelligence tables. Nothing here is estimated.

Single-word, available now

• saves.co.in — available

Already ours

• micro.co.in · parked, free to use

Also available (compound)

• mysaves.in
• gosaves.in
• saveshub.in
• saveskart.in
• savesmandi.in
• savesbazaar.in
• savesdirect.in
• savessupply.in
• savesconnect.in

Listed for sale

• saves.com · price not listed on afternic · seller holds 68 domains

In the expiry pipeline — watch

• gosave.in · 407 days · score 10

Taken and developed — do not chase

• saves.in · entropy 4.69
• savehub.in · entropy 5.67
• microhub.in · entropy 4.55
• micromart.in · entropy 4.56
• microsupply.in · entropy 4.82
• mysaving.in · entropy 5.98

---

Generated 2026-09-24 04:37 UTC. Topic from our research queue; no market-size figure appears here unless a source is named. The domain block above is read from our own intelligence tables and confirmed at the .in registry (RDAP); the model wrote the analysis, not the domain facts.