Skip to content

Latest commit

 

History

History
265 lines (198 loc) · 18.7 KB

File metadata and controls

265 lines (198 loc) · 18.7 KB

MiTanda — Product Requirements Document

Generated by idearalph — 2026-06-03 · PMF Score: 8.2/10


1. Executive Summary

MiTanda is the onchain reinvention of the tanda — the rotating savings and credit association (ROSCA) that hundreds of millions of people use across Latin America, Africa, and Asia. In a tanda, a group pools fixed contributions on a schedule, and each round one member receives the full pot, until everyone has had a turn.

The system works on trust — and that trust is regularly broken. The organizer ("banker") can vanish with the pool, members default mid-cycle, and everyone must physically meet to pay. MiTanda removes the human point of failure: contributions and payouts are governed by a smart contract, so no one can run off with the money, payments happen from a phone, and a built-in commitment bond rewards members who pay in full.

Status: Contracts are deployed on Base and Arbitrum, accepting USDC and MXNB. A Bitso integration is in progress to let users fund tandas via traditional rails (ACH / Mexican banking), making the product reachable by non-crypto users.

Market signal: A low-effort, non-onchain tanda app already has 10K+ users in an otherwise uncontested category — demand is proven, and the competitive bar is on the floor.

Business model: 2% protocol fee on funds flowing into each tanda + 3% referral fee to tanda creators (a growth incentive). Future: sponsored/artist receipt NFTs.


2. Problem Statement

The pain

ROSCAs are a primary savings vehicle for the unbanked and underbanked. The model is beloved but structurally fragile:

Pain point Real-world impact
Organizer theft / "banker runs off" The single most cited ROSCA failure. One person custodies the pool with zero enforcement. Losses are total and unrecoverable.
Member default A member takes an early payout, then stops contributing. Remaining members absorb the loss.
Physical friction Weekly/biweekly in-person collection. Costs time, travel, and limits group size to people who can physically meet.
No record / no reputation A lifetime of disciplined saving leaves no verifiable trail. It builds no credit, unlocks no financial products.
No upside You get back exactly what you put in (minus the risk). Discipline isn't rewarded.

Quantified context

  • ROSCAs intermediate hundreds of billions of USD-equivalent annually worldwide (World Bank / financial-inclusion literature consistently cite ROSCAs as a dominant informal savings mechanism in emerging markets).
  • In Mexico alone, tandas are used by a large share of adults, the majority of whom are underbanked.
  • Stablecoin adoption in LatAm is among the fastest-growing in the world, driven by inflation hedging and remittances — the on-ramp behavior MiTanda depends on is already forming.

Competitive landscape

Player Onchain? True ROSCA / rotating payout? UX quality Notes
Generic onchain group-savings (e.g. Goodghosting/Halofi, Kolektivo-style) Yes No — goal-savings or yield pools, not rotating tandas Varies Closest in tech, but they don't model the tanda mechanic.
Existing Play Store tanda app No Yes Poor 10K+ users despite low effort — validates demand, signals an open lane.
Traditional in-person tanda No Yes N/A The status quo MiTanda displaces.
MiTanda Yes Yes Target: high Trustless + insured + on-ramped + reputation layer.

Insight: Nobody is doing an onchain, true-rotating, well-built tanda. The tech players skipped the mechanic; the mechanic players skipped the tech and the craft.


3. Target Market

TAM / SAM / SOM

  • TAM — Global ROSCA volume: Hundreds of billions USD-equivalent in annual pooled contributions across LatAm, Africa, South & Southeast Asia. At a 2% take, even a fraction of this is a very large fee pool.
  • SAM — Spanish-speaking LatAm + US Latino diaspora with smartphone + stablecoin reachability: Tens of billions in annual tanda volume among users who can plausibly fund via Bitso/stablecoins in the next 3–5 years.
  • SOM — 3-year realistic capture: Beachhead = Mexico + US→Mexico remittance corridor. Target low-single-digit % of reachable digital-tanda users. Benchmark: the incumbent's 10K users is the floor; a credibly better, trustless product should multiply that.

Methodology: top-down from ROSCA-volume literature, cross-checked bottom-up against the incumbent app's demonstrated 10K-user pull in a single under-served market.

Primary persona — "Lucía, the disciplined saver"

  • 28–45, Mexico or US Latino diaspora, smartphone-first, underbanked.
  • Already participates in 1–2 tandas/year with family, coworkers, or neighbors.
  • Job to be done: "Help me save a lump sum I couldn't save alone — without risking that the organizer disappears or someone defaults."
  • Fears: losing money to a dishonest banker; complexity; "crypto scams."
  • Wins with: trustless guarantee, paying from her phone, getting her commitment bond back as a bonus.

Secondary persona — "Marco, the organizer/creator"

  • The trusted community member who runs tandas today (social capital, does it for free).
  • JTBD: "Let me run a bigger, safer tanda and actually get rewarded for the work."
  • Wins with: the 3% creator referral fee, automated collection, no custody liability, a verifiable track record.

Tertiary persona — "Diaspora remitter"

  • Sends money US→MX; already touches stablecoins/exchanges.
  • JTBD: "Turn remittances into structured savings for my family back home."

4. Solution

Product vision

  • 1-year: The trusted, beautiful, mobile-first way to run an insured onchain tanda in Mexico — fundable by card/ACH via Bitso, settled in USDC/MXNB, with receipts and a join/completion identity.
  • 3-year: The reputation and savings layer for the LatAm underbanked — the completion soulbound token becomes a portable credit primitive that unlocks loans, better rates, and DeFi access; MiTanda expands across LatAm corridors and ROSCA cultures globally.

Core value proposition

"Save together, the way you always have — but no one can ever run off with the money, you do it all from your phone, and you get a bonus for paying on time."

Unique differentiators

  1. Trustless custody — the contract is the banker. Eliminates the #1 failure mode.
  2. Commitment bond / built-in insurance — 10% refundable bond aligns incentives; defaulters fund the diligent, full-payers get a bonus.
  3. On-ramped — Bitso ACH means non-crypto users can join. This is the wedge most onchain projects fatally ignore.
  4. Identity & reputation NFTs — join SBT, completion SBT (proof of full payment), and tradeable receipt NFTs.
  5. Cultural fit + craft — built for the tanda, not a generic savings pool, and actually well-designed.

Competitive moat strategy (addresses lowest score: defensibility 6/10)

Contracts are forkable, so the moat is not the code. It is:

  • Reputation data network — the completion SBT becomes a portable credit score that third-party lenders/dApps read. The longer MiTanda runs, the deeper the proprietary repayment graph. This is the durable moat.
  • Brand & trust — in a category defined by who you trust with your money, being the recognized, audited, never-rugged name compounds.
  • Network of active tandas + creators — creators with track records and recurring groups create switching costs.
  • First good-mover — owning the "trustworthy digital tanda" position before anyone else builds it well.

5. Detailed Feature Spec

MVP scope (Must-have)

  1. Create a tanda: set contribution amount, currency (USDC/MXNB), member count, frequency, payout order method.
  2. Join a tanda via invite link; mint join SBT.
  3. Fund contributions via wallet (USDC/MXNB) and via Bitso (ACH/card → stablecoin).
  4. Automated scheduled contributions + the 10% commitment bond.
  5. Automated rotating payout per schedule, enforced by contract.
  6. Default handling: forfeited contributions/bond redistributed to the tanda per rules.
  7. Bond refund + bonus distribution on full completion.
  8. Receipt NFT minted per payment.
  9. Completion SBT minted at cycle end (proof of full payment).
  10. 2% protocol fee + 3% creator referral fee handled in-contract.
  11. Dashboard: my tandas, next payment, payout date, status.

Prioritization (MoSCoW)

  • Must: items 1–11 above.
  • Should: push/SMS payment reminders; multi-language (ES first); creator analytics; in-app KYC where required.
  • Could: artist-commissioned receipt art; secondary-market view for receipts; reputation-score profile page.
  • Won't (now): paid advertising on receipts; cross-chain bridging UX; lending products on top of reputation (Phase 3).

User stories (sample, ~story points)

  1. As Lucía, I can join a tanda from an invite link without understanding crypto, so I can start saving. (8)
  2. As Lucía, I can fund my contribution with my bank account via Bitso, so I don't need to buy crypto first. (13)
  3. As Lucía, I get a reminder before each payment is due, so I don't accidentally default. (5)
  4. As Lucía, I receive a receipt NFT after each payment, so I have proof. (3)
  5. As Lucía, I get my 10% bond back plus a bonus when I complete, so discipline is rewarded. (5)
  6. As Marco, I can create a tanda and set the rules in under 3 minutes. (8)
  7. As Marco, I earn a 3% referral fee on funds from members I bring in. (5)
  8. As Marco, I never custody member funds, so I have no liability. (3)
  9. As a member, if someone defaults, the contract redistributes their forfeited funds fairly. (8)
  10. As a member, I receive the pot automatically on my payout round. (5)
  11. As a member, I earn a completion SBT proving I paid in full. (5)
  12. As a user, I can see all my active tandas and next due dates on one dashboard. (5)
  13. As a user, I can switch between USDC and MXNB tandas. (3)
  14. As a user, I can view a tanda's full payment history transparently. (3)
  15. As a skeptical user, I can verify on-chain that funds are contract-governed, not held by a person. (5)
  16. As a Spanish speaker, the entire app is in natural Spanish. (5)
  17. As a creator, I see analytics on my tanda's health and member status. (8)
  18. As a user, I can off-ramp my payout to my bank via Bitso. (13)

Key flow wireframe descriptions

  • Onboarding: Social/email login (account abstraction — no seed phrase) → language select → "Join a tanda" or "Create a tanda."
  • Join flow: Open invite → see amount, schedule, members, payout position → "Confirm & fund" → choose wallet or bank (Bitso) → join SBT minted → dashboard.
  • Payment flow: Reminder → one-tap pay → receipt NFT → updated dashboard with next due/payout.
  • Payout flow: Your round → auto-payout notification → option to keep in stablecoin or off-ramp to bank.
  • Completion: Final payment → bond + bonus returned → completion SBT minted → prompt to start/join the next tanda (growth loop).

6. Technical Architecture (product-level)

  • System overview: Smart contracts (deployed: Base + Arbitrum) handle custody, scheduling, payouts, bond, fees, and NFT minting. A mobile-first web/app frontend reads/writes via wallet or embedded account-abstraction wallet. Bitso integration bridges fiat ↔ stablecoin. An indexer serves dashboard/history data.
  • Tech stack rationale: L2s (Base/Arbitrum) for low gas on micro-payments — essential for small recurring contributions. USDC for stability/liquidity; MXNB for peso-native users. Account abstraction so non-crypto users never see a seed phrase.
  • Data model (high level): Tanda (rules, members, schedule, currency), Member (address, SBTs, payment record), Payment (receipt NFT), Payout, Bond ledger, Fee ledger.
  • Scalability: Stateless frontend; contract logic per-tanda; indexer scales reads independently.
  • Security: Third-party smart-contract audit before scaling custody volume (non-negotiable for a trust product); formal handling of default/edge cases; reentrancy and access-control review; transparent verifiable on-chain state as a feature.
  • Third-party integrations: Bitso (fiat on/off-ramp, KYC), wallet/AA provider, push/SMS notifications, NFT metadata/storage.

7. Business Model

Revenue streams

  1. Protocol fee — 2% of all funds flowing into each tanda. Primary, volume-scaling.
  2. Creator referral — 3% to tanda creators. (A growth cost/incentive, not net revenue — drives acquisition.)
  3. Future — sponsored / artist receipt NFTs (advertising or commissioned art). Speculative; activate at scale.
  4. Future — reputation/credit layer (rev-share with lenders reading completion SBTs). The long-term high-margin play.

Unit economics (illustrative framework)

  • Revenue per tanda = 2% × total contributions over the cycle. A 10-person tanda contributing the equivalent of $100/round across 10 rounds = $10,000 volume → ~$200 protocol revenue per tanda cycle.
  • CAC: Driven down by the inherent group-recruiting loop + 3% creator incentive; one creator brings N members per tanda.
  • LTV: Members run multiple tandas/year and refer others; completion SBT increases retention and unlocks future credit-layer revenue.
  • Margin: Software margins once contracts and ramp are built; main variable costs are on-ramp fees (Bitso), gas (subsidized on L2), and support.

8. Go-to-Market

Launch strategy

  1. Closed beta — recruit existing real-world tanda groups (intact trust networks) in one city. Migrate whole groups, not individuals.
  2. Soft launch — Mexico beachhead, ES-only, Bitso live.
  3. Public — expand to US→MX diaspora corridor, then broader LatAm.

Marketing channels (prioritized)

  1. Existing tanda organizers — recruit creators directly; they bring whole groups.
  2. Diaspora communities & remittance corridors — US Latino communities already touching crypto.
  3. Short-form social (TikTok/Reels) in Spanish — explain "the tanda where the banker can't run."
  4. Mine the incumbent app's 1-star reviews — target its frustrated 10K users directly with the fixes they're begging for.

Growth loops / virality (leverages virality 9/10)

  • Structural loop: you cannot run a tanda without inviting members → every tanda is an acquisition event.
  • Incentive loop: 3% creator fee rewards recruiting and sharing.
  • Completion loop: finishing a tanda prompts starting the next, re-triggering invites.

Partnerships

  • Bitso (on/off-ramp, distribution).
  • Stablecoin issuers (USDC/MXNB co-marketing).
  • Community orgs / fintech-inclusion NGOs in target markets.
  • Lenders/DeFi (future) to consume the reputation layer.

9. Success Metrics

  • North star: Total value successfully cycled through completed tandas (captures trust + volume + retention in one number).
  • First 6-month OKRs:
    • O1: Prove trust at small scale → KR: 100 tandas completed end-to-end with zero loss-of-funds incidents.
    • O2: Prove the ramp → KR: ≥50% of new members fund via Bitso (non-crypto-native).
    • O3: Prove the loop → KR: viral coefficient > 1 from creator referrals.
    • O4: Beat the incumbent's bar → KR: cross the incumbent's 10K-user floor with materially better retention.
  • Dashboard metrics: active tandas, completion rate, default rate, bond-refund rate, on-ramp conversion, CAC via referral, repeat-tanda rate.

10. Risks & Mitigations

Type Risk Mitigation
Technical Smart-contract bug with custody of real funds Independent audit before scaling; bug bounty; start with small pool caps.
Market Users distrust "crypto" Lead with trust/never-rug message; hide crypto via AA + Bitso; onboard intact trust groups.
Adoption On-ramp friction kills conversion Bitso ACH/card; off-ramp to bank; subsidize gas on L2.
Defensibility Fork/clone Compound the reputation-data moat + brand + creator network; move fast as first good mover.
Regulatory 2% fee on pooled funds + "insurance" may resemble unlicensed money-transmission/deposit/insurance activity Early legal counsel per jurisdiction; reframe "insurance" as a refundable commitment bond; structure as non-custodial protocol; KYC via Bitso.
Execution Solo/small team needs local trust + distribution Recruit creator-evangelists; partner with community orgs; hire for LatAm GTM.

11. Resource Requirements

  • Phase 1 (MVP/beachhead): Founder (product/contracts) + 1 frontend/mobile dev + part-time designer + smart-contract auditor (contract) + LatAm community/GTM lead (part-time/advisor).
  • Phase 2 (scale): + backend/indexer engineer, + growth marketer (ES), + support/community manager, + compliance/legal counsel.
  • Key hires to prioritize: LatAm GTM lead (trust/distribution) and compliance counsel — the two areas code doesn't solve.

12. Timeline & Milestones

  • Phase 0 — Hardening (now): Audit contracts; finish Bitso integration; account-abstraction onboarding; ES localization.
  • Phase 1 — Closed beta (next): 5–10 real tandas, intact groups, one city. Milestone: first fully-completed insured tanda with zero incidents.
  • Phase 2 — Soft launch (Mexico): Public, ES, Bitso live. Milestone: 100 completed tandas; viral coefficient > 1.
  • Phase 3 — Corridor expansion: US→MX diaspora; broader LatAm. Milestone: cross 10K active users; launch reputation-score profile.
  • Phase 4 — Reputation/credit layer: Open completion-SBT data to partner lenders. Milestone: first third-party product underwritten on MiTanda reputation.

13. Appendix

Competitive analysis detail

  • Generic onchain group-savings dApps: strong tech, but model goal-based or yield pools, not rotating ROSCA payouts. Gap = the tanda mechanic + LatAm cultural/on-ramp fit.
  • Incumbent Play Store tanda app: non-onchain, poor UX, yet 10K+ users. Demonstrates demand and a low competitive bar; its negative reviews are a ready-made feature roadmap.
  • In-person tandas: the true status quo; MiTanda's job is to be as trusted as your favorite organizer, but unable to betray you.

Research references (directions to substantiate before fundraising)

  • World Bank / financial-inclusion literature on ROSCA prevalence and informal-savings volume in emerging markets.
  • LatAm stablecoin-adoption and remittance reports (e.g. exchange/issuer market data) for timing evidence.
  • Primary research: interviews with active tanda organizers and members; teardown of the incumbent app's reviews; corridor sizing for US→MX remittances.

PMF baseline: Problem 9 · Market 8 · Uniqueness 9 · Feasibility 9 · Monetization 8 · Timing 8 · Virality 9 · Defensibility 6 · Team Fit 7 · Ralph Factor 9 → 8.2/10