AI Security

I still get excited when I see a boring task and think, “I think I can do something about it, I can build something to automate this.” That is partly the GTM engineering mindset I’ve been in for a while now. And so much of the work is spread across things that do not really belong together. CRM fields, spreadsheets, call notes, dashboards, Slack messages, enrichment tools, random CSV exports, and someone asking for an update five minutes before a meeting. ...

I have spent the last year working around AI security and governance, so I already understood the high level idea behind guardrails. Agents should have boundaries. Tools should have scopes. Read access and write access should mean different things. A system that can touch files, APIs, CRMs, Slack, browsers, or internal docs should probably have a stronger plan than “hope it behaves nicely.” Okay, that last sentence already sounds like I am about to sell you a whitepaper. ...

I have become the annoying person who asks, “Can I run this locally?” This is mainly because after working around AI security and governance for a year, I have started noticing how easily data leaves the systems we understand and enters systems we barely think about. I admit that this is a slightly irritating change in my personality. A year ago, if I found a tool that helped me automate something, summarize something, enrich some data, or speed up a GTM workflow, my first question was usually: does this work? ...