Bindu Nariani Karnik
Chief Executive Officer
Leads ShepardTri's strategy and enterprise partnerships, bringing 20+ years of experience to how the company builds and delivers MATRIX.
Our people
The team behind MATRIX
ShepardTri is led by engineers and operators who have spent years inside the document-heavy processes we now automate. The people who scope your project are the people who stay with it after go-live.
Leadership
Who runs ShepardTri
Venkatanathan Dwarakanathan
Chief Technology Officer
Sets the technical direction for the MATRIX platform, drawing on 35+ years across enterprise technology and engineering leadership.
Devakumaran Kailasapathy
Head of Delivery
Runs client engagements end to end and keeps deployments on schedule across banking, healthcare and logistics, backed by 20+ years in delivery leadership.
SakthiVel S
Director of Engineering
Directs the engineering teams building and maintaining the MATRIX platform, with 15+ years of hands-on engineering experience.
Abhinav Kharbanda
Head of Sales & Customer Engagement
Leads sales and customer engagement, working with prospective and current clients to scope automation that fits their real workflows, with 20+ years in the field.
Thawpeek Abbasali
Chief Architect
Owns the architecture behind MATRIX's document processing pipeline, with 16+ years of experience designing systems for scale and reliability.
Denesh Chakravarthy Velusamy
Engineering Manager
Manages the engineering team delivering MATRIX features and integrations day to day, with 16+ years of experience in software engineering.
How we operate
What working with this team looks like
Small teams, direct access
You work with the engineers building your pipeline, not a layer of account managers relaying questions back to them.
Numbers over narrative
Progress is reported as measured accuracy on your documents. If a number moves the wrong way, you hear it from us first.
We stay after go-live
The same team supports the platform in production — monitoring accuracy, retraining on new formats and extending into new document types.
Talk to the people who'll build it
Bring us the process that's costing your team the most hours. You'll be talking to the engineers who would run the engagement, not a sales layer.