Skip to content

Two forms for different development needs

Fixed project or dedicated team?

Do you want to have software built but are unsure whether to choose a fixed project or dedicated developers? The main difference lies in what is agreed in advance. With a fixed project, we agree on a clearly defined assignment. With dedicated development, APPelit makes development capacity available and you decide which tasks get priority.

  • 01Fixed project
  • 02Dedicated team
  • 03Development capacity
  • 04Software development

A fixed scope or available capacity

Where is the difference?

With a fixed project, it is clear in advance which functionalities need to be realised. You provide the functional specifications, desired operation and relevant starting points for this. APPelit works out the technical realisation and carries out the agreed development, testing and QA work within the defined scope.

With dedicated development, the focus is not on a fully predetermined end result, but on the available technical capacity. You determine, from within your organisation, which tasks are on the backlog and what priority they receive. This provides room to bring forward other development tasks during the collaboration, without having to specify all future functionalities in advance.

Two professionals discuss data and graphs during a business meeting.

Collaboration

Your course, our craft

You know your organisation, your processes and your users best. That is why you make the functional choices, and we make sure the technology fits them seamlessly. We are happy to think along, while you stay in charge.

Where you set the direction

  • Your business strategy and how IT supports it
  • Standard software or custom build: what fits best
  • Package choices and how your processes map onto them
  • The functional requirements for the custom build
  • Which data needs to move to the new system
  • Rollout and training of your users

Where we deliver the technology

  • Technical specification of the custom build
  • Software development
  • Testing and quality assurance (QA)
  • Software security
  • Technical execution of the data conversion
  • Hosting and monitoring

Clear roles, one shared result

Clear in advance what needs to be built

When fixed?

A fixed project can be suitable when the desired functionalities are sufficiently detailed to define the assignment in advance. Think of a new application, a specific module or an extension for which user roles, operation and relevant dependencies have already been described. Based on this, scope, work, planning and price can be agreed upon.

If the functional specification changes during the project, or you wish to add extra functionality, the required technical implementation may also change. This work does not automatically fall within the original assignment and can be assessed and carried out separately. A fixed project therefore mainly offers clarity when the desired outcome is sufficiently concrete in advance.

Capacity for ongoing development

When dedicated?

Dedicated developers may be a better fit if you want to develop, expand or renew software over a longer period and want to decide yourself which work is picked up and when. APPelit makes the agreed technical capacity available for this. Depending on the need, this can be one developer or a team with multiple technical disciplines.

You determine the functional direction, manage the priorities and provide the necessary specifications and feedback. With an agile or Scrum way of working, product ownership and scrum master tasks are fulfilled from within your organisation. APPelit focuses on the agreed technical execution. This approach can suit, for example, existing business software, SaaS platforms and other applications that are regularly extended. You can read more about this under dedicated developers.

Look at what is already known in advance

Which form fits?

Are the functionalities fully described and would you like a clearly defined assignment to be realised? Then a fixed project may be a good fit. Would you rather have development capacity available over an agreed period and be able to adjust priorities yourself? Then dedicated development is more appropriate. Neither form is automatically better; they divide scope, capacity and management differently.

Is technical insight into existing software needed first before work can be properly scoped? Then a software audit can provide insight, as a separate step, into the code examined, the technical setup and points of attention. The outcomes can then be used as technical input when determining the follow-up assignment.

Abstract glass shield as a symbol for information security
ISO 27001 · NEN 7510

Information security

Secure by design. Demonstrably.

Do you work with personal or healthcare data? Then you want to be sure that your software partner handles information carefully. APPelit is ISO 27001- and NEN 7510-certified.

ISO 27001

The international standard for information security. Risks, access and incidents are recorded in a management system that is periodically assessed.

NEN 7510

The Dutch standard for information security in healthcare. Important when your software works with medical or health data.

  • Security requirements included from the very first specification
  • Test cases that align with recorded security requirements
  • AI functions also fall within the same data agreements
More about ISO 27001 and NEN 7510

Contact

Discuss your question

Leave your details. Within 24 hours, a specialist will contact you for an introductory meeting.

We only use your details to respond to your request. Privacy statement