Skip to content

What it looks like from the front office.

The gaps look much the same whether you make equipment, parts or other companies' products.

  1. 01

    Quotes live in email and spreadsheets.

    An RFQ arrives, engineering prices it, sales sends a PDF, and nothing tracks it until an order shows up in the ERP.

  2. 02

    HubSpot doesn't know our prices or what shipped.

    Products, price lists, orders and inventory live in the ERP. Reps check it by phone, or not at all.

  3. 03

    We don't know who the dealer sold to.

    Dealers and distributors own the end-customer relationship, and territories overlap between dealers, reps and the direct team.

  4. 04

    Every deal has a buying committee we only half know.

    Engineering, purchasing, operations and finance all weigh in over months, and the CRM shows one contact.

  5. 05

    Parts and service revenue slips away after the sale.

    Machines in the field need parts and service for years, but nobody tracks what is installed where, or when it is due.

What we build.

The ERP stays the system of record. HubSpot becomes the place where quotes, accounts, channels and the installed base meet.

01 / 03

Data model

  • Accounts, dealers and territories

    End customers, dealers and distributors as companies in a parent-child hierarchy, each assigned to a territory and the rep or dealer who covers it.

  • Quotes with a buying committee

    RFQ to quote to order on the deal, with line items from the ERP's products and price lists, each revision kept, and every stakeholder associated by role.

  • Installed base

    Each machine or assembly shipped as its own record: serial number, model, ship date, site, warranty end and service history. On Enterprise this is a custom object.

02 / 03

Integrations

  • ERP product, pricing and order sync

    Products, price lists, orders, shipments and inventory from the ERP into HubSpot on a schedule, with the ERP kept as the system of record.

  • Quote-to-order handoff

    An accepted quote creates the sales order in the ERP; the order number and ship status come back to the deal.

  • Dealer sell-through

    Dealer orders, sell-through reports and warranty registrations matched to the same account hierarchy and installed base.

03 / 03

Agents

  • RFQ intake

    Reads an incoming RFQ and its attachments, creates the deal with the parts, quantities and due date, and routes it to the right estimator for a person to confirm.

  • Aftermarket watch

    Flags installed machines due for service or wear parts, and accounts whose parts reorders are running late against their usual cadence.

  • Buying-committee check

    Compares a long deal's associated contacts with the roles it needs, using logged emails and meetings, and suggests who is missing.

FIG. 01RFQ-TO-REORDER MODEL07:00 CTSample HubSpot data model for a manufacturer: end customers, dealers and reps, contacts, deals with line items, ERP orders, installed assets and service tickets.

Three workflows we start with.

Each one closes a gap between the front office, the ERP and the field.

  1. Workflow 01

    RFQ to quote

    TriggerAn RFQ arrives in the sales inbox

    1. Create the deal with the customer, parts, quantities and due date
    2. Pull current pricing and lead times from the ERP
    3. Route it to the estimator for that product line
    4. Track the quote revision and its expiry on the deal

    ResultEvery RFQ tracked from the minute it arrives, and nothing priced from a stale list.

  2. Workflow 02

    Won quote to ERP order

    TriggerDeal moves to Closed Won

    1. Check the quote revision, terms and ship-to address
    2. Create the sales order in the ERP
    3. Write the order number back to the deal
    4. Update the deal as the ERP reports ship status

    ResultNo retyping between sales and the plant.

  3. Workflow 03

    Aftermarket follow-up

    TriggerAn installed asset reaches its service interval

    1. Find the asset's site, owner and servicing dealer
    2. Draft a parts and service offer from its history
    3. Route it to the dealer or the direct rep for approval
    4. Log the outcome on the asset

    ResultParts and service worked on schedule, not when the machine breaks.

Blueprint

How we build it.

A blueprint for a manufacturer's portal, assembled from components that already run in production.

  • Scheduled loads that are proved against live data before they publish
  • Verified webhooks and idempotent writes, so a retry never duplicates a record
  • Merge plans reviewed before anything merges
  • Agents and workflow actions that work from the record, with a person approving what matters
Read how those components were built in the field notes.Read the field notes

Figures show illustrative sample data. Names, companies and values in them are invented.

Show us the quote that got lost.

And the ERP screen your reps keep asking about. We'll sketch the system that connects them.