What this prompt does
This prompt designs the complete loan application and approval journey for your lending product. You provide [product_name], [loan_type], [target_borrowers], [time_target], [regulations], and [framework], and it designs every stage: pre-qualification, a multi-step application wizard, a document upload center, application review and submission, an applicant status dashboard, an underwriter approval interface, and [framework] implementation notes.
The structure works because lending flows are where applicants either drop off or push through, and each stage has a specific anxiety to defuse. The prompt designs a soft-pull pre-qualification with clear consent language, an auto-saving wizard so progress is never lost, and document upload with quality checks and auto-detection. It ties consent and disclosure language to your [regulations] and targets your [time_target] for completion, with the explicit goal that the flow feels like a conversation, not a government form.
When to use it
- You're building a lending product and need the full application-to-disbursement journey designed.
- Applicants are dropping off and you need a pre-qualification soft pull and auto-saving wizard to keep them.
- You need a document upload center with quality checks and auto-detection of IDs and pay stubs.
- Your
[regulations](TILA, ECOA, fair lending) require specific disclosures built into the flow. - You need both an applicant status dashboard and an underwriter approval interface designed.
- You want
[framework]guidance for multi-step form state, chunked uploads, and WCAG 2.2 AA accessibility.
Example output
You get a stage-by-stage journey design: a pre-qualification screener with soft-pull consent and an instant eligibility result (or a clear reason and alternatives if declined); a multi-step wizard with auto-save, smart pre-fill, conditional fields, and resume-by-magic-link; a document upload center with drag-and-drop, camera capture, auto-detection, and blur/quality checks; a readable review-and-submit step with e-signature; an applicant status pipeline (Applied → Under Review → Verified → Decision → Funded); an underwriter queue with side-by-side data and documents and decision buttons; and [framework] implementation notes.
Pro tips
- Set
[loan_type]precisely; a personal loan, mortgage, and business line of credit need different fields and disclosures. - Use
[target_borrowers]to tune tone and complexity to who's actually applying. - Make
[time_target]realistic — it drives how aggressively the wizard pre-fills and trims fields. - Name your real
[regulations]so consent language and disclosures are built into the right stages, not bolted on. - Keep the auto-save and resume-by-link features; abandoned applications are the biggest leak in lending funnels.
- Match
[framework]to your stack and prioritize the mobile-first, WCAG 2.2 AA notes since most applicants are on phones.
