How Should I Price a Custom Dynamic Sound Feature for My Hobby Project?
Asked by
MellowPine47
I'm developing a live wallpaper engine for creating interactive 3D wallpapers with rigged, animated characters, interchangeable outfits, expressions, and animations. It's still a work in progress, but a small group of people has shown interest in it. Someone offered to pay me to add dynamic sound system support, which wasn't part of my original plan. I expect the implementation to take roughly three or four days of my free time, plus some ongoing maintenance. Since this is primarily a hobby project and I don't usually do paid programming work, how should I calculate a fair price for the feature?
Answers
The right price depends heavily on whether this is a private customization or a feature that will become part of the main product. If it’s only for one person, price it based on your time and the value of having it made specifically for them. If everyone will get the feature, you can justify charging less because it may help the project grow. Agree on a clear scope and deliverables before quoting anything.
Reply to this answer
For a small hobby project, you don’t necessarily need to charge a full commercial consulting rate, but the payment should still make giving up several days of your free time worthwhile. A simple estimate would be your expected hours multiplied by a rate you feel comfortable defending, with extra time for bugs and maintenance. The fact that the audience may be niche is more relevant to what the client is willing to pay than to how much work the feature requires.
Reply to this answer
Be careful about the scope of “dynamic sound system support.” If the engine already has the underlying audio capabilities and you’re only adding triggers, playback rules, and controls, that’s one kind of job. If it also involves sourcing, recording, editing, or producing audio content, the work can expand quickly. Write down exactly what is included, what is not included, how many revisions are allowed, and who pays for future changes. Otherwise a seemingly small feature can turn into an open-ended customization project.
Reply to this answer
Start by estimating the full number of hours, including testing, documentation, integration problems, and future maintenance. Then multiply that by a reasonable freelance development rate—something like $40–$80 per hour depending on your experience and the complexity. Since this is a new feature that may need updates as the engine changes, add a maintenance buffer. If only one person is funding it, they should generally cover the full development cost. If the feature will benefit many future users, you could discount it somewhat as an investment in the project. Getting part of the payment up front is also sensible.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine47: I originally wasn’t planning to monetize the project at all. It’s mostly a personal project that some 3D artist friends became interested in, and I’m estimating three or four days of free time for the initial implementation, plus maintenance. I don’t normally take on paid programming work, so I’m mainly trying to find a fair starting point.