Hourglass Content Intelligence
← All conversations

Conversation

23 Oct 2026, 11:53 UTC · 3 questions · ID 0f2012595209
Who asked
Industry
Financial services
Pages visited (17)
  1. /
  2. /chat-response
  3. /chat-response
  4. /chat-response
  5. /chat-response
  6. /chat-response
  7. /chat-response
  8. /
  9. /chat-response
  10. /
  11. /chat-response
  12. /chat-response
  13. /chat-response
  14. /chat-response
  15. /chat-response
  16. /Questions 1 and 2 asked here
  17. /chat-responseQuestion 3 asked here
Question 1

“We're a brokerage and wealth management firm. I am CIO”

Answer
Partly answered

The financial services page covers approval steps, an audit trail and agents for banks, credit unions and insurers, and /security lists SSO, encryption and data region choice. Nothing addresses brokerage or wealth management firms, there are no customer stories from them, and no compliance certifications are named for an IT review.

Section on the siteStatusTicket
/solutions/financial-servicesBuilt for regulated teamsPartly answers it
Add brokerage and wealth management use cases to /solutions/financial-services

Ticket

Paste this into your ticketing tool.

Add brokerage and wealth management use cases to /solutions/financial-services

Who needs it: Brokerage and wealth management firms (this visitor: CIO)
Section: /solutions/financial-services › Built for regulated teams

What is missing:
- Brokerage and wealth management firms are never named; the page speaks only to banks, credit unions and insurers.
- No use cases for advisors, client households or portfolio reviews.
- No mention of whether Hourglass connects to the account, custody or trading systems these firms run.

Where: Update this section: add a third card beside "Approvals where you need them" and "The service members expect".
  Related sections: Know every member and client, and keep every message compliant · Your data, connected and under control

What to do:
1. Confirm with product which brokerage and wealth management use cases and source systems Hourglass supports.
2. Write the card covering advisor and client relationship work, the review steps it relies on and the systems it connects to.
3. Extend the banner intro so it names brokerages and wealth managers alongside banks, credit unions and insurers.

Done when: /solutions/financial-services names brokerage and wealth management firms and shows how advisors and their systems work in Hourglass.

From: conversation 0f2012595209, question 1: "We're a brokerage and wealth management firm. I am CIO"
Who needs it: Brokerage and wealth management firms (this visitor: CIO)
What is missing
  • Brokerage and wealth management firms are never named; the page speaks only to banks, credit unions and insurers.
  • No use cases for advisors, client households or portfolio reviews.
  • No mention of whether Hourglass connects to the account, custody or trading systems these firms run.
Where
Update this section: add a third card beside "Approvals where you need them" and "The service members expect".
Related sections
Know every member and client, and keep every message compliant · Your data, connected and under control
What to do
  1. Confirm with product which brokerage and wealth management use cases and source systems Hourglass supports.
  2. Write the card covering advisor and client relationship work, the review steps it relies on and the systems it connects to.
  3. Extend the banner intro so it names brokerages and wealth managers alongside banks, credit unions and insurers.
Done when: /solutions/financial-services names brokerage and wealth management firms and shows how advisors and their systems work in Hourglass.
/solutions/financial-servicesHow banks, credit unions and insurers grow with HourglassMissing here
Add a brokerage or wealth management customer story to /solutions/financial-services

Ticket

Paste this into your ticketing tool.

Add a brokerage or wealth management customer story to /solutions/financial-services

Who needs it: Brokerage and wealth management firms (this visitor: CIO)
Section: /solutions/financial-services › How banks, credit unions and insurers grow with Hourglass

What is missing:
- No customer story from a brokerage or wealth management firm; stories cover two banks and an insurer only.

Where: Update this section: add a fourth story beside "Mercantile Bank", "Allica Bank" and "Alacrity Solutions".

What to do:
1. Confirm with customer marketing whether a brokerage or wealth management customer can be featured.
2. Add the story with a quote and two results, matching the format of the existing stories.

Done when: The financial services stories slider includes a brokerage or wealth management customer with its results.

From: conversation 0f2012595209, question 1: "We're a brokerage and wealth management firm. I am CIO"
Who needs it: Brokerage and wealth management firms (this visitor: CIO)
What is missing
  • No customer story from a brokerage or wealth management firm; stories cover two banks and an insurer only.
Where
Update this section: add a fourth story beside "Mercantile Bank", "Allica Bank" and "Alacrity Solutions".
What to do
  1. Confirm with customer marketing whether a brokerage or wealth management customer can be featured.
  2. Add the story with a quote and two results, matching the format of the existing stories.
Done when: The financial services stories slider includes a brokerage or wealth management customer with its results.
/securitySecurity and control, built into every hubPartly answers it
Add a compliance certifications section to /security

Ticket

Paste this into your ticketing tool.

Add a compliance certifications section to /security

Who needs it: CTOs and IT or security reviewers checking a vendor
Section: /security › Security and control, built into every hub

What is missing:
- No compliance certifications or audit reports are named.
- No explanation of how a reviewer requests security documentation.
- Financial services regulations Hourglass supports are not mentioned.

Where: New section on /security, placed after "Security and control, built into every hub".
  Related sections: Security and control, built into every hub · Agents that ask. People who decide.
  Main topics: certifications held · audit reports and how to request them · financial services regulations supported · security review documentation

What to do:
1. Confirm with the security and compliance teams which certifications Hourglass holds and which reports can be shared.
2. Add the section listing each certification and the request route for its report.
3. Link to the new section from the financial services page.

Done when: /security names each certification and how to request its report.

From: conversation 0f2012595209, question 1: "We're a brokerage and wealth management firm. I am CIO"
Who needs it: CTOs and IT or security reviewers checking a vendor
What is missing
  • No compliance certifications or audit reports are named.
  • No explanation of how a reviewer requests security documentation.
  • Financial services regulations Hourglass supports are not mentioned.
Where
New section on /security, placed after "Security and control, built into every hub".
Related sections
Security and control, built into every hub · Agents that ask. People who decide.
Main topics
certifications held · audit reports and how to request them · financial services regulations supported · security review documentation
What to do
  1. Confirm with the security and compliance teams which certifications Hourglass holds and which reports can be shared.
  2. Add the section listing each certification and the request route for its report.
  3. Link to the new section from the financial services page.
Done when: /security names each certification and how to request its report.
Answer full page
Here is how Hourglass fits a regulated financial firm, seen through an IT lens. It covers bringing client accounts, conversations and campaigns onto one record with approval steps and an audit trail, the security controls your team will ask about first, and agents that work inside the permissions you set.
Open the answer page ↗
Sections in the answer pageStatus
/solutions/financial-servicesKnow every member and client, and keep every message compliantAnswers it
/solutions/financial-servicesAgents that work alongside every teamAnswers it
/solutions/financial-servicesBuilt for regulated teamsPartly answers it
/securitySecurity and control, built into every hubPartly answers it
/solutions/financial-servicesHow banks, credit unions and insurers grow with HourglassMissing here
Question 2

“Our business wants to use AI on customer data, but compliance keeps saying no. What are other companies doing?”

Answer
Partly answered

The site covers the controls that let agents work on customer data under oversight, and illustrative bank and insurer stories show compliance signing off agent-drafted messages. Nothing describes how companies won their compliance team's approval to use AI on customer data, and the Run AI agents safely page has no customer stories about it.

Section on the siteStatusTicket
/solutions/govern-aiRemarkable results, in every industryMissing here
Add stories of compliance teams approving AI agents to /solutions/govern-ai

Ticket

Paste this into your ticketing tool.

Add stories of compliance teams approving AI agents to /solutions/govern-ai

Who needs it: Regulated firms whose compliance teams review AI use (this visitor: CIO at a brokerage and wealth management firm)
Section: /solutions/govern-ai › Remarkable results, in every industry

What is missing:
- No customer story describes how a compliance team was brought to approve AI on customer data.
- No story shows which controls a regulated customer started with and how it widened agent permissions over time.
- The stories on this page are about cross-sell, campaigns and quotes, not AI governance.

Where: New section on /solutions/govern-ai, placed after "Agents that earn trust over time".
  Related sections: Four controls for every agent · Agents that earn trust over time · How banks, credit unions and insurers grow with Hourglass
  Main topics: Compliance objections raised before rollout · Controls agreed with compliance · First narrow use case · How permissions widened over time · Audit log use in compliance reviews · Outcome figures

What to do:
1. Confirm with customer marketing which customers can describe their compliance review of agents, and in which regulated industries.
2. Add story cards covering the starting controls, the review process and results, with financial services first.
3. Link the section to the financial services page and to the security page.

Done when: /solutions/govern-ai shows customer stories that explain how a compliance team approved agents on customer data and which controls it required.

From: conversation 0f2012595209, question 2: "Our business wants to use AI on customer data, but compliance keeps saying no. What are other companies doing?"
Who needs it: Regulated firms whose compliance teams review AI use (this visitor: CIO at a brokerage and wealth management firm)
What is missing
  • No customer story describes how a compliance team was brought to approve AI on customer data.
  • No story shows which controls a regulated customer started with and how it widened agent permissions over time.
  • The stories on this page are about cross-sell, campaigns and quotes, not AI governance.
Where
New section on /solutions/govern-ai, placed after "Agents that earn trust over time".
Related sections
Four controls for every agent · Agents that earn trust over time · How banks, credit unions and insurers grow with Hourglass
Main topics
Compliance objections raised before rollout · Controls agreed with compliance · First narrow use case · How permissions widened over time · Audit log use in compliance reviews · Outcome figures
What to do
  1. Confirm with customer marketing which customers can describe their compliance review of agents, and in which regulated industries.
  2. Add story cards covering the starting controls, the review process and results, with financial services first.
  3. Link the section to the financial services page and to the security page.
Done when: /solutions/govern-ai shows customer stories that explain how a compliance team approved agents on customer data and which controls it required.
Answer full page
This page shows how banks, credit unions and insurers such as Mercantile Bank, Allica Bank and Alacrity Solutions use Hourglass, in illustrative stories. It also covers the controls that tend to win compliance over: you decide what each agent can read and do, require approval where it matters, review every action and pause any agent.
Open the answer page ↗
Sections in the answer pageStatus
/solutions/govern-aiFour controls for every agentAnswers it
/solutions/govern-aiAgents that earn trust over timeAnswers it
/solutions/financial-servicesBuilt for regulated teamsAnswers it
/solutions/financial-servicesHow banks, credit unions and insurers grow with HourglassAnswers it
/solutions/govern-aiRemarkable results, in every industryMissing here
Question 3

“Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?”

Answer
Partly answered

The site explains building one customer record from existing systems with two-way syncs, without custom code or ripping systems out. It never shows a customer, financial or otherwise, that kept its sales and marketing systems and synced them, and never names which of those systems Data Hub connects to.

Section on the siteStatusTicket
/solutions/unify-customer-dataWhat one record changesMissing here
Add stories of unifying data without replacing systems to /solutions/unify-customer-data

Ticket

Paste this into your ticketing tool.

Add stories of unifying data without replacing systems to /solutions/unify-customer-data

Section: /solutions/unify-customer-data › What one record changes

What is missing:
- No customer story shows a company that kept its existing sales and marketing systems and synced them into one record.
- The stories on this page describe tools retired or replaced, not systems kept and connected.

Where: New section on /solutions/unify-customer-data, placed after "What one record changes".
  Related sections: Four steps to one trusted customer record · Remarkable results, in every industry · Keeping what you built
  Main topics: which systems each customer kept · how the syncs were set up · time to one view · results after unifying · a regulated firm example

What to do:
1. Confirm with the customer marketing team which customers synced existing sales and marketing systems rather than replacing them.
2. Add two or three short stories with the systems kept and the results, including at least one financial services firm.

Done when: /solutions/unify-customer-data shows customer stories that name the systems kept and synced into one record.

From: conversation 0f2012595209, question 3: "Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?"
What is missing
  • No customer story shows a company that kept its existing sales and marketing systems and synced them into one record.
  • The stories on this page describe tools retired or replaced, not systems kept and connected.
Where
New section on /solutions/unify-customer-data, placed after "What one record changes".
Related sections
Four steps to one trusted customer record · Remarkable results, in every industry · Keeping what you built
Main topics
which systems each customer kept · how the syncs were set up · time to one view · results after unifying · a regulated firm example
What to do
  1. Confirm with the customer marketing team which customers synced existing sales and marketing systems rather than replacing them.
  2. Add two or three short stories with the systems kept and the results, including at least one financial services firm.
Done when: /solutions/unify-customer-data shows customer stories that name the systems kept and synced into one record.
/solutions/financial-servicesMercantile Bank (card)Partly answers it
Show which systems were kept and synced in the Mercantile Bank story on /solutions/financial-services

Ticket

Paste this into your ticketing tool.

Show which systems were kept and synced in the Mercantile Bank story on /solutions/financial-services

Who needs it: Financial services (banks, brokerages, wealth managers and insurers)
Section: /solutions/financial-services › Mercantile Bank (card)

What is missing:
- The story mentions four systems but never says whether they were kept and synced or replaced.
- No financial services story shows sales and marketing data unified while existing systems stay in place.

Where: Update this section: in the "Mercantile Bank" card, beside the quote about switching between four systems.
  Related sections: Four steps to one trusted customer record

What to do:
1. Confirm with the customer marketing team which of the bank's systems stayed in place and were synced.
2. Add a line and a metric to the card naming the systems kept and what one view changed.

Done when: The Mercantile Bank card on /solutions/financial-services states which systems were kept and connected to Hourglass.

From: conversation 0f2012595209, question 3: "Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?"
Who needs it: Financial services (banks, brokerages, wealth managers and insurers)
What is missing
  • The story mentions four systems but never says whether they were kept and synced or replaced.
  • No financial services story shows sales and marketing data unified while existing systems stay in place.
Where
Update this section: in the "Mercantile Bank" card, beside the quote about switching between four systems.
Related sections
Four steps to one trusted customer record
What to do
  1. Confirm with the customer marketing team which of the bank's systems stayed in place and were synced.
  2. Add a line and a metric to the card naming the systems kept and what one view changed.
Done when: The Mercantile Bank card on /solutions/financial-services states which systems were kept and connected to Hourglass.
/products/dataTwo-way syncs, without custom code (card)Partly answers it
Name the sales and marketing systems Data Hub syncs with on /products/data

Ticket

Paste this into your ticketing tool.

Name the sales and marketing systems Data Hub syncs with on /products/data

Who needs it: CTOs and IT or data teams planning integrations
Section: /products/data › Two-way syncs, without custom code (card)

What is missing:
- Ready-made syncs are listed only for warehouses, ERPs and billing tools; sales and marketing systems such as existing CRMs or email tools are not named.
- The site never says which existing sales and marketing systems can stay in place alongside Hourglass.

Where: Update this section: add a line to the "Two-way syncs, without custom code" card after "Ready-made syncs for warehouses, ERPs and billing".
  Related sections: The tools in Data Hub

What to do:
1. Confirm with product and engineering which sales and marketing systems have ready-made two-way syncs.
2. Add those system types or names to the card and link to the app marketplace.

Done when: /products/data names the sales and marketing systems Data Hub can sync with.

From: conversation 0f2012595209, question 3: "Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?"
Who needs it: CTOs and IT or data teams planning integrations
What is missing
  • Ready-made syncs are listed only for warehouses, ERPs and billing tools; sales and marketing systems such as existing CRMs or email tools are not named.
  • The site never says which existing sales and marketing systems can stay in place alongside Hourglass.
Where
Update this section: add a line to the "Two-way syncs, without custom code" card after "Ready-made syncs for warehouses, ERPs and billing".
Related sections
The tools in Data Hub
What to do
  1. Confirm with product and engineering which sales and marketing systems have ready-made two-way syncs.
  2. Add those system types or names to the card and link to the app marketplace.
Done when: /products/data names the sales and marketing systems Data Hub can sync with.
Answer full page
This page shows how teams build one customer record from the systems they already run. Data Hub syncs those systems both ways without custom code, so nothing has to be ripped out. It keeps the banks, credit unions and insurers stories so you can see how regulated firms like yours work this way.
Open the answer page ↗
Sections in the answer pageStatus
/solutions/unify-customer-dataOne record for each customer, built from every system you runAnswers it
/solutions/unify-customer-dataFour steps to one trusted customer recordAnswers it
/compare/build-your-ownKeeping what you builtAnswers it
/solutions/financial-servicesMercantile Bank (card)Partly answers it
/products/dataTwo-way syncs, without custom code (card)Partly answers it
/solutions/unify-customer-dataWhat one record changesMissing here

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 23 Oct 2026.