Create a personalized sales demo

Turn a prospect’s domain into a demo that looks familiar and uses relevant, verified account context. Context.dev supplies brand data and website evidence. Your application supplies CRM history, the product demonstration, and delivery. MarketBetter uses brand context for sales meeting preparation, and Comp AI built a branded sales-deck generator. This recipe produces a saved demo configuration that your own renderer can preview.

Resolve the prospect first

Start with a verified company domain from your CRM or a rep’s selection. If the flow begins with a work email, use Brand by email and let the rep confirm the result. Similar company names, subsidiaries, and platform-hosted pages can otherwise produce the wrong branding. Keep the sender and prospect as distinct identities:

Identity	Purpose
Sender	Who built the demo, owns its claims, and will share it
Prospect	Whose approved branding and public context personalize the experience
Example data	Clearly labeled sample records used to demonstrate the product

Gather branding and selected facts

On your server, use an API key from the Quickstart to retrieve the Brand profile. Use Styleguide only when the template needs additional design context. Read selected about or product pages as Markdown, or use a bounded Extract request. For example, the following body asks only for public product context:

Extract request body

{
  "url": "https://example.com/product",
  "maxPages": 3,
  "maxDepth": 1,
  "followSubdomains": false,
  "factCheck": true,
  "schema": {
    "type": "object",
    "properties": {
      "product_description": {
        "type": ["string", "null"],
        "description": "The product's stated purpose. Return null if unavailable."
      },
      "stated_audience": {
        "type": ["string", "null"],
        "description": "The audience explicitly named on the site. Do not infer the company's buying goals."
      }
    },
    "required": ["product_description", "stated_audience"],
    "additionalProperties": false
  }
}

Keep urls_analyzed and the retrieval time with the result. Before approving a fact for the demo, inspect the relevant page and retain its supporting URL or excerpt. The source list does not automatically provide field-level citations. A full-site crawl should not be required to preview a demo. Let an unavailable page remain missing, and keep a neutral theme and editable company name when brand data is partial.

Keep website evidence and CRM history distinct

Public website text can support a description of a product. Your CRM can support a rep’s meeting notes or a stated next step. Neither source should silently overwrite the other.

demo-model.ts

type Fact = {
  id: string;
  text: string;
  source:
    | { kind: "website"; url: string; retrievedAt: string; excerpt: string }
    | { kind: "crm"; recordId: string; updatedAt: string };
};

type DemoTheme = { accent: string; logoUrl: string | null };
type DemoOverrides = {
  headline?: string;
  accent?: string;
  logoUrl?: string | null;
};

type DemoConfig = {
  version: number;
  state: "draft" | "approved";
  preparedBy: string;
  preparedFor: { name: string; domain: string };
  headline: string;
  theme: DemoTheme;
  facts: Fact[];
  sampleDataLabel: string;
  sourceVersion: string;
  overrides: DemoOverrides;
};

export function buildDemo(input: {
  senderName: string;
  prospectName: string;
  prospectDomain: string;
  reviewedTheme: DemoTheme;
  approvedFacts: Fact[];
  sourceVersion: string;
  previous?: DemoConfig;
}): DemoConfig {
  if (input.previous && input.previous.preparedFor.domain !== input.prospectDomain) {
    throw new Error("Start a separate demo for a different account");
  }
  const overrides = input.previous?.overrides ?? {};
  return {
    version: (input.previous?.version ?? 0) + 1,
    state: "draft",
    preparedBy: input.senderName,
    preparedFor: { name: input.prospectName, domain: input.prospectDomain },
    headline: overrides.headline ?? `A product demo for ${input.prospectName}`,
    theme: {
      accent: overrides.accent ?? input.reviewedTheme.accent,
      logoUrl: overrides.logoUrl !== undefined
        ? overrides.logoUrl : input.reviewedTheme.logoUrl,
    },
    facts: input.approvedFacts,
    sampleDataLabel: "Illustrative sample data",
    sourceVersion: input.sourceVersion,
    overrides,
  };
}

approvedFacts means facts checked against their source for this revision. Keep their IDs tied to content or a source version so a changed claim cannot inherit an old approval. Rebuilding creates a draft while preserving design and headline edits; it does not silently update an already-shared demo.

Populate the product demonstration

Use the configuration to select and fill components you control. A model can suggest which product features to highlight, but its output should reference approved fact IDs and a fixed list of available demo sections. Do not infer the prospect’s budget, purchase intent, goals, customer relationships, or results from its branding. Keep sample accounts, transactions, metrics, and testimonials visibly illustrative unless the rep supplied approved real data. In the preview, show the sender and recipient labels, the source links behind account facts, and controls to replace the logo or edit the copy. Keep internal CRM notes out of the shared payload unless the rep intentionally selects content appropriate for the recipient. Persist the configuration and source-bundle version with your CRM account ID. A share action should select an approved revision and create the appropriate application link or export. Email sending, CRM updates, access controls, and link expiry belong to your application. Try one complete prospect profile, one missing logo, a failed product-page read, and an edited headline. Regenerate the demo and verify that edits survive, unsupported claims remain absent, and the shared version stays unchanged until a new revision is approved.

Lead enrichment

Save company and person context without replacing rep edits.

Branded documents

Render the approved meeting brief as a report or deck.

Brand experiences

Sales and content

Web research

Create a personalized sales demo

Resolve the prospect first

Gather branding and selected facts

Keep website evidence and CRM history distinct

Populate the product demonstration

Lead enrichment

Branded documents

​Resolve the prospect first

​Gather branding and selected facts

​Keep website evidence and CRM history distinct

​Populate the product demonstration

​Save and share the reviewed revision

Lead enrichment

Branded documents

Resolve the prospect first

Gather branding and selected facts

Keep website evidence and CRM history distinct

Populate the product demonstration

Save and share the reviewed revision