Prudhvi Nath

I build revenue systems on Salesforce — the machinery between "the customer said yes" and "the invoice went out". Mostly that means Revenue Cloud, CPQ, and the integrations that connect them to everything else a business runs on.

I came to it sideways. My first Salesforce job was configuring Sales Cloud for a real-estate business in Hyderabad; six years later I'm an Application Architect working on quote-to-cash migrations for SaaS companies in the US. In between: automotive rollouts at TCS, and two years of healthcare integration work at UnitedHealthcare where the interesting problems were rarely about Salesforce at all — they were about what you're allowed to copy, and what you have to fetch.

How I work

The expensive mistakes in revenue systems are almost never code. They're data model decisions made early, quietly, by someone who didn't realise they were deciding anything. A bundle structure that can't express a mid-term amendment. A pricing procedure that works until the first multi-currency deal. Most of my job is finding those decisions before they harden, and writing down why we chose what we chose.

I'm also a fan of boring infrastructure. Migrations behind flags, releases you can roll back, and environments you can rebuild from scratch.

The channel

I started Learn Salesforce with Prudhvi because the material I wanted when I was learning didn't exist: not "click here, then here", but why the platform is shaped the way it is, and what an architect actually weighs when choosing between two options that both work.

Each video gets a companion page here with the sources, the demo steps and the gotchas — so you can read it instead of scrubbing back through a recording.