# Cal.com App Store for Time before integration backlog

> Turn the integration backlog into a developer platform before every adjacent workflow has to be built by the core team.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/calcom-app-store-for-time-before-integration-backlog/
- Source: [cal.com](https://cal.com/blog/cal-v-1-5)
- GrowthDex source hub: [Cal.com Blog: Series A and v1.5](/sources/cal-com-blog-series-a-and-v1-5-cal-com/)
- Last checked: 2026-06-09T14:08:46.000Z
- Rarity: epic
- Budget: high
- Channels: Developer Platform, Integrations, Marketplace
- Stages: app store, api, integration backlog, developer platform, marketplace expansion


## Why this can grow

Scheduling touches calendars, video calls, payments, CRMs, reminders, hiring tools, telehealth, and more. That breadth can bury a startup under requests. Cal.com's v1.5 move was to launch an App Store and API so the product could become more modular and developer-extensible. The growth lesson is that integrations are not just retention features. In the right category, they become distribution surfaces, partner hooks, and proof that the product is infrastructure rather than a narrow app. The timing matters. Launching a platform too early creates empty shelves. Waiting too long turns the roadmap into an endless support queue. Cal.com waited until the product had launch traction, funding, and enough demand to make extensibility credible.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where cal.com app store for time before integration backlog can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Developer Platform and Integrations channel.
3. Use the evidence from cal.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Cal.com announced its $25M Series A alongside v1.5, the App Store, API, dynamic booking links, and more than 180 new features, saying the App Store made Cal.com's architecture more modular and easier for developers to build on.

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The link should sell the infrastructure quietly](/blog/the-link-should-sell-the-infrastructure-quietly/) - open source, product-led growth, developer platform

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.