# monday marketplace starting-point onboarding to main workflow

> Set one monday feature or template as the starting point so a fresh install lands on the workflow that proves the app first.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/monday-marketplace-starting-point-onboarding-to-main-workflow/
- Source: [developer.monday.com](https://developer.monday.com/apps/docs/user-onboarding)
- GrowthDex source hub: [monday Developer Docs: User onboarding](/sources/monday-developer-docs-user-onboarding-developer-monday-com/)
- Last checked: 2026-06-05T10:45:00Z
- Rarity: rare
- Budget: low
- Channels: Product-led Growth, Onboarding, Marketplaces
- Stages: activation, first-run ux, template onboarding, install handoff


## Why this can grow

A lot of apps lose the user right after install because the first screen is neutral when it should be opinionated. monday lets developers choose a specific feature, a template, or both as the onboarding starting point. That means the first-use path can open on the workflow that best explains the product instead of dumping the user into a generic blank state. The docs also let developers test that onboarding flow from the Installed outside the marketplace section before it goes live, which makes first-use friction easier to catch before it becomes review fuel.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 monday marketplace starting-point onboarding to main workflow can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product-led Growth and Onboarding channel.
3. Use the evidence from developer.monday.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

monday's onboarding configuration lets developers pick a specific feature or template as the starting point, requires users to choose the destination workspace or board, and allows the flow to be tested before marketplace launch from the Installed outside the marketplace section.

## Adjacent tactics in the same lane

- [Salesforce AppExchange Trialforce template with sample data](/growth-ideas/salesforce-appexchange-trialforce-template-with-sample-data/) - 3 shared channels, 1 shared stage
- [Stripe Apps install links carry intent before marketplace browse](/growth-ideas/stripe-apps-install-links-carry-intent-before-marketplace-browse/) - 3 shared channels
- [Teams Store first-run account with preloaded proof](/growth-ideas/teams-store-first-run-account-with-preloaded-proof/) - 2 shared channels, 1 shared stage
- [Salesforce AppExchange connect organization before listing polish](/growth-ideas/salesforce-appexchange-connect-organization-before-listing-polish/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The monday marketplace page should survive the request-to-add click](/blog/the-monday-marketplace-page-should-survive-the-request-to-add-click/) - marketplaces, brand trust, onboarding

## Advisory

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