22 Oct 2026, 06:58 UTC · 1 question · ID 1c5e6bd9968b
Who asked
Industry
Manufacturing
Pages visited (40)
/chat-response
/
/chat-response
/chat-response
/chat-response
/chat-response
/
/contact
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/chat-response
/chat-response
/products/marketing
/
/products/marketing
/products/salesQuestion 1 asked here
Question 1
“I'm the CTO at a manufacturer. How does Hourglass handle our data?”
Answer
Partly answered
The site covers syncing ERP, warehouse and billing data into one record, field-level permissions, change history, single sign-on, encryption in transit and at rest, and a choice of data region. It never lists the storage regions, names any compliance certifications, says what happens to data when a customer leaves, names the ERP systems it syncs with or addresses data handling on the manufacturing
Add certifications, storage regions and data ownership to /security
Who needs it: CTOs and IT or security reviewers checking a vendor
What is missing
No compliance certifications or audit reports are named.
The "Data region choice" card does not list which storage regions are offered.
Nothing says who owns customer data or how it is exported or deleted when a customer leaves.
Where
Update this section: Expand the "Data region choice" card and add cards beside "Encryption" and "Audit history" for certifications and data ownership.
What to do
Confirm with the security and compliance teams which certifications Hourglass holds, which storage regions it offers and its data export and deletion policy.
Add the region list to the "Data region choice" card.
Add cards for certifications with how to request reports, and for data ownership, export and deletion on leaving.
Done when: /security names each storage region, each certification and what happens to customer data when a customer leaves.
Name supported ERP and warehouse systems on /platform
Who needs it: IT and data teams setting up syncs
What is missing
The ERP systems Data Hub syncs with are not named.
The data warehouses supported are not named.
Where
Update this section: add a line listing supported systems under "Two-way syncs with the systems you run" in the "Bring every source into one record" card.
Related sections
The tools in Data Hub
What to do
Confirm with engineering which ERP systems and data warehouses have ready-made two-way syncs.
Add the named systems to the card, grouped by ERP, warehouse and billing.
Done when: /platform names the ERP systems and data warehouses Data Hub syncs with.
Add a data and security section to /solutions/manufacturing
Who needs it: Manufacturing CTOs and IT leaders
What is missing
The manufacturing page says nothing about how customer and ERP data is synced, protected or controlled.
No security or compliance information appears for manufacturing buyers.
Where
New section on /solutions/manufacturing, placed after "Built for complex products and long relationships".
Related sections
Quotes from your real price lists · Security and control, built into every hub · Your data, connected and under control
Main topics
ERP and pricing data sync · field-level permissions for distributors and reps · encryption and storage regions · certifications · links to /security and /platform
What to do
Summarise ERP sync, distributor access controls and encryption for manufacturers, drawing on /platform and /security.
Add links to /security and /platform from the new section.
Done when: /solutions/manufacturing has a section on how data is synced and protected, linking to /security and /platform. Depends on: “Add certifications, storage regions and data ownership to /security”
Answer full page
Here's how Hourglass handles your data: Data Hub syncs your warehouse, ERP and billing tools into one customer record, with field-level permissions and a history of every change. It also covers the security controls your IT team will ask about, and how agents only read what you allow.