IMPLEMENTATION GUIDE
Use enrichment to suggest, not block
Start users in a default onboarding path before enrichment completes. When the completed company profile arrives, suggest an alternative only if it adds value. Industry and employee count describe the company, but they do not tell you the user’s immediate goal or the size of the team using your product.
Keep the user in control
Map a small set of firmographic segments to templates your product already offers. Explain why a recommendation might be useful and allow users to change it. If the email comes from a personal provider or there is insufficient company data, keep the general path and ask a targeted question when it helps.
Measure activation in your product
Store the chosen path separately from the enriched company segment. Use your product analytics to compare setup completion and activation across paths. Do not repeatedly change a workspace’s onboarding as data refreshes. EnrichLoops provides context; your product owns recommendations and the onboarding interface.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentAdd company context from a domain or LinkedIn company URL.Common questions
Can company data identify a user’s onboarding goal?
Company data can support a recommendation, but it does not establish the user’s goal. Offer a useful default and let the user choose or change the suggested path.
What happens before the profile is ready?
Show your default onboarding immediately. Enrichment runs asynchronously and your app can use the completed result when it arrives.