TL;DR

A feature request is feedback or input for Hubhus and does not include any commitment to implementation or timeline.

Paid development is work that Hubhus agrees to prioritise, scope, and deliver for a customer. When development is handled as paid work, you are paying for prioritisation and commitment — not necessarily for something that will remain unique to your account.

On this page

Jump to any section using the links below

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
• that it will be prioritised
• that it will be added to a public roadmap
• that it will be 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.

What is paid development?

Paid development is relevant when you want Hubhus to prioritise and commit to a specific change, feature, or improvement.

This applies whether the request is:

• highly specific to your business
• broadly useful to other customers
• related to existing functionality
• a new capability or improvement

If Hubhus agrees to handle the request as paid development, this means the work is treated as a committed and prioritised task rather than general product feedback.

In other words, you are paying for:

• prioritisation
• planning
• commitment
• delivery of the agreed scope

Paid development is not necessarily customer-exclusive

Paid development does not necessarily mean that the result will be unique to your account or only available to your business.

In many cases, work requested and funded by one customer may later become part of the broader Hubhus platform if it creates value more generally.

This allows Hubhus to continue improving the product as a whole while still offering customers the option to accelerate and secure delivery of specific work.

When paid development is the right option

Paid development is usually the right option when:

• you need a specific change to be prioritised
• you want greater certainty that the work will actually be carried out
• the request goes beyond normal support, setup, or guidance
• you need an agreed scope and delivery commitment
• timing or business need makes it 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?

As a general rule:

A feature request is the right route if you want to share an idea or suggestion and are comfortable with Hubhus evaluating it as part of normal product development.

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

If you are unsure

You are always welcome to submit your request through the support portal.

If the request appears to be better suited for paid development than a normal feature request, we will let you know and explain the next step clearly.

Summary

Feature requests are valuable product feedback with no promise of build order, roadmap placement, or deadline; paid development is how you buy prioritisation, planning, and delivery of agreed scope when you need commitment and capacity. Paid work may still ship as part of the general platform later. Use the support portal if you are unsure which path fits, and see Free vs Paid Support for how support differs from billable work.

Common searches

feature request • paid development • custom feature • product feedback • prioritise development • roadmap request

Also known as

enhancement request • bespoke development • commissioned work • product idea • professional services

Related articles

Free vs Paid Support
How to Submit a Support Request
Response Times and Service Expectations
Customer-specific Code and Custom Logic
Roadmap Policy (Development folder — link when published)
Prioritised Development (Development folder — link when published)