If your customers request new features, do you implement them for free of for a fee?

Question

Sergey Koshevoy · Accepted Answer

For free but we use it as a hack to sell big Enterprise licenses

M Anees · Answer

It's depend on the situation. If the hange is align with our product road map and benefits a large no of user, we may consider implementing it :)

Carleigh Griffiths · Answer

For me it's depend upon the situation and complexity of feature.

Faisal Ishaque · Answer

That's a nice question. At the moment, we are not at a stage to take customer requests for features directly. We closing the loop currently i.e. Bring users to the website (done), get them to post a job/event (done), get Talent to make an offer on the job/event (done), get the customer to hire/pay (pending).

However, a product should provide value to the customers and make money for the stakeholders. If I can get the customers to pay for a feature (strategically), then I'll for sure get them to pay for it.

Tymek Zapała · Answer

@dcupl Yes, that's a good way to look at it. I have similar thoughts.

Janak Patel · Answer

It depends on the feature; small improvements may be free, but larger, custom features typically come with a fee.

Kushal Gandhi · Answer

It depends on the scope—simple tweaks might be free, but bigger features usually come with a fee. 😊

AlexisNavarro · Answer

It really depends on the feature and its complexity. For small, quick changes, we usually include those at no extra cost. But for bigger requests that require more development time, there might be a fee. We always discuss this upfront with our clients to make sure everyone's on the same page.

Tymek Zapała · Answer

@carleigh_griffiths Yes, complexity of feature is a big factor. Nothing worse than spending a lot of time on feature that will be used by only one user or none at all.

Tymek Zapała · Answer

@koshevoysergey Smart approach!

Alex Fino · Answer

It depends on the goal. If the goal is to retain users, then it should be a free renovation of features😃. But if the task is to increase the value of the product, then this should lead to an increase in its cost. If your customers are already paying for a subscription, gradually adding new features often feels expected, and they are unlikely to pay extra for it. However, you can bundle and package a significant set of new features into an entirely new plan. In this case, the added value will be justified 🤷‍♂️

Answer

If my client wants significant feature requests that require substantial development time and resources, we may charge a fee.

Christopher Allen Scott · Answer

If it's a small feature that will benefit many users, we usually do it for free to keep customers happy. But for big custom features, we charge extra, especially for enterprise clients. Gotta keep the $$$ flowing, ya know? 💰

Answer

Simple feature requests are usually free, but more advanced or custom features often require a fee to implement.

If your customers request new features, do you implement them for free of for a fee?

Replies