Salency
Memory

The memory layer, in detail.

Three calls indexed for Hudson Terrace Capital. Click any card for the transcript snippet.

Hudson Terrace Capital · live memory3 calls indexed
Memory compounds with every call
How it stays anchored

Every signal points back at a line.

The brief above isn’t conjured. Every claim resolves to a transcript line, with the cite-link visible. Below, one Hudson Terrace call with extracted signals shown beside the source.

Transcript · call-001 · Mar 09 · Discovery
3 signals extracted
Raw transcript

[00:01:24] Maya Chen: When you say ceiling, what specifically?

[00:01:28] Daniel Voss: Two things. First, latency. We're seeing three to five seconds of settlement delay on our internal transfers, and that's killing us during volatility windows.

Last week during the ETH move we had a trader locked out of a fill because our margin didn't settle fast enough. That's six figures of P&L on one trade.

[00:01:52] Maya Chen: That's painful. What's the trader's reaction when that happens?

[00:01:56] Daniel Voss: They yell at me. Not joking.

Our head trader has literally said, in a Monday morning standup, “if I miss one more fill because of settlement, I’m going to lose my mind.”

Extracted signals
Pain

“3 to 5 second settlement delays, killing us during volatility windows.”

cited at 00:01:28 · conf 0.96

Pain → product

Atlas Settlement · sub-second settlement

resolves 00:01:28 · primary · conf 0.94

Stakeholder

Daniel Voss · COO · champion

inferred from 00:01:56 + 7 other lines

What’s stored

Seven signal types, cited.

Every call extracts a typed payload. Same 7 shapes, every account, every successor. Below, each type with one Hudson Terrace example.

Pain
7 across 3 calls
A customer-stated problem the rep should remember. Verbatim quote, speaker, citation, urgency-ranked.
speakerDaniel Voss · COO
text“3 to 5 second settlement delays, killing us during volatility windows.”
confidence0.96
Objection
2 across 3 calls
A stated blocker or buying friction. Tracked separately from pain so closing logic can route them.
text“MAS-recognized infra vendors by Q4.”
callMar 23 · Technical · 00:07:07
blockingtrue
Contradiction
1 across 3 calls
When a buyer's stated position shifts between calls. Both citations preserved so the rep sees the delta, not the overwrite.
topicLatency: blocker → resolved workaround
from“killing us during volatility” · Mar 09
to“gotten used to it” · Apr 06
Commitment
3 open
Something we owe the customer. Owner, due date, status. Closes when delivered.
itemSOC 2 Type II report
ownerMaya
statusopen
Stakeholder
3 mapped
Who's in the room and where they sit. Stance is inferred from quote patterns across calls.
nameDaniel Voss
titleCOO
stancechampion
Product match
5 ranked
A pain ranked against your catalog. Confidence-scored, role-tagged primary or secondary.
pain3-5s settlement delays
productAtlas Settlement
confidence0.94
Change delta
2 detected
A non-contradiction shift. Cadence change, scope change, owner change. Same anchor pair, different topic.
topicSOC 2 cadence: annual → quarterly
fromMar 09 · Discovery
toApr 06 · Pricing
Not another CRM field

Memory is a graph with time. CRMs store flat rows.

SignalIn your CRMIn Salency
Customer painFree-text field, last writer winsCited quote, speaker, timestamp, ranked by confidence
Contradiction between callsInvisible. Fields overwrite silentlyFlagged with both source citations
Pain → product fitOne value per field, no rankingConfidence-ranked, top-N per pain
Pattern across accountsCSV export to a spreadsheetSearch “settlement delay”, every account that flagged it surfaces

Flatten the graph and you kill the thing. Read our memory thesis →

Pilot cohort · Spring 2026

Inherit every account’s memory from Day 1.

First account memory stands up in a week. By month two, the rep inheriting it reads the story, not a notes field.