Cold outreach fails most of the time not because the product is wrong or the price is too high, but because the opening message or call shows no evidence of having done any research. Decision-makers are inundated with generic pitches. The ones that get through are the ones that demonstrate specific knowledge about the prospect's situation. Kaissa.nl's lead enrichment pipeline is designed to make that knowledge available before you make contact — automatically, in under two minutes.
Lead enrichment in Kaissa.nl is triggered either automatically when a new lead is created with a website URL, or manually by submitting a URL to the platform via WhatsApp or the dashboard. The enrichment process runs in three stages:
The entire pipeline completes in under 90 seconds for most sites. For complex or slow-loading sites, it may take up to three minutes.
The enrichment summary attached to each lead record includes:
This summary does not replace your own research — it accelerates it. A salesperson who has read a two-paragraph enrichment summary before a discovery call is already more prepared than one who opens a browser tab as the client picks up the phone.
The enrichment data feeds directly into proposal generation. When you request a proposal for an enriched lead, the AI already has the business context it needs — it does not re-crawl the site. This means the proposal is faster to generate and the content is more specific, because the enrichment has already done the heavy lifting of identifying what matters about this client's situation.
The proposal's situation summary section draws directly from the enrichment data. The recommended services are filtered by the service fit assessment. The scope of work reflects the gaps identified during enrichment. This coherence between the enrichment summary and the proposal content is one of the things clients notice — it reads like you actually paid attention.
Lead enrichment data has a shelf life. A company that was enriched six months ago may have relaunched their website, pivoted their product offering, or changed their leadership team. Kaissa.nl stores the enrichment date alongside the summary and flags records where the enrichment is older than 90 days. You can trigger a refresh manually, or configure the platform to refresh enrichment automatically when a proposal follow-up is due.
Refreshed enrichment is diffed against the previous version — if significant changes are detected, you receive a WhatsApp notification summarising what changed. This is particularly useful for leads that went cold and have since re-engaged: you can see at a glance whether anything material has changed at their end.
The full enrichment record for any lead is accessible via the Kaissa.nl REST API at GET /api/leads/:id/enrichment. This endpoint returns the raw extracted signals as a structured JSON object alongside the plain-text summary. If you are integrating Kaissa.nl with a CRM or another tool, this endpoint lets you push enrichment data downstream without manual copy-paste.
Enrichment data is scoped to your account — you cannot access enrichment records created by other Kaissa.nl users, and your enrichment data is not shared with any third party outside the Claude AI processing pipeline.
Enrichment is only as good as the website it reads. Companies with minimal web presence, login-gated content, or heavily JS-dependent sites may return sparse enrichment summaries. Kaissa.nl flags low-confidence enrichments clearly in the summary — if the crawler could not find sufficient signal, you will see a note indicating what was and was not retrieved, rather than a summary that presents thin data with false confidence.
When enrichment is sparse, the platform suggests alternative signal sources: LinkedIn company pages, Companies House filings for UK entities, or the KVK register for Dutch businesses. These are linked in the enrichment record but require manual lookup — Kaissa.nl does not scrape third-party platforms it does not have permission to crawl.