"Vendor Detail: Stack Fit (Ecosystem Fit)"

What it is

Stack Fit is the section of the vendor card that answers a narrower, practical question than cost or score: if you actually turned this vendor on tomorrow, would it work with what you already run? A vendor can have a strong Verinode Score and a fair price and still be a poor fit day one, because it needs a platform you don't run, a piece of hardware you don't own, or because it plugs in cleanly with a tool that's already part of your stack. Stack Fit reads your equipment inventory and your active vendor relationships, checks them against the compatibility rules Verinode's research team has attached to that vendor, and gives you a plain verdict plus the reasons behind it.

Verinode does not decide whether the vendor is right for you. It surfaces what would need to change, what already lines up, and what's simply nice to have, so the decision is informed instead of a guess.

Where to find it

Open Vendors from the sidebar at iq.verinode.ai/vendors. Click any vendor tile (from the Most recent row, the Stack view, a decision tile in Take Action, or the Compare modal) to open its detail card. Stack Fit is one of the section pills in the row beneath the hero and health bar, alongside The Contract, Renewal & People, Ratings & Feedback, Score & Research, Alternatives, and the rest. See Inside a vendor card for how that whole card is laid out.

Stack Fit does not appear on every vendor. It is a conditional pill: Verinode hides it entirely when there is nothing worth telling you, rather than showing an empty or generic section. The two reasons it can be missing are covered below.

How Verinode builds your stack fingerprint

Before it can say anything about fit, Verinode assembles a fingerprint of what you actually run, from two sources:

• Equipment. Every piece of equipment logged in your inventory on the Equipment page (/equipment), resolved to its equipment class, plus every class above it in the hierarchy. If you own a specific model of moisture meter, that also counts as owning the general moisture meter class it belongs to, so a compatibility rule written at either level matches what you actually have on the truck.
• Platforms. The tools you run, detected from your active vendor relationships on /vendors. Verinode maps a relationship's vendor name to a known tool (Xactimate, XactAnalysis, QuickBooks Online, QuickBooks Desktop, Xero, and several job-management and project platforms) and treats it as a platform you run. Xactimate and XactAnalysis both count as running Xactimate; QuickBooks Online and QuickBooks Desktop both count as running QuickBooks. Archived relationships don't count, only active ones.

Because the fingerprint comes from data you already have on file, there's no separate onboarding step to build it. Keeping your equipment inventory current and keeping the vendors you actually use marked active (not archived) is what keeps Stack Fit accurate.

The headline read

At the top of the section, a colored dot and a short label give you the fastest possible read:

• Fits your stack (green dot). The vendor has no unmet requirements, and at least one real integration boost with a platform you already run.
• Fits, with tips (gray dot). No unmet requirements and no integration boosts either, just soft notes about hardware that would make the fit better. Nothing here is blocking you.
• Needs hardware you may not have (amber dot). The vendor requires a piece of equipment that isn't on your inventory. This is a soft block, not a hard one, the equipment is buyable, so Verinode surfaces the gap rather than dropping the vendor from consideration.
• Stack mismatch (red dot). The vendor requires a platform you don't run, most often a different estimating or accounting system than the one you're on. Switching platforms is not a casual purchase the way buying a piece of equipment is, so this is treated as the more serious verdict.

When more than one issue applies, the worst one wins: a platform mismatch outranks a hardware gap, which outranks a soft note. So a vendor that both needs a platform you don't run and could benefit from equipment you don't own still reads Stack mismatch, the individual reasons underneath list both.

The reason list

Below the headline, one row per reason, each with its own colored dot, in this order: integration boosts first, then blockers, then soft notes.

• Native integration with your {platform} (green dot). The vendor natively integrates with a platform you already run, for example Xactimate or QuickBooks. This is a positive signal only, Verinode only asserts an integration when your fingerprint shows you run that platform; it never claims a vendor lacks an integration just because the data doesn't confirm one.
• Built for {platform}, which you do not run (red dot). A hard platform requirement your fingerprint doesn't satisfy. This is what drives the Stack mismatch verdict.
• Needs a {equipment}, none on file in your equipment (amber dot). Required hardware that isn't in your equipment inventory. This is what drives the Needs hardware you may not have verdict, the cost of that hardware is the honest "all-in" cost of adopting this vendor.
• Works better with a {equipment} (gray dot). A nice-to-have. The vendor works fine without this equipment, it's just a soft tip, and it never downgrades the headline verdict.

The platform or equipment name in each line is written in its proper brand form (Xactimate, QuickBooks, a 360 camera, a thermal imaging camera, a hygrometer, a pin or pinless moisture meter, and so on), never as a raw database label. Where Verinode's research team has written a specific note explaining the requirement, that note replaces the generic line above, so a reason can read as plain custom guidance instead of the template text.

A footer line under the reason list reads:

Based on your equipment inventory and the tools in your stack.

That's a reminder of exactly where the read comes from, and a cue that if either changes, the read here can change too.

Why the section is sometimes missing

Stack Fit is hidden, not shown empty, whenever there's nothing useful to say. That happens in two cases:

1. The vendor isn't matched to Verinode's research catalog, so no compatibility rules exist to check against.
2. The vendor is matched, but the check comes back with nothing to report: no unmet requirements, no soft notes, and no boosts (usually because you don't run any of the platforms the vendor integrates with, and the vendor has no equipment requirements at all).

Either way, the pill simply doesn't render in the section row. This also means the section can pop in a beat after the rest of the card, Stack Fit is fetched in the background alongside Alternatives and Related SOPs, so it's one of the last pieces of the card to settle.

Using it to decide

Read Stack Fit alongside Score & Research and Alternatives, not instead of them. A vendor with a strong score and a Stack mismatch verdict is a vendor you'd need to change your estimating or accounting platform to adopt, worth knowing before you spend time evaluating it further. A vendor with Needs hardware you may not have is still very much in play, you're just pricing in the equipment. And a vendor that reads Fits your stack with a native integration boost against a platform you already depend on is a real point in its favor that a bare score number wouldn't show you on its own. None of this rules a vendor in or out for you, it puts the practical, plug-in-tomorrow facts next to the cost and score facts so the call is yours to make with the full picture.

Data sources

Related articles

• Inside a vendor card: the detail view
• Vendor detail: the contract, renewal & people
• The Vendors section
• Connecting your data
• How benchmarks work
• The decision workspace

</content>