I explored Huspy’s mortgage calculator

I explored Huspy’s mortgage calculator through the lens of Progressive Disclosure.

The question I wanted to test was simple:

Does every input need to be visible from the start?

In the current experience, users see predefined mortgage rates alongside a manual percentage field, even when the preset already provides that rate. The rate choice also appears before users fully define their property value, downpayment, and loan duration.

In this design exploration, I reorganized the flow so users first define their mortgage context, then choose an interest rate. Predefined rates remain immediately available, while Custom Rate reveals the manual interest-rate field only when the user explicitly needs it.

The goal wasn’t to remove flexibility. It was to keep the common path simple while preserving advanced control for users who need it.

This is a design exploration based on the publicly visible experience, not a claim that Huspy’s current solution is wrong. Real user behavior, mortgage knowledge, business constraints, and usability testing would still be needed to validate these decisions.

Would you prefer the custom interest-rate field visible upfront, or only when you choose a custom rate?