About Rohit Kapoor
Rohit Kapoor is 35, a senior solutions architect and sales engineer at a 350-person data-integration company, twelve years into the industry and seven of them in pre-sales after starting as a backend engineer. He partners with four enterprise sellers, runs the technical track of every proof of concept, owns the technical answers in requests for proposal, builds custom demonstration environments over a weekend, and mentors two mid-level colleagues. He owns a house in Cedar Park with his wife, a paediatrician, and their two-year-old son. He travels two weeks a month, dislikes it, and is negotiating it down. Weekends are cricket, elaborate cooking and a camera.
His governing principle is not selling what the company cannot build, and he has walked deals backwards when the product did not match his own demonstration. He is calm and structured, speaks slowly and with weight, and switches cleanly between deep technical register with a customer’s architects and plain business language with their executives. His recurring questions are what the failure mode is and how it has been tested, and his recurring move is to name a limitation out loud along with the workaround and the ticket he filed. What frustrates him is the gap between marketing claims and shipped reality, a seller who oversells on a discovery call and leaves him to walk it back, and generated demonstration flows that a customer can immediately tell are fake.
He is strongest at consideration and decision for enterprise software in the $100,000 to $1M range, because he is the technical voice that makes or breaks those deals without holding any budget himself. He is the right subject for catching when a vendor’s claims have overshot the product, when an automated demo will read as synthetic, and when a tool has been designed by people who have never watched a pre-sales workflow. He reads well on the transition from what was sold to what was deployed, which makes him useful on adoption and mastery and on the renewal risk that begins the day implementation gets ugly. He is a weak subject for awareness-stage messaging; he listens to his professional community and a few peers, and to almost nothing else.
YouTube, Google search, LinkedIn, podcasts and email score high. LinkedIn is active — he posts as well as reads — and a pre-sales professional community, its Slack and its newsletter are his real information channel. He works through conference talk archives, listens to long-form interview and business-history podcasts on flights and commutes, and follows cloud architecture accounts on X. His trusted sources are that community, three peer sales engineers at other companies, and the senior architects on his own accounts, several of whom have become friends. Instagram, Threads, Reddit, X, connected television, text and in-app push are mid; Facebook, TikTok, Pinterest, out-of-home and print are low; Snapchat and direct mail are minimal. His day is demo preparation from seven, customer calls either side of an internal midday block, family from half past five, and more preparation after nine.
