| No general counsel yet | CEO, CFO or owner | The founder or a finance or operations manager, sometimes asking outside counsel | Price, setup effort, whether it cuts outside counsel hours | Nobody owns the legal problem; legal software competes with every other budget line |
| First general counsel | The GC, inside a budget the CEO or CFO sets | The GC personally | Time saved on contracts and requests, ease of use, fit with tools the company already runs | The GC's own calendar; a one-lawyer team has little room for a long evaluation |
| Small legal team, no legal operations | The GC or CLO | A deputy GC or senior counsel who owns the area, such as contracts or privacy | Fit with how the lawyers already work, adoption, an IT sign-off | Evaluation is nobody's job; procurement and IT security show up late |
| Department with legal operations | The GC or CLO; legal ops may decide some AI purchases while accountable to the GC | Legal operations, which often makes the pick | Roadmap fit, data, integrations, total cost, adoption measures | Competing projects on the legal ops roadmap; build versus buy |
| Enterprise with procurement and IT security | The GC or CLO, plus procurement and finance approval thresholds | Legal operations with IT, security and procurement | RFP answers, security review, contract terms, AI governance, pricing transparency | Security questionnaires, contract redlines, AI review, AI choices tied to the company's wider AI program |