Blog | Dream Home is a real estate workflow, not a mortgage calculator

Buying a home in Chile is not one calculation.

It is a messy comparison between salary, savings, UF, credit capacity, interest rates, property price, location, quotes and uncertainty. People usually solve that mess with spreadsheets, screenshots, browser tabs and conversations.

Dream Home starts from that reality.

The problem is not the formula

A mortgage calculator can tell you an estimated payment. That is useful, but it is not the full decision.

The real questions are closer to this:

which homes are actually within reach?
how much depends on the down payment?
what happens if the UF changes?
how does the location affect the decision?
which property should I keep comparing?
what quote or document is still missing?

When those questions are spread across tools, the decision becomes harder than it needs to be.

Why Chile needs local context

A housing tool for Chile has to understand local financial language.

UF matters. The down payment matters. The common idea of keeping a dividend within a reasonable share of income matters. The map matters because two properties with the same price can mean very different lives.

If the product ignores that context, it becomes generic. Dream Home tries to keep the local decision visible.

What Dream Home is trying to solve

Dream Home is not only a mortgage capacity calculator. It is a workspace for comparing home buying scenarios.

The public app shows the product direction:

estimate buying capacity
work with UF assumptions
compare candidate properties
review map context
keep the decision in one place

That last point is the important one. The product should remember the comparison so the user does not have to rebuild it every time.

How I think about the product

For me, Dream Home is a product exercise about turning a spreadsheet habit into software.

The spreadsheet exists because the decision is real. People need columns, notes and comparisons. The product should not fight that. It should preserve the useful parts and remove the friction.

That means Dream Home should behave like a decision surface:

each property becomes a candidate
each financial assumption is explicit
each comparison can be revisited
location is part of the decision
exports and notes are allowed, not treated as failure

The product is useful when it makes the next conversation easier.

What other people can reuse from this idea

The pattern applies beyond housing.

Any high stakes decision has the same structure:

options
assumptions
constraints
comparisons
follow up actions

If a product captures those five pieces, it becomes more useful than a single calculator.

That could apply to insurance, credit, vendor selection, internal platform choices or even career decisions. The product does not need to decide for the user. It needs to make the decision clearer.

What Dream Home should not do

Dream Home should not pretend to be financial advice.

It can help users compare assumptions, understand gaps and organize information. It should not tell someone that a property is “the right decision.”

That boundary matters. The product is strongest when it makes uncertainty visible.

What I would build next

The most useful improvements are around continuity:

save multiple scenarios per property
compare properties by financial gap and location
track quotes or bank conversations
add clearer export views
explain assumptions in plain language

Those features keep the product close to the real process of buying a home.

References

Dream Home is interesting because it treats housing as a workflow. The calculator is only one piece. The comparison is the product.