Company Enrichment from Website
Turn company homepage URLs into structured value proposition, industry, audience, and market context records in JSONL, Markdown, and HTML.
Turn company homepage URLs into structured value proposition, industry, audience, and market context records in JSONL, Markdown, and HTML.
A list of company URLs is not yet useful for CRM segmentation or account research because every site uses its own language. This workflow gives you one structured record per homepage with value proposition, industry, target audience, and market context fields for review and import. Fetch Homepages collects readable public text, Enrich with AI maps that evidence into the requested attributes, and Finalize Enrichment writes the machine-readable file and review documents. Add the graph to your visual workflows when another list needs the same field set. It normalizes company attributes from source text, rather than producing a general page summary.
fetch-sites, script) retrieves readable public text from each supplied company URL.enrich-agent, agent) maps the fetched text into the requested company attribute fields.finalize, script) writes the reviewed records to JSONL plus Markdown and HTML renderings.Illustrative output from finalize. The documentation domain and attribute values below show the record shape, not a real company or a completed enrichment run.
company-enrichment.jsonl
| homepage | value_proposition | industry | target_audience | market_context |
|---|---|---|---|---|
| https://www.example.com | Illustrative placeholder for a concise offer statement | illustrative category | illustrative buyer group | Derived only from the supplied homepage text |
The Markdown and HTML artifacts render the same fields for review before import.
The default fields are value proposition, industry, target audience, and market context. Change the attribute set in Enrich with AI when your CRM or research sheet uses a different schema.
No. It works from readable public homepage text. Join the JSONL artifact with existing CRM records after you review the source-based attributes.
Pages with little readable text produce shorter, less specific records. Review those fields instead of treating unsupported detail as fact.
Yes. Fetch Homepages accepts a list of URLs, and the final artifacts keep one structured record per homepage.
Get a personalized demo
A 30-minute walkthrough. We map the platform to your stack and answer pricing and deployment questions for your environment.