The program
GoPMM was built by practitioners from Razorpay, Swiggy, and Freshworks who were tired of watching people get PMM wrong. Six live sessions across 9 weeks, each one covering a different part of the role, followed by a 3-week capstone on a real company brief.
Problem statement
RazorpayX: one banking suite, three different buyer problems.
RazorpayX is Razorpay's business banking suite. Current Accounts + Payouts, Payroll, and Corporate Cards. It runs inside a payments platform that millions of Indian merchants already use. The core question was whether that PG footprint is an asset to build on, or a ceiling to break through.
Path 01
Fully Embedded
Sell banking only to existing Razorpay merchants. Use the PG as the sole acquisition channel for all three modules.
Ruled out
Path 02
Fully Standalone
Build RazorpayX as an independent neobank. Compete directly with Jupiter, Fi, and traditional banks for SMEs outside the PG base.
Ruled out
Path 03
Hybrid Two-Motion GTM
CA+Payouts and Cards grow through the PG, that's where 50–80% of those users already come from. Payroll gets its own motion, because its buyer (HR, compliance teams) has no reason to come through a payment gateway.
Our recommendation
What we did
01
30+ user interviews: mapped acquisition by module
We spoke to current users, churned users, internal employees, and people who had evaluated RazorpayX and chosen something else. The pattern was clear: CA+Payouts acquires 50–60% of users through the payment gateway. Corporate Cards: 70–80%. Payroll gets none of that. Its buyer is an HR manager or compliance head who has no touch point with Razorpay's PG.
02
Competitive scan, 4 competitors across 3 modules
We scored RazorpayX against Cashfree, PayU, Paytm, and Jupiter, feature by feature, per module. CA+Payouts came out ahead on most dimensions. Payroll had a strong product but weak distribution. HRMS players like Darwinbox and Keka own that buyer relationship. Corporate Cards had feature parity with competitors but no clear reason to choose it. That last finding pointed to a positioning problem, not a product one.
03
Market sizing: TAM / SAM / SOM across 3 modules
We built TAM/SAM/SOM models for each module using bottom-up estimates, not analyst report quotes. CA+Payouts SAM: $20B. Corporate Cards SAM: $42B. Payroll SAM: $2.29B, and the majority of it sits outside the PG base entirely. That $2.29B figure is what made the standalone motion case. You can't reach most of that market through Razorpay payments.
04
Built the hybrid two-motion GTM
Embedded motion: in-product upsells, PG-linked nudges, freemium entry, and partner channels via CAs and ERPs. Low acquisition cost because the trust already exists from the payments relationship. Standalone motion: inside sales, ABM, HRMS partnerships, and dedicated support SLAs for SME compliance buyers and enterprise finance teams. Separate buyer, separate message, separate funnel.
05
Wrote distinct positioning for each module
CA+Payouts: "Unified current account, bulk payouts, and reconciliation, in one programmable system."
Payroll: "Payroll that pays the government for you. No uploads, no compliance anxiety."
Corporate Cards: "No personal cards. No reimbursements. Finance teams get full control."
What it built
Frameworks only land when you use them against something real.
ICP Thinking
The ICP work had to happen at module level, not company level. CA+Payouts is bought by founders and CTOs with a payout volume problem. Payroll is bought by HR leads under compliance pressure. Corporate Cards is bought by CFOs who are done chasing reimbursement spreadsheets. Same product family. Completely different trigger, decision-maker, and alternative for each one.
GTM Design
"Embedded or standalone" was the wrong question. The interview data showed that two modules already acquired most users through the PG, so forcing a standalone motion there would create unnecessary CAC. Payroll had the opposite problem: its buyer never came through payments. The GTM had to follow the buying pattern, not the other way around.
Positioning
Corporate Cards had feature parity with every competitor on the scorecard. The problem was that it was being positioned as a spend tool when the actual buyer, the CFO, cares about control and visibility, not convenience. We rewrote the positioning around finance oversight, not employee experience. Same product, different message, different buyer.
Note on this project
This was a structured PMM exercise, not a live campaign. There are no revenue or pipeline results to report. What it produced was a complete GTM architecture — ICP maps, competitive scoring, positioning lines, and a two-motion strategy — built under the same constraints you'd face on the job.
The frameworks from class are easy to learn.
Applying them to a real product
is where the gaps show up.
The capstone wasn't a memory test for the frameworks we covered. It was a test of whether we could use them when the answer wasn't clean, multiple buyer types, acquisition data that contradicted each other, and a competitive landscape where the obvious move didn't hold up under scrutiny.
Nine weeks. Six frameworks. One real brief. That's what builds PMM judgment, not just PMM vocabulary.