82,891
edits
Legaltech landscape: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
With gratitude to {{author|Alex Hamilton}} for this categorisation in his excellent book {{br|Sign Here}}, here is a ''functional'' breakdown of the [[contract tech]] landscape — as Alex points out, any of these functions are captured by more than one tool — itself a commercial problem for Vendors, because no-one likes to buy duplications. By way of prediction as to what will fly, what won’t, and what will lumber along the ground like a rhinoceros flapping miniature gossamer wings and wondering why she cannot get airborne, the JC has added commentary along the lines of [[cui bono]] — management or lawyer? — how hard is each to implement, how readily will a legal eagle take to it, if it is implemented, and to what extent does its careless implementation aggravate problems the installation was meant to solve? | |||
{| class="wikitable sortable" style="text-align: left;" | {| class="wikitable sortable" style="text-align: left;" | ||
!<small>Phase</small> | !<small>Phase</small> | ||
| Line 141: | Line 144: | ||
|<small>'''High''': In order for it to be available, let alone working, there must already be a [[military-industrial complex]] of rent-seeking already in place.</small> | |<small>'''High''': In order for it to be available, let alone working, there must already be a [[military-industrial complex]] of rent-seeking already in place.</small> | ||
|} | |} | ||