Skip to main content

Guide: Use Hermes for Sales Research with Persistent Memory

· 5 min read
Ben Bartholomew
Ben Bartholomew
Hindsight Team

Guide: Use Hermes for Sales Research with Persistent Memory

If you want Hermes for sales research, persistent memory is what makes it useful after the first session. Without memory, every account brief starts from zero. With Hindsight, Hermes can retain account facts, stakeholder notes, past objections, buying signals, and the decisions you made last time you looked at the deal.

That changes the workflow from “generate one-off research summaries” into “maintain an evolving understanding of the account over time.”

This is the setup pattern that works best: keep one stable bank per account or per account team, use Hermes as the front end, and let Hindsight handle the long-term memory layer underneath.

Quick answer

  1. Connect Hermes to Hindsight.
  2. Pick a bank strategy that matches your sales motion.
  3. Use one bank per account, territory, or rep-owned portfolio.
  4. Let Hermes retain research notes, call prep, objections, and stakeholder context.
  5. Reuse the same bank before every new account touchpoint.

Why memory matters for sales research​

Sales research is not a single prompt problem. It is an accumulation problem.

You learn a little about an account from the website. Then more from a 10-K. Then more from LinkedIn, call notes, and internal handoff messages. The high value context is spread over days or weeks.

Without memory, you either lose that context or keep re-pasting it. With memory, Hermes can carry forward facts like:

  • which teams the buyer cares about
  • what tools the account already uses
  • what objections came up on the last call
  • which initiative or deadline is driving urgency
  • which competitor keeps appearing in the deal

That is exactly the kind of context that gets more valuable every time you talk to the account.

Step 1: Connect Hermes to Hindsight​

The shortest path is the native memory provider:

hermes memory setup

Choose Hindsight as the provider, then decide whether you want Cloud, Local Embedded, or Local External mode.

For sales workflows, Cloud is usually the easiest choice because the same memory bank can follow you across devices and teammates.

Step 2: Pick the right bank strategy​

This is the most important design decision.

For sales, the best default is usually one bank per account.

That keeps account context clean. Your notes about Acme do not bleed into Globex. A simple pattern looks like this:

  • sales-acme
  • sales-globex
  • sales-initech

If one rep owns many related accounts and wants shared context, a portfolio bank can work too. But account-scoped banks are the safer default because they prevent noisy retrieval.

Step 3: Decide what should become memory​

The best sales memories are not raw transcript dumps. They are the durable facts behind the motion.

Good examples:

  • “VP of Operations is the likely champion”
  • “Renewal date is in October”
  • “Security review is the main blocker”
  • “Current stack includes Salesforce, Snowflake, and Zendesk”
  • “Buyer responded well to the compliance angle, not the automation angle”

That is the information you want Hermes to recall before the next account review or prep session.

Step 4: Use Hermes in the highest leverage moments​

Account prep before a call​

Start with:

What do we already know about this account, and what should I ask on today's call?

Hermes can pull forward the stakeholder map, prior objections, and open questions instead of making you rebuild them.

Research between calls​

As you learn new facts from articles, earnings reports, job postings, and product launches, Hermes retains what matters. That makes the next session cumulative instead of repetitive.

Handoffs between teammates​

If multiple reps or sales engineers share the same bank, the next person picks up real context instead of reading a thin CRM summary and guessing what matters.

Step 5: Verify recall is helping, not hurting​

A memory setup is only good if retrieval stays sharp.

A fast way to test it:

  1. Store a few real account facts across two or three sessions.
  2. Start a fresh session.
  3. Ask Hermes what it remembers about the account's stakeholders, timing, and blockers.
  4. Check whether the answer is specific and relevant.

If recall feels noisy, the usual fix is to make the bank narrower. One bank per account is almost always cleaner than one giant bank for the whole pipeline.

What this workflow is good at​

Hermes + Hindsight works especially well for:

  • account research that compounds over time
  • multi-touch outreach and follow-up
  • multi-person deal teams
  • technical sales where product fit details matter across calls
  • founder-led sales where the same person runs discovery, follow-up, and proposal work

It is much less valuable for one-off lead enrichment where you never revisit the account.

Common mistakes​

  • One giant sales bank for everything — retrieval gets noisy fast
  • Saving raw notes but not clear decisions — the durable facts matter more than the transcript itself
  • Changing bank names constantly — continuity depends on stable bank IDs
  • Expecting memory to replace your CRM — memory helps the agent think with context; it does not replace system-of-record tooling

FAQ​

Should I use one bank per rep or per account?​

Per account is the safer default. Use per-rep only when shared portfolio context matters more than precision.

Can a sales engineer and AE share the same bank?​

Yes. That is one of the strongest use cases.

Does this replace Salesforce or HubSpot?​

No. It complements them by giving Hermes a working memory layer during research and prep.

Next Steps​