Request beta access

Installed-base visibility for HubSpotPrivate beta

Know what every customer has installed — and what comes due next.

Bring installed-equipment data from spreadsheets or ERP exports into HubSpot, safely match each unit to the right company, and see upcoming warranty, service and replacement opportunities.

Request beta accessSee how it works

Apply in about a minute. No sales call or phone number required.

Sample data
The Qurevi review screen, shown with synthetic sample data. A group called Qurevi Demo Foods, covering two equipment records, is flagged 'needs review - 2 companies normalise to qurevi demo foods'. Two fictional candidates are listed with identical scores of 98: Qurevi Demo Foods S.A. at foods-eu.example and Qurevi Demo Foods SA at foods-mx.example. The available actions are accept, leave unassociated, or skip.
Ambiguous match? Qurevi stops and asks instead of guessing.Real Qurevi product UI shown with synthetic sample data.
  • CSV and XLSX importsMessy exports, junk rows and odd headers included
  • Deterministic company matchingHubSpot Company ID, domain, then normalized name
  • Human review for uncertain matchesA false match is worse than an unmatched row
  • Built for HubSpotAssets associate to the Companies you already have
Why it matters

See the replacement window before it closes.

Qurevi turns installed-equipment history into visible replacement, warranty and service opportunities inside HubSpot.

Customer installed baseSample data
Qurevi Demo Packaging has four machines on site. Three went in recently; the LB-90 Labeller was installed in 2017, which puts it nine years into an expected ten-to-twelve year service life, so Qurevi surfaces it as a potential replacement opportunity on the Company record in HubSpot.The signal comes from installed-equipment lifecycle data, not from telemetry. Qurevi does not monitor machines, predict failures, decide what to sell or create the deal for you.Conceptual illustration with fictional sample data. Not a product screenshot, not a customer, and not a usage figure.
The problem

Manufacturers know what they sold. The installed base is harder to see.

You can answer "who bought from us" from HubSpot today. Answering "what equipment does this customer have, how old is it, and what expires next" usually means a spreadsheet and somebody's memory.

  • The sale is recorded. The machine isn't.

    HubSpot holds the customer and the original deal. It rarely holds the individual units that customer actually has installed.

  • The installed base lives outside the CRM.

    Serial numbers, models and install dates sit in spreadsheets, ERP exports and whatever the service team keeps their own notes in.

  • Lifecycle dates go unwatched.

    Warranty and service-contract end dates exist somewhere, but not anywhere a revenue team looks at the moment they start to matter.

How it works

From a spreadsheet export to a structured installed base.

Five steps, with a human decision point where the data is uncertain. Matching is never silently assumed.

  1. Import your equipment data

    Start from the export you already have - CSV, XLSX or an ERP extract. Serial numbers, models, installation dates, warranty and service-contract end dates.

  2. Match assets to HubSpot Companies

    Each row is matched against your existing HubSpot Companies using conservative deterministic rules, so an asset is associated with the customer that owns it.

  3. Review the uncertain matches

    Confident matches go through. Anything ambiguous is held for your review rather than silently guessed at.

  4. One Installed Asset record per physical unit

    Each unit becomes its own structured Installed Asset record, associated with its HubSpot Company - not a note field, not a spreadsheet column.

  5. Surface lifecycle opportunities

    With lifecycle dates on every asset, the installed base can be read forward: what is ageing, what expires, and when.

The result

One structured Installed Asset record per physical unit, related to its HubSpot Company.

Not equipment details flattened into a note, a text property or a spreadsheet attached to the account. Each unit is its own record, carrying its own serial number, model and lifecycle dates, so the installed base can be filtered, reported on and worked like any other object in HubSpot.

HubSpot CompanyQurevi Demo Packaging
  • HX-440 FillerSN 4471-08812
    Installed
    Mar 2018
    Warranty ends
    Mar 2026
  • HX-220 CapperSN 2210-00934
    Installed
    Sep 2016
    Service ends
    Dec 2026
  • LB-90 LabellerSN 0090-17755
    Installed
    Jul 2014
    Match
    Needs review

3 sample assets1 awaiting review

Illustrative structure of the installed-base record, with a fictional company and sample assets. Not a product screenshot, not a customer, and not a usage figure.

Qurevi is in private beta and the HubSpot integration is under review.What that means today.

Why it's different

Not just another import.

Qurevi handles messy equipment exports, detects the relevant columns, normalizes lifecycle dates, matches assets to existing HubSpot Companies, and holds uncertain matches for review instead of silently guessing.

  1. Messy exportJunk rows, odd headers, inconsistent date formats, duplicate units.
  2. NormalizationRelevant columns detected, values and lifecycle dates parsed into one shape.
  3. Safe matchingHubSpot Company ID, then domain, then normalized name. Conservative throughout.
  4. Human reviewAnything genuinely ambiguous is held for a decision instead of guessed.
  5. Structured Installed AssetsOne record per unit, associated with the right HubSpot Company.

The goal is a clean, structured installed base in HubSpot without turning every import into a manual data-cleaning project.

What it helps you identify

The lifecycle data already exists. Qurevi makes it usable inside HubSpot.

Once each asset carries its own lifecycle dates, these become ordinary questions to ask of your installed base.

  • Equipment approaching expected replacement

    Units whose age is passing the replacement window you expect for that model.

  • Warranty expirations

    Assets whose warranty end date is approaching, grouped by the customer who owns them.

  • Service-contract expirations

    Contracts approaching their end date, so renewal conversations start before the lapse rather than after it.

  • Installed equipment by customer

    Everything a customer has installed, in one place, rather than reconstructed per request.

Qurevi Installed Base structures this data and makes it queryable. It does not run outreach for you, and it does not decide which opportunities are worth pursuing.

Who it's for

B2B manufacturers and equipment distributors selling long-lived equipment.

The kind of business where a unit sold in 2016 is still in service with a customer today, and still represents revenue.

For RevOps, aftermarket, service and commercial teams responsible for installed equipment across customer accounts.

  • Industrial equipment
  • Packaging machinery
  • Commercial equipment
  • Laboratory equipment
  • Specialised hardware

A good fit if

  • You sell physical equipment that stays in service for years.
  • You run your commercial side on HubSpot.
  • Your installed-base data currently lives in spreadsheets or an ERP export.

Not what this is

  • You need dispatch, scheduling or technician routing - this is not field-service software.
  • Your product is software or consumables with no serialised physical unit.
  • You are looking for a full asset-maintenance system of record.

Before you apply

Do I need an ERP integration?
No. The beta starts from CSV/XLSX or an export you already have.
What happens when a company match is uncertain?
Qurevi holds it for review rather than assigning the asset automatically.
Is this field-service software?
No. Qurevi focuses on installed-base visibility and lifecycle opportunities inside HubSpot. It does not handle dispatch, technician scheduling or routing.
Is the HubSpot integration available today?
Qurevi is accepting private-beta applications while the Installed Asset integration is under HubSpot review. We confirm exactly what is available before any installation.
Private beta

Request access to the private beta.

Four questions about your installed base. We'll review your use case and reply by email with availability and next steps.

  • Limited onboarding

    We take on a small number of teams at a time so each one gets real attention during the beta.

  • Built for HubSpot users with installed equipment

    The beta assumes you already run on HubSpot and have equipment data you can export.