Stop adding columns to mobile menus

Too many AI personal assistants, too little time to assess all of them. Nice work here: assistantbenchmark.com

Welcome Hunter, Salesforce’s new outbound sales agent. She built $500M in pipeline last quarter. See her work at Dreamforce. #DF26

Want to build a domain-specific agent harness? This is a great practical guide by @sydneyrunkle on designing and building your own custom agent harness. Worth reading if you’re exploring agentic systems and AI-native products. langchain.com/blog/how-to-bu…

Authenticator support in Instinct Instinct can now securely and seamlessly handle the “enter your 6-digit authenticator code” step for you. It uses the same time-based one-time password (TOTP) standard as Authy, Google Authenticator, Microsoft Authenticator, and other popular authenticator platforms. Once an account’s authenticator is set up in Vault, your agent can generate and enter its verification codes to unblock itself on your task. 37% of users store at least one account password in Vault within their first three weeks. A lot of everyday work happens behind a login. However, even with your password saved, an authenticator prompt can mean stopping the task, opening an app on your phone, and sending over a code before it expires. Instinct can now handle that step and keep working. On supported services, Instinct can complete the enrollment and save the details alongside your login in Vault. You may need to approve the initial sign-in or an existing security check. Where a service allows an additional authenticator, you can keep using the one on your phone. Once setup is complete, Instinct can use its own saved key to generate codes for future sign-ins. Phone approvals and other security checks may still need your input. Authenticator support is another step toward giving Instinct the tools it needs to complete tasks on your behalf in the real world, with fewer interruptions along the way. This is available across all of our users today.

Very few will vibe code their own CRM. Some will, but mainly for hyper-specific needs. Soon though most of us will have a composable “CRM.” Each of us will have a different surface, a different front end. The CRM becomes the system of record and the API. The UI becomes one client among several. Packaged front ends, essentially as skills. We already run this ourselves at SaaStr AI: •We drive Salesforce + more through its API, inside our AI VP of Revenue, “10K” •We also interact with it in Slack •Our CRM talks to inbound leads automatically, generates a real-time proposal and deck, and even closes some deals autonomously •And yes, one human on our team still logs into the Salesforce UX itself. One. Our agents work directly with our CRM, hundreds of times a day. And they don’t need an interface at all. And yes, some of that “CRM” isn’t in a CRM at all. It’s in Postgres and other, less structured databases. The agents read and write across all of it, and it looks like one system to the humans. The old CRM is dying. Slowly, but it’s terminal. The future is everyone gets the CRM they need. Agents, humans, customers. A new front end takes minutes to build now, not the better part of a year. Built in real-time, if need be. Long live CRM.

Welcome Slackforce, powered by Claude. ⚡️ A live Salesforce UI—Sales, Service, Marketing, Tableau, Data 360, and Slack—with governed access in the flow of work. Slackforce for Slack. Claudeforce for Cowork. See both at #DF26.