I need two standalone websites that work together as one fluid experience: a feature-rich mortgage platform and a lighter real-estate site that feeds qualified traffic back to it. The mortgage site is my main lead-generation engine, so every feature should nudge visitors toward starting an application while giving them the tools and confidence to move forward. Mortgage website requirements • Calculators: payment and refinance calculators available above the fold, mobile friendly, and embeddable on the real-estate site. • Secure application flow: initial loan application and pre-approval forms, both encrypted end-to-end. After submission, applicants land in a user portal where they can track status, upload documents, and message my team. • Lead management: direct, real-time hand-off into the CRM you recommend—Zapier, HubSpot, Salesforce, or a custom API—plus an internal admin dashboard for at-a-glance pipeline tracking. • Compliance & security: SSL, secure headers, role-based access, audit logs, and data retention controls that align with mortgage-industry best practices. • SEO-driven, fully responsive design so the calculators, forms, and content load fast on any device. Real-estate website This site is simpler—essentially a property showcase and education hub—but it must share a single sign-on with the mortgage site, surface the same calculators, and pass browsing or inquiry data back to the CRM. A clear “Get Pre-Approved” call to action should route users into the mortgage application flow in one click. Integration expectations • One backend (or tightly synced databases) so user credentials, leads, and analytics flow freely between the two sites. • API layer documented well enough for future mobile-app or third-party integrations. • Staging and production environments plus a hand-off session where you walk me through deployment and updates. Deliverables 1. Fully deployed mortgage website with the features above. 2. Companion real-estate website sharing authentication and key widgets. 3. Source code, build scripts, and technical documentation. 4. Short video or live walkthrough showing the admin side, user journey, and data hand-offs. If you have a preferred stack, let me know; just ensure it scales, is secure, and keeps page speeds high. I’m ready to move quickly once we agree on scope and timeline.