UpMyB

Invoice-to-cash assistant

Reads invoices from email, tracks who owes what, and chases politely until it is paid. For: Agencies, suppliers, freelancers.

The problem

Invoices go out, then nobody tracks them. Chasing feels awkward, so it is done late or not at all, and cash flow suffers.

How it works

Built from: gmail, gsheets, razorpay, whatsapp, claude.

flowchart LR
  C(["Your customer"]) <-->|"asks, pays, gets updates"| APP["Your app<br/>Owner app: who owes what, one tap to send a reminder"]
  APP --> L{{"Your logic<br/>the rules that are yours"}}
  subgraph EX["Apps that already exist: APIs and MCP servers"]
    A0["Gmail<br/>Where invoices arrive and reminders are sent"]
    A1["Google Sheets<br/>The ledger the owner can open and edit"]
    A2["Razorpay<br/>Payment links and paid status"]
    A3["WhatsApp<br/>Reminders where people actually reply"]
    A4["Claude (AI)<br/>Reads each invoice and writes the reminder in the right tone"]
  end
  L --> A0
  L --> A1
  L --> A2
  L --> A3
  L --> A4
  L --> DB[("What it keeps<br/>Customers and contacts, Invoices and due dates, Reminder history")]
  L --> OWN["Admin dashboard<br/>Aged-debt view and reminder schedule settings"]
  classDef yours fill:#1691D6,stroke:#0a5f95,color:#fff
  classDef ext fill:#E6F3FB,stroke:#1691D6,color:#12112E
  class APP,L,DB,OWN yours
  class A0,A1,A2,A3,A4 ext

The logic

  1. When invoice email arrives: Read it, add a row to the ledger and create a payment link
  2. When 3 days before the due date: Send a friendly reminder with the link
  3. When on the due date: Send the invoice again with a short note
  4. When 7 days overdue: Send a firmer message and tell the owner
  5. When payment received: Mark paid, send a receipt and stop all reminders
flowchart LR
  subgraph R0["Rule 1"]
    direction TB
    W0{{"When: Invoice email arrives"}} --> T0["Then: Read it, add a row to the ledger and create a payment link"]
  end
  subgraph R1["Rule 2"]
    direction TB
    W1{{"When: 3 days before the due date"}} --> T1["Then: Send a friendly reminder with the link"]
  end
  subgraph R2["Rule 3"]
    direction TB
    W2{{"When: On the due date"}} --> T2["Then: Send the invoice again with a short note"]
  end
  subgraph R3["Rule 4"]
    direction TB
    W3{{"When: 7 days overdue"}} --> T3["Then: Send a firmer message and tell the owner"]
  end
  subgraph R4["Rule 5"]
    direction TB
    W4{{"When: Payment received"}} --> T4["Then: Mark paid, send a receipt and stop all reminders"]
  end
  S(["Start"]) --> R0 --> R1 --> R2 --> R3 --> R4 --> E(["Done and logged"])
  classDef when fill:#E6F3FB,stroke:#1691D6,color:#12112E
  classDef then fill:#1691D6,stroke:#0a5f95,color:#fff
  classDef end1 fill:#12112E,stroke:#12112E,color:#fff
  class W0,W1,W2,W3,W4 when
  class T0,T1,T2,T3,T4 then
  class S,E end1

What can be developed

The money (illustrative example)

The customer pays ₹1999 per business, per month. API and hosting costs: AI reading invoices ₹300, WhatsApp reminders ₹250, Hosting ₹100, together ₹650. Net profit ₹1349.

sankey-beta
Customer pays,AI reading invoices,300
Customer pays,WhatsApp reminders,250
Customer pays,Hosting,100
Customer pays,Net profit,1349

Watch out for

Build this for me