u/Sad_Character156

Four months ago I posted here about our slightly embarrassing sales process.

Open Claude. Paste the pipeline. Ask who to chase. Repeat tomorrow.

We’d basically become the API between our CRM and the thing we actually wanted to work in.

That post turned into a much bigger conversation than we expected. People wanted access. Others asked fair questions about where the data lives, what happens when Claude gets something wrong, and whether this actually removes any work.

We’re a small team in Stockholm, and we’ve spent nine months building Capable—including the four since that post.

Today, we’re opening it up.

Here’s what it looks like: short video

Give Claude your call notes or transcript. It proposes changes to your records. You review and approve them inside the conversation.

Next time you open Claude, it can work from those saved records. You can ask who needs attention without pasting your entire pipeline again.

Underneath, Capable keeps structured CRM records and a history of changes. There’s also a web view for when you or someone on your team wants to look at the pipeline directly.

It’s built for founders and small teams who already work in Claude and keep finding themselves copying the results somewhere else.

Try it for 14 days. For launch, the first 50 paying customers get 50% off for life with code REDDIT50.

Try Capable

If you were in that original thread asking for access, thank you for sticking around. Looking forward to seeing what you do with it.

Eight months ago my alarm went off at 6am, I hit snooze, and I didn't wake back up until 9:40. I missed a client call. Not a big one, not a career ender, just embarrassing enough that I sat on the edge of my bed afterward and actually said out loud, to nobody, "what is wrong with you."

Nothing was wrong with me. I just had a brain that was very, very good at negotiating with itself at 6am. Every night I'd set the alarm with total conviction. Every morning that version of me lost to the one still half asleep, and that one always won, because he was the only one actually in the room.

I'd tried everything people tell you to try. Alarm across the room. Two alarms. An app that makes you solve a math problem before it shuts off. None of it touched the actual problem. It's that turning it off had nothing to do with being awake.

So one random Tuesday, half out of frustration, I made a rule. The alarm doesn't stop until I've done twenty pushups. Not a math problem. Not a walk across the room. My body, doing something, on the floor, at 6am, groaning the whole time.

The first morning was miserable and I loved it a little. By pushup twelve your heart's going, your hands are cold on the floor, and somewhere around fifteen you have this small, stupid realization: I'm already up. There's no more negotiating to do. The decision got made by my body before my brain even weighed in.

I kept it going. Not because I turned into a disciplined person overnight, I still leave dishes in the sink for two days at a time. But that one pushup rule was the first domino. Awake and moving at 6:05 instead of foggy and resentful at 9:40 meant I actually ate breakfast. Eating breakfast meant I wasn't crashing at 11am. Not crashing at 11am meant I stopped reaching for a second coffee just to survive a Zoom call. None of that was willpower. It was just the first hour of the day finally pointing the right direction.

A friend of mine, a nurse who works rotating shifts, heard me talk about this at a barbecue and said something that stuck with me: "the reason none of the sleep apps work for me is they all assume the hard part is hearing the alarm. The hard part is what happens in the ten seconds after." She was right. That gap, between the sound stopping and your brain actually arriving, is where the whole day gets decided, and basically nothing is built for that gap specifically.

So I built something for it. It's called Znoose. The idea is exactly what got me off the floor that Tuesday: the alarm doesn't turn off until you've done the thing, whatever thing you pick. Pushups if that's your version of it. Walking to another room. Whatever gets your actual body into the actual day before your brain gets a vote. It's pretty fun to use too, and there's a streak built in so you can see the mornings stacking up.

I've been using a rough version of it on myself for months now, and the honest pitch isn't "you'll become a different person." It's smaller than that. It's just: the version of you that set the alarm gets to win the argument, because by the time there's an argument to have, you're already twenty pushups in.

There is a bunch of AI personas out there, but I was just too lazy to exit Claude and find what I'm looking for. Pakadoxically, as the lazy person I am, I built an MCP APP instead that opens personas I can click on directly in Claude everytime I type "don't sound like AI" cause I always fall into the same trap thinking that it will work the second time somehow. Anyway, this has been a lifesaver for me and I want to fill it in with more useful personas depending on what I'm writing and to who. Any recommendations for prompts?

View Poll

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.

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.

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.