Hardware & Software Asset Management · Gurugram, India

Discovery says one number. Procurement says another.

Crestavia builds Hardware and Software Asset Management on ServiceNow, and the CMDB underneath them that makes both numbers worth trusting. A specialist practice, not a general platform shop.

Start a conversation See where you stand

Entitlements on record

1,200

Installs discovered

1,476

Unlicensed exposure

276

The third column is where a publisher audit begins. Closing it is the job.

Illustrative

Why ITAM programmes stall

Almost nobody fails at buying the product. The failures happen in the three places below, and they are the same three every time.

Entitlements never got loaded

The platform goes live with discovery working and the contract side empty. Reconciliation runs against nothing, so every result is meaningless and the team stops looking at it.

The CMDB was never trusted

Duplicate CIs, no clear ownership, discovery that reaches half the estate. Asset management inherits that data and inherits the mistrust with it.

Nobody owns it after go-live

The implementation partner leaves, the configuration is undocumented, and within two releases the normalisation rules no longer match what the estate actually runs.

Where are you on this?

Most organisations that call us think they are further along than they are, because the platform is live. Being live is stage two. The value is in three, four and five.

Stage two feels like success because dashboards populate. The licence position is still unprovable.

Maturity model

Three things, done properly

Asset management fails in the joins between these, which is why we work across all three rather than taking one in isolation.

SAM PRO

Software Asset Management

From licence position to audit defence, with a reconciliation you can put in front of a publisher.

Entitlement loading and normalisation
Publisher packs — Microsoft, Oracle, IBM, Adobe, SAP, VMware
Reconciliation, true-up readiness, audit response
Reclamation, downgrade and upgrade rights
SaaS licence visibility and renewal timing

HAM PRO

Hardware Asset Management

The full life of an asset, from purchase order through to a disposal certificate you can evidence.

Procurement through to retirement workflows
Stockrooms, transfer orders, model normalisation
Refresh planning and depreciation schedules
Secure disposal and chain of custody
Consumables and bulk stock handling

CMDB · CSDM

Configuration data you can act on

The foundation both asset practices stand on, modelled and governed so it stays correct after handover.

CSDM alignment and class modelling
Discovery, Service Graph connectors, Intune and SCCM feeds
Identification and reconciliation rules
Health dashboards, certification, remediation
De-duplication and clear ownership

What reconciliation actually finds

The headline number is rarely the useful one. Below is how a licence position typically breaks apart once entitlements and installs are put side by side — a worked example, not a client result.

Reclamation usually pays for the engagement before the first renewal. Your numbers will differ.

Worked example

Three ways to start

Each one is fixed in scope and ends in something written down, so you can act on it whether or not you continue with us.

Implementation

A HAM Pro, SAM Pro or CMDB build from the ground up, or a stalled deployment taken to completion.

Typically 10–14 weeks

You receive

Configured and tested platform
Loaded entitlements and normalisation rules
Configuration documentation
Admin training and handover session

Health check

A fixed-price assessment of what you already have — where the data breaks, what it costs you, and the order to fix it in.

Two to three weeks

You receive

Findings report against the maturity model
Data quality assessment with examples
Prioritised remediation plan
Effort estimate per item

Co-delivery

Senior ITAM capacity alongside your internal team or your existing implementation partner, for the stretch where specialist depth matters.

By arrangement

You receive

Named senior consultant, no substitution
Work inside your governance and release process
Knowledge transfer as standard
Weekly written status

A typical implementation shape. Entitlement loading is the phase that slips, and it slips on contract data you have to find, not on platform work.

Indicative plan

Five questions worth asking any ITAM partner

Including us. If a prospective partner cannot answer these clearly, the engagement will be harder than the proposal suggests.

01

Who exactly will do the work, and can I meet them before signing?

Proposals are written by senior people. Delivery is often staffed by whoever is free. Ask for names, and ask what happens if those names change mid-engagement.

02

Show me a reconciliation you have produced.

Anonymised is fine. You are looking for whether entitlements, installs and the resulting position actually line up, and whether someone could defend it to a publisher.

03

How do you handle entitlement data we cannot find?

Every estate has contracts nobody can locate. The answer tells you whether the partner has done this before or is assuming your records are complete.

04

What exactly is out of scope, in writing, before we start?

Scope creep in ITAM usually arrives through data cleanup nobody costed. A partner who has been burned by this will have a clear answer ready.

05

What does my team have on the day you leave?

Documentation, trained administrators and the ability to maintain normalisation rules through the next two releases. If the answer is a support retainer, that is a different kind of relationship.

How we work

Senior people only

The person who scopes your work is the person who does it. No handover to a junior bench once the proposal is signed.

Asset management is the whole practice

We are not a general platform shop that also takes ITAM work. HAM, SAM and the CMDB beneath them are all we do.

Scope before contract

Deliverables, assumptions and dependencies in writing before anything is signed. Changes are priced, not absorbed quietly.

Your data stays yours

We work inside your instance, under your access controls and your release process. No entitlement or estate data is copied out to work on elsewhere.

Built to be handed over

Configuration is documented and your team is trained on it. The goal is that you stop needing us, not that leaving is difficult.

Honest about size

We are a specialist practice, not a global SI. For programmes that need a large certified bench across several regions, we will say so and tell you what we would be good for instead.

Who you'll be working with

Crestavia Technologies was founded by Rohit Charag, a ServiceNow architect with close to a decade on the platform and a specialism in IT asset management.

That decade has been spent inside large, messy estates across retail, industrial, energy and insurance — building SAM and HAM practices, untangling CMDBs that had drifted away from reality, and getting licence positions into a state where finance and procurement would both sign off on them.

The platform engineering grounding sits underneath all of it: Flow Designer, IntegrationHub, discovery and connector integrations, and release management on instances where several teams were shipping at once.

Crestavia exists to do that work directly, at a scale where the senior person stays on the engagement from the first call to handover.

Entity: Crestavia Technologies Pvt Ltd
Based: Gurugram, India
Practice: HAM Pro · SAM Pro · CMDB
Platform: ServiceNow
Experience: ~10 years on platform
Overlap: IST · CET · ET

Tell us what your licence position looks like.

If you are heading into a renewal, a true-up or an audit, or you simply cannot get a straight answer out of your CMDB, that is the conversation to start with. A first call costs nothing and usually tells you whether the problem is data, process or product.

Gurugram, India · Working with teams across IST, CET and ET