Business System Consultation Center - Our Business System ColumnVol.96 2020.02.01 Takahashi Minoru

System sovereignty belongs to the user company

Thank you for your interest and continued support.
This is Takahashi from the Marketing Plan Research Laboratory.


What would you do if the IT vendor you commissioned to build your system
goes bankrupt after the system is implemented, what would you do?


“I don’t know,” “They probably won’t go bankrupt,” “Whatever happens, happens”—
Most company presidents probably think along these lines.


I realize this may sound like preaching to the choir,
but the nature of business is that you never know what will happen.
I’m not saying, “We’ll go under first, ha ha ha” (lol).


Joking aside, even if it’s just a verbal agreement,
it’s crucial to have an answer to this matter before a crisis hits—while things are still peaceful.


① Make sure you find a system vendor to take over
Have them find another systems vendor with similar expertise
to continue maintaining the system
(I often receive this kind of inquiry from system vendors planning to liquidate or withdraw from the business)


② Ensure that both the source code and the database
in file format


③ Establish a system
in place


④ Having the assigned SE start their own business
This is surprisingly effective.
If the assigned SE is unfamiliar with starting a business, you can simply set up a company for them.


⑤ Hiring the assigned SE
This often ends up being quite expensive.


In any of the above cases, if the company goes bankrupt and disappears overnight,
the promises will go unfulfilled,
However, since many IT companies do not incur procurement costs due to the nature of their business,
sudden bankruptcies should be rare.
Please make sure to take preventive measures so you can handle the situation calmly.


That's all, Thank you for reading.

------------------------------

■ Previous / Next Column ■

＜＜＜ Next Column Vol.97 - Nothing is less useful in hiring an in-house SE than IT certifications 2020.03.01

＞＞＞ Previous Column Vol.95 - Are you familiar with the concept of non-functional requirements? 2020.01.01

Back to Column List