ΦPhi Intelligence
Menu
Book a walkthrough

An assessment of every customer, not the two you have time for

The Health Assessment Engine reads the vendor telemetry you already have channel access to, measures each customer's estate against the vendor's own documentation and their own business context, and returns a ranked set of findings under your logo.

Talk to us about vendor coverage

In development. Vendor coverage lands progressively, starting with the vendors you concentrate in.

Nothing gets installed anywhere

You already have channel access to your vendors' own telemetry platforms: AutoSupport, InfoSight, and the equivalent partner portals across your vendor set. They carry customer metadata, utilisation and trend analysis, and you are already entitled to see them.

So there is no agent, no collector, and nothing deployed in your customer's environment. The data is already on your side of the line. The engine reads what you can already reach.

Six questions, asked of every customer

Each one answered against the vendor's own documentation and the customer's own situation, across your whole book rather than the two accounts you have time for.

  1. Best practice. Is the customer running the product the way the vendor says it should be run?
  2. Code viability. Are they on a supported, viable release?
  3. Release track. LTS or preview, and is that the right choice for this customer?
  4. Fit to their needs. Is the configuration right for what this business actually does?
  5. Vertical and compliance fit. Is it right for their sector's regulatory reality: health, finance, public sector, critical infrastructure?
  6. Purchased versus consumed. Are they using the features they already bought, and using them correctly?

Four inputs, and the combination is the product

  • The vendor's own documentation. Best practice, configuration guidance, release and support matrices, capability reference.
  • The customer's telemetry. From the channel access you already hold.
  • The customer's persona and vertical. What this business does, what its sector requires, and what compliance frameworks bind it.
  • The customer's own context. Public filings, stated objectives, and the conditions around them. Inferred first, then confirmed with the customer before any finding rests on it.

Telemetry alone is monitoring. Vendor documentation alone is a chatbot. Business context alone is research. Together they produce a ranked, defensible set of findings.

Three artifacts

  • The scored assessment. The customer's estate measured against the six questions, with the gaps ranked.
  • The remediation plan. What to do, in order, with the commercial consequence attached. Some items are free: a configuration change, a feature already paid for and switched off. Some carry an incremental cost that pays for itself. The plan says which.
  • The branded report. Your logo, delivered to your customer. Phi does not appear in it.

The third one is the commercial point. A reseller who hands a customer that document is a different kind of supplier from one who emails a quote.

The same platform, pointed the other way

Upward, toward vendors

Revenue Intelligence Hub: renewal timing, program tiers, rebate thresholds, and the consumption evidence for a vendor meeting.

Revenue Intelligence Hub

Downward, toward customers

The Health Assessment Engine: what the estate actually looks like, what is not being used, and what to fix, in a report that carries your own logo.

Most resellers walk into a customer review with what the customer told them. This is the difference between attending that meeting and running it.

Why this assessment rather than anyone's

The lineage is the credibility. This is the same discipline behind a 36-for-36 proof-of-concept record: measuring the outcomes the competition was not measuring.

Business Impact Lab does it before the sale, as an engagement run by hand. The Health Assessment Engine does it after the sale, as software, across a whole book at once.

How Business Impact Lab runs

Availability

The engine is in development. Vendor coverage lands progressively, as each vendor's documentation and telemetry format is brought in.

Coverage is per vendor and confirmed with you per engagement, the way vendor coverage is confirmed for Revenue Intelligence Hub. Early customers get the vendors they concentrate in first.

Talk to us about vendor coverage

Deliberately out of scope

  • Not monitoring. A point-in-time assessment, not a watch.
  • Not a scoring tool. This is your view of your customer, not a vendor's view of its installed base.
  • Not automated remediation. It says what to do; engineers do it.
  • Not an agent in anyone's environment. Nothing gets installed.

Start with the vendors you concentrate in

Tell us which vendors carry most of your book, and we will tell you what the engine covers for them today and what is coming.

Talk to us about vendor coverage