Tyler Kramer

When you wear medical devices, you start noticing other people wearing them too. Saw a guy at the gym with an insulin pump tube hanging out of his pocket and a Dexcom G7 on his arm, so I went over to show him mine. He had the older Tandem pump, the one I used to wear. Pulled out my Mobi, the smartphone controlled, screen-less version, about half the size. He had no idea it existed. He's a current Tandem Diabetes Care customer, already wearing the exact setup the upgrade requires, and he didn't know the upgrade was available to him. Going through this myself is how I learned the warranty upgrade rule: once a pump goes out of warranty, the opportunity window to upgrade with a low-cost or free replacement expires. So I told him to check his warranty date before it lapsed. He pulled out his phone right there and started calling the company to find out if he still qualified. He hadn't gotten a heads-up from them or his endocrinologist. Only caught my own upgrade window because I got lucky, and he should have gotten the same notice I did. The company has his profile, his serial number, his install date, and his warranty clock. Every signal needed to reach him at the right moment already exists. It just never reached him. So the customer most likely to say yes to an upgrade never hears about it. He found out from a stranger at the gym instead of the company he’d been loyal to for years. What does it cost a device company when the customer most ready to buy again is the last one it reaches?

$200,000! The default monthly spend limit Anthropic automatically set on my account. This dollar amount is the ceiling on what I could get billed for, not what I'd actually spend. My actual usage runs a few cents a day. Been vibe coding over the past few weeks, building my first app with Claude and Lovable. I'm not super technical and I never took a coding course. Claude is my builder, strategist, and developer. I describe what I want, and it gives me the architecture, logic, and prompts to feed into Lovable, then I watch it build. Mid-build, Claude told me to check my spend limit before I'd even thought to look. That's when I found the $200,000 ceiling. The tool building my app caught something I would have missed. Made me wonder what other platforms default to numbers that protect their model, not mine. Worth checking before you find a surprise bill. Anyone else vibe coding and tripping over defaults like this?

Sitting in a patient waiting room, I overheard a man at the front desk who was frustrated. He'd filled out the online form. Selected his reason for visit and got directed to this location. Showed up, checked in, paid his copay. Then the nurse told him they don't have X-ray services here and he'd have to go to a different location. He was frustrated with the front desk, understandably. But the front desk didn't build the intake form. They just absorbed the patient's frustration. He'd selected the right reason for his visit, so the system knew what he needed. It routed him somewhere that couldn't help him anyway. He trusted the online patient intake form and it had great intent. The data was there and the gap was acknowledged, buried in a disclaimer nobody reads. But the connection between what the system knew and where it sent him never existed. It's not a staffing or a front desk problem. It's a data routing problem. In healthcare, this results in a patient driving to a second location with a broken bone. This is a workflow problem. And workflow problems are now solvable in ways they weren't two years ago.

If your team already lives in Slack, type @Claude in a channel. It picks up the context, works through the task, and posts back when it's done. Slackbot handles the automations. Claude reads the conversation and thinks. For healthcare teams, a nurse tags @Claude in the care channel. It reads the thread, writes the handoff summary, and posts it back. Kudos to the teams at Anthropic, Slack, and Salesforce who built this! https://lnkd.in/ggiPnUr2

Nobody enjoys entering their expense report in Concur. Nobody opens Workday early. And ask any physician how they feel about their EHR, you'll get the same answer, just with more sighing. A few months ago, Salesforce built an AI agent into Slack called Slackbot. No mandatory rollout, no training requirement, no campaign telling people to use it. It's now the fastest-adopted product in Salesforce history. You don't need to be an AI power user. You've used Google, maybe tried ChatGPT. You already know how to use Slackbot. The difference is, Slackbot knows you. Yesterday I asked it to make sense of a customer's contract structure. Two active contracts, five open opps, different renewal dates. In minutes I had a full breakdown and a new POV, without pulling in another team. That used to mean a call with deal desk, another with the account team, and nearly all day before you had an answer. My mom's CEO had a sign behind him on every Zoom call, "FITFO." At the time it sounded harsh. Now I do it. That's the gap between tools people are handed and tools people choose. One gets tolerated. The other gets passed around like a good restaurant recommendation. If you're not familiar with what Slackbot can do, ask me. I'll tell you exactly how I use it.