Founding Practice

ServiceNow

The platform we know deepest. Organizations tend to buy ServiceNow quickly and configure it slowly — and most of the value arrives long after the first module goes live.

Where the value actually sits

A ServiceNow implementation is rarely judged on whether the first module went live. It is judged eighteen months later, on whether the CMDB is trusted, whether upgrades happen on schedule or are perpetually deferred, whether the customizations somebody added in year one now block every release, and whether anyone internally understands how the thing is put together.

That later phase is the work we are built for. It is less glamorous than a greenfield implementation and considerably more consequential.

Customizations added Upgrade reviewcost rises Upgrade deferred Further behindon releases more to review so it waits gap widens built on an older base Scoped review, regular cadence breaks the loop here WHY DEFERRING AN UPGRADE GETS MORE EXPENSIVE EACH TIME
This is a reinforcing loop, not a schedule slip. Each deferred release adds customizations that the next upgrade has to review, so the cost of upgrading rises exactly as the appetite for it falls. The intervention is not a bigger upgrade project — it is scoping the review and holding the cadence, which is where we usually start on an instance that has fallen behind.

Coverage

Where we work on the platform.

Service management

ITSM across incident, problem, change and request. Process design first, configuration second — automating a broken process just makes it fail faster.

Operations & CMDB

ITOM, Discovery, Service Mapping, and the CMDB work that makes the rest credible. Asset and hardware management where licence position or lifecycle tracking matters.

Employee & customer workflows

HRSD and CSM for organizations extending the platform beyond IT — usually the point at which the original data model needs revisiting.

Security, risk & compliance

SecOps and Integrated Risk Management, including the control evidence and audit trails public sector customers are obliged to produce.

Platform engineering

App Engine custom applications, Integration Hub and REST/SOAP integrations, Flow Designer, and scoped development that upgrades cleanly.

Upgrades & platform health

Getting instances current and keeping them there — skipped-release recovery, customization review, and the technical debt that accumulates quietly.

Typical engagements

  • Platform health assessment. A bounded review of an existing instance — architecture, customization debt, upgrade posture, CMDB accuracy — producing a written findings document with prioritized remediation. Frequently the right first engagement.
  • CMDB remediation. Making the configuration data trustworthy enough that the processes depending on it can be relied upon. Usually the highest-leverage work available on a mature instance.
  • Module implementation. A new capability — HRSD, CSM, SecOps, asset management — designed and delivered without destabilizing what is already in production.
  • Upgrade recovery. Instances several releases behind, where customization has made upgrading feel impossible. It rarely is; it is usually just unscoped.
  • Retained administration. Ongoing platform ownership for organizations without a dedicated internal team.

Partner status

Tessivant is not currently a member of the ServiceNow Partner Program. Registration is in progress, and we will state our status here precisely when it is granted. We would rather be plainly new than imply a relationship we do not hold.

A person explaining a diagram on a board to two colleagues
The measure of the work is what your team can run without us.

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