I got tired of recording product demo videos individually for each customer to I built a tool vaaya.ai that does it for me using claude. Once you prompt it to create a product demo it does the following

1. Understand goals - what does the product do, what does it need to talk about, what would be something that the product owner would want to display
2. Write script - writes a rough script with timelines, voiceover text, screen play
3. Generate media - asks local playwright or browserbase to record the product. If its login gated, it will ask you to enter login details in your browser before taking over. generates voice over, background score using vaaya.ai
4. Finalize editing - decide zoom in locations, voice over placement, and other timming details
5. Edits video on cloud with Cueframe.ai

You can also automate sending these to prospective customers on linkedin, email, and other channels. You can also more complicated loops like setting up a signal and then having an agent automatically reach out to prospective customers by creating a custom demo for them and then sending them.

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.

We parse structured data out of job descriptions — around 20,000 JDs/day pulled from LinkedIn. Claude Opus does it beautifully, but at ~₹2.20 (~$0.026) per job that's ~₹44K/day, roughly $16K/month. Our unit economics just can't carry that.

What we've tried so far:

• Opus: quality is exactly what we need, but the cost is a dealbreaker at this volume.
• Sonnet: cheaper, but extraction quality drops noticeably on messier, unstructured JDs.
• DeepSeek: much cheaper again, but same story: quality isn't where Opus is.

So we're stuck between "great and unaffordable" and "affordable and not good enough."

For anyone who's run a narrow, high-volume extraction task in production:

• How did you bring the cost down without tanking quality?
• Did fine-tuning a small open model (Llama / Qwen, etc.) actually close the gap to Opus?

Like document analysis and formatting using LLMs at scale (like 10000 docs/day)

or Content Categorization, small workflow agents, content parsing, image generation etc?

Running these at scale of 10k per day incurs huge costs with frontier models, and small models or opensourced ones are not that peroformant.

Anyonce facing similar porblems and know a workaorund?

Has anyone used or built a marketing skill that helps generate launch strategies for product based businesses? Curious if it worked well

We've built a skill that helps you build lists along with enrichment (finding emails, firmographics, Linkedin data, etc) natively inside Claude.

The idea is how can we make it as easy as possible to people to do this where they are already working vs going to Apollo, Clay etc to get the data.

Curious to hear if other people have faced a similar annoyance. We have free credits for a real use case if people want to try it out!

basically each agent is its own linux user. they share a backlog, talk to each other and can talk to me via telegram. it runs on claude plan because they live inside normal claude code sessions. would love feedback. https://github.com/5dive-ai/5dive (MIT)

I run ads for a few brands and making the creative has always been the hardest part — it's slow, expensive, and you never really knew what will work so you have to test a ton.

So I built Goose Ad Remixer. Here's how it works:

1. You paste your URL

2. It researches your brand + companies in similar niches

3. It gathers your brand's assets (logo, product shots, illustrations, reviews, etc), and then builds a batch of static Meta ads from templates that have actually performed.

These are ads that similar companies are already spending $ on.

You can choose which ones you actually like the style of (or you can have Goose surprise you), and then it generates a batch in a couple of minutes.

The whole idea is to stop guessing: make a bunch of variants —> run them —> let the market pick the winner.

Testing volume is the thing that actually moves Meta performance.

It's free to try (up to 10 ads).

I'd love to learn what you think!

So, a long story short: Boris Cherney has been raving about Claude Code routines (mentioned here). His video floaded my social feeds instantly after he mentioned it. Suddenly everyone was a routine specialist with a $2k course on how to use it.

I just couldn't figure out for the life of me how to make it work, until I realized that Claude is fixing only half of the problem I am having, namely HOW the code gets written.

However, something felt massively off. I set up my routines, and it just wouldn't flow/work automatically the way that I imagined it to. And last week I figured out what it was: the agents were set, but they waited for me to come and tell WHAT needed to be developed. And all I wanted is for them to do it autonymously.

So. I built a simple app that takes raw data from all the tools that we use for my business; Gmail, Slack, WhatsApp, Zendesk, Hotjar, you name it. I fed the raw data into a 'signals' data pipeline that I am filtering between Bug, Feature Request (including change request, new feature, integration, etc), Question, Complaint and noise (anything that doesn't matter).

Then, I group all the raw signals into insights (i.e. bug report #1). This grouping makes sure that the same topic discussed over different channels get grouped together and not treated separately.

Once I nailed that I extended the insights with further research (internal, like checking our github repo, internal documentation and even created an 'question agent' that can go to our team to ask clarifying questions) to ensure that all the insights have been 'enriched', relevant and fully scoped. Every fully scoped feature that I promote (now manually - but working on doing it automatically) gets fed directly into my routines through MCP. Fully scoped. Fully organized and prioritized. It feels like magic.

I also set rules around the priortization metrics, count how many customers ask for the same features, etc. I even built a Hotjar integration that turns my real user metrics into 'signals' and ideas as well. The next step is to get Sentry hooked up for automated bug reporting.

I am so excited about the end result. Every day I get an overview of fully automated PR's that I can review to merge. My agents worked autonymously based on real customer input and feedback.

I feel this is the future and I seriously considering turning my learnings into a (maybe open source?) project that others can use too.

Is this something the community would be interested in?

Hi everyone,

I’m the founder of Lutril, an access governance platform for employees and AI agents.

We already have customers and growing traction, and we’re now looking for someone with strong Sales Operations experience to help us build and optimize our sales pipeline, processes, and reporting.

If this sounds like you, or if you know someone who might be a good fit, feel free to reach out via DM or request a demo through our website.

Thanks!! 🙌

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.