now then we moved into a different platform so at the time it was just Active Directory and then we touched on this little thing called Azure anybody want to take the first stab at that one I would like to not take the first stab at that I still

have nightmares about that implementation originally so I'll prime the discussion of just saying you know this has been years and years ago but it kind of emerged from a client that one of our workmates, Lee Christensen, and myself were working on, where he's like, okay, you know, we're moving stuff into Azure.

I have the feeling that, you know, we're probably making, or we might be making some of the same mistakes that we've made historically.

And there's just this huge push, you know, years ago, this huge push to just try to get everything up here.

And we just, we don't know how to handle this.

It's like, we barely... on the security side, they were struggling to even just understand how the entire system worked.

And Lee and I spent several weeks just kind of doing a crash course of the first initial very poor version of the model that is not what is the accurate version that's in the product now.

And maybe... will was the one that actually threw it into bloodhound uh i don't know if throw is the right the right verb but he did something um and maybe there was there were some struggles that kind of

And then maybe talk about why you needed some new solution to overcome them.

Sure.

I think...

A lot of this, and please jump in, Andy and Rohan, when I inevitably forget something, but a lot of this really kind of just evolved piecemeal over time, starting with the PowerView tool, which is a PowerShell kind of active directory, offensive automation, self-contained type scripts that embody a lot of our tradecraft for about...

I don't know, seven, eight, nine years or more.

So we used to operate in a couple of highly complex environments with a lot of domains, tons of different systems, talking tens or hundreds of thousands of systems users and all that.

And we started to stumble upon this concept of like, we kind of deemed it derivative local admin.

So, you know, this is day to day for me and still fun, still love it,

When you as the attorney get involved, where do you typically get involved and where do you like to get involved?

That's such a great question.

So lawyer, public service announcement, if we take a step back, I would say for any business owner that's thinking about selling their business, At least a year to two years out, they should think about the type of team that they want to have in place, the investment bankers, the brokers, and obviously the attorneys.

Take the time to meet with attorneys, see how they communicate to you, see how they communicate risk to you.

Have them do a temperature check of your business to see are your corporate governing documents okay? What type of agreements are you entering into? Are they all written down? You know, sometimes we have agreements that are more handshake and that can be a problem later down the line.

So, yeah, you don't want to deal with those issues when you're going through diligence.

So obviously, I would prefer to get involved at least a year, two years out.

And then when you're thinking through the best deal for the seller and buyer, how do you look at earnouts?