Coming soon
Named-account homepage hero
Personalize the homepage hero with industry-specific messaging for visitor segments you define. The personalization engine serves the variant, using audience data you supply.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Set up the account variants
Coming soonBlu builds a step
About this recipe
When to use it
The canonical ABM personalization move, swap the homepage hero's logo and messaging per identified target account, requires firmographic enrichment most teams never bother wiring up. This recipe wires it up.
What it delivers
Personalizes the homepage hero (logo, industry-specific messaging) per identified target account using firmographic enrichment, the same pattern Mutiny and Demandbase popularized.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Personalize the homepage hero with industry-specific messaging for visitor segments you define. The personalization engine serves the variant, using audience data you supply.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
StepWhat happensBuilds
- 01Set up the account variantsCreate a CLIENT PERSONALIZATION on /experiences titled "ABM Account Personalization". This is a PERSONALIZATION (audience-driven, no random split). Each variant binds to one or more target-account audiences. The pattern is: identified visitors from named target accounts see a hero customized to their company; unidentified visitors fall through to the default hero. ═══ PATH 1: Top-level configuration ═══ Experience type: client_personalization Variants (each binds to a target-account audience: adjust audience IDs to your target list): - Control (audience = all: fallback): standard homepage hero - Variant B (audience = "tier-1 target accounts: enterprise SaaS"): hero customized for enterprise SaaS visitors - Audience definition: account_id IN ("acc-001", "acc-002", ...): the explicit target list - OR account_industry = "Enterprise SaaS" AND account_employee_count > 1000 - Variant C (audience = "tier-1 target accounts: financial services"): hero customized for financial-services targets - Audience: account_industry IN ("Banking", "Financial Services", "Insurance") AND account_employee_count > 500 - Variant D (audience = "tier-2 target accounts: healthcare"): hero customized for healthcare targets - Audience: account_industry IN ("Healthcare", "Health Tech", "Medical Devices") AND account_employee_count > 100 Targeting (experience-wide): - Pages: homepage "/" and key conversion pages (/pricing, /demo) - Devices: any - Audience: specific (per-variant) - Display frequency: always Metrics (existing CRM/CDP: personalizations don't have hypothesis-bound primary/secondary): - Form submitted on demo-request form per audience (B2B's primary outcome) - Click on on primary CTA per audience - Account-level engagement (View page count per identified company in the targeting window) Schedule: continuous ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes: fallback for non-target traffic) Variant: B (Enterprise SaaS targets) HTML target selector: .homepage-hero (replace contents) Variant DOM: <section class="homepage-hero" data-variant="b" data-audience="enterprise-saas"> <h1>[Account name], scale your data ops without the platform tax</h1> <p>The infrastructure platform built for SaaS companies at scale. Trusted by [3-5 named SaaS customers].</p> <div class="hero-social-proof"> <img src="/customers/snowflake-logo.svg" alt="Snowflake" /> <img src="/customers/databricks-logo.svg" alt="Databricks" /> <img src="/customers/datadog-logo.svg" alt="Datadog" /> </div> <div class="hero-cta-row"> <button class="primary-cta" id="hero-cta-demo">Book a demo with [Brand]</button> <a href="/case-studies/saas" class="secondary-link">Read SaaS case studies to </a> </div> </section> Variant: C (Financial Services targets) HTML target selector: .homepage-hero (replace contents) Variant DOM: <section class="homepage-hero" data-variant="c" data-audience="financial-services"> <h1>SOC2 + PCI compliant infrastructure for [Account name]</h1> <p>Trusted by leading banks, insurers, and fintechs to handle high-stakes financial data.</p> <div class="hero-social-proof"> <img src="/customers/jpmc-logo.svg" alt="JPMorgan Chase" /> <img src="/customers/stripe-logo.svg" alt="Stripe" /> <img src="/customers/plaid-logo.svg" alt="Plaid" /> </div> <div class="hero-compliance-badges"> <span>SOC2 Type II</span> <span>PCI DSS</span> <span>ISO 27001</span> </div> <div class="hero-cta-row"> <button class="primary-cta" id="hero-cta-demo">Book a demo</button> <a href="/case-studies/financial-services" class="secondary-link">Financial services case studies to </a> </div> </section> Variant: D (Healthcare targets) Similar structure with HIPAA badges, healthcare customer logos, healthcare-specific copy. The Visual Editor allows the user to refine copy, swap customer logos to match the actual account's industry, and inject the [Account name] placeholder. Use the account's name in the HTML: the platform's personalization engine substitutes the actual account name at render time when the visitor is identified. Taxonomy notes: - REQUIRES FIRMOGRAPHIC ENRICHMENT: This recipe depends on visitor-to-account identification, typically via Clearbit, Demandbase, 6sense, ZoomInfo, or IP-based reverse lookup. Without enrichment, all visitors fall through to the Control variant. - The Accounts object stores firmographic attributes: account_industry, account_employee_count, account_revenue, account_id, etc. Ensure these are populated by your enrichment pipeline before launching this personalization. - Demandbase's research shows the operational sweet spot is 4-5 distinct account segments. Beyond that, content management overhead exceeds the personalization gains. - For the [Account name] template substitution, the platform reads from the Users object's company association: typically `Users.company_name` or `Accounts.name` for the matched account. - Mutiny's playbook: tier-1 accounts (top 100 named accounts) get fully custom heroes; tier-2 (industry segments) get vertical-specific heroes; everyone else gets the default. This recipe encodes that pattern.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /abm-account-personalization in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe More recipes by Sid Chaudhary
Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe
