Reading…
Reading…
Kelpie scores each account from customer silence, open commitments and product usage, and puts the renewals at risk at the top of the week. In Claude, ChatGPT, Codex or Grok, whichever your team already uses.
You never forget a promise.
Reads email and calendar, and usage via CSV upload · Never stores a message body · One database per customer
You: Prep me for my 2pm with Northstar.
ChatGPT, using Kelpie: Northstar · meeting prep. At the last meeting, Maya wanted to see the reporting export before agreeing the rollout. Source: meeting, 29 September.
One open commitment. You promised a sample export by 2 October. It is still recorded as open. Source: email, 30 September.
Start here: “Did the sample export give you what you need for the rollout?”
You: I sent it yesterday. Mark that promise as done.
ChatGPT, using Kelpie: Closed your export commitment. Closed by you, recorded against the promise.
/prep Wattle & Co, renewal call at 2pm
Wattle & Co is at risk, 50. Notice deadline in 30 days. Usage is 62% below its four-week average, and the customer has not written in 11 business days.
Open promise. Priya said on 2 Sep she would send the training plan for their new team. No reply found that settles it.
Last meeting. Their ops lead is moving teams in October. A new contact has not been named.
The number, the reason, and the message it came from.
20 of 62 accounts
hand-typed health scores the customer's mailbox disagreed with, the first time Kelpie read a real book.
The replies get slower, then stop. Your CSM keeps sending check-ins, so the account still feels busy. The spreadsheet stays green right up to the renewal call, where the customer mentions they decided months ago.
One account sat at “20, fine” after 29 business days without a word from the customer. Nobody was lying. Nobody was counting the silence.
Not with a trawl through the inbox, last week's meeting notes and the spreadsheet, trying to remember who was waiting on what.
Counted in business days since the customer last wrote, and only while your side sent the last message. Chasing an account does not make it look healthier. An out-of-office is not a reply.
What the mailbox cannot see goes in with a quote and a message ID. The score moves by a fixed, published amount and expires on a review date.
Each one cited. A decision. A risk. A contact change. A request: something the customer asked for that we do not do. A commitment, with a name against it.
Roy will send the export by Friday.
A forgotten promise is a customer left waiting. They do not chase you for it. They just stop expecting things from you. Kelpie catches every promise made in mail and meetings, puts the overdue ones in the 7am email, and closes each one when your sent mail shows it was done.
A customer can stop writing and still use the product every day. Or keep writing and stop using it. Kelpie reads both, and the working says which one moved the number.
Connect Kelpie once to Claude, ChatGPT, Codex or Grok. Every CSM asks in the assistant they already use, and every one of them reads the same memory. When somebody leaves, what they knew stays.
/prepBefore a call. Health with the working, the last five meetings, every promise still open.
/todayAt the start of the day. Meetings, commitments due, a notice deadline landing today.
/mondayFor the week. Renewals with a notice deadline closing, worst first, and the open promises under each.
/housekeepingOnce a week. The questions only a human can answer, one at a time, fifteen minutes.
Connect an agent now and ask it about the demo book:
claude mcp add --transport http kelpie https://mcp.kelpie.pro/mcp
Add the Kelpie connector to your assistant and sign in. Mail and calendar for the conversations, plus product usage via CSV upload.
Each night it reads, scores, and works out what it cannot answer on its own.
It asks the account owner those questions, one at a time, and records each answer under their name.
Health with the working, the last five meetings distilled, and every promise still open. Asked for in the assistant your CSMs already use.
Silence is counted from the customer's side and usage against the account's own average. Chasing an account does not make it look healthier, and nothing on the page can be nudged green.
Renewals and notice dates first, then the day's meetings, with the open promises under the account they belong to. Illustrative.
| Account | Health | Notice | Silence | Owner |
|---|---|---|---|---|
| Wattle & Co | 50 | 30 days | 11 bd | Priya |
| Open promise: Priya, send the training plan. No reply found that settles it. | ||||
| Harbour Optics | 40 | rolling | 43 bd | Priya |
| Ridgeline Outdoors | 40 | 140 days | 29 bd | Tom |
| Pelican Press | 0 | rolling | 2 bd | Mei |
| Saltbush Labs | 0 | 210 days | 1 bd | Tom |
Worst first. The open promise sits under the renewal it belongs to. Illustrative.
The head of CS is the buyer. Your CSMs use it every day. You are the one asked which renewals are safe, and why you think so.
When a CSM leaves or accounts are reassigned, Kelpie gives the new owner every open promise, the recent decisions, the contacts and the health score with its working.
See how early it would have flagged them. This is not in the product yet.
A guessed renewal date is worse than none. Everything downstream treats it as fact.
Bodies are read, turned into observations, and dropped. The storage layer has nowhere to put one.
A mechanical check refuses any fact carrying either. Across the first book, the count is zero.
Not a customer column in a shared table. Row-level security stays on underneath as a second wall.
59 accounts and 15,355 records brought back, row for row.
USD 125 a seat a month.
A seat is a mailbox Kelpie reads. Managers who only read the dashboard are free. No platform fee, no minimum. The head of CS is the buyer.
Built for CS teams up to 15.