Concierge onboarding pattern

How the pattern works

On signup, the user is offered (or required) to book a 30-minute call with the founder. The call walks them through setup, configuration, and the first meaningful action. The founder learns the customer's context in real time and adjusts the product roadmap based on the patterns.

Activation metric

Activation rate among concierge-onboarded users vs self-serve users. Almost always 2-3x higher for concierge. The decision to scale away from concierge is about cost, not activation.

Implementation considerations

1. Add a calendar link on the post-signup page. Cal.com or similar.
2. Make the call optional but visibly offered. Forcing the call drives some users away who would have self-served fine.
3. Develop a call agenda: 5 min context, 15 min setup, 10 min Q&A. Keep it tight.
4. Take notes during every call. The patterns across calls shape the product more than any other data source.
5. Retire concierge gradually as you cross 50-100 customers. Move to async support + recorded onboarding videos.

Common mistakes

• Treating concierge calls as sales calls. The user has already paid; the call is for setup and learning.
• Skipping notes. The patterns the founder absorbs over 50 concierge calls are the most valuable founder asset; without notes, the patterns leak.
• Continuing concierge past 100 customers without a transition plan. The founder burns out.

Variations

• Async concierge — Loom video walkthrough personalized to the customer's signup answers.
• Hybrid concierge — call optional but available; recorded onboarding video as the default.

Frequently asked

Should I require the concierge call?

Make it strongly offered, not required. Required-call models filter out qualified users who would have self-served. Strongly-offered models let the users who want the help opt in.

Other onboarding patterns

• Linear walkthrough onboarding pattern
• In-product checklist onboarding pattern
• Sample-data onboarding pattern
• Just-in-time onboarding pattern