Calvin Cupino's first sales job involved calling relatives and strangers to ask whether he could demonstrate kitchen knives in their homes. It was uncomfortable, repetitive, and full of rejection. It was also useful preparation for becoming a revenue operations leader.
His path moved from Cutco to finance, frontline technology sales, and eventually founding RevOps roles. That sequence gave him something operations teams cannot acquire from a process diagram: firsthand knowledge of what it feels like to execute the work their systems are supposed to support.
Discomfort is part of learning how selling works
Calvin does not romanticize the knife-selling job, but he does not regret it either.
You kind of need to be pushed into something that you are very uncomfortable with.
At 18, that meant making cold calls and walking into a stranger's home to run a demonstration. The immediate lesson was resilience. The deeper lesson was that confidence follows repetitions; it rarely arrives before them.
That principle carried into later sales roles. A seller learns through live conversations how quickly a message can fail, how rejection affects behavior, and why a process that looks simple from headquarters can feel very different in execution.
RevOps leaders with that experience are better positioned to separate avoidable process friction from the unavoidable discomfort of selling.
Frontline experience changes how you design systems
A workflow can be correct and still be unusable. A required field can improve reporting and still arrive at the worst moment in a sales process. A routing rule can be logically consistent and still send a seller toward an account with no realistic path to value.
Frontline experience gives an operator an instinct for those tradeoffs. It does not mean the field should determine every design decision. It means the person building the system understands what each requirement asks someone else to do.
Calvin's move from sales into operations made that perspective especially useful. He could evaluate process decisions through two lenses: whether the business needed the information and whether the seller could reasonably provide it.
Revenue operations requires both tactical and strategic work
When Calvin became the first RevOps hire at Pylon, he inherited a blank slate. There were no legacy Salesforce flows to debug and no established operating model to preserve.
That freedom came with a harder problem:
The hardest part is trying to find the balance between doing strategy work while also doing the tactical builds, because nothing existed.
Founding operators live in both time horizons. They have to define how the company should operate while also creating the fields, automations, reports, and handoffs needed for tomorrow morning.
The danger is spending every week inside tactical requests and never building the operating model. The opposite danger is designing an elegant future while the current team works around missing fundamentals.
A strong founding RevOps leader creates enough structure to make the next decision easier without pretending the business has already reached its final form.
A clean slate is only valuable when the principles are clear
Starting without legacy automation sounds ideal, but blank systems can become messy quickly. The advantage is not simply the absence of old errors. It is the opportunity to establish consistent design principles early.
Those principles might include:
- Define ownership before automating a handoff.
- Capture only data that informs a real decision.
- Make the system easier to use at the moment work occurs.
- Document why a rule exists, not only how it functions.
- Build for the company's current motion while protecting likely future needs.
Without principles, a clean CRM becomes a collection of individually reasonable requests. With them, the operating system can expand without losing coherence.
Commercial empathy does not mean saying yes
People sometimes interpret seller empathy as a mandate to remove every requirement the field dislikes. That is not the lesson.
RevOps still has to protect data quality, forecasting integrity, customer handoffs, and company strategy. The advantage of sales experience is knowing how to explain those requirements in terms the field recognizes.
An operator who has carried a quota understands that adoption is earned through usefulness and trust. They can also recognize when a complaint reflects ordinary resistance rather than a design failure.
That combination produces better decisions than either extreme: designing exclusively from headquarters or allowing every local preference to become a new exception.
The practical lesson for RevOps leaders
Calvin's path suggests that the strongest operators build across four layers:
- Execution empathy: understand how the process feels to the person doing it.
- Tactical fluency: know how the systems and workflows actually function.
- Strategic judgment: connect those systems to the company's commercial model.
- Operating discipline: create principles that keep one-off requests from becoming permanent complexity.
Sales experience is not the only path into RevOps. But some exposure to frontline execution is difficult to replace. It gives the operator a reality check every time a clean diagram meets an imperfect commercial environment.
About the guest
Calvin Cupino is VP of Revenue Operations at Pylon. His career includes finance, frontline technology sales, and building revenue operations as an early functional leader.
