We work as a team and therefore we need to stay organized on the code level as well. We run our own installation of GitLab in our infrastructure and all developers know the best practices of the GIT-flow approach.
We automate as much as we can. The deploy process is as easy as clicking the button. The new version can be released at any stage within a few minutes.
Our infrastructure is based on amazon servers, so it is flexible and scalable. Next to the production environment we typically have DEV and TEST stages for development purposes.
We will build a customized system admin where data and model properties and functions will be stored and accessible for editing.
The user will be able to create a new account and then under login manage his details. Also includes pages needed for password recovery or changes.
Initially we suggest using a 3rd party ordering system chosen by the client (WooCommerce?). If needed, we can create our own solution and connect to payment gate(s) in the future, but the first version should be as simple as possible.
The crucial building brick of the system will be the „Investment project“. The user will be able to create and manage N projects under his account. Input for each project will be similar (or the same) as the inputs in the PacoShip excel tool.
Each project will have the calculated output data in the same format as the PacoShip excel tool. We believe we will be able to shrink those to fewer pages to provide a better user experience. It should be up to 10 analyses (data+chart) in the total.
We will have a lot of questions here. Ideally, we should understand what problems your tool is solving, who is your typical customer and other details. As for the output, we will design your online product from A to Z. Within this milestone, we will deliver a functional prototype explaining the whole user experience, a technical document that will describe any additional logic, and a final design system defining rules related to the user interface.
A minimal viable product version should be the minimum that can be launched in the production environment and will be able to fulfill the purpose of the product. We will take the output from the analysis and will start the implementation work. Whole development infrastructure and processes will be created within this step and will be useful even for further development in the future.
Ideally, we should not stop with the MVP launch. The team will be deeply involved in the project so it is a great opportunity to keep the progress at the same speed and start agile development of any new features and improvements the product will need. We will need to agree on the team size, team velocity, and appropriate monthly budget. Typically, we are working in 2 weeks sprints and deploy a new version at the end of each one of them.