Nevis is partnering with @AnthropicAI to power secure, enterprise-grade AI across the wealth management industry, helping financial advisors work smarter, grow faster, and deliver a higher standard of client service. From preparing for client meetings, to generating real-time insights, to automating key operational workflows, Nevis uses Anthropic’s foundational models to deliver AI that is powerful, intuitive, and transformative at the exact moments advisors need it most. Together, we are enabling firms to unlock meaningful productivity gains and scale without adding headcount. Our new joint case study with Anthropic highlights the impact already underway. Advisors using Nevis are saving hours each week, reducing operational burden, and generating significant ROI for their firms. This is only the beginning of what high-performance AI will make possible in wealth management. claude.com/customers/nevis

Check it out here m.youtube.com/watch?v=HS9JFa…

We’re thrilled to partner with @neviswealth as they come out of stealth with their Series A and build the AI operating system for wealth management. The team brings deep fintech experience from their years working together at Revolut and is unifying core advisor workflows into one AI-powered platform that helps firms streamline operations and focus on serving clients. Excited to support @MarkSwan_, Philipp Burda, Ivan Chalov, and the team as they help modernize and scale the advisor experience. Read more: bit.ly/3KjdvLw — Disclaimer: bit.ly/3H4dQj0

This is how I feel about vibe coding. Any project I try that has any kind of complication has this immediate burst of progress. Things are amazing and it feels like a superpower. Then... as I add more complexity, things crash to a halt. The only projects that I think I can create are ones that fall in this "vibe zone". Prototypes, UIs, products—anything that's simple and has low complexity fits right in that zone. Proof of concepts, interactions, stuff like that. The tools are able to make things that fit in that slot. But. Everything falls to pieces as that complexity curve increases. And the problem is that any good product design process has increasing complexity. A basic prototype turns into a good prototype as soon as it has layered interactions, transitions, good affordances, hover states, 1000 tiny little details that make something feel correct and real. The benefit of vibe coding is supposed to be that you move fast and you can whip things out—letting AI do all the work for you. The problem is it loses steam as soon as the necessary complexity is added. It keeps redoing itself, rewriting code, affecting things that are unrelated and then causing other issues. But if you add that complexity, every vibe coding session quickly turns into a whack-a-mole bug-bashing session. I'm not sure the solution to this. With traditional prototyping the solution is to duplicate, add more complexity, create more frames/scenes, tweak, fork, etc. However with vibe coding, one little prompt can destroy literally everything. There's a stage where I end up walking on prompt eggshells-- trying not to give it too much or too little context so that it doesn't go rogue and break everything. There's only a few exceptions to this. @cursor and @framer. I can make great progress with Cursor, give it narrow context, and I have to approve the edits that it makes. This feels like a correct workflow. The problem is, I can't see the thing that it's making because it's an IDE, not a visual environment. Yes, I can create local builds and refresh my browser and all that kind of stuff. But the visual aspect is totally lost from the coding experience. It's a developer tool. Framer gets this right because it only allows narrow updates within a single component on the page. Yes, it's limiting because it can only do a single thing at once, but at least it's not trying to create the entire page from scratch and manage it all through a prompt interface. These seem like the right approach. @Cursor: Allow the AI to edit anything but allow the user to approve those edits and see them in context. @Framer: Allow the AI to only narrowly edit a single file or component to keep the complexity down to a minimum and reduce catastrophic edits. I'm optimistic that tools like @Figma, @Lovable, @Bolt, and @V0 can make cool prototypes, but I just keep running into walls when it comes to doing anything more than just a basic interaction prototype. They need to do less IMO. Hopeful that those tools add more controls that are in the same line as Cursor and Framer. I'll also add that this is similar to how we do it with @Basedash chart generation as well. But we're not a vibe tool in the normal sense so the parallels are a little bit harder to draw.

I would love to hear everyone’s take on the difference between managerial technology and operational technology and why it might matter. I will give my take tomorrow.