<!--
  This markdown file mirrors the canonical content of an ept AI page.
  It is generated from content/pages/ and intended for AI/LLM consumption.
  Canonical URL: https://www.ept.ai/industries/scientific/
  Last modified: 2026-04-23
-->
<Component name="PageMeta">
title: "Scientific Instruments | ept AI"
lastUpdated: "2026-04-23"
route: "/industries/scientific"
description: "Purpose-built AI for scientific instrument OEM sales. Application-specific expertise at every evaluation, without your specialists in the room."
products: ["Deal Room", "AI Product Channel", "Application Room"]
owner: "rob@ept.ai"
kpis: [
  "Pilot requests ≥ 8% of visitors",
  "Avg scroll depth ≥ 75%"
]
devNotes: {
  images: "No stock imagery. Specialist knowledge and instrument complexity emphasis.",
  ariaRoles: "Stat grid & solution cards labelled for assistive tech"
}
</Component>

---

<Component name="HeroSection">
layout: "text-left-animation-right"
h1: "Researchers ask deep questions before they buy. Your specialists can't be on every call."
subhead: "Lab equipment. Analytical instruments. Measurement systems. High-value purchases made by technically sophisticated buyers — researchers, lab managers, procurement — who need application-specific answers before they commit. ept AI makes your application specialists' expertise available at every evaluation, without them being in the room."
imagePath: "/images/pages/scientific.png"
altText: "Scientific instrument configuration complexity across mass spectrometry, chromatography, electron microscopy, and spectroscopy"
ctaPrimary: "Request a pilot"
ctaPrimaryUrl: "https://go.ept.ai/meetings/eptai-demo/ept-ai-demo"
</Component>

---

<Component name="SplitCards">
backgroundColor: "transparent"
eyebrow: "Four gaps. Four mechanisms."
title: "Where scientific instrument sales breaks — and how ept AI rebuilds it"
subtitle: "Each row: the measurable before-state, the problem it creates, and the ept AI mechanism that closes it."
pairs: [
  {
    theme: "Application discovery",
    problem: {
      heading: "Application-specific product discovery is a specialist-only function",
      text: "A lab manager evaluating a spectroscopy system for process analytical technology applications needs to match on wavelength range, sampling accessory compatibility, fiber optic options, and software integration with their existing LIMS. A product comparison table doesn't answer that. An application specialist does — but can't be on every dealer demo."
    },
    solution: {
      heading: "AI Product Channel delivers application-specific instrument discovery",
      text: "Natural language product discovery grounded in Product and Application Living Profiles — built from your application notes, method briefs, configuration guides, and technical documentation. The dealer or researcher describes the application and gets the right instrument configuration with full technical context, cited to the relevant application note.",
      url: "/solutions/ai-product-channel"
    }
  },
  {
    theme: "Specialist bandwidth",
    problem: {
      heading: "Pre-sales technical Q&A compounds across a large dealer network",
      text: "Your application specialists field the same deep technical questions repeatedly across evaluations: method transfer feasibility, detection limits for specific matrices, software compatibility, upgrade paths, service contract options. These questions have known answers in your documentation — but answering them takes specialist time."
    },
    solution: {
      heading: "AI Applications Engineer handles first-layer technical Q&A at scale",
      text: "First-layer technical Q&A across chat and ticketing — grounded in Product and Application Living Profiles, including your application notes, method briefs, and compatibility matrices. Researchers and dealers get specific, cited answers. Your application specialists focus on the complex, application-development-level questions only they can answer.",
      url: "/solutions/ai-applications-engineer"
    }
  },
  {
    theme: "Institutional accounts",
    problem: {
      heading: "Institutional account intelligence is scattered and perishable",
      text: "A university research group, pharmaceutical company, or contract research organization is a multi-year, multi-instrument account. Different labs, different PIs, different procurement cycles, different application areas — but one institutional relationship. The intelligence that grows those accounts is scattered across specialist notes, email threads, and CRM records."
    },
    solution: {
      heading: "Deal Room maintains institutional account knowledge",
      text: "A live workspace grounded in Customer and Deal Living Profiles — stakeholder maps, application fit across your instrument line, competitive positioning, cross-sell signals across lab departments. Institutional account knowledge that survives specialist turnover and surfaces cross-sell opportunities across instrument families.",
      url: "/solutions/deal-room"
    }
  },
  {
    theme: "Portfolio patterns",
    problem: {
      heading: "Application area patterns stay invisible across your business",
      text: "Which application areas — proteomics, environmental monitoring, food safety, battery research — are driving the most evaluation activity across your instrument line right now? Which configuration questions come up most often? Which competitors appear in mass spec evaluations vs. chromatography evaluations? No individual specialist sees this in aggregate."
    },
    solution: {
      heading: "Application Room surfaces product intelligence across your business",
      text: "Aggregates signals across deals, catalog queries, and support interactions to surface application-level patterns. Which application areas are growing fastest? Which instrument configurations have recurring documentation gaps? Structured product intelligence for your product marketing and application development teams.",
      url: "/solutions/application-room"
    }
  }
]
</Component>

---

<Component name="TechnicalArchitecture">
eyebrow: "The knowledge problem"
theme: "light"
title: "Your application specialists have the knowledge. The challenge is making it available at every evaluation."
subtitle: "In scientific instrument sales, the knowledge that closes evaluations lives in your application specialists — accumulated from years of method development, customer applications, and instrument performance data. That knowledge doesn't scale linearly with headcount. And when a specialist leaves, it walks out the door."
overview: "ept AI builds Application and Product Living Profiles from your documented expertise — application notes, method briefs, configuration guides, technical FAQs, compatibility matrices. That knowledge becomes available at every dealer demo, every researcher inquiry, every post-sale support interaction. Your specialists stop being the bottleneck for questions their documentation can already answer — and every answer cites its source document."
callout: {
  stat: ">90%",
  label: "Pilot-to-rollout conversion",
  secondary: "Liquid Instruments — test and measurement instruments, complex configuration, technically sophisticated buyers"
}
layers: [
  {
    name: "Specialist Knowledge",
    description: "Application notes, method briefs, configuration guides, technical FAQs, and compatibility matrices — the accumulated expertise of your application specialists, documented and structured.",
    capabilities: ["Application notes", "Method briefs", "Configuration guides", "Compatibility matrices", "Technical FAQs"],
    icon: "/images/icons/brain.svg"
  },
  {
    name: "Living Profiles",
    description: "Application and Product Living Profiles built from your documentation. Continuously updated as new application notes, customer interactions, and product configurations are added.",
    capabilities: ["Product profiles", "Application profiles", "Customer profiles", "Deal profiles"],
    icon: "/images/icons/target.svg"
  },
  {
    name: "Every Evaluation Touchpoint",
    description: "Dealer demos, researcher inquiries, post-sale support, institutional account management. Your specialists' expertise available at every touchpoint, without them being in the room.",
    capabilities: ["Dealer and distributor support", "Researcher pre-sales Q&A", "Institutional account intelligence", "Application area analytics"],
    icon: "/images/icons/zap.svg"
  }
]
</Component>

---

<Component name="SolutionCardRow">
title: "Three interfaces. One platform. All grounded in your application expertise."
solutions: [
  {
    colSize: "3",
    title: "AI Product Channel",
    text: "Application-specific instrument discovery for dealers, distributors, and researchers. Cited answers from your application notes and technical documentation. 24/7.",
    learnMoreUrl: "/solutions/ai-product-channel"
  },
  {
    colSize: "3",
    title: "AI Applications Engineer",
    text: "First-layer technical and application Q&A across chat and ticketing. Your specialists focus on complex application development. Volume gets handled.",
    learnMoreUrl: "/solutions/ai-applications-engineer"
  },
  {
    colSize: "3",
    title: "Deal Room",
    text: "Account intelligence for multi-instrument institutional relationships. Stakeholder maps, application fit, cross-sell signals across lab departments — maintained by AI.",
    learnMoreUrl: "/solutions/deal-room"
  },
  {
    colSize: "3",
    title: "Application Room",
    text: "Product intelligence from researcher inquiries, application note engagement, and dealer feedback — structured for PMs and product marketing to guide instrument strategy.",
    learnMoreUrl: "/solutions/application-room"
  }
]
</Component>

---

<Component name="CTA">
backgroundImage: "/images/feature_highlight.png"
backgroundColor: "transparent"
headline: "See what ept AI looks like for your application specialists and your dealer network."
copy: "Every pilot starts with a clear ROI baseline — pre-sales Q&A deflection, specialist time saved, evaluation conversion intelligence. By week 12 you have quantified results to have confidence in the value to your organization."
ctaText: "Request a pilot"
ctaUrl: "https://go.ept.ai/meetings/eptai-demo/ept-ai-demo"
ctaSecondary: "Back to Industries"
ctaSecondaryUrl: "/industries/overview"
dataEvent: "cta-scientific-pilot"
</Component>