For CircleCI's orbs ecosystem, should we emphasize creating more first-party orbs or incentivize third-party developers to expand the marketplace?

Introduction

The trade-off we're examining today is whether CircleCI should focus on creating more first-party orbs or incentivize third-party developers to expand the marketplace for their orbs ecosystem. This decision will significantly impact CircleCI's product strategy, developer ecosystem, and overall platform growth. I'll analyze this trade-off by considering various factors including business context, user impact, technical feasibility, and resource allocation.

Step 1

Clarifying Questions (3 minutes)

• Based on CircleCI's current market position, I'm thinking this decision could significantly impact our competitive advantage. Could you provide more context on our market share and main competitors in the CI/CD space?

Why it matters: Helps understand the competitive landscape and how this decision might affect our positioning. Expected answer: CircleCI has a strong position but faces competition from GitHub Actions and GitLab CI. Impact on approach: Would influence whether we prioritize differentiation or ecosystem growth.

• Considering our revenue model, I assume orbs play a role in user retention and potential upsells. How do orbs currently factor into our monetization strategy?

Why it matters: Clarifies the direct business impact of orbs on our bottom line. Expected answer: Orbs indirectly drive revenue by increasing platform stickiness and enabling more complex workflows. Impact on approach: Would help determine if we should focus on high-value first-party orbs or a broader third-party ecosystem.

• Looking at user behavior, I'm curious about the adoption rate of existing orbs. What percentage of our users actively use orbs in their workflows?

Why it matters: Indicates the current importance of orbs to our user base. Expected answer: A significant portion (e.g., 60-70%) of users incorporate orbs in their CI/CD pipelines. Impact on approach: High adoption would suggest focusing on quality and variety, while low adoption might require more first-party orbs to drive usage.

• From a technical perspective, I'm wondering about the complexity of creating and maintaining orbs. How resource-intensive is it for our team to develop first-party orbs compared to supporting third-party developers?

Why it matters: Helps assess the feasibility and scalability of each approach. Expected answer: First-party orb development requires significant ongoing maintenance, while third-party support involves initial documentation and tooling investment. Impact on approach: Would influence the balance between in-house development and ecosystem enablement.

• Regarding our current roadmap, how urgent is this decision? Are there any upcoming features or partnerships that might be affected by our choice?

Why it matters: Helps prioritize this decision within our overall product strategy. Expected answer: The decision is important for Q3 planning but not immediately critical. Impact on approach: Would determine the depth of analysis and experimentation we can afford before making a decision.