Aaron Levie

I'd rather accelerate the timelines, hold people to a high bar of how quickly things should happen.

And then revealed preference will just be what tools do they use?

How do they incorporate that in their workflows?

We don't necessarily need to hand everybody the exact template to go follow.

Yeah, so I love that idea of a user budget or employee budget.

And that's exactly probably what I'd recommend to anybody outside of our company.

Right now, we have not kind of created any sort of stated limit.

And mostly because I don't know what I would have our organization do.

And for example, so within Box, Box AI basically connects almost any leading AI model to your data.

And so that means that as an employee, you can go into Box and, let's say, create a document and use Cloud 3.7 to generate any of the content in that document.

So you're effectively able to use any of the leading AI models within our company.

And we don't have a budget limit only because

I think it's very provocative and I think it's the right thing to do for us.

We've just said, go run wild.

We want to learn what everybody's doing.

We might now, who knows, if you could kind of like parallelize a hundred coding agents all using Cloud 3.7 doing long running agent, you know, agentic coding tasks.

maybe we'd be like, okay, sorry, you've just spent $200,000, you know, building some feature, like then that'll be a problem.

We are not there yet.

And so maybe we'll have to check in at some point if we've had to kind of evolve our practices on that.

That's an important segue.