Skip to content
Sign in
  • There are no suggestions because the search field is empty.

From feature request to release: our process from idea to working feature

When you share a new feature idea with SyncForce, there are a few clear steps before it becomes a working feature in your environment.

To manage expectations and investments transparently, we distinguish between:

  1. A first conceptual outline and ballpark estimate

  2. A detailed solution design and investment estimate

  3. A funding proposal that determines the priority level

  4. Planning and delivery in one of our major releases

In this article we explain each step in more detail, how your input is used, and how funding influences whether a feature becomes Level 4, Level 5 or Level 6 in our priority model.

For the full description of the L1 to L6 priority levels, see:
How SyncForce prioritises and plans new features.

1. First concept and ballpark estimate

When you share a new feature request, we start with understanding the context and intent rather than directly estimating effort.

To prepare a first conceptual outline and a ballpark estimate, we ask you to provide at minimum:

  • A short deck or description of the current situation

  • The main challenge or opportunity

  • The requested solution direction at a high level

Based on this, our team creates a first outline of the possible solution in SyncForce and a rough investment indication. This ballpark is not a quote and the feature is not yet planned. Its purpose is to help you decide:

  • Do we want to move forward and invest in a detailed solution design?

  • Do we want to consider funding or co funding this feature to increase its priority?

If you decide not to proceed after the ballpark, the idea can still remain on our generic backlog as an unfunded Level 6 request.

2. Detailed solution design and investment estimate

If you indicate that the ballpark investment is worth considering, we move to a more detailed Invest phase.

For this step, we need more complete input, typically in the form of a deck or document covering:

  • A clear as is analysis of the current process, data and systems

  • A detailed description of the desired to be situation

  • A more concrete requested or suggested solution direction in SyncForce

Based on this input, our consultants and product team design:

  • A detailed functional and technical solution

  • The required configuration and development scope

  • Dependencies on other features, data or integrations

From this design we create a more accurate investment estimate. At this stage, we still have not assigned a development slot in a specific release, but this estimate forms the basis for a formal funding proposal.

Internally, these Invest requests are also prioritised so that the oldest and most critical ones are worked out first.

3. Funding proposal and priority level (L4 or L5)

Once the detailed solution design is aligned with you, we send a formal proposal for:

  • 100 percent customer funded development, or

  • 50 percent co funded development (SyncForce and customer both invest)

Only after this proposal is accepted and the order confirmation is signed, the feature gets a concrete priority level in our roadmap:

  • Level 4 for 100 percent customer funded features

  • Level 5 for 50 percent customer funded features

Within Level 4 and Level 5, features are then planned on a first in, first out basis, using the order confirmation date as the date stamp.

If you choose not to fund the feature after receiving the proposal, the request can still remain on our Level 6 backlog as an unfunded item. In that case, SyncForce will decide if and when it can be picked up as part of the standard SaaS roadmap, based on overall impact, number of customers requesting it and available capacity.

For the full explanation of the L1 to L6 priority model, see:
How SyncForce prioritises and plans new features.

4. Planning, development and release

Once a feature is funded and assigned Level 4 or Level 5, it enters our planning and delivery cycle.

We work with:

  • 3 week development sprints

  • 16 major releases per year, delivering around 200 new or improved features annually

When we plan a feature into a release, we consider:

  • Its Level (4 or 5) and order confirmation date

  • Dependencies on other planned features

  • The capacity of the relevant development teams

  • Time needed for data preparation or configuration on your side

After development, features go through testing and quality checks before they are included in a major release of SyncForce. You will see the planned release number in our communication and in the Release Journal once it is confirmed.

For unfunded Level 6 features, there is no fixed timeline. These items are funded by SyncForce as part of the SaaS licence and are planned only when there is room next to higher level items (L1 to L5).

In summary:

  • Ballpark and design help clarify scope and value.

  • Funding decisions determine whether a feature becomes Level 4 or 5.

  • The priority level and order confirmation date then decide when the feature can be planned into a release.