Feature Requests vs Paid Development

Modified on Fri, 8 May at 1:36 PM

Feature requests vs. paid development

Every feature we build goes into the platform for all customers. We never build something exclusively for one account. The difference between a free request and paid development is purely about timing and priority.

TL;DR

Free feature request = submit the need → we evaluate → if it fits the platform, it enters the roadmap (no timeline guaranteed). Paid development = we pause the current roadmap and prioritize your request next. The feature is still built into the platform and released to all customers — what you pay for is the priority, nothing more.

3 things to understand

1

All features go to all customers

Hubhus is a shared platform. Everything we build — regardless of who requested it or who paid for prioritization — is released to every customer. We do not build customer-specific features or private functionality. When a new capability ships, all accounts on the platform get it.

2

Paid development = buying priority, not exclusivity

If you need a feature sooner than the roadmap allows, you can fund its prioritization. We pause ongoing roadmap work and build your request next. You pay for the time it takes to move your need to the front of the queue — the result still ships to everyone. Free requests follow the standard roadmap order with no timeline guarantee.

3

How to submit a request

Submit via the standard support ticket form. Describe the business need and why timing matters. We will evaluate fit for the platform and respond with either a roadmap note (free) or a scope and quote (paid prioritization).

Read more⌄

What is a feature request?

A feature request is an idea, suggestion, or input about something you would like to see added, improved, or changed in Hubhus. Feature requests help us understand customer needs and may influence how we improve the platform over time.

However, a feature request should be understood as feedback — not as a confirmed task, project, or delivery commitment. Submitting a feature request does not guarantee that it will be implemented, prioritised, or delivered within a specific timeframe.

How Hubhus handles feature requests

Hubhus continuously evaluates ideas and suggestions based on overall value, product direction, customer impact, technical considerations, and available capacity.

We do not operate with a fixed public roadmap. Our internal planning is handled in an agile way, which allows us to change direction quickly when we identify higher-value opportunities or more important priorities.

This means that even relevant and well-founded feature requests may not be implemented, or may be implemented later than expected.

When is paid development the right option?

Paid development is usually the right option when:

you need a specific change to be prioritised and committed to
the request requires Hubhus to pause ongoing roadmap work
you want greater certainty that the work will actually be carried out
timing or business need makes delivery important for your organisation

If a request requires Hubhus to change priorities and allocate development capacity to a specific task, this is typically handled as paid development.

Feature request or paid development — which to choose?

Feature request is the right route if you want to share an idea and are comfortable with Hubhus evaluating it as part of normal product development (no timeline).

Paid development is the right route if you want Hubhus to actively prioritise, scope, and commit to the work on a defined timeline.

If you are unsure

You are always welcome to submit your request through the support portal. If the request appears better suited for paid development than a standard feature request, we will let you know and explain the next step clearly.

Common searches

feature request • new feature • paid development • product roadmap • custom build • request feature

Related articles

Free vs. paid support
Customer-specific code and custom logic
How to submit a support request