Upaman Research

Last reviewed: July 26, 2026

Who writes this site

Research and content on Upaman are the work of one person: Shravan Cherukuri, a software engineer. He builds the calculation engines, writes the guides, and maintains the site. There is no separate research department, and this page exists so you know exactly who is accountable for what you read here.

You can reach him through the contact page, or read more about the project on About Upaman.

What that means for accuracy

A one-person site cannot lean on institutional authority, so it has to be checkable instead. Three things make that possible:

Rules come from primary sources. Tax bands, contribution ceilings, and statutory charges are taken from published statutes, official rate tables, and government or regulator releases — not from other calculator sites. Each region-specific tool states its tax year, jurisdiction, and currency so the assumption set is visible.
Worked examples are generated, not typed. The numbers in the prose come from the same engine the calculator runs. That makes it structurally impossible for the explanation to drift away from the result when a rate changes.
The engines are unit-tested. Calculation logic is covered by automated tests that assert documented worked examples, statutory boundaries, and slab edges, so a rate update that breaks an assumption fails before it ships.

What this page is not

Upaman is educational planning software written by an engineer, not by a chartered accountant, tax advisor, or licensed financial professional. Nothing on the site is personal financial, tax, or legal advice. For decisions with real money at stake, confirm the output against the official source the tool cites, or against a qualified professional.

Corrections

If a figure looks wrong, it may well be. Reports are welcome and are treated as bugs: reproduce, fix the engine, update the tests. See the Corrections Policy for how issues are logged and acknowledged.