Skip to content


Meet the Leadership Team

Our expertise is providing efficient technology for complex business solutions.

The Intelliworx Leadership Team has decades of experience in public and private sector technology and management.  Whether through technology or process, Intelliworx can help you build relationships, efficiencies and trust with the persons who bring the actual value to your organization: your employees.

Chief Executive Officer

Rob Hankey

Chief Executive Officer (CEO)

Rob is the CEO of Intelliworx and cofounded the company in 2003 to help government agencies automate their employee life cycle processes. He is responsible for setting and implementing the business strategy of Intelliworx; also ensuring Intelliworx provides the highest quality products and exceptional customer service. 

Rob has a BS in Aeronautical Engineering and a MS in Engineering and Process management. Prior to a career in government contracting and business ownership, Rob spent 22 years as an officer and aviator in the US Army. Rob has served the US Government for 40 years, allowing him to understand the complexities associated with government administrative processes, compliance and security mandates.

Chief Operations Officer

Tom Riley

Chief Operations Officer (COO)

Tom is the Chief of Client Operations for Intelliworx. He has over 30 years of client service consulting and project management experience for a wide variety of clients, ranging from small, privately held companies to Fortune 500 firms. 

Tom manages the client operations and the coordination of long-range projects, which involves interfacing with clients, partners and internal resources. His leadership abilities, exceptional organizational skills, and conviction that “client relationships matter” is valued by Intelliworx and clients alike.

Chief Technology Officer

Scott Coldwell

Chief Technology Officer (CTO)

Scott is the Chief Technology Officer and Chief Architect at Intelliworx. He has over 15 years’ experience in software design and architecture. 

Scott is responsible for designing, developing and managing our ‘Intelliworx Platform’ on which our web-based software solutions are based. He is an innovator and is tireless in his dedication to providing quality business solutions to customers. Scott is also an avid musician and recording engineer.

Chief Infrastructure & Security Officer

Mike Howlett

Chief Infrastructure & Security Officer (CISO)

Provides security, technology and risk management leadership. Manages a team of specialists in systems administration and cybersecurity. Develops training, policies & procedures, and system security plans based on multiple compliance frameworks. Manage projects, IT budgets, vendors, security agreements, SLAs with both public and private partners. Builds secure environments to FedRAMP (via NIST 800-53, 800-63, FIPS 140-2, others) standards and best practices. 

Manages all security operations including security architecture and planning, incident response, contingency planning/disaster recovery, vulnerability assessments, risk analysis, compliance, and continuous monitoring.

Chief Business Officer

Corinne Koshuta

Chief Business Officer (CBO)

Corinne is the Chief of Business Operations at Intelliworx. She runs the company’s daily business operations as well as the company’s human resources. Corinne has worked with many small technology companies in her career and provides Intelliworx with a ‘people-centered approach’ to business and employee relations. She prepares and maintains corporate financial forecast, budget, and cashflow documents and has working knowledge of government accounting requirements under FAR and CAS.

Chief Product Officer 

Mark Bates

Chief Product Officer  (CPO) 

As Chief Product Officer, Mark works with all internal and external stakeholders to provide technical requirements, research, recommendations and communications regarding product development and their associated systems. 

Critical to Mark’s responsibilities as CPO, he communicates as high or low on the technical scale as the audience requires and clearly describes technical concepts and details in a non-technical way.