23 Oct 2026, 16:26 UTC · 2 questions · ID e4cbeaec3d17
Who asked
Persona
CMO (Chief Marketing Officer)
Company
Whirlpool Corporation
Industry
Manufacturing
Pages visited (2)
/Question 1 asked here
/chat-responseQuestion 2 asked here
Question 1
“If we move our brands onto Hourglass, what happens to our SAP and product-registration data, and can my team still personalize from it?”
Answer
Partly answered
The site covers two-way syncs from ERPs into the Smart CRM, custom objects for products and segments built from any field on the record. It never names SAP as a supported ERP and never mentions product-registration data or using it to personalize marketing across brands.
Add product-registration marketing to /solutions/manufacturing
Who needs it: Manufacturing (this visitor: Whirlpool Corporation)
What is missing
Product-registration data is not mentioned.
Nothing explains how marketing personalizes campaigns from ERP or registration data across brands.
Where
Update this section: add a third card beside "Quotes from your real price lists" and "Service history on every ticket".
Related sections
Segments that update themselves · Two-way syncs, without custom code · Custom objects
What to do
Confirm with product how product registrations are stored (custom objects or synced data) and used in segments.
Add a card covering registration data on the account and segments built from it for each brand, linking to Data Hub and Marketing Hub.
Done when: /solutions/manufacturing explains where product-registration data lives and how marketing segments from it across brands.
Answer full page
Your ERP data stays where it is: Data Hub syncs systems like your ERP into the Smart CRM with two-way syncs, and custom objects let you model records that don't fit standard fields, such as product registrations. Marketing Hub then builds segments that update themselves from that record, so your team can personalize campaigns across every brand. The index doesn't name SAP or product registrations specifically, so we can confirm those details for your setup.
“If I ask our CFO to fund consolidating every brand onto one platform, what will they push back on, and what's my best answer?”
Answer
Partly answered
The site makes the qualitative case: one price instead of several subscriptions, fewer logins and bills, a phased move that avoids the usual migration failures, multi-brand support, and stories like Eventus replacing seven tools. It never quantifies cost savings, total cost of ownership or payback, and never says what Enterprise pricing for many brands looks like.
Add cost-savings and payback evidence to the Cost row on /compare/point-tools
Who needs it: Leaders building a consolidation business case for finance
What is missing
No figures for what consolidating separate tools saves in subscriptions, admin time or integration upkeep.
No payback period or total cost of ownership comparison is given.
Where
Update this section: Expand the "Cost" row, which today reads "One price that grows with you" against "Several subscriptions that grow separately", and the line under the table.
Related sections
Bringing your tools together · Teams that made the switch
What to do
Confirm with the revenue team which savings and payback figures, from customers or modelled, can be published.
Add the confirmed savings and payback detail to the Cost row and link it to the customer stories that back it.
Done when: /compare/point-tools states what consolidating tools typically saves and how long payback takes.
Add a multi-brand consolidation business case section to /solutions/enterprise
Who needs it: Marketing leaders building a business case for finance (this visitor: CMO, Whirlpool Corporation)
What is missing
No business case for moving many brands onto one platform: cost compared with today's tools, payback and risk.
No guidance on the questions finance teams raise about consolidation and how Hourglass answers them.
Where
New section on /solutions/enterprise, placed after "Built to run across the whole organization".
Related sections
Many teams, one platform · A rollout planned with you · Why software projects stall, and how a planned move avoids it · One platform or a stack of tools
Main topics
Cost compared with separate tools per brand · Payback timeline · Risk of a phased rollout · Proof from multi-brand customers · Help building a business case
What to do
Confirm with the revenue team and product which cost, payback and business-case support Hourglass can state.
Add the section and link it to the point-tools comparison and the migration risks section on /solutions/switch-crm.
Done when: /solutions/enterprise has a section answering the cost, payback and risk questions finance asks about consolidating brands. Depends on: “Add cost-savings and payback evidence to the Cost row on /compare/point-tools”
Explain how multi-brand pricing is built on the Enterprise card on /pricing
Who needs it: Organizations with many brands or business units
What is missing
The Enterprise card says only "Priced for your organization", with no indication of how many brands, regions and seats are priced.
No payback or cost-comparison detail on the pricing page.
Where
Update this section: Add a line to the "Enterprise" card beside "Many brands, regions and business units".
What to do
Confirm with the revenue team how Enterprise pricing is structured for many brands and what can be published.
Add the pricing basis and a link to the consolidation business case on the card.
Done when: The Enterprise card on /pricing explains what multi-brand pricing is based on.
Answer full page
A CFO will likely ask what consolidation costs, whether the move puts the business at risk, and who has done it before. This page answers each in turn: the cost and admin case against separate tools, what the plans include, how a planned, phased rollout avoids the usual failure points, and teams like Suzuki that switched one team at a time. Your strongest answer is to bring the tools you pay for today, and our team will build the business case with you.