Contact Us Platform Source Code Purchase Workflow

Source Code Purchase steps:

1. Building a team
2. Knowledge transfer from to your team and Product Quality Acceptance
3. Making the Source Code Purchase decision
4. Source code transfer
5. Follow-up support

Stage 1. Building a team Platform is a complex software that consists of several components and requires a highly skilled team of software developers for maintenance and feature development.

List of team members for code acceptance:

  • Business analyst
  • Senior Java developer
  • Manual QA Engineer
  • DevOps
  • Senior Vue.js developer
  • Senior Android developer (Kotlin)
  • Senior iOS developer (Swift)

Total: 7 specialists

The requirements for these team roles can be found here. In some cases, we can help clients screen prospective candidates for technical knowledge.

Please note that we recommend allocating a team of 15-25 people for maintenance and feature development. The small team of 7 outlined above is enough to make a start.

Once you have a team in place, we can proceed to the next stage. 

Stage 2. Knowledge transfer and Product Quality Acceptance

Given the complexity of this solution, you should make the Source Code Purchase decision once you have a clear understanding of the Product Quality and whether the software meets your requirements. 

To ensure this, we split the Source Code Purchase into two instalments. The first and smallest instalment corresponds to the Knowledge transfer and Product Quality Acceptance stage. At the end of this stage, you can decide whether you want to proceed with the Source Code Purchase or not. 

This way, you can evaluate the Platform to see if the Product Quality meets your needs and expectations. At this stage, you can onboard team members so they can start to understand and learn the Platform early for better productivity in the future. 

As a result of this stage, you will have a complete understanding of the Platform to make a well-informed Source Code Purchase decision. Your team will be ready to modify the code, maintain the Platform, develop features, and handle full SDLC.

Based on our experience, this stage takes about one to two months.

The Product Quality Acceptance involves a thorough examination of the following components:

1. Back-end (Java EE)
2. Front-end:

  • Web (vue.js)
  • iOS (native)
  • Android (Kotlin)

3. CI/CD on AWS (DevOps scripts)

What is the work process?

1. Product documentation and access sharing

We share all system documentation and provide access to the Source Code on our servers with your team (without the option to download). We provide your team with step-by-step instructions on how to assemble the applications. 

2. Question and Answer (Q&A) sessions
Our team shares knowledge with your team and conducts Q&A sessions (remotely over video calls and chat) about the documentation, settings, development, testing, and everything related to the Source Code and Platform architecture.

3. Product testing by your team
You can test all features (import project/run project, create/test new features, make an introduction to the project architecture and other high priority functionality)

Please find a more detailed explanation here.

Stage 3. Making the Source Code Purchase decision

Once your team completes the Platform learning and examination stages, you have to decide whether you want to purchase the Platform or not. If you choose not to purchase the Platform, you do not pay more. 

The total cost of the platform is €396,000, divided into two instalments:

1. The non-refundable* payment of €46,000 must be paid before you begin Stage 2, “Knowledge transfer and Product Quality Acceptance”.

2. The second payment of €350,000 is due only if you decide to purchase the Platform after Product Quality Acceptance of the system by your team.

* Please note, if you decide not to purchase the source code for any reason, your first payment of €46,000 will not be refunded.

Stage 4. Source code transfer to GitLab

When both parties sign the Code Quality Verification Certificate, the code will be transferred to your GitLab account.

From that moment on your company controls the Source Code and everything about it: databases, infrastructure, and SDLC.

Stage 5. Follow-up support

Additionally, based on your needs, can offer a follow-up support period with direct communication between your team and with weekly calls/meetings of both teams to discuss any issues. 

We estimate this period to last for 4 to 6 months, resulting in almost zero questions a week at the end of the support period.

The cost of the follow-up support period is based on the hourly rates of developers. An additional agreement is needed.