Roadmap
What comes next, and when.
Pathayam is built by one person in the evenings — four or five hours in a good week. These dates are paced for that, honestly, rather than for a team that does not exist.
How to read this
Everything below is an intention, not a commitment. Nothing here is sold, nothing is pre-paid, and an item can move or be dropped if it turns out to be the wrong thing to build — which happens, and is usually a good outcome rather than a failure.
The order is deliberate. Cheap and safe work comes first, and anything that touches the accounting engine — the part that guarantees your accounts, envelopes and Ready to Assign always reconcile to the rupee — is treated with more suspicion than anything else, because that guarantee is the product.
Two items near the bottom depend on decisions that are not about engineering at all. They are listed as longshots and may never happen. Saying so on the roadmap seems better than leaving them implied.
Recently shipped
So the pace above has something to be measured against.
- Schedules on a weekday — “the first Sunday of each month”, “the last Friday”, alongside the existing date rules. Sep 2026
- Envelope lines everywhere — one control for splitting across envelopes, on adding and editing both transactions and schedules. The first line takes whatever the others leave, so the lines can never disagree with the total. Sep 2026
- Capital gains in the tax estimate — sorted by asset class and holding period, taxed at their own rates rather than slab rates. Sep 2026
- Sign in without Google — a password, or any OpenID Connect provider you already run. Sep 2026
Planned
In order. Each phase starts when the one before it lands, so a slip early moves everything after it — which is why the later dates are wider.
-
Locked envelopes Q4 2026
Mark an envelope so its money cannot be moved out — school fees, the insurance sinking fund, anything that must survive a tight month. Adding to a locked envelope always works; only taking from it is refused, and spending you actually did is still recorded.
Roughly 4–6 weeks.
-
Targets on a whole group Q4 2026 – Q1 2027
Set one target across a group of envelopes rather than on each, and see the group’s own subtotal on the budget screen. Useful when you care that “Food” gets ₹18,000 and not how it divides between groceries, vegetables and eating out.
Roughly 10–16 weeks for both halves.
-
Spending in another currency Q2 2027
Enter a transaction as $40 and have it stored as the rupees it cost. Your envelopes stay rupee envelopes — the conversion happens as you type, not inside the budget.
With one honesty built in: on a card used abroad the real rupee figure is your bank’s, markup and cross-currency fee included, which is typically a few percent away from a market rate. So the converted amount is marked an estimate until your statement arrives, and then corrected to what you were actually charged.
Roughly 8–12 weeks.
-
Card milestones Q2 – Q4 2027
Track spend against the thresholds your cards actually use — per statement cycle, per financial-year quarter, and per financial year — so an annual fee waiver or a quarterly voucher does not pass you by unnoticed.
It will say plainly that it is an estimate. Bank statements and SMS do not carry the merchant category reliably, so the rules work off your envelopes and payees, which is close but not the issuer’s own arithmetic.
Roughly 14–20 weeks.
-
Logging by chat Q4 2027 – Q1 2028
Send “450 groceries hdfc” to a Telegram bot and have it land in your budget, with a confirmation before anything is written. Telegram first because it needs nothing but a bot token and works on a home server behind a normal router.
Roughly 10–16 weeks.
Longshots
These are wanted, and neither is blocked on effort. Both are blocked on a question that has nothing to do with code, and they may never happen.
Account Aggregator sync No date
Pulling transactions automatically through the RBI’s Account Aggregator framework requires being a registered Financial Information User — an entity-level registration with an aggregator, not something an individual household can hold. It could only work for instances we host, and only if your financial data passed through us on the way to you.
That is the opposite of how Pathayam is built, so it is not a thing we will do quietly. If it ever happens it will be an explicit, separate, opt-in choice, described in full before you make it — and it is entirely possible the answer stays no.
WhatsApp logging No date
The same question in different clothes. WhatsApp requires a publicly reachable webhook, which a self-hosted instance behind a home router does not have — so it would mean your messages passing through a relay we operate. Telegram achieves the same thing without that, which is why Telegram is on the plan above and this is not.
Considered and set aside
Listed because “we thought about it and decided against it for now” is more useful than silence.
- Envelopes that hold foreign currency. Different from entering a transaction in another currency, which is planned above. An envelope that genuinely holds dollars either breaks the guarantee that everything reconciles, or splits Ready to Assign into one figure per currency. Rupees only, on purpose.
- Envelopes nested inside envelopes. Group subtotals are planned; envelopes that fund each other are not. A parent holding money while its children also hold money is an easy way to count the same rupee twice.
- Reward points arithmetic. Milestones are planned; points accrual is not. Rates, accelerated categories and monthly caps change often enough that the numbers would go quietly stale, which is worse than not showing them.
Want something that is not here?
The roadmap is shaped by what households actually run into. If something is missing for you, say so.
Last reviewed 20 September 2026.