"shared development cost"?
Hello and my apologies for a seemingly silly question about semantics.
Our company funded the in-house development of a custom software application.
We have a customer that has requested a proposal for the use of this application for 12 months, possibly more.
Normally we would propose a renewable annual ┬?licensing fee┬? for the use of the software.
However (for reasons beyond the scope of this post), we need to avoid the use of the term ┬?licensing fee┬? or ┬?software lease┬?, or ┬?software subscription┬? or ┬?software rental┬?.
Instead, we┬?re looking for an industry standard term (if there is one), that addresses what we┬?re attempting to do: recover the costs we've incurred in developing the software application.
About the only term that we┬?ve hit upon so far is: ┬?Software Development Recovery Fee┬?.
This term is ┬?okay┬? but it seems a bit awkward, especially if there┬?s something more conventional that┬?s already in use.
In terms of our business model, our primary proposal is for services and the software application is not so much of a revenue stream, as it is a ┬?cost of doing business┬?.
The challenge is that the customer has agreed to cover our software development costs, but not as a single contract line item (CLIN) and only if the costs can be distributed over time and as a function of usage.
Thanks in advance for any inputs!
The term I have usually seen used for this is "non-recurring engineering" cost or fee, often simply referred to as "NRE".
NREs is a good approach but that may violate the "line item restriction"
Since you are likely to be supporting the product, here are two related ideas...
First, consider giving them one year of services that includes SW maintenance, support and non-recurring software fees. This could be billed quarterly.
The second option is to eliminate any mention of the software fees and "bury" the software use as part of the services you will be providing. (Make it clear to your POC that this is for his/her company's convenience.)
[COLOR=DarkRed][B][URL="http://www.softwarepricing.com"]Software Pricing Partners, Inc.[/URL] [COLOR=Black]+508-647-0330[/COLOR][/B][/COLOR]
We need to be careful that we don┬?t somehow convey that by the customer reimbursing us for our upfront development costs (which have already been spent in developing the application) that they ┬?own┬? the software.You're right, that is extremely important. There is one and only one answer, and it's not the line item description on the invoice. The one and only solution is a signed contract that explicitly states that you own the software and are granting them a license to use it under certain conditions. Any other approach risks the probability that the software becomes a "work made for hire" that they own (the same way that your company owns software written by your employees and contractors -- at the end of the day there's not much legal difference between your people's relationship with you and your relationship with this customer).
There are many instances where NREs are charged in conjunction with a licensing fee.
It seems to me that there is a bigger issue here than terminology. I get the distinct impression that you have one thing in mind (you own the software) and they have another (they simply asked you to do a prototype to see what you could do,with no committment on their end, and now want you doing work for hire).
Frankly, this is the sort of thing that always needs to be negotiated at a very early stage to avoid a real mess, and work being done under a misunderstanding. Of course I don't have all the details, but from what you have disclosed, it seems to be what needs to happen is an honest discussion about each parties interests and needs. I don't think that any amount of wordsmithing or dancing around the issue will replace that.
Thanks for posting that, Phil. I was uncomfortable with the original question but I couldn't quite put my finger on it.
The earlier you get everyone's expectations in alignment, the better. These things get very expensive to sort out down the road.
I can't say it any better than Phil. No amount of wordsmithing will change the underlying reality.
On a more "positive" note, let me say that I used to encounter this objection fairly often in my very long-ago contract programming days: "why should we pay you to develop this, and then you go out and sell millions of copies."
There are a number of counters to that objection:
- There is a lot to the software publishing business besides development. If I get lucky with this software as a product, it will be because of a lot of effort on our part (you can enumerate here if you wish) not just development.
- Do you really want to own it outright? Is there a benefit to you in doing so? Okay, the price with full rights is $XXXX (perhaps a 50% to 100% premium).
- The software business is tough. There are very few products that sell a million copies, so we are worrying about nothing.
- A variation is "if you're not willing to pay for this software, what makes you think that a million others will?"
- Perhaps they are worried that you sell it to their competitors and they lose a strategic advantage. You can give them an X-year exclusive in their industry.
- Would you be interested in revenue sharing? If we sell the product, we would pay you 3% of each sale until you had received 200% of your costs. You in return would agree to endorse us at industry conferences, etc.
- You benefit if we re-sell the software. That would give you enhancements at no cost, and a guarantee that we would stick around and maintain it.
- Your core competency is the widget business; ours is software. You want the best widget management product; don't worry about our software business.
FWIW - there must be a champion inside the organization, or someone who commissioned the original work from you.
Perhaps it is time for a frank discussion with this person, and say you are not equipped as a company to manage their different groups and distill a common solution from their different requirements. In short, if they need someone to do that, it is not you and if that is your only option you'll spend your time elsewhere on customers who offer a better business prospect. In short, you can always threaten to take your ball home.
the customer has agreed to cover our software development costs, but not as a single contract line item (CLIN) and only if the costs can be distributed over time and as a function of usageIsn't that the answer to your original question. Can't you just bill them for a "software usage fee"? Couldn't that fee include (without your enumerating or breaking it out into components)
- your direct costs in providing the software as a service
- a partial (total over enough time) recovery of your up-front costs
- a contribution to your general overhead