Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteen“Kitna aana hai, kitna dena hai — and the honest answer most evenings lives in three WhatsApp threads, a paper diary and memory, not in one place anyone could check.”
A shop or small firm doesn't lose money because nobody is watching it. It loses money because watching it means adding up unpaid invoices by hand, guessing which bills are actually due this week, and finding out the account is short only when a cheque bounces. None of that is a spreadsheet problem — it is a nobody-has-time-to-add-it-up problem. Laxmi never tells you what to do with the answer — it reports your own numbers and stops, because it is a regulated financial-domain agent with no route that can advise, invest or move money.
How it works
Three steps, and the third one stops exactly where a route that could move money or advise would begin.
Log an invoice, a bill or a spend when it happens — a quick entry or a photographed receipt for the parts of it that are text-readable today. Every amount is stored as an integer count of paise beside its currency, never a float, so a rupee figure can never quietly drift by a paisa on the way to a screen.
One cash position per currency, receivables aged by days overdue, payables due and committed, a budget that shows unconfirmed spend beside the total, and a forecast that lists what it assumed — including the bank feed nobody connected. Every figure is what this workspace recorded, not a projection dressed up as fact.
A reminder is drafted, not sent — an owner reads it and taps approve. A payment link is generated through a licensed gateway, never held by Laxmi itself. A low-balance alert states the fact and the date. Nothing past this step happens without a person, because a route that could move money or send unattended is exactly what this product does not have.
Every UPI tap, card swipe and cash note at a counter like this is a line in the cash position — or isn't, until someone records it.
One view
Computed from account opening balances plus the append-only ledger, not from a bank connection — Laxmi does not have one yet. If a customer paid you in a way this workspace never recorded, that payment is not in this number, and the page says so rather than presenting a partial figure with full confidence.
Get paid
Invoices are priced in integer minor units and aged in bands per currency. An invoice cannot be marked paid by editing a status field — only by recording the money arriving, so the receivables total can never be quietly nudged to look better than it is.
Look ahead
The weekly projection is built from recorded invoices, bills and templates marked recurring, labelled an estimate rather than a guarantee. Every run names what it assumed — and one of those assumptions is, plainly, that no bank feed is connected, so nothing outside this workspace's own records can be in the number.
Stay on budget
A category limit is compared against confirmed expenses only — but the count and value of anything logged and not yet confirmed is reported right alongside it. A half-entered month cannot read as on track just because three receipts are still sitting unconfirmed.
Follow up
Laxmi drafts a factual reminder naming the invoice, the amount and the days overdue, in a tone the collection-guard checks before it's ever shown to you. There is deliberately no send route Laxmi controls on its own: an owner reviews and taps approve, and even the owner's own added note is checked for language that drifts into advice or a threat.
What it does
Every one of Laxmi's specified capabilities has a real implementation — the label on each card comes straight from the backend's own status module, not from this page.
Cash held, owed to us, owed by us — from opening balances plus the ledger. Not a bank connection: nothing here reflects a transaction only the bank has seen. Connecting an account needs an Account Aggregator webhook secret this deployment has not been given.
Needs a keyAgeing by currency, and an invoice is only marked paid by recording the money arriving — never by editing a status.
Works todayVendor bills, due dates, part payments and a committed-payables total all work, and a bill photo can now be attached directly. Reading the amount and vendor off that photo automatically still needs a document-extraction credential this deployment hasn't set — confirming it stays a person's job either way.
Needs a keyDrafting, the tone gate and the seven-day cap all work locally. There is no send route — delivery needs a connected WhatsApp number or email provider.
Needs a keyEach row marked documented or projected. The schedule marker is the owner's own note — nothing here initiates a payment.
Works todayWeekly projection from recorded invoices, bills and recurring templates, labelled an estimate. Two assumptions — unpaid invoices, recurring templates — are real toggles; what you owe and your balance can't be switched off. Every forecast is later scored against what the ledger actually recorded, once its horizon has passed.
Works todaySaved scenarios run against a copy, so the real books stay untouched. Comparisons keep the order you asked for and never rank them.
Works todayRecording, categorising and confirming work today. A spend paid on the spot posts exactly one ledger entry, unconfirmed spend stays out of every total, and a receipt photo can now be attached to it directly. Reading that photo automatically still needs a document-extraction credential this deployment hasn't set.
Needs a keyConfirmed spend against the limit, with unconfirmed spend's count and value reported alongside — not folded silently into either total.
Works todayTemplates, schedules, pausing and a stale-amount flag all work. Sending the generated invoice needs a connected WhatsApp number or email provider.
Needs a keyConfirmation required on every suggested match, cross-currency pairs never suggested. Your own bank statement can now be imported as rows and matched against open invoices and bills the same way Wavy's payment orders already are — still a manually supplied statement; no live Account Aggregator feed is connected.
Works todaySort by due date, amount or vendor. The response states the ordering is not a recommendation about which bill to pay first.
Works todayAverage days to pay and overdue counts per customer, plus a workspace-wide summary across all of them — no score, rating or risk field anywhere, and customers come back in name order, never sorted by how late they run.
Works todaySeven Indian statutory deadlines from a ruleset held in code, each with a last-verified date and no amount on any of them — the calculation stays Khata's job. Professional tax now carries real per-state due dates for eight states once your compliance profile names one; an unregistered state still falls back to 'confirm yours locally' rather than guessing.
Works todayOwner-set thresholds checked against the live balance and the near-term forecast, each breach labelled with which one triggered it. Pushing the alert needs a provider.
Needs a keyCash, receivables and payables grouped by branch tag, plus the combined total. A real branch registry and per-user membership now back it: an owner or admin sees every branch, but anyone else sees only branches they were explicitly given — and nothing at all with zero membership rows, rather than defaulting to everyone seeing everything.
Works todayCreated through Wavy's own payments layer; paid state comes back from the gateway's signed webhook. Needs a UPI VPA or gateway credential — returns a clear 503 until then.
Needs a keyCSV of cash position, ageing, payables and the ledger, watermarked unaudited with a generation timestamp — and now a shareable link too, re-signable for seven days, with nothing touching this host's own disk. A formatted PDF still needs a rendering service this deployment doesn't have; it returns a clear 503 until then.
Needs a keyWhat Laxmi will never do
Laxmi is a regulated financial-domain agent. These are not features waiting to be built — they are routes that do not exist and a test that fails if one ever gets added.
Laxmi is Domain.FINANCIAL in the framework's registry. "You should invest in this fund" is refused by the same gate every financial-domain response passes through, and the refusal names a real adviser to talk to instead of answering.
There is no route whose path contains advise, recommend, invest, transfer, remit, withdraw, disburse or send — a test scans every declared route in Laxmi's router and fails if one of those words ever appears in a path. A payment link is created through a licensed gateway; funds custody never touches Laxmi.
The customer payment-behaviour report has no score, rating or risk field — a payment score is a credit assessment under another name. Sorting payables by due date or amount states plainly that the order is not a recommendation about which bill matters more.
If an owner adds a note to a reminder draft or a scenario that reads like investment advice — "you should invest the surplus in a debt fund" — Laxmi refuses to compose the message and redirects to a real adviser, rather than passing the sentence through because a human typed it.
Still needed
Every 'partial' or 'needs a key' label on this page traces to one of these — never a vague 'coming soon'.
The cash position works from what this workspace has recorded, not from a bank connection — that needs an Account Aggregator consent, which is not wired up yet. Until it is, a transaction that only happened in the bank is not in this number. Reconciliation and the forecast no longer wait on this: both work fully today from a manually supplied statement or your own recorded invoices and bills.
A drafted reminder, a generated recurring invoice, a low-balance alert and a payment link all stop at being created. Actually sending or issuing one needs a connected WhatsApp number, an email provider, a push provider or a UPI/gateway credential respectively — none of which Laxmi holds on its own.
A vendor bill or receipt can be entered by hand today, and a photo can now be attached to it directly through a presigned upload — nothing touches this backend's own disk. Text already typed or pasted is read by a shared document agent today; automatically reading the scanned image itself still needs an OCR credential this deployment hasn't set. Confirming an amount stays a person's job either way.
CSV exports and a shareable, time-limited link both work today — the object-storage blocker behind the share link is gone. A formatted PDF still needs a rendering service this deployment doesn't have; it returns a clear 503 naming that until one is configured.
Not sure which one
All three touch money, and from outside it will not be obvious which to open first. This page will not pretend the line between them is cleaner than it is.
Running the business day to day — what you're owed, what you owe, a forecast, a budget. This is operational cash flow, not the books themselves.
The actual double-entry ledger, kept in a state your accountant can review. Khata does not replace your CA — it stops at handing the CA a reviewable pack.
Read-only banking information pulled from your own accounts with your consent — statements, balances, a loan-readiness checklist. It cannot move money and is not a lender.
There is an open question inside the product about whether Laxmi and Khata eventually merge into one ledger. They are not there yet, and building as if they already had would be its own kind of dishonesty.
Before you switch
Tell us how you track money today and we'll tell you plainly what Laxmi can carry now, and what still needs your own bank consent or a connected number.
Questions
No. Laxmi reports what this workspace's own numbers say and stops there. It is Domain.FINANCIAL in the framework's registry, so investment, loan, insurance and tax advice are refused by the same gate every financial response passes through, and a test scans every route Laxmi declares to prove none of them can advise, transfer, remit, withdraw or send.
No. A payment link is created through a licensed payment gateway's own API, and the paid state comes back from that gateway's signed webhook — Laxmi never itself holds, moves or settles funds. The bill scheduler lets you mark a bill as scheduled for your own tracking; it never initiates a transfer.
No, and it says so on the screen every time it appears. It is a mechanical projection built from your own recorded invoices, bills and recurring templates, with every assumption it made listed alongside the number — including the fact that no bank feed is connected, so nothing outside this workspace's own records can be part of it.
Because hiding it would let an incomplete month read as on track. The limit is checked against confirmed expenses, and the count and value of anything logged but not yet confirmed is reported right beside that total, not inside it and not omitted.
No. Laxmi drafts a factual reminder — invoice number, amount, days overdue — and an owner reviews and approves each one individually before it goes anywhere. There is no send route Laxmi controls unattended, the tone is checked before you ever see the draft, and even an owner's own added note is checked for language that drifts into advice or a threat.
No. The customer payment-behaviour report shows average days to pay and how often invoices went overdue — factual history only. There is no score, rating or risk field anywhere in the response; that would edge into a regulated credit-assessment function Laxmi deliberately stays out of.
All three touch money, and from outside it will not be obvious which to open first. This page will not pretend the line between them is cleaner than it is. Laxmi: Running the business day to day — what you're owed, what you owe, a forecast, a budget. This is operational cash flow, not the books themselves. Khata: The actual double-entry ledger, kept in a state your accountant can review. Khata does not replace your CA — it stops at handing the CA a reviewable pack. Dena: Read-only banking information pulled from your own accounts with your consent — statements, balances, a loan-readiness checklist. It cannot move money and is not a lender.
