Mobile Banking Education & Lead-Gen App

Financial Literacy & Lead-Generation App — Project Description

Overview
We are building a mobile-friendly application for a bank that helps everyday users understand insurance products and other financial instruments (savings, investment, and protection products) in a simple, friendly, and multilingual way. The app is educational and lead-focused: users learn about products, get their questions answered by an AI assistant, and can submit an enquiry that is routed to the bank's sales/agent team for follow-up. This is a non-transactional platform — no purchases, payments, or account opening in this phase.

Goal
Improve financial literacy, present the bank's products in an accessible format, and generate qualified leads — while giving the bank full control to manage content and products themselves, without needing a developer for every change.

Key Features

Educational content organised by topic/category (insurance, savings, investments), with rich formatting, search, and FAQs.
Product catalogue with detail pages (description, key features, eligibility, benefits) and a simple side-by-side comparison view.
Multilingual experience — user-selectable language; start with 1–2 languages, expandable later. All content and UI text must be translatable.
AI chatbot / virtual assistant that any user (including guests) can use to ask questions in natural language and be guided to the right content or product. The chatbot must be grounded in the bank's approved content only — no fabricated answers and no personalised financial advice — with a clear "general information only" disclaimer, and the ability to hand off to the enquiry form or a human agent when appropriate.
Lead capture — an enquiry form linked to a product or topic, capturing name, contact details, product of interest, and preferred contact method, with input validation, consent capture, and confirmation. Leads are routed to the bank's team (notification + admin queue) and are viewable/exportable by admins.
Admin CMS — a content-management back-office where administrators create, edit, publish, and translate content and products, manage categories and ordering, control the chatbot's knowledge sources, view/export leads, and manage admin roles (role-based access control).
Basic analytics — content/product views, lead submissions, funnel drop-off, shown on a simple admin dashboard.
Optional push notifications for new content or products, with user opt-in/opt-out.

Platform & Technical Preferences

A responsive mobile web app (PWA) is preferred — installable, app-like, and works across iOS and Android from a single codebase. Native apps are acceptable only if specifically justified.
Clean, simple, accessible UI for non-technical users; readable typography and clear navigation.
Content changes must not require code deployment (CMS-driven).
Product data may be maintained in the CMS or ingested via a simple feed/API. No core-banking integration is required in this phase.

Non-Functional Requirements

Security: HTTPS/TLS everywhere; personal (lead) data stored securely with access controls.
Privacy & compliance: consent, data retention, and data-protection compliance; the AI assistant must not send sensitive personal data to external AI services without consent and safeguards. A self-hosted or region-compliant AI approach is preferred given the banking context and data-residency needs.
Performance: content and product pages load within ~3 seconds on a standard mobile connection.
Availability & scalability: monitoring, automated backups, and an architecture that grows with users and content without redesign.
Hosting flexibility: deployable to the bank's own infrastructure / private cloud or a standard cloud provider, per data-residency preference.
AI safety: guardrails to keep chatbot responses grounded, safe, and compliant; the assistant should indicate uncertainty or hand off rather than guess.

Out of Scope (this phase)

Transactions: product purchase, premium payment, account opening.
Identity verification / e-KYC and regulated onboarding.
Payment gateways, wallets, or settlement.
Core-banking or insurer policy-system integration.
Gamification, rewards/referral programmes, advanced personalisation.
These may be scoped as a later phase and will change security, compliance, and integration requirements.

Post-Delivery Support & Maintenance (2-Year AMC)
We require a two-year (24-month) maintenance arrangement following go-live, covering: corrective maintenance (bug fixes), security patching, adaptive updates (OS/browser/library changes and store re-submissions if native), uptime monitoring and incident response, regular backups/DR checks, a small allowance for minor enhancements and configuration, CMS/content support, and chatbot upkeep (knowledge-base refresh and guardrail tuning). Support should follow priority-based response targets (critical / high / medium) to be agreed in a support SLA. New features, major enhancements, and any Phase-2 transactional work are handled separately.

Deliverables

Fully working application (PWA, iOS + Android reachable) with the features above.
Admin CMS with role-based access.
AI chatbot integrated and grounded in approved content.
Source code, documentation, and deployment/handover support.
Ongoing maintenance under the 2-year AMC.

Ideal Skills
Full-stack development (React or similar + a backend framework), PWA experience, CMS/back-office development, multilingual/i18n implementation, AI chatbot / LLM integration with retrieval and guardrails, cloud or on-prem deployment, and a security-conscious approach suitable for a banking client.