Lessons from scaling Ramp | Sri Batchu (Ramp, Instacart, Opendoor)

Batchu describes growth teams organized around channels alongside a product-engineering team that helps them work more effectively. The account makes growth a cross-functional effort rather than only a marketing task. It is his description of Ramp at the time, not a current organization chart.

He describes a small team exploring ideas that did not fit neatly into an existing channel. Early work could remain small, with more investment considered if it worked. A team boundary should not automatically disqualify a useful experiment.

Batchu says the team reinforced attention to days rather than only quarters or years. The practical issue is reducing avoidable delay between deciding and doing. This account describes their operating style without claiming that speed alone produces good results.

He says a cross-functional growth team worked in two-week sprints and prioritized work together. That gives different functions a common rhythm and a place to compare work. It is a coordination practice, not a mandate that every team should use the same sprint length.

Batchu highlights responses that made the next owner and deadline clear, even when the task was not completed immediately. A useful response can therefore move the work forward without pretending it is done. This separates responsiveness from instant completion.

He describes calendar audits and blocks for focused work alongside response time. The question is whether the time being spent matches what the person or team says matters. The account does not require constant availability or uninterrupted messaging.

Batchu says failure is not learning, rather than simply missing an outcome. A team should capture what a test taught it so an unsupported idea is not repeatedly restarted. This is a conceptual learning principle, not a statistical testing guide or a claim that any single test proves a hypothesis false.