Tax information is a perfect example of a problem that is important, searchable and unnecessarily difficult to use.
The information exists. Rules are published. Tax slabs, rebate limits and definitions can be found. But a normal person rarely wants to read a long document and manually translate every rule into arithmetic.
They want to answer a much smaller question:
“Given my numbers, what does this mean for me?”
That is the product problem behind TaxHishab.com.
I started it as a practical Bangladesh-focused utility site: take rules that are normally buried inside official language, convert them into transparent calculations, and make the result usable from a phone without forcing someone through a spreadsheet.
Over time, the idea expanded from one calculator into a small collection of financial tools and explanatory content.
The real product is not the formula
It is tempting to think a tax calculator is mostly arithmetic.
It is not.
The difficult part is deciding how the user moves from a messy real-life situation to the inputs the formula expects.
For a tax tool, that includes questions such as:
- Which assessment or income year applies?
- What counts as taxable income?
- Which threshold or slab applies?
- Is a rebate based on investment, taxable income, or the lower of multiple limits?
- Which assumptions should be visible?
- What should happen when a user leaves a field blank?
- How do you explain a result without pretending to provide personalized tax advice?
A formula can be mathematically correct and still produce a terrible product.
The interface has to make the meaning of the formula understandable.
What TaxHishab includes
The site has grown around a simple principle: each tool should answer one concrete question.
That has included tools such as:
| Tool | User question |
|---|---|
| Income Tax Calculator | How much tax could apply to my taxable income? |
| Maximum Rebate Calculator | What is the maximum rebate amount under the applicable rules? |
| Zakat Calculator | How can I estimate Zakat using current Nisab assumptions? |
| Retirement Calculator | What could a long-term retirement target look like? |
| Trade Explorer | What does Bangladesh’s import/export data show for a product or market? |
These tools are different, but the product pattern is similar:
structured inputs → transparent calculation → useful output → supporting explanation
That consistency matters. A site feels much more trustworthy when each tool behaves predictably.
Versioning rules is a product requirement
A calculator built from policy is not “done” when it launches.
Rules change.
That means the underlying product needs to distinguish between interface code and policy configuration.
A bad implementation scatters numbers directly through UI components:
if income > X:
tax = ...That becomes dangerous as soon as the next tax year changes a threshold.
A better mental model is:
User Interface
↓
Calculation Engine
↓
Year-specific policy configuration
↓
Result + explanationThe exact implementation can vary, but the principle is the same: rules should be replaceable without rebuilding the whole product.
It also makes testing easier.
For every year, you can maintain example cases:
- below threshold;
- exactly at threshold;
- one slab boundary;
- multiple slabs;
- maximum rebate edge case;
- zero or missing values.
If a future update changes a rule and one of those examples suddenly produces an unexpected answer, that is a useful warning.
Explainability beats cleverness
Financial calculators are not places to be mysterious.
A user should be able to understand why the answer looks the way it does.
A good result screen therefore needs more than one giant number.
For example:
Estimated tax: BDT X
Underneath that, the product should explain:
- taxable income used;
- tax-free threshold;
- slab-by-slab calculation;
- applicable rebate or credit;
- final estimated liability.
That creates something much more useful than a black-box calculator.
It also gives users a way to spot incorrect inputs.
If the result looks strange, they can inspect the path rather than assuming the website is wrong.
Zakat created a different data problem
The Zakat calculator introduced a different challenge: some inputs are not fixed policy values.
Nisab can depend on gold or silver values, and market prices change.
That means the product has to separate:
- religious calculation assumptions;
- weight units;
- current market values;
- the user’s assets and liabilities.
A useful interface should make those assumptions explicit instead of hiding them.
This is a recurring lesson in data products:
When an output depends on a changing external value, show the value and its source rather than pretending the number is permanent.
Calculators need guardrails
A public financial tool should also be very clear about what it is not.
TaxHishab is designed for information and estimation. It is not a substitute for professional tax, legal or investment advice.
That distinction belongs in the product itself.
Useful guardrails include:
- visible year/version labels;
- source references where practical;
- methodology notes;
- an update date;
- disclaimers;
- examples;
- clear error states.
Trust is partly a data-quality problem and partly an interface problem.
Why I added content around the tools
A calculator can answer what.
Content helps answer why.
Someone may calculate a number and immediately ask:
- Why is the result different from last year?
- What does a rebate actually mean?
- Which inputs should I include?
- Why does Zakat change with the selected metal?
- How should I interpret a trade statistic?
That is why I do not see the site as a directory of calculators.
The stronger model is:
Search question
↓
Useful explanation
↓
Interactive calculator/tool
↓
Methodology + source
↓
Related questionThat structure is better for users and much more defensible than producing dozens of thin pages around keywords.
The Trade Explorer changed the scope
The Trade Explorer pushed TaxHishab beyond personal finance.
The idea is to let someone search a product and explore Bangladesh-related trade data visually: how much was imported or exported, which partner countries were involved, and how the pattern changed over time.
The important shift is that the site is no longer only translating formulas.
It is also translating public data into decisions.
For a small business owner or someone evaluating a product idea, a raw trade database can be intimidating.
A search box, chart and clear filters can make the same information much more approachable.
What I learned from building it
1. Small public tools create real product discipline
A personal project still has production users.
Inputs will be weird. Phones will be small. People will misunderstand labels. External data will fail. Search engines will discover pages you forgot existed.
That forces better decisions.
2. Correctness has layers
There is:
- mathematical correctness;
- policy correctness;
- data freshness;
- interpretation correctness;
- interface clarity.
Passing one does not guarantee the others.
3. “Simple” interfaces require more thinking
The user should not need to understand the internal data model.
Every complexity removed from the interface has to be resolved somewhere else: defaults, validation, naming, documentation or preprocessing.
4. Useful beats comprehensive
It is easy to imagine fifty calculators.
That is not necessarily better.
A smaller set of tools that are maintained, explained and actually useful creates more value than a large graveyard of barely maintained pages.
What I want the product to become
The long-term direction is not “more calculators at any cost.”
I want TaxHishab to become a collection of Bangladesh-specific decision tools.
That could mean:
- tax;
- personal finance;
- trade data;
- investment-related calculators;
- public-data explorers;
- practical explainers.
The common thread is not the topic.
It is the interaction:
Take something complicated, make the assumptions visible, and let the user explore the answer themselves.
That is also why I consider TaxHishab one of my most useful data projects.
It sits exactly where I like working: data, product design, public information and practical decision-making.
Explore the live project: TaxHishab.com
Important: calculators and articles on TaxHishab are informational tools, not individualized professional advice. Always verify important legal, tax or financial decisions against current official rules and your own circumstances.