• Professional Java Server, iOS and Android Programming

How we work

How We Work

Here is the structure and the phases of a typical project, it includes standard contract terms, operational structure etc. The structure may vary on a project-to-project basis; this is dependent on the client’s preferences or organizational structure.

To measure if an effective partnership is possible we will first start with a pilot project – a project which will test if we are the right fit for you and if the partnership can work. At the same time it limits the risks for the customer – we cover the risks for you.

The typical steps may include:

  • Sign NDA (just to make it easier) and simple agreement
  • Preparation of the pilot project specification with success criteria defined.
  • If we do not think the project is the right fit for both of us, we walk away.
  • After the preliminary discussion, we will prepare and deliver the initial time and price estimations for the pilot project (project analysis and/or specification). All free of charge.
  • If you are satisfied with the result, we will deliver the pilot project as planned and defined previously. Again, free of charge.
  • During this pilot project you have the opportunity to evaluate all aspects of our partnership.
  • When the project is delivered, you decide if you pay for it or not. You will get the full rights to the software only if you pay for it.

When we are both ready to proceed with the main project, the typical steps are:

  • Sign the standard (frame) contract
  • Define the project type (fixed price, T&M) and project structure
    • In the case of a fixed price project, we will agree to define the project stages and success criteria for the stages. The invoice will be issued after each stage is accepted (to be paid within 20 days)
    • In the case of a T&M project the work is defined on a case by case basis by the project management team. We issue an invoice monthly (to be paid within 20 days).
  • Define responsibilities on both sides and have a communication structure, change management, success criteria, QA
  • Establish project tools and standards (including reporting tools, issue repository, source code repository, project management, timesheet etc.)
  • The developers meet to discuss technology and knowledge transfer. This is typically a face-to-face meeting or videoconference.
  • The project will grow gradually from a few developers to the maximum required capacity. The number of developers might change during the project based on the customer’s requirements.
  • The Project’s progress is monitored as per the agreement in the contract – standard weekly reports, timesheets, meetings, mail communication, IM communication, face-to-face meetings. The latter, Face-to-face meetings are preferable when a new project phase (stage) is being defined.

Types of the projects

Fixed price projects

  • Pros: If clearly defined, it is easy to deliver, test and verify the deliverables
  • Cons: Requires a detailed specification up front, less flexible, not easy to incorporate into a changing business environment.


T&M projects

  • Pros: flexible, easy to fully utilize resources, no need to specify a lot of documentation upfront
  • Cons: developers must be closely managed – new pieces of work must be defined in regular intervals, this type of project requires constant communication.


Mixed approach– we would recommend this approach:

  • From the beginning, use T&M model, to get all the developers familiar with the project
  • Then transfer to bigger project chunks (with the key developers as team leaders for their sub-projects) – fixed price projects.
  • The knowledge transfer period will take time from your in-house development team (lower productivity).
  • The initial knowledge transfer is best face-to-face.
  • It is essential to have the project infrastructure set-up properly (issue database, source code repository, automatic build systems etc.). We have all of this in place now and we can set it up for you when required.