A curated scientific evidence directory

Scientific marketing studies for SaaS and technical founders

Explore peer-reviewed field experiments and meta-analyses on SaaS trials, email, paid search, referrals, content sharing and choice design. Compare methods, context and limits.

357 studies21 topics

Search studies:

Topic:

Study design:

Full-text access:

2 studies match your filters

Clear filters

Download & reuse

JSON dataset

Developer ecosystems and adoptionEvidence check: 3.5/5

Impacts of License Choice and Organizational Sponsorship on User Interest and Development Activity in Open Source Software Projects

Stewart, K. J., Ammeter, A. P., & Maruping, L. M. (2006). Impacts of License Choice and Organizational Sponsorship on User Interest and Development Activity in Open Source Software Projects. Information Systems Research.

Plain-English take: License restrictiveness and organizational sponsorship interacted: users were most attracted to projects sponsored by nonmarket organizations and using nonrestrictive licenses. Licensing and sponsorship also addressed complementary developer motivations, so licensing’s relationship with development activity depended on sponsor type. Founder-use interpretation: Use this as a question to test in your own product context, not as a universal benchmark. The publisher abstract does not provide an explicit limitations section or a causal identification strategy. Because the evidence is observational and tied to Freshmeat.net/project-home-page listings, representativeness and causal interpretation beyond those projects remain uncertain.

Question: Impacts of License Choice and Organizational Sponsorship on User Interest and Development Activity in Open Source Software Projects?

Design: Peer-reviewed empirical study or research synthesis. Open-source software projects listed on Freshmeat.net, with project-home-page information; outcomes are user interest and development activity. The publisher abstract does not report a project count.

License restrictiveness and organizational sponsorship interacted: users were most attracted to projects sponsored by nonmarket organizations and using nonrestrictive licenses. Licensing and sponsorship also addressed complementary developer motivations, so licensing’s relationship with development activity depended on sponsor type.

Information Systems Research · 200610.1287/isre.1060.0082Publisher article or abstract page directly retrieved with Firecrawl; full methods access varies.

Developer ecosystems and adoptionEvidence check: 3.5/5

How Peripheral Developers Contribute to Open-Source Software Development

Setia, P., Rajagopalan, B., Sambamurthy, V., & Calantone, R. (2012). How Peripheral Developers Contribute to Open-Source Software Development. Information Systems Research.

Plain-English take: Peripheral developers made significant contributions to product quality and diffusion, especially when projects were in more mature product-development stages. Founder-use interpretation: Use this as a question to test in your own product context, not as a universal benchmark. The publisher abstract does not report a dedicated limitations section. The study is observational and its sample consists of 147 open-source products, so representativeness, measurement validity, and causal interpretation beyond the sampled projects cannot be established from the publisher record alone.

Question: How Peripheral Developers Contribute to Open-Source Software Development?

Design: Peer-reviewed empirical study or research synthesis. 147 open-source software products; peripheral developers are external volunteers whose contributions include product-quality work and word-of-mouth advocacy/diffusion.

Peripheral developers made significant contributions to product quality and diffusion, especially when projects were in more mature product-development stages.

Information Systems Research · 201210.1287/isre.1100.0311Publisher article or abstract page directly retrieved with Firecrawl; full methods access varies.

Reviewed 2026-10-09. The summaries are original paraphrases. Consult the linked paper and any correction before citing or applying a result.