Different outlets might sell the same game at different prices for reasons of strategy: for example, some retailers will choose to sell a high-profile game at a discount for a short time to draw customers. However, publishers will also change their suggested retail prices with time, lowering them when demand decreases ([Larame03]). What happens to developer royalties at that time?
If the royalty rate has been set as a fixed percentage of the publisher's sale price, for example 20%, the royalty amount decreases proportionally with the price. One consequence of this fact is that, if the game has not yet earned back its advance at the time of a price drop, the developer might have to wait until unit sales reach much higher levels than expected before he receives a check.
The other royalty model, in which the developer receives a fixed dollar amount per copy of the game sold no matter what the publisher's sale price might be, would therefore seem more attractive. Unfortunately, this model has a serious flaw of its own: as the publisher's price
From the developer's point of view, the optimal agreement ought to generate royalty income as soon as possible and keep the game on the shelves as long as possible. One way to build this strategy into a
Set a ceiling to the unit sales that can be used to recoup the advance. For example, an advance of $1,800,000 at a royalty rate of $9 per unit corresponds to 200,000 units sold at full price. The contract might therefore specify that the developer is entitled to receive royalties as soon as unit sales reach 250,000 copies, even if the advance has not yet been recouped due to price cuts.
Set an escalating royalty percentage once the advance has been earned back.
For example, the royalty on the first 100,000 units might be 20% of the publisher's price, the rate on the
Finally, most publishers pay royalties on a quarterly basis, and only on copies that retailers have paid them for (because they have been sold to consumers). This means that it takes some time for money to flow back into developers' pockets: if a game
Case Study 1.3.2: Royalties versus Guarantees
|
|
Sarbakan, a developer of online
"We want to maintain a 50–50 split between creating our own projects and providing our services to other intellectual property
In
SteppenWolf
's case, Sarbakan sold all rights to the property to Warner Bros. The publisher provided a budget sufficient to insure profitability, and Sarbakan retained a share of future earnings tied to the property. "This way, we
By selling the rights to SteppenWolf to Warner Bros., Sarbakan accepted a smaller share of the property's revenue. However, with the power of the conglomerate behind SteppenWolf , this small share might actually amount to more, in the long run, than what Sarbakan might have been able to generate on its own.
"Plus, Warner has allowed us to retain a great deal of creative control over the
|
|