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.
Use this paper as evidence about sustaining superior performance in business ecosystems: evidence from application software developers in the ios and android smartphone ecosystems in the stated context; compare its population, treatment and outcome with your own decision.
Plain-English take
Higher ecosystem complexity helped developers sustain superior performance, especially experienced firms; platform transitions made sustained superiority harder, with the adverse effect amplified by complexity.
International Journal of Information Management · 2016
For your marketing
Use this study as a bounded example related to third-party mobile app developers’ continued participation in platform-centric ecosystems: an empirical investigation of two different mechanisms; evaluate whether its customers, intervention and outcome match your own context.
Plain-English take
The study identifies and empirically investigates two contrasting routes to continued participation: genuine desire/dedication and need/constraint; it argues platform owners must manage the exchange relationship from developers' perspective to retain them.
Treat this as evidence for the specific marketing capability and growth question studied. Compare the setting and sample to your company before changing a growth decision; use a local experiment where the paper does not match your context.
Plain-English take
SBOM adoption is low but rising. SBOMs are mostly generated through build-integration tools or GitHub Actions; fewer than half of analyzed projects include them in version control or public release artifacts. Only a limited fraction contain minimum/recommended information, and some are noncompliant with existing SBOM standards. For a founder, use this as a question to test in your own context, not a universal playbook.
Journal of Open Innovation: Technology, Market, and Complexity · 2023
For your marketing
Treat this as evidence for the specific marketing capability and growth question studied. Compare the setting and sample to your company before changing a growth decision; use a local experiment where the paper does not match your context.
Plain-English take
The abstract reports significant relationships between FOSS adoption and low cost, performance expectation, social influence, and system quality; safety/security, interoperability, and usability are described as especially important in adoption decisions. The paper proposes a new adoption model. For a founder, use this as a question to test in your own context, not a universal playbook.
ACM Transactions on Software Engineering and Methodology · 2024
For your marketing
Treat this as evidence for the specific customer behavior and adoption question studied. Compare the setting and sample to your company before changing a growth decision; use a local experiment where the paper does not match your context.
Plain-English take
Practitioners more often sought guidance or learning than ready-to-use software artifacts; simple artifact generation and brainstorming were useful, complex tasks were harder; about two-thirds expressed high or moderate trust but none trusted outputs entirely, and lack of sources reduced trust. For a founder, use this as a question to test in your own context, not a universal playbook.
Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems · 2025
For your marketing
For developer-tool founders, measure perceived and behavioral productivity together, segment by user, and make provenance, ownership, responsibility, and output-quality workflows explicit. Avoid assuming that aggregate positive sentiment means every team or task benefits.
Plain-English take
The assistant generally produced net perceived productivity increases, but benefits were not experienced equally; the study also surfaced motivations, expectations about speed/quality, and questions about ownership and responsibility for generated code. For a SaaS founder: For developer-tool founders, measure perceived and behavioral productivity together, segment by user, and make provenance, ownership, responsibility, and output-quality workflows explicit. Avoid assuming that aggregate positive sentiment means every team or task benefits.
Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE 2014) · 2014
For your marketing
Useful for product/engineering workflow hypotheses and user research, not proof that a tool improves delivery metrics; pair perceived productivity with cycle time, quality, and wellbeing measures.
Plain-English take
Developers perceive days as productive when completing many or large tasks without significant interruptions/context switches, although substantial task/activity switching can coexist with feeling productive. Founder-use interpretation: Useful for product/engineering workflow hypotheses and user research, not proof that a tool improves delivery metrics; pair perceived productivity with cycle time, quality, and wellbeing measures.
Strong evidence for testing AI-assisted engineering productivity, not a promise of proportional headcount or SaaS growth; run a controlled rollout with quality, security, rework, and customer outcomes.
Plain-English take
Pooling the experiments, AI access increased completed tasks by 26.08% (SE 10.3%); less-experienced developers adopted more and had larger gains, while individual experiments were noisy and heterogeneous. Founder-use interpretation: Strong evidence for testing AI-assisted engineering productivity, not a promise of proportional headcount or SaaS growth; run a controlled rollout with quality, security, rework, and customer outcomes.
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.
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.
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.
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.