The AI Dog Chef Problem


One of the reasons AI agents break all our security infrastructure can be described like this:

It's as if suddenly, we realized that our family dog has an uncanny talent for cooking

So now we want to make him our personal chef.

The problem with this:

Sparky might nail it on baking tasty treats, but we still can't trust him not to go bonkers and destroy the kitchen when a squirrel runs by.

All of our basic kitchen protocols (for preventing fires, knife injuries, and general mayhem) were built over decades FOR HUMANS.

They don't really work on Sparky.

And the guardrails that used to keep dogs like Sparky safe

-- Gating off certain rooms, leashes, crates --

They don't work anymore either,

Because we need him to be able to access the kitchen to do his job,

But also, the kitchen is where he's most likely to burn down the house.

It's the same with AI agents.

We're attempting to give agents jobs that humans used to do

And we know they can be really good at it,

But like a dog, they don't behave like humans, they don't understand morality or nuance, or other human things.

So our typical infrastructure to protect humans from doing the wrong things doesn't work on them.

And they can - without much warning - wreak absolute havoc.

And just like with our dog example, we DO have guardrails for software, classically.

But when we ask software to do the types of things we want agents to do, those guardrails become impossible:

We can't sandbox apps effectively because they often REQUIRE access to some of the most dangerous areas in our systems to do their jobs.

We need to let them use the proverbial kitchen.

And so now we're stuck.

So what do we do about this?

Well, it's complicated.

So I built a course about it:

FREE class tomorrow -- AI Security Basics for Finance: The Need-to-Knows

September 3rd, 1PM ET / 10AM PT, hosted by Ramp.

(It'll be recorded, but you only get access to the slides if you sign up for the live event)

We'll get into:

  • The shape of the threat - the AI you use, and the AI being used on you
  • 6 strategies for lowering your AI risk: least privilege, the lethal trifecta, data hygiene, why prompts are not controls, vibe-coded vulnerability, and what your security stack needs now
  • Where to keep learning, because all of this is going to keep changing

It's built for people in a finance department - anything from bookkeeper to CFO

No technical knowledge or other prerequisites required,

Just a willingness to learn. And an appreciation of dog metaphors is a plus.

Sign up here!

See you there!

Your Daily CFO,

Lauren

Founder-Friendly Finance

CEO-turned-CFO & finance instructor, Lauren Pearl, drops a daily tip that helps startup founders grow their businesses and control their destinies. Learn why this growing list with a 60% open rate led to LP being named top 25 Finance Thought Leader and host of the #3 CFO podcast for 2025

Read more from Founder-Friendly Finance

In times of great change, bet on someone who can learn. In my first semester of college, I called home in a panic. It was a couple months in, and I'd hit a snag: I'd completely fallen in love with the very first course I'd taken. In all my other courses, I found myself constantly distracted, pulled back into the subject. I'd even gone to office hours, and had been offered a slot into a graduate-level elective course taught by the same professor. And this was a terrible terrible problem......

Being a CFO in a new industry can feel like a completely different job. I've spoken with dozens of CFOs about this: Cameron Kinloch, who described the muscles she had to rebuild switching from Consumer Goods to SaaS to FinTech Darian Wright, who walked me through his move from Hospitality to Non-Profit And many others Which is why I got so excited a few months ago when NetSuite offered me the chance to build a new webinar series around exactly this idea — deep dives into CFO journeys from one...

As a startup CFO working with CEOs, there are just certain things that feel like they should be easy to CEOs But that are actually ALWAYS a pain in the butt for a finance operator (Hello, real-time accounting data... sigh...) Here's the one that always breaks my brain: Per-project profitability. It comes up CONSTANTLY. And for good reason: Figuring out which projects (or products, or customers, or departments, etc.) are making money Is really important to leadership. Because one of the most...