feat: UX conversion fixes — hero rewrite, before/after, trust layer, progressive disclosure

[simonCatBot]

Context

ChatGPT startup-investor audit identified positioning + funnel clarity as the #1 conversion weakness. Detailed analysis in CHATGPT_AUDIT_ANALYSIS.md.

Core finding: "Good product hidden behind weak conversion" — the features are strong but the homepage doesn't lead with the wedge or create urgency.

P0 — High Leverage (Do Now)

1. Rewrite hero copy — lead with wedge + differentiator

Current: "Finally, a Rental Experience Everyone Loves"
Problem: Vague, doesn't say what Manay does or why it's different
Fix: Lead with the pain + WhatsApp differentiator

• Title ideas: "Stop Chasing Rent on WhatsApp. Automate It." / "Your Rent, Collected. Your Agreements, Registered. All on WhatsApp."
• Subtitle: sharpen to action + outcome
• Keep Landlord/Tenant toggle (ChatGPT missed this — it's good)
• Make WhatsApp the hero differentiator, not a footnote

2. Add Before/After section ("The Old Way vs Manay")

Current: No pain amplification — we describe features, not the problem
Fix: Add contrast section near WhatsApp flow:

Before Manay	With Manay
Chasing rent on WhatsApp groups	Auto-collected via UPI mandate
Paper agreements, no legal standing	Kaveri 2.0 registered, Unique Tenancy ID
"You damaged this" deposit fights	Property care visits document everything
No credit history from 10 years of rent	Karma Score builds your rental credit
Cash payments, no proof for HRA	Instant receipts, HRA-ready

3. Add founder/why story section

Current: No human face behind the product
Fix: Short "Why We Built This" section:

• "Built by Bengaluru renters who got tired of chasing deposits and arguing over damages"
• Humanizes the product, creates trust before asking for data
• Can be 2-3 sentences + name/photo placeholder

4. Restructure homepage flow — progressive disclosure

Current order: Hero → Features (all flat) → Legal → WhatsApp → Trust → Karma
Proposed order: Hero → Before/After → WhatsApp flow → Features (wedge first) → Legal → Trust → Karma → CTA

• Lead with Zero-Chase Payments (the wedge)
• Then show what else (agreements, verification, karma)
• Legal compliance and trust as reinforcement, not the opening

P1 — Medium Leverage (Do Soon)

5. Add "Free to start" to hero area

• ChatGPT said no pricing visibility → we have a pricing page, but the hero doesn't mention it
• Add "Free for landlords" near the CTA button
• Reduces perceived commitment

6. Dynamic waitlist counter

• "Join X Bengaluru landlords/tenants on the waitlist"
• Even a placeholder ("Join the waitlist" → becomes dynamic when we have numbers)
• Social proof without faking numbers

7. Strengthen CTA microcopy

• "Join Waitlist" → add a line: "We'll ping you on WhatsApp when we launch"
• Makes the next step explicit

8. Partner/integration trust row

• "Powered by UPI • Kaveri 2.0 Ready • RBI-Regulated Payments"
• Logo-style row of tech integrations
• More credible than self-claiming "secure"

P2 — Nice to Have

9. Product screenshots/mockup

• Show the actual app dashboard, not just chat bubbles
• Even a stylized mockup increases perceived completeness

10. FAQ: "Why switch from WhatsApp/Excel?"

• Directly address status quo bias
• "But I already collect rent on WhatsApp" → "Yes, but do you get auto-receipts, credit building, and legal compliance?"

11. WhatsApp Flow: add pain setup

• First chat bubble should acknowledge the pain before showing the solution
• "My tenant is 2 weeks late again..." → then show Manay's resolution

What NOT to Change

• Hero toggle (Landlord/Tenant split) — ChatGPT missed it, it works
• WhatsApp chat flow demo — best conversion tool we have
• Karnataka 2026 legal section — major differentiator
• Good Karma teaser — unique IP
• Trust badges — foundation is there
• Pricing page — already clear
• Guide pages — deep content, SEO value
• Rental Law 2026 page — authority builder

Not for Pre-Launch

• Progressive onboarding (product-side, not website)
• Customer testimonials (no customers yet)
• Usage metrics (would be dishonest)
• Ad landing page variants (premature)

---

Full analysis: See CHATGPT_AUDIT_ANALYSIS.md in repo root.