Mandy S

Product Manager / Selected work

01 / Overview — Contents

Home / Selected Work / HomeScope SG

HomeScope SG

2026 · PrototypeProptechSingapore HousingDecision Support

A housing decision engine
for Singapore homebuyers

A buyer-first prototype that turns representative property scenarios into clearer housing decisions by layering lease, CPF, financing and MRT context into one comparison workflow.

Explore the prototype
Role
Product strategy · UX/UI · Prototype build
Scope
Discovery · Decision logic · Interaction design
Status
Working prototype · Representative dataset
Tools
Lovable · Product logic modelling · Figma
homescopesg.lovable.app
01
HomeScope SG / Current prototype

A working decision-support prototype. Representative scenarios and imagery; not live listings.

The harder problem is not finding homes.
It is knowing whether they still work for you.

Buyers already have discovery tools. The harder work is interpreting remaining lease, CPF implications, financing assumptions, MRT proximity and long-term fit across fragmented sources.

Mainstream property portals are primarily designed around discovery and enquiry flows. HomeScope explores a different layer: decision support, with the buyer’s constraints visible alongside the property.

  1. 01 →Search

    Find possible homes

  2. 02 →Cross-check

    Interpret the context

  3. 03 →Calculate

    Understand assumptions

  4. 04 →Shortlist

    Compare trade-offs

  5. 05 Decide

    Verify before committing

From property attributes
to buyer consequences.

Principle 01

Show the property in the buyer's time horizon

Purchase year and buyer age change how remaining lease should be interpreted.

Principle 02

Surface decision signals, not just raw attributes

Prioritise remaining lease, age-95 coverage, CPF signal, estimated mortgage and estimated cash top-up.

Principle 03

Keep the tool transparent and non-transactional

Representative scenarios and explicit assumptions—not live listings, duplicate entity-resolution or agent services.

The housing
decision engine.

Fig. 02 / From scenario to comparison

  1. 01
    ↓

    Property scenario

    Price · property type · tenure · lease start · MRT distance

  2. 02
    ↓

    Buyer context

    Purchase year · buyer age

  3. 03
    ↓

    Lease decision

    Remaining lease at purchase · years to age 95 · covers buyer to 95? · lease remaining at 95

  4. 04
    ↓

    CPF signal

    No lease-duration restriction / Eligible for CPF use, subject to limits / CPF use may be pro-rated / CPF use generally unavailable / Review

  5. 05
    ↓

    Financing assumptions

    Loan type · LTV · rate · tenure · monthly CPF OA available

  6. 06
    ↓

    Estimated financing output

    Estimated mortgage · estimated cash top-up · HDB tenure constraint / potential LTV prorating signal where applicable

  7. 07
    ↗

    Shortlist / compare

    Bring the decision signals together, side-by-side. No overall winner or score.

HomeScope does not calculate personalised CPF entitlement, lender approval, MSR/TDSR outcomes or exact HDB loan approval. It uses transparent editable assumptions to help buyers interpret likely trade-offs.

Four surfaces.
One decision workflow.

homescopesg.lovable.app
A
Discovery feed

Cards foreground remaining lease, age-95 coverage and estimated cash top-up instead of treating listings as static inventory.

homescopesg.lovable.app
B
Property detail

A scenario expands into lease context, financing assumptions and CPF-related signals with explicit methodology.

homescopesg.lovable.app
C
Browse MRT

A simplified MRT schematic supports station-led browsing and 500 m / 750 m / 1 km distance filtering.

homescopesg.lovable.app
D
Shortlist comparison

Buyers can compare 2–3 shortlisted homes side-by-side on price, PSF, remaining lease, age-95 coverage, CPF signal, estimated mortgage, estimated cash top-up and MRT distance.

Current prototype captures · Source labels (PropertyGuru, 99.co, EdgeProp, SRX, HDB Resale, Ohmyhome and Stacked Homes) are illustrative within a representative dataset, not live feeds. Images are representative, not exact listing photos.

The decisions behind
the decision support.

01

Purchase year became a first-class input

A property should be evaluated at the buyer's intended purchase point, not only in the present.

02

Age 95 became the more meaningful signal

The product asks whether the remaining lease covers the buyer to age 95, reflecting current CPF/HDB rules where age-95 lease coverage can affect CPF usage limits and HDB loan-to-value limits. This signal alone does not determine approval or exact CPF entitlement.

03

Financing assumptions are visible and editable

Expose loan type, LTV, interest rate, tenure and monthly CPF OA assumption rather than hiding them inside a calculator.

04

The prototype stays honest about scope

Representative dataset and imagery. “Open source site” redirects to source platforms. There is no live listing ingestion, duplicate entity-resolution or agent/contact workflow.

05

MRT is a decision filter, not decoration

The map was redesigned as a station-selection and distance-filtering interaction, with clearer selected-line labels and “Show homes” as the outcome. MRT Distance is proximity, not a routed walking-time calculation.

Building sharpened
the product thesis.

01 / Initial assumption →

A better buyer product mainly needed cross-platform aggregation.

01 / What changed →

Aggregation alone did not create a meaningfully better decision.

01 / Product response

Shifted the product thesis toward a housing decision-support engine using buyer context and consequences.

02 / Initial assumption →

Generic lease-health scores would simplify the problem.

02 / What changed →

Arbitrary red/amber/green thresholds masked the actual Singapore housing consequence.

02 / Product response

Replaced them with remaining lease, age-95 coverage and CPF-related signals.

03 / Initial assumption →

Extra prototype affordances such as duplicate badges and contacted states made the product feel more complete.

03 / What changed →

Those UI states implied capabilities that were not implemented.

03 / Product response

Removed duplicate-detection and agent-contact surfaces and tightened provenance/scope language.

A working prototype.
Not a validated outcome.

What the prototype demonstrates

  • Buyer-specific lease interpretation using purchase year and age
  • Age-95 coverage as a clearer decision signal
  • Editable financing assumptions and estimated cash top-up
  • MRT-led discovery with selectable distance radius
  • Shortlist and 2–3 property comparison
  • Transparent representative data and non-transactional scope

What still needs validation

  • Whether these signals improve real buyer confidence or decisions
  • How buyers interpret and trust CPF/financing signals
  • Whether shortlist and comparison create meaningful repeat-use value
  • Official / production-grade property and transaction data integrations
  • Production-grade listing freshness and ingestion architecture

Evidence status / Prototype behaviour reviewed. No validated real-user outcome metrics are claimed.

The prototype tests one product thesis: property discovery becomes more useful when the constraints behind the decision are visible at the same time.

Explore the prototype

/ Current prototype