Frame the real job
Use AI to challenge the product brief, identify missing scenarios, compare alternatives and explain assumptions. The person remains responsible for choosing what is true and useful.
Last updated By Sho
Bila Boleh began with an uncomfortable question: if a spreadsheet already calculates retirement, what is genuinely worth building?
Distinguish a calculator from a persistent, connected financial planning system and see where AI helps without becoming the arithmetic engine.
Nothing personal. The worked checks below use fictional figures; do not upload actual financial records.
Inspect the architecture, challenge one double-counting failure, and define evidence that would make the system trustworthy.
A reusable checklist for state, deterministic calculations, assumptions, privacy and verification in AI-assisted product builds.
A good spreadsheet can already calculate compounded returns, inflation, drawdown and a retirement date. It can preserve a sophisticated model, too. A prettier dashboard on its own would not be a strong reason to build another product.
The actual question was different: can someone keep one coherent picture of the money they own, the debts they owe, the income they receive and the life they want — then return next month to ask a different question without rebuilding the plan?
That is the difference Bila Boleh is attempting. Not one answer, but a plan that can be revisited, corrected and challenged.
Don't build another calculator. Build a plan whose numbers still agree after the user changes something.
EPF · savings · holdings · income · debts · spending
Recorded facts + stated assumptions + deterministic rules
Retirement age · spending gap · accessible capital · scenarios
The public Bila Boleh planner brings EPF/KWSP, other savings, shares and dividends, household income, spending, assets and liabilities into a shared retirement outlook. The point is not to count how many calculators exist. It is to make the same underlying values drive the overview and the detail pages.
| Layer | Responsibility | What must not happen |
|---|---|---|
| Recorded facts | User-entered balances, assets, liabilities, income and spending. | Present an entered number as a live verified bank balance. |
| Planning assumptions | Inflation, returns, contribution rates, retirement ages and spending stages. | Quietly turn a chosen assumption into a guarantee. |
| Calculation engine | Deterministic projections, availability dates, cash flow and asset values. | Count the same transfer, repayment or dividend twice. |
| Saved plan | Keep inputs and scenarios consistent across pages and later visits. | Force someone to re-enter their working model every session. |
| Presentation | Explain the outcome, the shortfall and the assumptions behind the chart. | Confuse net worth with cash that can be spent today. |
The hard parts appear between the rows. Dividends can be reinvested or spent. Loan principal reduces debt but is not new wealth. A property can add net worth without funding next month's expenses. Retirement funds may have access-age restrictions. These are product and financial-model decisions, not prompt-writing problems.
Use AI to challenge the product brief, identify missing scenarios, compare alternatives and explain assumptions. The person remains responsible for choosing what is true and useful.
Let coding agents implement UI, parsers, model changes and regression tests inside explicit repository contracts. Require observable evidence, not an agent's declaration that it works.
Review test results, deployment status, model invariants, rule freshness and recovery paths. A passing code change is not by itself proof of production behavior.
AI can help write and inspect the product. Retirement arithmetic belongs to deterministic, testable code — not an LLM inventing a forecast.
That separation makes the numbers reproducible. It also means an AI assistant can explain a result without being its financial source of truth.
Use a fictional plan. Suppose a person records a shareholding that pays dividends, then chooses to reinvest those dividends instead of using them for monthly spending. A convincing interface might still show the income in two places. A dependable model must distinguish the economic event from spendable cash.
This is a proposed check to reproduce, not a claim that these exact five steps were run as a benchmark for this note. The useful measure is whether the whole financial story remains consistent after a controlled change.
At the time of this note, Bila Boleh offers browser-only planning by default, without connecting to a bank or brokerage. It also describes optional encrypted Sync for users who choose cross-device storage, alongside JSON export for portability. Browser-only copies are not encrypted at rest. The product's current privacy explanation describes the applicable choices and limits; this field note is not a security audit.
The trade-off matters. Saving in a browser is simple and private by default, but users can lose a device-only copy if browser storage is cleared. Sync adds recovery and security responsibilities. An export helps portability, but the file itself becomes sensitive. The interface needs to explain those differences rather than hiding them behind a Save button.
The real deliverable is not generated code. It is a question answered with traceable inputs, defensible rules, consistent state and checks another person can repeat.
This is a dated build reflection, not investment advice or an assertion that every possible financial edge case has been solved.