Websockets Return on Investment (ROI) (Part 2)

I was expecting more criticism for the generalized call that was made in part 1 of our ROI for real-time web projects. Because it sure is possible to measure certain parameters when you want to future-proof your web projects.
Below I will show you some important things to consider when starting a realtime web project, regarding your return on your investment.

The first thing to do

The first thing you should consider is the selection of developers. Many call themselves web developers, but far from any guarantee that your application is designed for the future. Responsive design is easy to check off but what about the database, code-language and choice of hoosting partner? Beautiful and cool is not equal functional

The Second thing

The second thing you should take into consideration are: do the developers work with standardized frameworks? For you as a client, this is vital. What happens if you want to re-place the web producer in the middle of the project and no one can continue with the work they started?!

The Third thing

The third thing you must do is to read about the different options that are out there. If your manufacturer chooses a framework that requires 2000 lines of code to run your application in realtime when there is others that can be implemented with only 25 rows and performs the same function as the first.
Why shell you pay for the time that the extra 1975 rows takes to write?

Entire systems

For those who want to upgrade their internal systems, I would like to point out difference between choosing a framework that is self hosted over cloud-based services. Do you really want to send data out of your system and back just to increase speed, when you can get better performance while retaining all the data inside your firewalls?! I guess not.
Or like Phil Leggetter - Real-Time Web Software and Technology Evangelist says in his tweet October 26, 2012:

If you're looking for a .NET self-hosted solution then XSockets, SuperWebSockets & Alchemy are options. 

At last

The last thing you should consider is the proof of concept. Have your web agency done anything like this before? Or are YOU their proof of concept?
Today there are a lot of applications that are only created just for proof of concept. The market is so young. And then the side effect of a variety of applications which only serves to show what can be technically.
You want the customer benefit. You want to make money from your application.
Ensure that this is the case!