On this page
Project NamastePay
Building a payments company's go-to-market engine on Salesforce
For learning only. NamastePay is fictional and all data is synthetic. Razorpay, Stripe and Wise are mentioned only as public industry examples. Not affiliated with them or with Salesforce.
What we're building
- A fictional Indian payments company that onboards businesses by invite only
- The full system its teams use, from invite request to first live payment and ongoing revenue
- Built with point-and-click tools in a free Salesforce Developer Edition org
Why invite-only?
- Payment companies must verify businesses (KYC) before they can accept live payments
- Razorpay: quick signup, live payments only after verification
- Stripe: build in test mode, activate with business details
- Wise: verify customers before money moves
- Activation = first live payment, not signup
How the company uses Salesforce
- Sales: prioritized leads, deal stages, AI deal summaries
- Compliance: risk review queue, approve or reject with an audit trail
- Onboarding: track invited businesses, messages and at-risk merchants
- Leadership: one dashboard with KPIs, trends, predictions and a weekly AI report
The journey
- Request: phone OTP and invite form
- AI enrichment: Claude classifies the business and flags risk
- Scoring and routing: sales, compliance, auto-approve or waitlist
- Review: sales deals and compliance decisions
- Invite and nurture: email, WhatsApp and reminders
- Activation: first live payment creates the merchant
- Growth: daily revenue, churn risk, next product to pitch
Tools
- Salesforce (Flows, approvals, permission sets, reports, CRM Analytics)
- n8n, Claude API
- Twilio Verify, SendGrid, WhatsApp
- Python, Faker, GitHub
Success metrics
- Request to invite: under 1 hour
- Compliance review: under 48 hours
- Invite to activation: 40%+
- Days to activate: 7 or fewer
Learn it yourself
- Free course: Build a Payments Company on Salesforce
- No coding needed, free Developer org
- Each lesson covers one Salesforce skill, the business "why," click paths and a quick check