Is developing non-interoperable software always a bad thing?

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Pretend that you are a single-person software shop and you design something that you think has value. For lack of better example say its patient record software at a hospital that does something "revolutionairy" (no I'm not developing for medical industry it has too many big players and its already Been Done(tm).)

Now you can take a year to fully develop the system on your own time and dime. You put a lot of soul and creativity into it and feel that you should be rewarded when you market it. But after you have a few sites using it (made a handful of money and the prospects are looking good for more rollouts) all of a sudden some big businesses see it and say "there is money in that, lets get something on it!".

They put a 6 man team on developing the same software to compete with yours. They've stolen any creative ideas you had and market them as their own. Two months later they've developed the same sort of system and because they are a big company they already have friendly business with the medical industry, already have them using 10 other products of theirs and have support contracts etc.

So the hospital say "gee whiz, why pay $40,000 for the independent's solution when these friends of ours will sell it to us for $30,000 and we already have positive relationship and track record". Hospitals all around start buying the big names solution and not yours. You effectively can't compete.

Now what if the software (patient record system) has to operate with other sites (hospitals) and medical record repositories (government ones). Say you design your system so that it won't operate with any other type of client somehow even if they reverse-engineer the system. Do you think it is right to make your system non-interoperable on purpose in this situation? By having the market adopt your solution first you will have critical mass if you get say 100 sites to use it by the time your competition has theirs ready. Any potential customer will say "hrm these 100 sites use the independent and that is the ONLY way I can communicate with them". They would risk the reason for the system in the first place (to share medical records between sites) just to save $10,000 so they would see it as a must and go with you.

We always scold big companies that do it but do you think its okay for an independent if its the only way they can protect their creative invention?

Patents don't matter. Intellectual property is a joke. If you patent your system do you realize how long it will take to have the patent approved (sure you can use patent pending as defense) but the big companies can just tie you up in court for years before you see anything out of it. And by then they've sold millions of dollars of the software and you won't get a cent. Sure you get the court to rule in your favour but by that time your software has failed because you've spent every day in court trying to go after them. The court may make the company kick a few bucks to you but you wont get what you "could have made" because that is all theoretical and they avoid that stuff.

So the law and patents won't help. And then what happens when the socialized healthcare system (Canada) comes back and says "Hey our friends at Big Company say that you won't let your software work with theirs. We can't afford your prices because we are in big debt and can't give more money to the healthcare field. You charge more than Big Company, the one that lines our pockets during campaign time (or some crap), so you know, we are forcing you to open up your software and allow the other companies to communicate with yours because you are a monopoly" or something similar which could easily happen.

Question is how can you even compete? Should you just outright sell your system after its done? That way you have no headaches of support, continued development and competition. (This of course would result in you making lots less money...you might only make 1/4 what you would have if you maintained the control)

How else can you compete?

Cliff notes: do you like brown spots on old lady hands?
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Originally posted by: Farfrael
Sue big company, make even more bucks

Like I said that would take forever :p Surely it would be more favourable to avoid legal problems.
 

DAGTA

Diamond Member
Oct 9, 1999
8,172
1
0
I worked for a guy that was doing exactly this. He was writing medical software and selling it on his own. It's a ton of work and travel and communication but you can succeed. He's made millions so far and built a client base of over 100 medical facilities. Aim for a underdeveloped niche market and go from there. Build a reputation and don't worry about always being the cheapest. If you have a good reputation (stand by your product, fix bugs quickly, good people skills) there are hospitals and facilities that will pay the extra for your product.

It is tough, but not impossible. I've seen it work first hand.
 

Farfrael

Senior member
Mar 6, 2002
312
0
0
my answer was half a joke, would take too long to explain but i DO strongly believe that all software should be able to interoperate
problem in your case seems to come from being copied.
Try to follow the solution open source software developpers adopt : offer services, customisation etc. If your product is really good and brings something needed try opening it and bring some people on the project (haven't got much left to loose if the big boys have already developped a competing solution ...)

Edit : Dagta's right, reputation and close contact with the poeple are worth a lot when decision time comes
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
DAGTA:
But has the competition seen his niche market yet? If not they soon will (hes making millions) and if you have over 100 medical facilities using it then someone will begin to take notice. That is what I worry about.

The initial rollout of it would be successful and you may get say 100 places using it but say you were targetting 1000 and the other company gets the other 900 remaining that would have probably bought your system had they not been in bed with big company who has more marketing ability, man power, money and whatnot.

BTW Did your friend make his software non-interoperable (if it needed to communicate) with competitors?
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Offering services and customisation would yield a lot less money I'd bet. I wouldn't want to live off support contracts :( On top of that big businesses and hospitals run critical stuff so they (wrongly) equate free with being sh!t. The more money they pay they tend to see it as insurance. Its a crooked view but thats the way it works.
 

gunblade

Golden Member
Nov 18, 2002
1,470
0
71
The way I see it is that the age of monopolizing a market to get the maximum profit is long gone. Now is an age of working with standard. I think utilizing your early entrance to the market to maximise market share and then make a standard interface that other late-comers would have to conform to. I think living of loyalty fee is much easier than competing with non-interoperable interface since the big corporation have too much money and other market power to crush you.

Well, making the standard/loyalty way also depends on how mature the niche market get in the near future.
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Originally posted by: her209
If you are making so much money, why not hire more people???

Hire more people for what though? I'm not making money and this is a theory but a realistic scenario too ;) Hire more people to help roll it out faster and make the sales first? or what?
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Originally posted by: gunblade
I think living of loyalty fee is much easier than competing with non-interoperable interface since the big corporation have too much money and other market power to crush you.

The whole idea about critical mass is that you quickly gather a strong piece of the situation. For example, say you have 500 potential customers and you manage to sell it to 100 people. The other 400 looking at buying the system will want their software to work properly and be able to communicate with the others. They would go for the software the critical mass has otherwise they would be isolated. In that situation it doesn't matter what the big corporation has (unless of course the government some how forces you to open up your software).
 

DaveSimmons

Elite Member
Aug 12, 2001
40,730
670
126
Making it interoperable is nice but in this case I'd agree with keeping the interconnections proprietary, at least until you gain enough market share in the niche until you become the standard and people are committed to your program.

My employer uses a proprietary, unpublished file format for our data files. We've had a few requests from other companies to give details to the format, but we can't really afford to at this point.

Open source and services income? That's a very risky change to the business plan. Our customers have their own IT people, so they would pay us little or nothing for services and do any such work in-house.

How often has anyone reading this paid extra for services on the software they use? Some do, but most people get by with whatever free support services are offered, and do any customizing through in-house work or hiring low-bid local contractors.
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
Thanks for the feedback DaveSimmons

Ever notice how cheap businesses are too? Most people don't want to pay for services. They will call you up and ask for something but don't want a bill.

Thats why I think I'd rather stick to the system cost. The question becomes how big must you grow before non-interoperability is a Bad Thing(tm) ? When does the idea stop being yours and others should be able to make the same thing? After 1 million dollars in sales? 10 million? 100 million? I don't know the answer but I'm willing to hear feedback on it.

Should it be indefinite since you were the one who conceived of the unique idea and implemented it? Should those who "borrow" your idea have some sort of entitlement or right to be able to profit from it?
 

her209

No Lifer
Oct 11, 2000
56,336
11
0
Originally posted by: DWW
Originally posted by: her209
If you are making so much money, why not hire more people???
Hire more people for what though? I'm not making money and this is a theory but a realistic scenario too ;) Hire more people to help roll it out faster and make the sales first? or what?
Yes, hire more people to get the software programmed and rolled out faster. BTW, how did the "big" company get a hold of your software? Did they install it and then reverse-engineered it?
 

DaveSimmons

Elite Member
Aug 12, 2001
40,730
670
126
One thing we're careful about is concentrating on sales of a reasonably-priced annual site license rather than a high up-front cost and/or paid upgrades.

With an annual fee we have good ongoing revenue without needing to add bloatware to our product (pointless look-and-feel changes, new features 99% of our users get no value from, etc.). It also acts as a slight against competitors who are following the one-time-sale plus upgrades model.
 

DAGTA

Diamond Member
Oct 9, 1999
8,172
1
0
Originally posted by: DWW
DAGTA:
But has the competition seen his niche market yet? If not they soon will (hes making millions) and if you have over 100 medical facilities using it then someone will begin to take notice. That is what I worry about.

The initial rollout of it would be successful and you may get say 100 places using it but say you were targetting 1000 and the other company gets the other 900 remaining that would have probably bought your system had they not been in bed with big company who has more marketing ability, man power, money and whatnot.

BTW Did your friend make his software non-interoperable (if it needed to communicate) with competitors?
He's not really my friend anymore. ;)

There was already competition from some big names when he entered the market.

He makes most of his money on the support contracts, I think. The way he makes his money is by working long hours and very hard. He works about 12 hours a day when home and travels usually two or three times a month to be onsite. Not much of a life outside of work but he's successful. Reputation is the key. You can still enter the market, and have some small first years, but if you build that reputation, you can succeed.

His software is created to the federal standards. He's willing to write interfaces and conversions (propietary per client) for other software for a fee. I wrote one of the interfaces when I worked for him.

-DAGTA
 

DWW

Platinum Member
Apr 4, 2003
2,030
0
0
her209:

No I didn't even write this but I've been thinking it might be possible for a few things I've wanted to do.
It doesn't matter how fast you write the software. It will remain under the radar until its first used so one person could take 10 years making it. But when a few places start using it others will hear about it.

As far as reverse-engineering software you can still design systems to not communicate with other 3rd-party solutions even if they figure out your protocol. Using a combination of certificates and centralized authentication you could design your software to only communicate with peers that have been verified running your software and legally own a license to it. Quite simple.