Over these last 20 years we have repeatedly tuned and fine-tuned "The Stansoft Way".

Business Requirement Development
There are two approaches of software development Bottom-Up Development and Top-Down Development, Our development method is a mixture of both but biased towards the bottom-up approach. i.e. a requirement based approach.

New Technology Development
Interesting new technologies come up regularly, Every Stansoft employee has the freedom to experiment with something different or something new.
When an interesting new feature is incorporated, we wait and watch for a few FUAs (Feature Usage Audits). If we see growing acceptance it is implemented throughout wherever applicable otherwise only limited areas are retained as a showcase so that Business Partners are aware that this technology is available and they can suggest us a modified implementation.

Regulatory Requirement
Whenever a regulatory requirement comes up, our Business Partners inform us of the upcoming requirement which is implemented in time. Sometimes this can become an emergency development right on the effective date.

Testing and Quality Assurnace
We do try to test as best as we can, but since the nature of changes can be varied and development is very rapid, a change made in one area may sometimes affect other areas - one of the diadvantages of object-oriented programming.
We are looking at ways to reduce this and in the process we implemented a software testing system in 2008, since then problems have reduced 20%.

Documentation
The training that we provide is a hands-on training as a result of which reliance of our users on documentation is minimal. Expert users of certain modules train new users also on a hands-on method. When the new user has a doubt or a problem he/she goes to the person who trianed them and only if they are not sure do they call our support line. They are free to contact us on any ofthe support channels we have.
A printed documentation is quite useless as changes happen in the software almost on a daily basis. Entry screens,reports and dialog boxes can change their appearance overnight. And on the other hand the usage of the documentation is occassional i.e.about once in 2-3 months. Due to this nature, we have always had a complete documentation online which is available by clicking Exit -> Online Help in the SharePro.Desktop
To make it more interesting, we are in the process of making a library of videos so that the documentation is more interesting and appealing and can be understood without any help.

Training
At the time of implementation training is imparted to the core team by the Stansoft Implementation person/team. After six months of regular usage, our implementors push these users into the Expert level so that from then on they become the new inhouse Level 1 support for the organization and the branches and clients. After another six months in this level, their skills mature and they will be able to differentiate whether a problem is due to a configuration setup or a software error. The time frame mentioned can vary depending on the number of tranactions handled by the person. More the number of transactions handled faster the learning and fewer the number of transactions slower the learning

Support during the Year End Processing
SharePro EOY process is a two step process. First the masters are rolled over followed by multiple carry forward routines. In the first year this process must be done under observation by Stansoft throughout the process.

Support during Inspections
Please inform us when you receive intimation of inspections and forward us the relevant portions of the requirement list so that if something new is required we are also aware of it.
Alert us on the day of the inspection so that we are ready in case you need any help from us regarding immediate requirements of the inspection teams.

Product Upgrade Paths
Upgrades are provided free of cost for the entire tenure of the licence. All SharePro users across the country and across all sizes use the same software. All SharePro features can be implemented by every SharePro user with our support.

Minimum Notice for Product Withdrawal
So far Stansoft has never withdrawn a product. Withdrawal of products would be in 2 phases i.e. Development De-Tooling would happen first (i.e.new developments will be halted permanently) this would be followed later by Support De-Tooling (i.e.our support centers will be unable to provide support in these areas).

[The first product to be withdrawn would be SharePro DOS for which the Development De-Tooling date has not yet been announced. We are trying to upgrade all our Business Partners from the DOS to the Windows version so that withdrawal would have minimum impact.
If there remains a few users who do not want to change they could theoretically continue using the software, but no further changes would be implemented. Our support centre will continue to provide support till the Support De-tooling takes place.]

Competitive Environment
The present environment is very competitive. Competitors in one area may be collaborators in other areas. Hence we treat our competitors as equals and with respect and deal with them in a fair manner. We shall not disparage their products and services and resort to comparison marketing.

Poaching Of Staff
When joining Stansoft we require a No-Objection from your present employer if your employer is a client or a business partner or any other associate organization of Stansoft.