Paul Dix

Okay.

Maybe, I don't know.

But I mean, the thing is at this stage, I think any more than three is more than you need.

I think it's like two or three.

Yeah, I think two or three, mostly just two though, where like you can almost do like a PM and an engineer, right?

That kind of thing.

Yeah, you need accountability and responsibility.

Most of the work at this point is like trying to figure out, okay, what is the problem we're actually trying to solve and defining that well?

Then you've come up with a rough structure for how to solve it.

But then the agent just does all the work.

And then the other side of this is verification and iteration, right?

Like verification is like, does it actually do what it's supposed to do?

And then the other piece is like, is the user experience what we want it to be?

And then you just have to like tune it and polish it, right?

Because there's still like a difference between...

The output of an agent where somebody is iterated with it multiple times to produce a more polished product versus the one shot example.

Right now, I think it's bespoke per team.

Well, I think it's bespoke per team using whatever agentic tool they want, right?

And it's almost like...

It's almost like when you hire somebody, a human, you train them on what you want them to do, right?