Rohit Bedi
Chief Revenue Officer
As Chief Revenue Officer (CRO), Rohit is responsible for overseeing all global sales and international regions and expansion. He also oversees Duck Creek’s global partner ecosystem, as well as our global solution consulting practice.
For more than 25 years, Rohit has held senior leadership positions at technology companies, leading market-facing organizations in roles that have included sales management, revenue growth, business development, partnerships and channels, marketing, and customer management. His business leadership has spanned across multiple verticals and worldwide geographies, along with significant exposure to technology ecosystems and partnerships across the globe.
Rohit brings a best-in-class experience in enterprise software. His strategic-planning acumen and well reputed execution focus drove successful growth initiatives most recently at MetricStream, a business and Cyber risk SaaS leader, and at other notable software companies, including Siebel Systems, PeopleSoft, Cognizant, Cymbal, many of which became dominant market share leaders in their markets during his tenure.
Rohit earned his MBA from Harvard with honors. He earned his undergraduate degree in engineering from the Delhi College of Engineering, and his post graduate Master of Science in engineering from The University of Alabama, both with honors. Rohit is also part of advisory boards and supports organizations helping underprivileged youth advance in sports and education.
Meet the Duck Creek Team
Our leadership team is comprised of industry veterans and technology experts with decades of experience solving the complex challenges unique to the P&C industry. Every one of our employees is passionately dedicated to shaping the future of insurance.
We like “Why not?” more than “Why?
The team at Duck Creek lets companies bring their amazing ideas to life quickly and easily by building software that thinks and works like they do. We’re fueled by sharing ideas openly, challenging conventions, trying new things, and valuing “Why Not?” over “Why?”