<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">James Makienko</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Q&amp;A. How do you motivate potential participants to pay to join a platform?</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Business Resource</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">09/2010</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://timreview.ca/article/382</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Talent First Network</style></publisher><pub-location><style face="normal" font="default" size="100%">Ottawa</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">A company that operates a multi-sided platform must convince participants to pay an affiliation fee to access the platform. The challenge is to determine what it will take to motivate the participants to pay to collaborate with each other.

To motivate participants to pay an affiliation fee, a multi-sided platform must deliver unique value to the various stakeholder groups its sides represent. For example, if a platform is designed to generate revenue from three stakeholder groups: developers, users and researchers, it must deliver unique value to each of these three groups. Developers must receive more value from participating in the platform than the value received from not participating in the platform. The same holds true for users and researchers.

To generate revenue, a platform must be designed to deliver compelling value propositions for each stakeholder group. To illustrate how this can be achieved, we will describe five lessons learned while defining value propositions for a technology company. 
</style></abstract><issue><style face="normal" font="default" size="100%">July 2010</style></issue><work-type><style face="normal" font="default" size="100%">Q and A</style></work-type><custom1><style face="normal" font="default" size="100%">Carleton University
James Makienko is an M.A.Sc. student in the Technology Innovation Management program at Carleton University. His research interests include business ecosystems, go-to-market channels, deal and contract development, and web-based deal development platforms. He holds a B.Eng. in Computer Systems Engineering from Carleton University and previously worked in software development, technical support, and security. </style></custom1></record></records></xml>