claude

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-14

Final complete day: 2026-10-14. Attention was 1.6% — this entity appeared in 14 of 883 analyzed posts/comments in the seven days ending that day (17 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-14 20:04 UTCComment

   Yep, that order. For content review....I don't get a ton of this - they don't usually have videos, which IMO is a shame. But if there is a video, a timestamp for each feature would be helpful. For the 1-pager, if I can't get a good idea in 1 page then I usually ask someone else to explain it to me (that person now being Claude). I'm not really interested in the fancy "how we add value" slides a lot of sales calls try and build into their presentation and neither is my CISO. If we're on a call with you we already know we want your product (or something like it) and we already understand the value prop, we just want to see how it works, and make sure it does what we need it to do.

2. 2026-10-13 09:20 UTCComment

   You're mixing two jobs. An intern can take bounded tickets off your plate, but they aren't the person to tell you whether the current system is safe to scale. I'd spend the first money on a short, fixed-scope review by a senior engineer. Don't ask for a vague 'architecture audit.' Ask them to restore a backup, trace one feature from request to production, review auth and permissions, identify the failure modes that could lose data or expose customers, and turn that into a ranked 90-day plan with rough effort. That review should tell you what to hire for. If the bottleneck is mostly implementation volume, a junior contractor with tight review could help. If it is security, architecture, or operations, you need someone senior enough to disagree with both you and Claude. Another Max subscription will produce more code, but it won't give anyone responsibility for the outcome.

3. 2026-10-12 20:37 UTCComment

   Give Claude code or whatever a dataforseo api key and ask it to do keyword research looking for keyword search volumes for what someone might search for if they have this specific problem. If you see some volume there then you have some demand. Also see if there are competitors which also signal demand.

4. 2026-10-12 18:05 UTCComment

   Yeah, my partners and I had a similar problem. I'm non-technical and do marketing, networking, and product design and all of us are involved in the buisness decisions/direction. The biggest issue was understanding each other's position and how to align incentives without getting bogged down in endless meetings coaching each other. What's been a dramatic help was leveraging ai for this. Not Claude or get, mind you. We use open source tools for sensitive stuff like proprietary data and our own software, which uses all of the models for stuff like site metrics and insights about customers and general problems we need to overcome. We also set up a bunch of different data pipelines from Stripe payments to Google analytics. Using these, I use our app to build and release weekly team newsletters that literally breaks everything down, excluding sensitive information. This tells the team where we are, what we need to be focused on, and where we're going, including health metrics for the site, anonymoized user behavior, product considerations, marketing opportunities, and development feats. And all of this is connected to several expert agents with reasoning layers embedded into them from professional books. So it gives us perspective from a range of different lenses like human behavioral psychology to marketing and sales funnels. And since we have our code mapped out in our open source agents whenever I come up with with a product idea, I can have it translate all of that for our dev to understand in a way that's actually grounded to what's possible now. This avoids frustrating the team. Unify communications through a single chatbot and use open source for more sensitive stuff.

5. 2026-10-12 17:00 UTCComment

   We sell into a tiny, conservative B2B niche too. Our first 5,10 came almost entirely from C + B: warm intros from advisors/customers, then stacking meetings at 2 industry events where we pre-booked as many “quick coffee?” chats as possible. What surprised me: 3 actually mattered earlier than I expected. We tracked “recommended by ChatGPT/Claude/Perplexity” and citation sources via seoforgpt, then wrote super-specific comparison / “how to choose X” pages. That started showing up in AI answers and created a trickle of very qualified inbound.