Exploratory POCs are tricky. When you do not have a handle on the internal working, then you cannot be sure of the reason behind its success or failure. Did it fail because the concept is inherently flawed, or did it fail because the implementation messed up?

However, this was not the case with our POC because of the transparency provided by our visual model. This POC was developed in 3 months with Xsemble/Python stack. It not only proved the feasibility, but also gave them a cost effective way of achieving what they wanted.

A manufacturing setup that has 100+ products comprising of 100+ parts each found it challenging to cater to multiple orders. Orders worth a few crores could not be shipped because some small part was not ordered in time.

We developed a searchable product catalog for them, with Xsemble/Java web stack. Different roles are assigned different accesses. The customer team now uses the application to maintain their products, view the Bill Of Material (BOM), and plan their work based on lead time. The product has undergone many enhancements based on customer need since it was first created.

An online gaming application having a high traction needed to be re-engineered from PHP to Java technology stack for performance reasons. The high volume of transactions gave rise to not only a high cloud bill but also delays in a time-critical operation.

We re-engineered the application to Xsemble/Java web stack. MongoDB was used as the backend. For similar load, the new application was tested to do the time-critical number-crunching faster on an ordinary PC than the old application on highly upgraded cloud hardware.

Creation of the competency models involves processing large amount of conversational data from which meaningful information needs to be extracted quickly. Natural Language Processing (NLP) was used for this purpose.

The application was developed with Xsemble/Java web stack. We researched and finally selected a pre-trained NLP engine to use. Later, that NLP engine became one of the components that fit into the larger application.

This kind of association needed a good level of trust from the client side. We could win that because of our ethical and transparent approach. What resulted was a beautiful business relationship.

We turned around their engagements that got stuck in delivery problems. Some other engagements where we were involved from the start proceeded smoothly and uneventfully.

An IoT company needed these applications based on BACnet protocol developed with Java stack within the hard deadline. They did not have a Java team, and the new developers who came aboard did not have any BACnet exposure. However, to everyone's amazement, we pulled it off. The applications were neatly embedded within docker containers and shipped to their client, within the deadline.

How? → Our visual model of the software enabled inhouse domain experts to contribute meaningfully, and the freshers found it easy encode well-defined business logic within auto-generated code templates.