For B2B founders & customer success teams
You sold customers an outcome
Can you prove they got it?
Promises brings your calls and CRM together. Recover what each customer wanted, follow what they have reported since, and see what the evidence supports, and what still needs a conversation.
Start with your existing calls and CRM. Use in Claude or ChatGPT.
The shape of one record
The outcome your customer said they wanted, or the commitment your team made.
Kept as spoken · attributed · dated · linked to its source
Every later report about it, whether progress, setbacks or concerns, from calls, emails and CRM notes.
Customer words and team reports stay distinguishable
What the record supports, what is still unconfirmed, and the next question worth asking.
Fulfillment is a dated human assessment, never inferred
01 · The problem
Closing the deal doesn’t close the question.
The sale records a commercial agreement. Knowing whether you delivered requires something more: the outcome the customer expected, the updates that followed, and a way to compare them.
Across a customer base, memory leaves gaps. Recent conversations get attention. Older commitments and unconfirmed outcomes are harder to see.
You need a way to follow the promise through to the evidence.
02 · Promise
What outcome was expected?
Promises finds the goals customers stated in their recorded conversations, along with targets and timeframes when they were explicitly mentioned. Customer goals and explicit team commitments are kept separate, each with its own dated evidence and conclusion.
03 · Evidence
What has been reported?
Promises brings calls and CRM activity together by customer. Each finding retains its wording, date and source. Customer claims, team commitments and team-written reports remain distinguishable. Missing dates and source links remain missing.
04 · Conclusion
What does the record support?
Your team can confirm or reject a relationship and record a dated assessment with an explanation and supporting evidence. Similarity never verifies fulfillment.
05 · Sources
Connect what your team already records.
One connection per provider per workspace, company-wide credentials only. Credentials go from your browser to Nango's hosted Connect UI and are never stored by us.
Fathom
Paste an API key from Fathom settings. Available on every plan, including free.
Fireflies
Paste an admin API key from Fireflies. Needs a plan with API access.
Granola
Paste an API key from Granola. Business and Enterprise plans only.
Gong
Paste the access key and secret a Gong admin creates in Company settings.
HubSpot
Sign in with a HubSpot user who can install apps on the portal.
Salesforce
Sign in with a Salesforce admin. Read access to accounts, contacts, and opportunities.
A Salesforce admin installs the Promises package in your org once, choosing Install for All Users, before Connect works.
What Promises reads
Calls: title, date, attendees, transcript lines with speaker, and a link back to the recording.
CRM: accounts, contacts, deals, plus notes, logged meetings, calls, tasks and emails with their associations.
CRM stays the source of truth. Promises never writes back to it.
06 · Setup
Add Promises to Claude or ChatGPT.
https://www.promises.so/api/mcpWorks on Claude Free, Pro, Max, Team and Enterprise.
- Open Claude in your browser and go to Customize › Connectors.
- Click the "+" button, then "Add custom connector".
- Paste the link above into "Remote MCP server URL".
- Click "Add". Claude asks you to sign in. Use the same email you use here.
- Start a new chat and ask about one of your customers by name.
On a Claude Team or Enterprise plan?
Only an organisation owner can add a new connector. If that’s you: go to Organization settings › Connectors, click Add, hover Custom, choose Web, paste the link, and click Add. Everyone else then opens Customize › Connectors and clicks Connect. They never need the link. If you are not an owner, send them this page.
Adding the connector in Claude · A short walkthrough, start to finish
07 · Questions
A few things to know.
What do you mean by ‘promise’?
An outcome the customer explicitly wanted, or a commitment your team explicitly made to that customer. Separately recorded promises stay separate; Promises does not choose a single main promise.
Can Promises prove we delivered the result?
It helps you establish what the available conversations and CRM records support. An explicit customer report can substantiate reported achievement. A positive comment or a related update is not proof that a goal was met.
How does this help with retention?
Progress toward the outcome a customer bought can be an early signal of the value supporting a renewal. Promises does not predict churn: budgets, priorities, and other factors also affect renewal. Missing evidence is a reason to ask rather than assume.
What if we have no post-purchase calls?
Available CRM notes and logged emails can contribute evidence. If no usable update is available, the outcome remains unconfirmed. Promises keeps that gap visible.
How are CRM notes treated?
Team-written notes are identified as your team's account of what was said. They are kept distinct from the customer's own words in transcripts and inbound emails.
Where do we use it?
In ChatGPT or Claude. The dashboard handles setup, sources, team access, and settings. You can also receive a weekly email brief.