Our vision with LookStat was to create a web platform for microstock contributors that not only tracked sales but made it easy for contributors to really analyze their performance and ultimately use that information to make their microstock activities more profitable.

Over the next few weeks, I’ll be writing about ways to think about your microstock activities as a business and various metrics that are interesting in that regard. This post is focused on Return per Image (RPI).

Acknowledgements

James, Laurent, Lee, Matt & Yuri all have great posts about RPI. I would urge all of you interested in this topic to check them out. One of the things I love about microstock is how willing the community is to share their knowledge.

Return per Image per Month

One of the more commonly quoted metrics in the microstock blogosphere is RPI. This is not revenue per download, but rather it gives you an indicator of how much each image (across all sites) will generate in revenue for you every month. This number is important because it measures the earning power of your images.

While it’s a useful top-level indicator, it does have some limitations. The most glaring one is that it doesn’t really convey what happens over time. Matt has written a great post about this and the core issue is that older images sell less and RPI at the aggregate level obscures this since it only looks at the aggregate portfolio and doesn’t account for age.

Calculating RPI:

Consider the following two scenarios:

Scenario 1:

You have 10 images in your portfolio and they are listed at 5 sites. You earn $100 in sales at each site every month. In this situation, your return per image is:


Scenario 2:

In this scenario, everything is the same as in Scenario 1, except you have 100 images at each site. In this case, your revenue per image would be:

As you can see, the images in Scenario 1 have 10 times the earning power of the images in Scenario 2. Please, keep in mind, these are made up numbers. RPI varies quite a bit and the numbers above are very high based on what I’ve seen published. In general, based on conversations I’ve had, if you’re at $1-$2 RPI/month across all sites you’re in pretty good shape.

Limitations of RPI

RPI is a useful number but as such doesn’t give you enough information on how to proceed. Matt’s thought about selecting the top 100 images in a month and looking at their RPI is a good one. Another option is to look at age. Compare how your latest uploads perform in their first month with how your last batch did in their first month, i.e. cohort analysis. Each image has a revenue curve that varies over time and looking at batches is a way to better compare apples to apples. Laurent has a post discussing this that is well worth your time. In his post about Advanced Stock Theory, Yuri also discusses some of the factors that skew RPI.

Analyzing Sales over Time

The chart below was generated from LookStat data and shows the total revenue curve of a few of our images across multiple sites. Each curve tells a different story. A constant slope means steady sales over time. A flattening curve means declining sales over time etc. RPI at the aggregate level obscures this data. Tracking RPI at the same point in an image’s life cycle would yield more interesting data. For example, looking at RPI for an image for the first 30 days that it is listed would be fairly instructive.

(the data above is total sales hence the curves that rise and flatten)

Other Useful Slices

Another useful way to use RPI is to group images by category, by location, by model, by site and to see if certain groups stand out relative to others. By segmenting your revenues in this way, it’s possible to tease out some of the meaning that’s obscured by the aggregate RPI number. For example, you might find that within the business category, your RPI for isolated images is much higher than your RPI for images shot on location. Again, it’s important to compare apples to apples so looking at RPI at similar stages in an image’s lifecyle is important.

How LookStat can Help

The main problem with increasing the granularity with which you look at RPI is that it’s a giant pain to calculate. If you’re doing it by hand, you need to track sales by image and by day and then you have a dataset that you can slice and dice. This is fine with a handful of images, but it quickly becomes unwieldy. Unfortunately, this analysis is most valuable when you have a larger portfolio spread across multiple sites.

LookStat tracks sales at the individual image level and we aggregate data across sites. As a result, it’s easy for us to get at the details of the data. Basically, for every image in your portfolio, we know when it was uploaded and how many sales it had each day. We also store all the metadata associated with an image so in the future, we will be able to use that information to analyze sales even further.

Ultimately, we want our users to be able to look at their portfolios and see which models in their business images generate the most revenue for them at Dreamstime vs. Shutterstock.

Ultimately, we believe that better data for contributors means they’ll have a better sense for what buyers want which in turn will lead to them producing better-selling images. The beauty of microstock is that this should benefit all participants in the chain.

A Request

Please let me know which metrics you like to track and what you’d like to be able to track if you had access to the relevant data. Hopefully we can start a thread that would be valuable to the community and I’d love to be able to build in some of the most useful pieces of data into LookStat as the service evolves. Because of the granular way in which we build transaction histories, creating new data slices is relatively easy.