273 Ventures

Are you fed up with all the noise in the Legal AI space? To orient yourself better within the jungle of Legal AI, Marco Mendola and Hadassah Drukarch have interviewed a keynote expert in the field: Jillian B., Chief Risk Officer at 273 Ventures. A background in accounting and many years of experience in due diligence, compliance, and risk management across various highly regulated industries. Titled “At the intersection of AI and ethics in LegalTech: a deep dive into KL3M”, in this discussion we went beyond our comfort zone and expertise discussing with Jillian how KL3M is become the world’s first-ever ethically trained legal LLM, unpacking the practical applications of KL3M in the legal context, and stressing the need to foster of ‘Responsible AI’ projects. At the core of our chat, we also explored business purposes, and how to deal with assumptions and general misconceptions when running and piloting tech solutions in legal. Without further ado, take a listen to our latest episode on your podcast platform of choice ➡️ https://lnkd.in/emDPCgrd. #legalai #largelanguagemodels #legalinnovation

What if you could draft a contract or answer legal research questions with a model that ran locally on an old MacBook air? Would that change the way you think about the future? (We've been quiet at 273 Ventures lately, but we haven't been idle...)

Well, that was a dramatic weekend.  Though it seems unwise to make any claims before the dust finishes settling, there is one clear learning so far - never underestimate the importance of supply chain risk management.  Back in February, I warned that “if interruption or discontinuance of [services] wasn't already on your risk register, it better be now. It's time to start thinking about 1) what your backup plan is if a particular vendor (OpenAI in this case) is no longer available, and 2) what your overall AI strategy entails (e.g., building your own LLM, managing regulatory/statutory risk).” AI-enabled products and services rely on models. Whether they are open source models that are used locally or proprietary commercial models that can only be accessed through a web interface or API, each method carries its own set of risks. When we built Kelvin, we worked hard to make it model agnostic, so that our customers could choose the model and access methods that best suited their business and needs. We’re also working harder than ever to help customers use and build models they control on their own hardware.  Unlike other competitors in the market, a seismic shift in OpenAI’s (or any particular other model provider’s) availability, access method, cost, or contractual terms isn’t a game changer for us. Though this wasn't on our bingo card, we did expect the game to change and built our product to withstand it. 🎯 CC Jessica Katz Daniel Katz Michael Bommarito

Happy Halloween from our Headless AI to you and yours! If you look closely, you'll see that this WordPerfect-themed command line interface shows the table that Daniel Katz posted yesterday (including Lucille's bonus). Would you really run an M&A diligence checklist in the command line? Probably not (unless you're me). Would you really design a modern UI to look like Halloween WordPerfect? Sadly, no. So, what's the point of this screenshot? It proves that behind our chat interface, the Agent has no Head - or more accurately, that you can easily swap user interfaces, should you so desire. The beauty of Kelvin Agent is that you can embed its capabilities into any product or system you already have, from vanilla O365 to whichever DMS, ELM, or CRM you live in day-to-day. Stay tuned for more content from Jessica Katz and Jillian B. on agents soon, including what they are, how to manage them, and how they work.