Flexible Engagement Models for Software Outsourcing

Your software projects will be delivered on time and at the highest standard of quality if you rely on a dedicated development team at Fortech. Depending on specifics of the project, we will recommend one of the following engagement models:

  • the time and materials (t&m) approach, which is recommended for long term projects with specifications that are either vaguely defined or with an unpredictable evolution. It is also advisable to rely on this method for projects that require substantial business knowledge for a specific industry or area of activity that specialists from your partner software house have already acquired (e.g. knowledge about the processes followed in distribution chains from the food industry in the United States). Under this arrangement you would lead the team of Fortech specialists that meets the project’s needs;
  • the fixed price model, in which we work based on time and cost estimates based on the project details you provide;
  • hybrid models, in which parts of the work can be done on a per project basis and others by Fortech specialists permanently allocated to your projects for a certain period of time.

Experience in Multi-site Projects with Mixed Teams

A significant proportion of our new customers expressed their concern regarding our experience with multi-site software projects, where parts of the team act in different locations and where time and cultural differences may impose challenges. We have been working both with software houses and with end customers, in projects with work usually performed at two or more sites (nearshore team at Fortech and client’s team) and even projects where multiple teams located in different parts of the world were involved. Thus we are very seasoned in managing mixed, distributed team projects and can prevent pitfalls that occur in such contexts.

Building Dedicated Nearshore Teams

In a typical collaboration we build dedicated nearshore teams for our client. We may employ other engagement models based on the method of delivery and on the location where the activities take place.


Dedicated team

In terms of the delivery method, we generally create dedicated partnerships. This model implies that we build teams for the long term needs of our client, that are fully dedicated to that client’s projects. The client has the possibility to get involved in the selection and motivation of the team members, being permanently in direct contact with us and benefiting from a transparent workflow and flexible engagement contract.

Time and material model

This model is employed when the total effort corresponding to a project cannot be estimated in advance and the scope of work can be changed during the development process. A charge based on the total effort reported by the team and accepted by the client is issued on a monthly basis.

This approach offers the flexibility to balance team size and project workloads and offers continuous control of time, budget and deliverables.

Fixed price model

In particular cases, we can also accommodate fixed price projects, most effective when the scope and specifications of the software development project are reasonably clearly defined.

Generally, this model is appropriate for projects developed in several fixed price iterations. It indicates clearly what needs to be delivered, when and what the costs will be (on-time, on-budget delivery of projects).


Nearshore team

In terms of location, we normally engage in nearshore collaborations. In this model, teams located at Fortech act as virtual extensions of our clients’ teams. Such an approach assures costs optimization for our clients, due to flexibility and quick resource allocation. Also, it implies that our clients benefit of access to a large pool of software engineers and IT professionals.

Mixed team

If necessary, we can also accommodate on-site presence at the client’s premises.

This implies that the team or part of the team members travel to the client, usually at the start-up of a complex project.

On-site presence may be needed when intense knowledge transfer is required or when the requirements definition and planning stages require direct contact.