Mortgage Calculator Suite
Two embeddable calculators for a Brisbane mortgage brokerage — stamp duty and transfer costs, and borrowing capacity — built to end in a real number, not a lead form.
Two small calculators built for a Brisbane mortgage brokerage's website: one estimates stamp duty and transfer costs by state, the other estimates borrowing capacity from income and deposit. Both are embeddable widgets, not standalone apps.
Why a calculated number, not a quiz that ends in a form
The easy version of this brief is a five-question quiz that ends with "enter your email to see your result." Both calculators here do the opposite: they run the real calculation — stamp duty by state, borrowing capacity against a mandated assessment-rate buffer — and show the actual number first. The stamp duty tool follows its result with an optional assessment offer; it doesn't gate the number behind one.
Why the disclaimer is a designed element, not fine print
Borrowing-capacity estimates are compliance-sensitive — a wrong impression here isn't just a bad UX outcome, it's a regulatory one. The disclaimer on the result card is set at full readable size with its own visual block, not shrunk into grey 10px type at the bottom, because the estimate is genuinely provisional and the interface should say so as clearly as it says the number.
Why they're separate components, not one wizard
Stamp duty and borrowing capacity are two different financial questions with different inputs and different state-specific logic. Splitting them into two focused calculators, each embeddable independently on whatever page needs it, keeps either one simple instead of forcing a single mega-form to cover both.