Software development and IT services companies
Delivery teams adopted coding assistants faster than anyone wrote a rule about them, and client contracts often contain confidentiality or source-code clauses that were drafted before any of it existed. The exposure is rarely the tool itself; it is the absence of a decision about which tools, in which configuration, on whose material. We establish that, check it against what your client agreements actually say, and give your delivery leads an answer they can give on the call.
When this usually becomes urgent
Governance work rarely starts from a general wish to be responsible. It starts from an event with a date on it. These are the ones that bring this business to us.
- A client asked whether their source code goes near an AI tool
- Developers are using assistants nobody formally approved
- A new master services agreement contains AI clauses
- You are bidding for work that requires an AI policy to qualify
Where this business usually starts
Not a bundle - three engagements that answer the triggers above, in the order they normally bite. Each is bought on its own, and the badge on every card says how much of the governance model that engagement actually covers rather than leaving you to guess.
Software development and IT services companies
Start with the trigger you already have.
Published ranges, a written scope with its exclusions named, and an honest view of whether the engagement is worth buying at all. Scoping the problem costs nothing.