About
A specialist firm, deliberately
Built around depth in platform delivery rather than breadth across everything, with a structure designed to add practices without losing the discipline that makes the first one work.
Why the firm exists
Enterprise platform work is usually sold by people who will not be delivering it. A partner scopes the engagement, a proposal describes a methodology, and the people who arrive on Monday are meeting the requirements for the first time. The gap between what was sold and what gets built is where most platform disappointment lives.
Tessivant is built the other way around. The person advising on the architecture is the person accountable for it working. That constrains how much work we can carry at once, which is a deliberate trade rather than a limitation we are working to overcome.
Core Principles
Two commitments, and everything else follows from them.
Trust
In public sector work, trust is not a sentiment. It is procedural — showing up when scheduled, documenting decisions so they survive a change of staff, and telling a client the thing they would rather not hear while it is still cheap to hear it.
In practice: we will tell you when a scope does not need us, when a platform is the wrong answer to your problem, and when a deadline is not going to hold. A firm that only ever agrees with you is not earning its fee.
Value
Value is measured by what the platform does after we leave — not by hours billed while we are there. A system that works only while consultants are in the building has not been delivered. It has been rented.
In practice: we build so your team can run it, document so they can extend it, and treat our own eventual redundancy as the goal rather than a risk to be managed.
Leadership
Founded on delivery experience.
Suresh Ganapathy
Founder and Principal
Suresh is an enterprise platform architect who has spent his career on large-scale ServiceNow implementations, including a deployment serving more than 62,000 users at Hewlett Packard Enterprise.
His background spans platform architecture, service management and the organizational side of transformation — the part where a technically correct design still has to be adopted by people who did not ask for it.
- Focus
- Enterprise platform architecture
- Scale
- ServiceNow deployment serving 62,000+ users
- Background
- Hewlett Packard Enterprise, T-Mobile
- MBA
- Kellogg School of Management, Northwestern University
- Engineering
- B.E., National College of Engineering
The Practice Model
Built to add practices, not to be defined by one.
ServiceNow is where we begin, not what we are. New practices attach to the same architecture, governance and delivery method rather than requiring the firm to become a different company. Each is listed at its true status.
ServiceNow
Architecture, implementation, integration and managed services across the platform.
Cloud & infrastructure
Platform hosting, migration and modernization for organizations moving workloads off legacy infrastructure.
Cybersecurity
Security operations, risk and compliance workflows, and the controls platform work increasingly has to satisfy.
Data & AI
Making the data an enterprise platform accumulates useful — reporting, analytics and applied automation.
Contact
Tell us what you are trying to make work.
Start with the problem and we will tell you honestly whether we are the right firm for it.
contact@tessivant.com