- Financial rules can become outdated.
- Edge tax and loan scenarios may not be covered.
- No lead generation or backend means a weaker commercial loop.
- Most calculators are low-frequency tools.
Case study 01 · Financial decision toolkit
Financial decisions,
made clearer.
KiraMY is a privacy-first educational toolkit for early-stage Malaysian money decisions. It does not replace a bank, government portal, or professional adviser; it helps a user understand the question before taking the next step.
RoleProduct, UI & frontend
PositionEducational decision support
Scope7 live calculators
EvidenceProduct built · market proof needed
Problem
Early financial decisions are often made before a person is ready to speak with a bank, adviser, or government agency.
A student estimating PTPTN payments or a young worker testing a first home loan needs a quick orientation: what inputs matter, which assumptions shape the result, and which official resource should come next.
Market reality
Malaysia already has mature calculators from banks, financial platforms, and official agencies. KiraMY is not trying to replace them or claim more authoritative data.
The product hypothesis is that a consistent orientation layer can still be useful at the beginning of a decision.
Faster understanding
Reduce each question to the inputs and outputs a first-time user needs to understand the decision.
Transparent assumptions
Show the method, review date, limitations, and official sources instead of presenting one unexplained number.
One interface language
Tax, loans, EPF, stamp duty, PTPTN, car finance, and rent-versus-buy use a consistent interaction model.
No forced lead form
Users can explore a sensitive scenario without submitting contact or financial details.
Early-decision audience
The current focus is students, young workers, and people forming a first view before seeking an official calculation or quotation.
Product response
I designed one consistent toolbox for seven common decisions, with one task per page and a readable result breakdown.
Guidance before precision
Plain-language context helps users understand what the calculator can and cannot answer.
Malaysia-specific context
RM formatting, local terminology, progressive bands, and links to relevant agencies keep the experience locally legible.
Progressive disclosure
Advanced inputs and detailed breakdowns appear only when they help, keeping the first interaction approachable.
My role
I took the suite from opportunity framing to deployed product.
I defined the scope, designed the shared interaction language, implemented the calculation logic and responsive frontend, wrote explanatory and SEO content, added trust notes and official links, and deployed the static site through GitHub and Vercel.
Product trade-off
No account system or backend is an MVP choice, not a belief that the product should never have them.
What the choice enables
Lower friction, no mandatory financial-data submission, simple deployment, fewer infrastructure risks, and low ongoing maintenance cost.
What the choice prevents
No cross-device sync, saved customer history, user-level personalisation, or reliable view of retention and repeat use.
Commercial consequence
Without consented contact capture or partner actions, the current product has weak lead generation and limited monetisation potential.
MVP conclusion
The trade-off is appropriate while the main question is usefulness. If demand and repeat intent are validated, optional accounts, a backend, or partner flows can be reconsidered.
Engineering reliability
A financial tool needs visible provenance and reproducible checks, even when it is presented as an educational estimate.
Current rule basis
Income tax currently uses Year of Assessment 2025 bands. A target identifier such as MY-INCOME-TAX-YA2025-v1 is planned once rules are extracted from page code into versioned modules.
Official sources and review date
Calculator pages link to LHDN, KWSP, Bank Negara Malaysia, and PTPTN. The current trust review date shown in the tools is 21 June 2026.
Known limitations
Results are simplified estimates. They do not cover every relief condition, bank-specific rate or fee, contribution-table rounding, future policy change, or individual eligibility case.
Automated test plan
KiraMY calculation fixtures are planned but are not yet part of the current automated test suite. The next step is boundary, zero-value, regression, and official-example fixtures for every calculator.
Reproducible example
Home loan input: RM450,000 financed at 4% p.a. over 30 years. Expected output: approximately RM2,148 per month using the standard reducing-balance formula.
Second fixture
Car finance input: RM80,000 financed at a 3% flat rate for 7 years. Expected output: RM16,800 interest, RM96,800 total repayment, and approximately RM1,152 per month.
Commercial next step
The next commercial question is not how to add more calculators. It is whether the current tools create enough trust and intent to support a useful next action.
Lightweight feedback
Add a short, privacy-conscious form for incorrect assumptions, missing cases, and general usefulness.
Anonymous intent survey
Ask what decision brought the user in and what they plan to do next, without requiring identity or financial values.
Actionable result pages
Pair each result with the relevant official resource, a checklist, and a clear next step rather than ending at the number.
Optional rule updates
Test a consent-based email subscription such as “notify me when Malaysian tax rules change,” kept separate from calculator access.
SEO content loop
Connect calculators with useful mortgage, PTPTN, tax, and first-salary content pages that answer the questions around the calculation.
Evidence before infrastructure
Only consider a backend, saved profile, or partner referral flow after feedback and intent data show a real reason to build one.
Current state
7
live tools share one interaction language and one local-first delivery model. This is product scope, not proof of traction: KiraMY currently has no claimed user, revenue, conversion, or retention result.
What I learned
Low-frequency tools need to earn trust quickly and make the next action useful. Clear assumptions and official links improve the decision experience, but a credible product also needs a way to learn whether users understood the result and acted on it.
What I would improve next
The next iteration prioritises reliability, portability, and evidence over feature count.
Rule versioning
Give every policy-dependent calculator an explicit rule ID, effective period, review date, and changelog.
Calculator test fixtures
Move calculation logic into pure modules and test official examples, thresholds, invalid inputs, and regressions.
Result export / print summary
Let users keep a dated copy of inputs, assumptions, rule version, result, and official follow-up links.
Privacy-friendly feedback channel
Collect calculation issues and intent without requiring financial values or an account.
Comparison pages
Help users compare scenarios such as different loan tenures or renting versus buying, not only produce one result.
Optional saved scenarios
Test local saved comparisons first; consider sync only if users show a repeat, cross-device need.