Software-as-a-service: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|tech|}}[[Software as a service]] — fondly known as [[SAAS]] but known to [[user]]s as [[rent-seeking]] as a service — is | {{a|tech|}}[[Software as a service]] — fondly known as [[SAAS]] but known to [[user]]s as ''[[rent-seeking]]'' as a service — is [[rent-seeking]] by means of [[intellectual property]] or some other kind of monopolistic behaviour. It is also basically the only business model [[reg tech]] entrepreneurs — a.k.a. refugee managing associates with [[School-leaver from Bucharest|JavaScript developers from Bucharest]] they found on the dark web — can figure out. | ||
The equivalent of selling a warranty on a toaster. Charging a running cost for a software application which shouldn’t ''need'' a lot of maintenance, unless you ''built it'' to need maintenance. | The equivalent of selling a warranty on a toaster. Charging a running cost for a software application which shouldn’t ''need'' a lot of maintenance, unless you ''built it'' to need maintenance. | ||
If your software were any good you would design a [[user interface|user-interface]] easy enough for the [[meatware]] to deal with ''so you didn’t need a service contract''. Right? | If your software were any good you would design a [[user interface|user-interface]] easy enough for the [[meatware]] to deal with ''so you didn’t need a service contract''. Right? | ||
===The [[reg tech]] business model conundrum=== | |||
{{quote|'''Lesson one''': Insist on an unsupervised pilot where ''real'' users get to push and pull the product by themselves without help from the vendor, and not just a chaperoned proof of concept where the software vendor can control inputs and outcomes to make the product seem satisfactory.}} | |||
It is a familiar experience amongst buyers of [[reg tech]] and [[legal tech]] that hawked products do fabulously when demonstrated to the [[general counsel]] at the pitch (often by performing some kind of [[magic]] on a pre-prepared [[non-disclosure agreement]]), but underwhelm upon implementation when set upon by the [[morlock]]s who actually need to use them to solve real-life problems. | |||
This is partly because the yen to be [[thought leader|thought-leading]]s [[agent]]s for [[step-change]] in their industry, plays to a [[general counsel]]’s innate credulity and weakness for flattery, but has a profounder operating cause: [[reg tech]] struggles mightily with a business model that ''scales''. [[Reg tech|reg tech]] strives to automate [[tedious]], repetitive and manual tasks, thereby removing a significant cost item from the departmental budget, and accelerating and improving the output quality at the same time. | |||
===Then there’s [[blockchain]], of course=== | ===Then there’s [[blockchain]], of course=== | ||
The latest iteration — talked about in tones of reverent optimism [https://www.forbes.com/sites/ilkerkoksal/2019/10/23/the-benefits-of-applying-blockchain-technology-in-any-industry/#7253848c49a5 here] — is “[[blockchain as a service]]”. But a service to whom? And did I hear a siren going off? | {{bs}}The latest iteration — talked about in tones of reverent optimism [https://www.forbes.com/sites/ilkerkoksal/2019/10/23/the-benefits-of-applying-blockchain-technology-in-any-industry/#7253848c49a5 here] — is “[[blockchain as a service]]”. But a service to whom? And did I hear a siren going off? | ||
{{sa}} | {{sa}} | ||
Revision as of 09:13, 7 February 2021
|
JC pontificates about technology
An occasional series.
|
Software as a service — fondly known as SAAS but known to users as rent-seeking as a service — is rent-seeking by means of intellectual property or some other kind of monopolistic behaviour. It is also basically the only business model reg tech entrepreneurs — a.k.a. refugee managing associates with JavaScript developers from Bucharest they found on the dark web — can figure out.
The equivalent of selling a warranty on a toaster. Charging a running cost for a software application which shouldn’t need a lot of maintenance, unless you built it to need maintenance.
If your software were any good you would design a user-interface easy enough for the meatware to deal with so you didn’t need a service contract. Right?
The reg tech business model conundrum
Lesson one: Insist on an unsupervised pilot where real users get to push and pull the product by themselves without help from the vendor, and not just a chaperoned proof of concept where the software vendor can control inputs and outcomes to make the product seem satisfactory.
It is a familiar experience amongst buyers of reg tech and legal tech that hawked products do fabulously when demonstrated to the general counsel at the pitch (often by performing some kind of magic on a pre-prepared non-disclosure agreement), but underwhelm upon implementation when set upon by the morlocks who actually need to use them to solve real-life problems.
This is partly because the yen to be thought-leadings agents for step-change in their industry, plays to a general counsel’s innate credulity and weakness for flattery, but has a profounder operating cause: reg tech struggles mightily with a business model that scales. reg tech strives to automate tedious, repetitive and manual tasks, thereby removing a significant cost item from the departmental budget, and accelerating and improving the output quality at the same time.
Then there’s blockchain, of course
The latest iteration — talked about in tones of reverent optimism here — is “blockchain as a service”. But a service to whom? And did I hear a siren going off?