Reading…
Reading…
Kelpie
Kelpie reads your team's mail and calendar and scores every account from what the customer actually did. The working is printed next to the number. Your CSMs get the answers inside Claude, ChatGPT or Grok. You get a book you can defend to the board.
Reads email and calendar only · 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 Ridgeline Outdoors, call at 2pm
Ridgeline Outdoors is at risk, 40. The customer has not written in 29 business days and your side sent the last message.
Open promise. Tom said on 12 Aug he would send the revised rollout plan. 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.
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.
They had only ever existed in email. A fact is never edited: if Roy sends the export, a new fact says so and the old one stays as the record. Kelpie never decides a promise was kept.
Connect Kelpie once to Claude, ChatGPT or Grok. From then on your CSMs ask.
/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. The book, worst first.
/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, nothing else.
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. Chasing an account does not make it look healthier, and nothing on the page can be nudged green.
Meetings, commitments due, a notice deadline landing today. The email and the assistant run the same query, so they cannot disagree.
| Account | Health | Silence | Owner |
|---|---|---|---|
| Harbour Optics | 40 | 43 bd | Priya |
| Ridgeline Outdoors | 40 | 29 bd | Tom |
| Wattle & Co | 20 | 11 bd | Priya |
| Pelican Press | 0 | 2 bd | Mei |
| Saltbush Labs | 0 | 1 bd | Tom |
Managers get every number, the evidence behind it, and the questions nobody on the team could answer. Worst first.
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.
A thirty-minute walkthrough on your accounts. Built for CS teams up to 15.