Flask Web App Enhancement & Deployment

Project Title Flask Web App — Deployment, AI Resume Parsing, UI Redesign, and Configurable Payment System (3 Milestones) Skills (tag these) Python, Flask, HTML5, CSS3, JavaScript, UI/UX Design, Jinja2, SQLite, Web Deployment, Responsive Design, Razorpay, Payment Gateway Integration Project Type Fixed Price, split into 3 milestones Description (paste as one block) I have a working Flask web application (a candidate/HR matching platform) that needs to go from working prototype to a production-ready product, delivered in three milestones. Milestone 1 — Deployment + AI Resume Parsing Deploy to production (Render or similar — deployment config already exists) Domain, SSL, environment variables, production database setup AI-based resume parsing: extract name, contact, skills, experience, and education from uploaded resumes (PDF/DOCX) Must use a free-tier AI API (Google Gemini API free tier or Groq) — not a paid-per-call model like OpenAI GPT-4 or Claude Include a non-AI rule-based fallback for when free-tier limits are hit Milestone 2 — UI/UX Redesign Full visual redesign of all existing screens — modern, clean, professional, fully mobile-responsive One consistent design system across candidate, employer, and admin views Existing screens are functional but plain Jinja2 templates — needs a genuine design pass Milestone 3 — Configurable Payment System (built after Milestones 1-2 are tested; scope confirmed now so it's architected correctly from the start) Payment integration (Razorpay primary; PayPal as a secondary option for international customers) A master on/off toggle in the admin panel: when disabled, all payment buttons/prompts disappear from every user-facing screen and the product behaves as fully free; when enabled, paid flows appear When enabled, admin needs a pricing management screen to: Set and update prices for each paid feature/action Create time-limited offers and discount codes Create combos/bundles (e.g., multiple resume unlocks or subscription tiers sold together at a bundled price) Create and edit packages (e.g., Basic/Pro/Enterprise-style plans with different limits) This means the data model for pricing, offers, and packages should be designed in Milestone 1 or 2 even though the payment UI itself is built in Milestone 3 — please account for this in your technical approach. This is confidential, pre-launch work. Full requirements, the existing codebase, and design references will be shared only after signing an NDA.