正在加载视频...

视频加载失败

Your sales tech stack keeps growing. So why does critical customer context still fall through the cracks? Most sales teams prospect in one tool, hold meetings in another, and send contracts from somewhere else. Every handoff creates an opportunity for valuable context to disappear: A key objection from the...

23,820 次观看 • 26 天前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

54% of Anthropic's new enterprise logos in 2026 came through self-serve. Self-serve enterprise. Real ACV. Real terms of service. No AE in the loop. Anthropic's Head of Industries Eleanor Dorfman walked through at SaaStr AI 2026 last week how they rebuilt the entire sales org in 30 days after Claude Opus 4.6 broke their demand curve in December. 👉The constraint: couldn't 3x or 4x the sales team fast enough without lowering the recruiting bar. The thesis: don't buy a new stack. Thread Claude through the one you already have. What they kept: 1⃣ Clay for enrichment 2⃣LeanData for routing 3⃣ Salesforce as system of record 4⃣Gong for call coaching 5⃣Ironclad for contracts 6⃣Slack for everything else What they added: Claude as the connective tissue between all six. The four moves: 1/ Killed the PLG vs SLG orthodoxy. Launched enterprise self-serve in January. Intercom Fin guides the buyer through the journey. Now 54% of new enterprise logos. 2/ Threaded Claude through the existing stack. Every AE starts the day with a "morning brief" Skill that pulls context from Gmail, Gong, Slack, Salesforce, Intercom, Greenhouse. 3/ Made Slack the front door for every support function. Slack ticket in, Jira ticket out. Claude triages and resolves inline if it matches precedent. Escalates with full context if not. 4/ Codified what the best reps do as Skills. Every new rep gets a sales plug-in with 5 Skills: morning brief, call prep, customer follow-up, competitive intel, create-an-asset. Anthropic didn't replace anything. They invested in the stack they already had and let Claude be the seam between everything. Most companies will spend 2026 evaluating AI-native sales platforms. But Anthropic did it with its current stack + Claude. Almost none of it required new software.

Jason ✨👾SaaStr.Ai✨ Lemkin

437,853 次观看 • 2 个月前

The average dunning email gets ignored. You are literally sending "please ignore me" messages to customers who owe you money. Playbooks - our workflow system for intelligent collections - is now live on the Monk platform. A system that reasons, not just reminds. We filmed a 60 second video showing you an experiment between Joe Zhou and Frank collecting $100K. Finance, biz-ops and post-sales teams should not be spending time chasing customers. Many spend 10+hrs/week doing what Joe did in this video: - context switching between tools (slack, gmail, quickbooks, google sheets) - breaking flow from deep work - sending reminders because the average dunning email is ignored But agentic collections are not enough. Every customer relationship is different. Some need white-glove treatment and others a nudge. That’s why we built playbooks, giving every business a customizable collection workflow. With playbooks you can: - create triggers and workflows specific to a customer segment (tone shift, conditions, escalations to sales/customer support) - auto-resolve AP questions with context from relevant email threads - pause automatically when product questions or upsells opportunities come up Playbooks is how you get paid while you sleep. And we do it with professionalism and empathy that your customers deserve. Heading into Q1 with a gap between signed ARR and actual cash? Watch the video. And if you want to see bloopers from Frank/Joe filming, comment “payday” + tag a teammate and we will send you bloopers from the shoot.

George Kurdin

1,269,929 次观看 • 8 个月前

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,070 次观看 • 2 个月前