Turning 25 contact cards into 25 lead-capture funnels

The engagement started as "fix Bill's landing page." The competitive analysis ended it as something else. Every serious loan officer page in the benchmark set, from a solo operator running one high-converting page to a national lender running 2,800+ officer pages on a single template, treated the page as a conversion surface with purpose, proof, and path. HouseAmerica's 25 pages treated them as directory entries.

So the finding I delivered was not a design critique. The gap is not design, it is product thinking. And the fix is not one better page, because one better page leaves 24 broken ones and no leverage. The recommendation became a template system: shared modules, the flagship home-equity product block, lead magnet, FAQ, product grid, company stats, plus per-officer CMS fields for bio, testimonials, stats, and booking link. Deployed once, cloned 25 times.

The client's own words made the third audience explicit: rebuilt pages would double as a recruiting asset when pitching loan officers at competitor firms. One system, three audiences: homeowners, buyers and their agents, and recruitable loan officers.

A fast home-equity product became the hero of every page rather than sitting inside a product list, because it was the single offer that worked on all three audiences at once. The flagship product card is the only one on the page carrying a button. Everything else earns a "Learn more" link. Hierarchy as a business decision, not a styling one.

The recruiting track was restructured into three tiers. Asking a currently employed loan officer to book a call as step one was the original design's mistake: commitment has to be priced to what the visitor is risking by taking it.

Officers lost the ability to make a page "theirs" beyond the CMS fields. The system accepts that deliberately: consistency, maintainability, and a five-year-stale site all argue that governance wins in this case.

The system was built from scratch and locked before the build: a navy anchor connected to the existing brand, a golden wheat accent, soft linen backgrounds reserved for the flagship product sections only, and a full spacing, card, badge, and button vocabulary.

Two decisions worth pointing a reviewer at. The trust bar renders every stat in white except the single most impactful number, which takes the accent: one gold number reads as signal, five read as decoration. And gold eyebrow text failed contrast on light backgrounds, so eyebrows became navy text with a gold left border, keeping the accent's identity without failing WCAG. Body text on navy went through the same discipline, rejecting semi-transparent white for a solid tint that holds contrast.

The system shipped as a component reference document and a full-page mockup, then drove the production build. The iterations after implementation were the unglamorous kind that make a system real: fixing a hero card clipping into the stats bar, guarding count-up animations against double firing, de-emphasising a tag that read as a CTA, and repairing a comparison table's contrast so "them versus us" was legible at a glance.

Proof-of-concept pages are built for the championing executive: officer profile, product landing page, and recruiting page, all on the locked design system with inline booking embedded. The second officer deployment is queued, chosen for his strong social presence, and the template's CMS fields make each additional page a content task rather than a design project. Lead and booking metrics will be added as the rollout proceeds.