Do not hesitate to contact me with your questions, even if you feel you found the answer on this page. Each request is specific. There are always several ways to achieve your goals.
Depending on your project, there are several tools to choose from. My preferred one is Delphi (Delphi 10.3 Rio) for desktop client/server applications. Either PHP or C#/.NET tech stack is a primary choice for WEB projects. A mobile android/iOS application completes my offering.
It is not uncommon to build a hybrid, on-promises, and public/cloud infrastructure.
The most popular database today for small projects is the MS SQL server. PHP projects are traditionally built on MySQL database. Additional options are available for the multi-platform or the mobile environment.
There is always a risk when one wants to try anything new. The most typical reason for such risk is there are some unknowns. Over the years, I mastered a solid concept of identifying and addressing the most common issues.
See the page Methodology, where you can learn more about my unique approach.
The obvious choices are email, phone call, or my preferred way is videoconferencing. We can use skype, zoom, Microsoft teams or Google's meet service.
There is always an option to meet in person to discuss lengthly issues in more detail.
The remote support is available to any place on the planet.
Such a situation is not rare. I have encountered such problems regularly while working on previous projects.
The very first step is to get the problem fixed. This is the number one priority. There might be several sources of the problem: a user mistake, technical or hardware failure, or an undiscovered bug in the code. You might also need to adjust your application to new legislation requirements or your needs change.
I strongly encourage you to arrange for technical support. You will get help in any situation - regular tasks, unexpected issues, or an independent opinion on the issue at hand.
Part of my approach is offering a "warranty" for a particular period of time, typically one year. Such a warranty will be discussed before I start working on the project. I propose conditions they have worked on in previous projects of similar scope. Both parties benefit from clear rules. Specific terms are always open to discussion.
The typical project scopes from 5 to 60 Man-days. The scope refers primarily to the estimated number of hours that can be expected to be worked on the project. Such an estimate is a basis for the project cost.
However, a five-day project won't be done in a week. Both sides need time to review expectations and consider the best possible approach. Such idle time is not billable to the customer.
The typical time required to complete a custom software project is 1 - 6+ months. More specific rules and deadlines will be discussed as the project progresses.
Not necessary. A web-based application usually requires a computer running 24 hours, seven days a week. Such requirement can be fulfilled by a dedicated computer running in your office. A better option is renting services needed from a service provider. In the most cost-effective scenario, several customers share the same hardware. A dedicated virtual or physical server is an option for the more demanding customer.
If you are concerned about website accessibility in any possible situation (e.g., severe weather causing service interruption), a cloud-based service comes into the picture.