Five Products Should Not Mean Five Forms
Every multi-product lender drifts into the same sprawl: a personal-loan page, an auto-loan page, a home-improvement page, each with its own form, its own inbox, its own slightly different question set — and no way to answer ‘how did applications trend last quarter?’ without reconciling four spreadsheets. The borrower doesn’t care that the institution is organized by product. The borrower cares about one link that takes them seriously.
The router form is that link. One URL serves the whole lending portfolio; a product selector up front sends each applicant down their own branch; and every application — regardless of product — lands in the same pipeline, tagged and comparable.
The Router
One multiple choice at the top: personal loan, vehicle finance, education, home improvement, debt consolidation, other. The choice drives the flow — each branch carries its product’s specific questions while everything universal happens exactly once.
The Shared Spine
Under every branch sits an identical core: identity and contact details, and the universal capacity inputs. This sameness is the architecture’s whole point — the spine being byte-identical across products is what makes cross-product reporting true rather than approximate. Product-specific questions live only in branches, so a personal-loan applicant never sees a vehicle question and vice versa.
One Pipeline, Actually Usable
The response view becomes the whole portfolio’s intake — filterable by product branch, with hidden fields tagging each application’s campaign or broker source. Webhooks route each submission to the team that owns its product, and a self notification can flag the branches that need same-day touch.
Keeping the Router Honest
Three housekeeping rules keep the architecture clean over years: the product list shows only live products — pause a product with close or remove its branch rather than letting applicants apply into a void; rename the form by version when the branches change materially; and duplicate into a standalone form only when a product’s underwriting grows deep enough to deserve its own page — the router for intake, the standalone for depth, both feeding the same pipeline.
Frequently Asked Questions
Router form or dedicated product pages — which?
Start with the router; it consolidates intake and reporting from day one. Add a standalone page only when one product’s questions multiply past what a branch can carry — and link the two rather than replacing either.
What makes a branch different from a separate form?
The shared spine. Branches inherit identical universal questions and one pipeline; separate forms drift — different wordings, different fields, unreconcilable reporting.
Can brokers or intermediaries submit on behalf of applicants?
Yes — a hidden field in each broker’s tagged link attributes their submissions automatically, so the intermediary channel reads cleanly in the same pipeline.
What happens when a product is discontinued?
Remove its branch and note the change in the form’s version name. Historical submissions keep their tags, so past product performance stays reportable after the product is gone.