Start with the borrower’s question.
A mortgage website serves people at very different moments. Someone beginning to plan a purchase needs direction, while a buyer with an accepted offer needs a clear way to act. I created this proposal through BoiseWebCo to help Fulcrum’s website recognize those differences before sending everyone into the same application.
The homepage leads with a guided start. Visitors choose buying, refinancing, or exploring their options, then identify their current stage. The resulting recommendation makes the next step understandable, whether that means preparing for an application or beginning a focused conversation.
The journey uses progressive disclosure rather than a long qualification form. Goal and stage stay part of the route, making the context visible as the visitor moves through the demonstrated handoff. The concept explores how that information could support the existing secure application and team; it does not claim the production systems can already receive it.
Calculators create another useful entry point. Payment, affordability, refinance, and amortization tools give people a way to explore a scenario and bring a better question to the next conversation. Their estimates are framed as planning aids, with lending terms and eligibility left to the appropriate professional process.
I retained Fulcrum’s recognizable identity and used a consistent hierarchy across the homepage, guided journey, team content, and existing-client path. The proposal also demonstrates contact and portal states while making the boundary between a frontend preview and a working operational system explicit.
This is a proposal prototype, not Fulcrum’s launched website or evidence of improved applications. Production would require confirmed messaging and licensing, validated borrower paths, secure application and portal integration, appropriate consent and privacy handling, and measurement of guided-start completion and downstream contact or application activity.
