Scaling India's Payments: How PhonePe Built for 500-Million+ Users

Key Concepts

Co-founder Trust: The paramount importance of a co-founder with whom one shares a high level of trust, even "blind trust," for navigating difficult times.
Compounding Effect: The idea that good things in life, including relationships, startups, and friendships, benefit from compounding over time.
Complementary Skills & Interchangeability: The value of co-founders having complementary skills, which, over time, can lead to interchangeability and mutual support.
Data-Driven Decision Making: The convergence on using data as a strong pillar for decision-making, with a framework for resolving disagreements when data is insufficient.
Missionaries vs. Mercenaries: The distinction between employees driven by a mission and those motivated by other factors, and the importance of identifying and rewarding missionaries.
Building for Future Scale: The principle of designing systems and infrastructure to handle future growth and transaction volumes from the outset.
Learning from Chaos: The idea that startups can learn valuable lessons from chaotic situations, which might be reduced in more structured, VC-funded environments.
Tech Debt Hell: The state of being constantly behind on technological development due to prioritizing immediate business needs over long-term system health.
Simplicity Breeds Scalability: The belief that simple solutions are often more scalable and effective than overly complicated ones.
Tailwinds: External factors or trends that can significantly accelerate a company's growth, and the importance of being prepared to leverage them.
Engineering Tailwinds: Proactively working to create or influence favorable conditions for a company's growth.
Substance Over Surface: The overarching theme of prioritizing genuine impact and foundational strength over superficial appearances or quick wins.

Summary

The Importance of Co-founder Relationships and Trust

Rahul emphasizes that a great co-founder is crucial, not just for complementary skills but most importantly for a high level of trust. He shares a personal anecdote with his co-founder, Samir, dating back 30 years, highlighting their early playful rivalry that foreshadowed their entrepreneurial journey. This deep trust, he explains, is essential for navigating the "dark woods" of startup life. Over time, their complementary skills have evolved into a degree of interchangeability, allowing them to support each other through difficult periods. Open conversations about aspirations and energy levels are also vital for co-founders.

Early Entrepreneurial Experiences and Pivotal Decisions

Rahul recounts his first startup in the media distribution space (around 2009-2010), which was a challenging two-and-a-half-year journey. Despite rejections from VCs, they received an acquisition offer from Flipkart and an investment offer from Sony. Rahul's decision to sell to Flipkart, rather than take Sony's funding, was driven by his personal energy and vision for how the venture could thrive under Flipkart's umbrella. This decision underscores the importance of aligning personal aspirations with strategic choices, supported by a trusted co-founder.

The Evolution of Team Building Across Ventures

Rahul outlines three distinct stages of team building across his ventures: the pre-Flipkart startup, Flipkart itself, and PhonePe.

Pre-Flipkart Startup: This early venture involved a "beg, borrow, and steal" approach, leveraging college interns and individuals with strong hunger and a desire to build. Rahul recounts convincing parents to let their sons join the startup over more established companies.
Flipkart: Hiring at Flipkart was the toughest due to the phase when startups weren't as "sexy." The rapid growth demanded quick hiring at scale. A key strategy was identifying "missionaries" and rewarding them with significant accountability ahead of their experience. Flipkart's approach was to throw individuals into the deep end with the conviction they could succeed.
PhonePe: This was the easiest hiring experience, benefiting from the network built at Flipkart and the return of key talent ("Gurvabsi program"). The initial hiring philosophy for the first 100+ people was based on a "single degree of separation" – individuals directly known or known through someone directly known. A unique approach involved candidates bringing in two people they vouched for, taking responsibility for their success.

Learning from Chaos and Architecting PhonePe

Rahul views Flipkart as a "university for startups," providing compressed learning opportunities, especially from chaotic situations. He contrasts this with the current startup environment, where VCs can lead to more prescribed models, reducing opportunities for learning from chaos.

Key Learnings from Flipkart's Big Billion Day (2014):

Payment System Strain: The 2014 Big Billion Day exposed critical weaknesses in payment gateways and the checkout system. Banks underestimated the scale, comparing it to tatkal bookings, which proved to be a gross miscalculation.
Chaos and Recovery: The sale opening at 8 AM led to payment gateways crashing by 8:15 AM. Transactions succeeded then failed, and vice-versa. The company had to manage orders through COD or later payment processing, leading to significant chaos.
Architectural Analysis: This event prompted analysis of system architecture and preparation for similar events.
Avoiding Tech Debt Hell: A core principle at PhonePe, established with Chief Architect Shantan, is to never fall behind the business curve technologically. They built the payment stack from day one to handle 10 million transactions daily, a nine-month undertaking, which was unconventional for a startup but ensured future scalability. This "build for future scale" principle was applied to many PhonePe stacks.

Organizational and Technological Principles at PhonePe:

Future Provisioning: Building systems with future scale and provisioning in mind to avoid "tech debt hell."
Simplicity: A core value is that "simplicity breeds scalability."
Data Transparency: Sharing board decks, P&L, burn rates, and employee costs openly to foster understanding and engagement. Data access is unrestricted across categories.
Flat Hierarchy: Minimizing titles (Software Engineer, Architect, Engineering Manager, Head of Engineering) to reduce hierarchical pressure and focus on delivery and impact.
Detail Orientation: A preference for getting into the details of work rather than relying solely on a chain of command, fostering accountability.
Human Connection: Maintaining a human connection within the organization to preserve the essence of why the company was founded.

The Origin Story of PhonePe

PhonePe was Flipkart's fourth attempt at building a payments platform, following NG Pay, Space Zippy, and FKPG. Rahul clarifies that PhonePe was not incubated within Flipkart but was a separate venture started by him and Samir after quitting Flipkart. Their realization stemmed from the Big Billion Day experience, highlighting that without a solved payment infrastructure, digital commerce would be capped. They began building a solution on top of IMPS, similar to what UPI later offered, and learned about UPI through conversations with Nandan Nilakani and Sharat Sharma of iSpirt.

Key Motivations for PhonePe's Founding:

Payments Infrastructure: The need to solve digital payments at an infrastructure level to enable broader digital commerce.
Cash on Delivery (COD) Nightmare: The operational challenges, costs, and risks associated with COD, including armored trucks for cash collection, thefts, and counterfeit notes.
Microtransaction Challenges: The difficulty of processing small payments (e.g., 3-8 rupees for music tracks) via traditional methods, especially for impulse purchases, and the lack of microtransaction capabilities.
Avoiding Fundraising Cycles: A desire to build without the constant pressure of raising money for valuation, as experienced at Flipkart. Bini's commitment of significant funding allowed them three years of building freedom.

Identifying and Leveraging Tailwinds

Rahul believes that tailwinds are unpredictable in their timing but emphasizes the importance of having "serious bets" with significant impact creation and the conviction to pursue them. Solving a problem with significant impact naturally attracts tailwinds, which can manifest as policy changes, investment trends, or market shifts. He advises against building just features and instead focusing on solving impactful problems. He suggests that over a five-year timeframe, at least one tailwind is likely to emerge.

Engineering Tailwinds:

Betting Big on UPI: PhonePe's early and strong commitment to UPI, even when others were skeptical, was a strategic bet. They saw it as a "love at first sight" opportunity.
Ecosystem Collaboration: Actively sharing data and insights with NPCI and banks to improve UPI, even if it meant sharing proprietary information. This collaborative approach positioned them as partners in the ecosystem.
Leveraging Demonetization: During demonetization, PhonePe's existing infrastructure and experience allowed them to contribute to the development of the BHIM app, which drove awareness and education for digital payments, ultimately benefiting PhonePe.

Pivotal Decisions and Regrets

Brilliant Decision: Choosing computer engineering at Bombay University over civil engineering at IIT Bombay in 1990, a decision with a significant "butterfly effect" on his career trajectory. Joining a startup called "Systems" in 2001 after his Master's, despite offers from Intel, IBM, and Sun Microsystems, was another risk that paid off.
Sleepless Nights: The exponential growth of PhonePe and the increasing number of dependencies create a constant "paranoia" and "imposter syndrome," leading to sleepless nights, though this also drives continuous learning.

Navigating Fintech Compliance in India

Rahul advises that regulators typically engage when innovations become impactful. He suggests avoiding exploiting "gray spaces" in rules, as these will eventually be addressed. Instead, he recommends engaging with regulators early, especially through platforms like the RBI Innovation Hub, to discuss challenges and potential solutions. Transparency and understanding the regulator's concerns are key to paving a path forward.

The Power of Simplicity and Lean Models

Rahul acknowledges that his decision to take nine months to build PhonePe's payment stack was a luxury. He suggests that for B2B and SaaS models, building for scale is feasible. In consumer internet, where scale is critical, companies can test the market with lean models but must recognize when to invest deeply for a step-change in capability. He strongly believes that "simplicity breeds scalability" and advocates for asking users directly rather than over-relying on complex data analysis for simple problems.

Addressing Non-Smartphone Users and Feature Phone Solutions

For farmers and non-smartphone users, Rahul sees the primary opportunity in developing feature phone solutions for UPI. PhonePe has acquired IP in this area, though he acknowledges the limitations of feature phones.

The Most Misunderstood Aspect of Fintech in India

The most misunderstood aspect of building fintech in India is the notion that lending is the primary path to profitability. Rahul states that lending is globally the "graveyard of fintech startups."

Reading Recommendations

Entrepreneurship: "The Hard Thing About Hard Things" by Ben Horowitz, appreciated for its simple language and anecdotal evidence.
Science Fiction: "The Three-Body Problem" trilogy by Liu Cixin and works by Andy Weir (author of "The Martian").

Competitive Moat in the GenAI Space

Rahul believes that true competitive moats in technology, including GenAI, come from scale and performance. While functionality is becoming commoditized, the ability to deliver at a significant scale with high performance is the key differentiator. He notes that incremental improvements in areas like payments can yield greater value than new features.

Building Trust and Referenceability in Co-founder Dynamics

Rahul emphasizes that it's best to work with someone you've known personally or professionally before becoming co-founders. Discovering trust during the entrepreneurial journey is very difficult. The ideal co-founder dynamic involves complementary skills and the comfort to "hold the mirror" to each other. He suggests a hiring-like process to assess these dynamics before committing.

Conclusion

Rahul's journey highlights the critical role of deep trust and complementary skills in co-founder relationships, the importance of learning from chaos and building for future scale, and the strategic advantage of identifying and engineering tailwinds. His emphasis on simplicity, transparency, and a detail-oriented approach, coupled with a long-term vision, has been instrumental in building PhonePe into a dominant force in digital payments. The conversation underscores that true success lies in building substance over surface, with a focus on solving impactful problems and fostering a culture of continuous learning and accountability.