23 Oct 2026, 11:47 UTC · 6 questions · ID ac74d07caf58
Who asked
Profile
We don’t have a profile for this visitor.
Pages visited (14)
/
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/Question 1 asked here
/chat-response
/chat-response
/chat-response
/chat-responseQuestions 2, 3, 4, 5 and 6 asked here
Question 1
“We pay for too many sales and marketing tools that don't talk to each other. Where do I start?”
Answer
✓Answered well
The point-tools comparison page explains how one platform and one record replace a stack of disconnected tools. It also says to start with the tools that cause the most handoffs, usually email and the CRM, and connect the rest while moving. A customer story shows seven tools replaced in five weeks.
Answer full page
This page shows how Hourglass replaces a stack of separate tools with one platform and one customer record. It compares the two side by side and explains where to start: with the tools that cause the most handoffs, usually email and the CRM, then connecting the rest as you move.
“I'm the CFO of a global appliance manufacturer with several consumer brands”
Answer
Partly answered
The manufacturing page covers marketing every brand and quoting from ERP prices, Revenue Hub covers invoices, payments and accounting sync, and the enterprise page covers running many brands on one platform. Nothing speaks to a finance leader: no cost savings from retiring tools, no payback period and no financial results from manufacturing customers.
The Cost row says one price grows with you but gives no example of savings from retiring separate tools.
No link to plan pricing from the cost comparison.
Where
Update this section: Expand the "Cost" row of the comparison table, beside "Admin".
Related sections
Bringing your tools together
What to do
Confirm with the revenue team an illustrative cost comparison that can be published.
Add the comparison and a link to /pricing in the Cost row.
Done when: /compare/point-tools shows an example of the cost difference and links to pricing.
Answer full page
This page now speaks to a finance leader at a multi-brand manufacturer. It shows how one platform replaces your tool stack, including on cost, how quotes come from your real price lists, and how Revenue Hub keeps quotes, invoices and payments synced to accounting.
Manufacturing stories from Suzuki, Konica Minolta and Viessmann show faster quotes, retired legacy systems and fewer repeat visits, and Eventus replaced seven tools. No story reports cost savings from consolidating tools, features a multi-brand manufacturer, or shows Revenue Hub results such as invoicing or payment speed.
Add cost savings figures to the switch stories on /compare/point-tools
Who needs it: CFOs and finance leaders weighing tool consolidation
What is missing
The Eventus story says seven tools were replaced but gives no cost saved.
No story in the section comes from a manufacturer that consolidated sales and marketing tools.
Where
Update this section: add a cost-saved result to the "Eventus" card and a manufacturer story beside "Eventus", "Suzuki" and "Mercantile Bank".
Related sections
One platform or a stack of tools
What to do
Confirm with the customer marketing team the illustrative cost figures each story can show.
Add a cost-saved figure to the Eventus story and a manufacturer consolidation story.
Done when: /compare/point-tools shows at least one story with the cost saved by replacing separate tools, including one from a manufacturer. Depends on: “Expand the Cost row on /compare/point-tools”
Add a Revenue Hub customer story to /products/revenue
Who needs it: Finance teams evaluating quote-to-cash
What is missing
/products/revenue shows no customer story about quotes, invoices, payments or accounting sync results.
Where
New section on /products/revenue, placed after "Quotes checked before they go. Invoices when they’re accepted.".
Related sections
The tools in Revenue Hub · From quote to cash, without leaving the CRM · Remarkable results, in every industry
Main topics
A finance-led customer story · invoice and payment speed · discount approvals · accounting sync · month-end close time
What to do
Confirm with the revenue team and customer marketing which illustrative customer and figures to use.
Add a Customer Results section with one finance-focused story and its results.
Done when: /products/revenue shows a customer story with quote-to-cash results such as faster invoicing or payment.
Answer full page
Your page now includes customer stories from manufacturers and distributors, Suzuki, Konica Minolta and Viessmann, with their results. They sit alongside the tool-stack comparison, Revenue Hub and how Hourglass quotes from your real price lists. The stories are illustrative examples for this demo.
The comparison pages say teams go live in weeks, and the stories give results such as faster quotes and retired legacy systems. The site never states a payback period, a return on investment or how soon customers recover their spend.
Who needs it: CFOs and finance leaders building a business case
What is missing
No typical payback period or time to return is given.
No return on investment figures or method for estimating them.
No explanation of which costs a customer usually saves, such as retired tools or subscriptions.
Where
New section on /pricing, placed after "Pick the plan that fits today".
Related sections
Pick the plan that fits today · What every plan includes · Moving from your current CRM
Main topics
Typical payback period · Where the return comes from (retired tools, faster quotes, less admin) · How to get an estimate for your own business · Link to customer stories with results
What to do
Confirm with the revenue team which payback and return figures Hourglass can publish and how they were measured.
Add the section with the confirmed figures and the sources of savings, linking to customer stories and the contact page for a tailored estimate.
Done when: /pricing states a typical payback period or return and explains how a buyer can get an estimate for their business.
Add time to payback to the manufacturing stories on /solutions/manufacturing
Who needs it: Manufacturing (this visitor: CFO at a global multi-brand appliance manufacturer)
What is missing
The Suzuki, Konica Minolta and Viessmann stories give operational results but not how long until the investment paid back.
No story states time from kickoff to go-live or to first measurable return.
Where
Update this section: add a payback or time-to-return metric to the "Suzuki", "Konica Minolta" and "Viessmann" cards beside their existing results.
What to do
Confirm with the customer marketing team which payback or time-to-return figures each manufacturing story can show.
Add one time-based return metric to each story card alongside the existing results.
Done when: Each manufacturing story on /solutions/manufacturing shows how long it took to see a return. Depends on: “Add finance outcomes to the manufacturing stories on /solutions/manufacturing”
Answer full page
I don't have figures on how quickly customers see a return, so I can't promise a payback period. What I can say is that teams typically move their CRM in weeks, team by team, and there are no setup fees. I'm happy to put you in touch with the team to talk through a return estimate for your brands.
The site shows how a switch is de-risked: a planned move, a test import, team-by-team go-lives, history kept and an onboarding team. It never names the common reasons CRM projects fail, such as low adoption, poor data or scope creep, or how a multi-brand manufacturer's rollout avoids them.
Add common CRM project failure causes to /solutions/switch-crm
What is missing
The common reasons CRM projects fail, such as low user adoption, poor data quality, scope creep or a big-bang go-live, are not named.
How each step of the migration playbook addresses each of those risks is not explained.
Where
Update this section: Expand the "What your data team notices" card, which so far only names the fear of losing history, to cover the other common failure points.
Related sections
Four steps to a calm switch
What to do
Confirm with the onboarding team which failure causes they see most often in CRM moves.
Add each cause to the card and pair it with the playbook step that addresses it.
Done when: /solutions/switch-crm names the common reasons CRM projects fail and how Hourglass's migration approach addresses each one.
Add a rollout risks section to /solutions/manufacturing
Who needs it: Manufacturing (this visitor: CFO at a multi-brand appliance manufacturer)
What is missing
The manufacturing page has no content on rolling out across several brands, dealers and an ERP, or on the risks that derail such projects.
There is no link from the manufacturing page to the migration playbook.
Where
New section on /solutions/manufacturing, placed after "Built for complex products and long relationships".
Related sections
How manufacturers keep sales, service and partners in step · Four steps to a calm switch · A rollout planned with you
Main topics
Rollout across brands and business units · ERP and price list connection risks · Dealer and distributor adoption · Phased go-lives · Link to the migration playbook
What to do
Confirm with the onboarding team the typical rollout risks for multi-brand manufacturers and how they are handled.
Draft the section and link it to /solutions/switch-crm.
Done when: /solutions/manufacturing has a section on multi-brand rollout risks that links to the migration playbook. Depends on: “Add common CRM project failure causes to /solutions/switch-crm”
Answer full page
I don't have data on why CRM projects fail, but your page now shows how Hourglass lowers the usual risks of a switch. You'll find a planned move with a test import, go-lives one team at a time with history kept, and advice on retiring the tools that cause the most handoffs first. Your manufacturing stories, Revenue Hub and the tool-stack comparison are still here.
The manufacturing page has a short Suzuki story with a quote and two results, and /customers repeats it in a slider. There is no full case study to open, with the starting situation, the rollout and the outcomes in detail.
Link the Suzuki story on /solutions/manufacturing to its full case study
Who needs it: Manufacturing (manufacturers selling through dealers and distributors)
What is missing
The Suzuki card has a quote and two figures, with no link to a full case study.
The card does not say which hubs Suzuki uses or how its rollout went.
Where
Update this section: the "Suzuki" card, beside "Konica Minolta" and "Viessmann".
Related sections
Quotes from your real price lists
What to do
Add a link from the Suzuki card to its full case study page.
Add a line on the card naming the hubs Suzuki uses.
Done when: The Suzuki card on /solutions/manufacturing links to a full case study and names the hubs used. Depends on: “Add full case study pages to /customers”
No customer story has its own page with the challenge, the rollout and the results in detail.
Visitors cannot jump from /customers to a single full case study.
Where
New section on /customers, placed after "Remarkable results, in every industry".
Related sections
Remarkable results, in every industry · TRUSTED BY TEAMS IN BANKING, RETAIL, MANUFACTURING AND SOFTWARE
Main topics
one card per full case study · industry and size of each customer · the challenge before Hourglass · hubs and agents used · rollout timeline · results
What to do
Confirm with the customer marketing team which stories can be written up in full, starting with Suzuki.
Write a full case study page for each story.
Add a section to /customers with a card linking to each case study, labelled by industry.
Done when: /customers lists full case studies by industry, and each card opens its own case study page.
Answer full page
Here is the one manufacturing story that fits best: Suzuki, with its results from keeping sales, service and partners on one account. It's an illustrative story for this demo.