My actual job for three months was copy-pasting our pipeline into Claude

Every morning, same ritual. Open the CRM. Select all. Copy. Open Claude. Paste. "Ok who do I chase today."

Embarrassing? A bit. But it worked better than the CRM ever did. It caught a deal going cold that I would have missed. It remembered when a champion switched jobs. Better read on my pipeline than any view I ever set up, and I've set up a lot of them.

The problem was the context died with the tab every night. Next morning, rebuild it by hand. At some point I did the math and I was spending 40+ minutes a day being a data pipe between two windows. Not selling. Not thinking. Shuttling.

That's when it clicked. The thinking was already happening in the chat. The CRM was just where the data slept at night. So why does it live anywhere else?

We're building the fix now. A CRM that lives entirely inside Claude over MCP. No app, no tabs. You say what happened on the call and it moves the deal, updates the contact, logs the touch. The conversation is the CRM.

It's for founders and teams who are in Claude all day anyway.

What's the first CRM chore you'd hand over if Claude could actually write to your pipeline?

Small team in Stockholm. We think the thing that finally kills legacy CRMs isn't a nicer dashboard. It's no dashboard.

reddit.com
u/Sad_Character156 — 4 days ago
▲ 0 r/CRM

We deleted our CRM, started just telling Claude what happened on each deal, and somehow closed more. So we're building that.

Quick context before the question. We soft launched a week ago, hit our beta quota in seven days, and had to open a waitlist. Public launch is August 1.

Here's how we got here. For the last few months our entire sales process lived in a chat window. Every morning, same routine. Open Claude, paste the whole pipeline in as context, ask "okay, who do I chase today," close it. Next morning, paste the wall again.

Dumb? A little. Except it outperformed the actual CRM we were paying for.

That's the part that nagged me. Claude was never the bottleneck. The bottleneck was that our deal data lived in another tab and I was the integration, manually shuttling context back and forth before I'd had coffee. We'd turned ourselves into a very expensive, very slow API.

So the question got hard to ignore. If the whole company already runs through Claude, why is the CRM the one thing still sitting in a separate window we copy paste out of like it's 2009?

So we built the fix. A CRM that lives entirely inside Claude over MCP, with no separate app to open. You describe what happened on the call, Claude moves the deal, updates the contact, logs the note. The conversation is the interface. Every field change is still yours to approve, so it's not the LLM silently rewriting your pipeline.

A lot of the inspiration was watching people bolt Claude onto Notion, Airtable, and a graveyard of spreadsheets. Everyone's already building a scrappy version of this. We just put it on infrastructure that survives a real Tuesday. Persistent, secure, all the boring plumbing nobody posts about but everybody needs.

It's aimed at founders and small teams who already live in here all day.

So, within that context: what's the first thing you'd want a Claude native CRM to actually do? Genuinely collecting these to shape what ships August 1.

And if you want to be first in line when we launch, comment and I'll add you to the waitlist.

Small team, Stockholm, betting that the thing that finally makes legacy CRMs feel ancient isn't a prettier dashboard. It's no dashboard at all.

reddit.com
u/Sad_Character156 — 13 days ago
▲ 123 r/ClaudeGTM

We deleted our CRM and just started telling Claude what happened. It stuck.

For the last few months our entire sales process lived in a chat window. Every morning, same routine. Open Claude, dump the whole pipeline in as context, ask "okay, who do I chase today." Close it. Tomorrow, paste the wall again.

Stupid? Sort of. Except it worked better than the actual CRM ever did.

That's the part that bugged me. Claude was never the bottleneck. The bottleneck was that our deal data lived in some other tab, and I was the integration, manually shuttling context back and forth before I'd even had coffee. We'd basically turned ourselves into a very expensive API.

So the question got hard to ignore. If the whole company already runs through Claude, why is the CRM the one thing still sitting in a separate window we copy-paste out of like it's 2009?

We're building the fix. A CRM that lives entirely inside Claude over MCP, with no separate app to open. You describe what happened on the call, Claude moves the deal, updates the contact, logs the note. The conversation is the interface.

Honestly, half the inspiration was watching this sub bolt Claude onto Notion, Airtable, a graveyard of spreadsheets. Everyone's already building a scrappy version of this. We just put it on infrastructure that survives a real Tuesday. Persistent, secure, all the boring plumbing nobody posts about but everybody needs.

It's aimed at founders and small teams who already live in here all day. If that's you, I want two things.

If a Claude-native CRM existed tomorrow, what's the first thing you'd make it do?

And if you want early access, just say so in the comments and I'll get you in.

Small team, Stockholm, betting that the thing that finally makes legacy CRMs feel ancient isn't a prettier dashboard. It's no dashboard at all.

reddit.com
u/Sad_Character156 — 21 days ago