You’re thinking of a time when only “computer geeks” could install and run the software of their choice. When every office had fleets of IT admins to install the pre-approved applications people needed for their day-to-day.

Back then, learning how to manage your own PC and install software was tantamount to earning an IT certificate. Doing so for a few years in high school would be enough to qualify you for a career in IT.

So I politely disagree. The industry was never able to ship software that a non-technical person could install. Especially not B2B, but barely B2C as well.

"The industry" sold software in the 1980s that had use instructions like "Insert disk 1 and press the 'Reset' key to load".

In the very early 1990s, something like "Insert disk 1 and click the disk icon, then click <name of application>". Installation to the hard disk was optional, and might be one or two steps.

Later in the 1990s, installation was pressing "Next", "Next", "Next" after inserting the CD.

Yes, and now we have to deal with security theatre, whether it is corporate, or pushed on us by our OS.

Software has to handle much more hostile environments.

> You’re thinking of a time when only “computer geeks” could install and run the software of their choice.

Perhaps not thinking of a "time when", perhaps thinking of an OS that required an IT certificate.

Because even early Macintosh System Software (classic Mac OS before OS X) was bewildering to Windows users, since any user could "drag" a program from a floppy disk onto their hard disk, leave it anywhere, and it worked.

Arguably, OS X introduced the Applications folder in 2001 partly to give people a place to drag things to and feel more comfortable that's where they could find their "Program Files" (but mostly so multi-user system users would get to add and re-use apps in a common clear place they "should" be).

But you still didn't need an IT admin.

We do it right now on Android and Ubuntu.

Installing software means clicking the button, waiting, clicking yes on some permission prompts, and logging in with Google.

The only thing about any other software I can think of, that would be inherently any harder, is if it involves domain names and certificates. Which is a problem we should be working to solve, and I'm still annoyed at Mozilla for cancelling FlyWeb.

Unless you're such a big company you can definitely afford IT staff, you're probably not doing anything that needs separate services or a database or anything beyond one executable with SQLite, same as consumer apps.

Windows 7 Enterprise?

Mac OS X Server?

The vast vast majority of SaaS products talked about on HN are probably not even 1/10th as complex.

"But we want it to run on our chosen database product."

"But we want it to integrate with our single-sign on product."

"Our security team scanned it with our chosen tools and you have to fix these things before we will deploy it."

"We aren't willing to make those network changes to allow it to run."

"We won't allow it to connect to our <foobar> server but it is a requirement to connect to our <foobar> server if it is going to be hosted internally."

This is the stuff that makes "enterprise" deployments difficult. Oh and they want you to hold their hand through it but they aren't willing to pay for consulting.

> Oh and they want you to hold their hand through it but they aren't willing to pay for consulting.

These sound like tire kickers and un-serious customers, why focus on their expectations?

Serious customers, almost by definition, are willing to pay for custom work they want done.

I'm speaking from my experience selling both software and services to the Fortune 500. If they can cut a corner, slow pay you, try to do it themselves without paying you, etc - they will. Billions in profits but they will refuse to pay a $10K invoice just to spite you.

And in my experience you have to provide a lot of this up front BEFORE the contract is signed otherwise they won't even evaluate whether they will purchase it.