The largest contact database isn't automatically the best sales intelligence investment. A database answers one question, who might fit your ICP. It doesn't necessarily tell you whether a record is current, which account deserves attention, how a rep should act, or how intelligence should enter your product and CRM.

Buyers should separate prospect discovery, contact and company enrichment, live professional data, sales engagement, account-based intelligence, and intent signals. The right comparison therefore includes freshness, coverage, pricing transparency, workflow fit, integration effort, compliance considerations, and scalability. A prospecting interface, an enrichment platform, and an API can all appear on the same vendor list while solving entirely different jobs.

The category has moved well beyond niche software. One 2026 market summary estimates the global sales intelligence market at USD 4.42 billion in 2025, rising to USD 4.99 billion in 2026 and potentially reaching USD 9.15 billion by 2031, at a projected 12.89% CAGR. Mordor Intelligence's market analysis supports the broader conclusion: sales intelligence is becoming infrastructure for prospecting, enrichment, prioritization, and revenue operations.

Fetchin occupies a different position from most entries below. It's a B2B data API for SaaS products and GTM teams that need structured, current professional and company data inside their own workflows, rather than another dashboard for manual research.

Table of Contents

1. Fetchin

Fetchin is the strongest fit when sales intelligence must become a product capability, an automated workflow, or an input for an AI agent. Its profile and company endpoints turn a professional profile URL or company URL into structured JSON, allowing engineering teams to retrieve data without building a separate research interface. The profile endpoint returns 100+ attributes, including positions, education, skills, locations, and contact fields, while the company endpoint provides firmographics such as industry, headcount, headquarters, founding year, and verified domain.

The important distinction is delivery model. Fetchin fetches public professional data on demand instead of serving a periodic snapshot, with a median response time of approximately one second and approximately 1.5 seconds at P95 under production load, according to the publisher's product information. Failed requests don't consume credits, which protects budgets when an input is invalid or a downstream request fails. Teams can choose synchronous responses for immediate enrichment or asynchronous delivery for workflows that tolerate longer processing.

Central benefit: Live, integration-ready data can reduce stale-record problems without forcing a team to assemble separate engagement endpoints.

Where the API earns its place

The additional posts, comments, and reactions endpoints make Fetchin more useful than a simple profile lookup service. A GTM system can combine firmographics with engagement context, while recruiting and talent platforms can keep professional records current inside their own interfaces. The Buying Signals API also supports workflows that monitor public account activity and surface triggers such as hiring, funding, expansion, or complaints, though the usefulness of any signal depends on public-data availability and the quality of the team's activation rules.

Pricing is easier to model than a quote-only enterprise suite. Fetchin offers a 1,000-credit free tier, monthly credit plans, per-1,000-credit pricing, pay-as-you-go options, and enterprise terms. Self-serve rate limits start at 5 requests per second, while dedicated capacity can reach 100 requests per second. Higher sustained throughput requires provisioning, with capacity above 5 requests per second provisioned in approximately 2 to 5 business days and carrying additional cost.

Pros

  • Live retrieval: Fresh page-state data helps limit stale cached records.
  • Structured coverage: More than 100 profile attributes, firmographics, and engagement endpoints arrive in consistent JSON.
  • Cost protection: Failed requests don't consume credits, and dashboard controls expose credit volume and rate configuration.
  • Production flexibility: Synchronous and asynchronous delivery support different application architectures.
  • Compliance posture: The service sources public information and references CCPA and GDPR expectations.

Cons

  • Public-data boundary: Private contact details and proprietary records aren't available, so some enrichment requirements will remain unmet.
  • Provisioning requirement: Higher sustained throughput needs dedicated capacity and additional budget.
  • Engineering ownership: Teams must design authentication, caching policy, monitoring, retries, and downstream data governance.

Fetchin is recommended for SaaS product teams, AI automation builders, recruiting and talent platforms, and GTM systems that need fresh data inside an existing workflow. Explore the Fetchin B2B data API for current endpoint and pricing details.

Fetchin

2. LinkedIn Sales Navigator

Sales Navigator is the native professional-network prospecting choice for teams that need precise account and persona discovery, not a bulk data API. Advanced search, persona filters, account lists, saved leads, buying-group mapping, deal alerts, Smart Links, TeamLink, and InMail form a connected workflow for human-led prospecting.

Its value comes from relationship context. A rep can research an account, identify relevant stakeholders, see buying-group relationships, find warm paths through TeamLink, and coordinate outreach without switching to a separate database. That makes it especially useful for enterprise selling, where mutual connections and account familiarity can matter as much as contact volume.

The trade-off is architectural. Sales Navigator is designed for interactive prospecting and relationship intelligence, not high-volume enrichment or direct embedding inside a SaaS product. Teams looking to turn professional profile URLs into structured application data should evaluate a professional data API for live extraction, not treat a rep-facing search subscription as an equivalent integration layer.

Pros

  • Precise discovery: Advanced filters and account lists help reps narrow searches to relevant personas.
  • Relationship workflows: TeamLink, buying-group mapping, deal alerts, and InMail support account-based selling.
  • Familiar adoption: Its professional graph is already part of many GTM teams' research habits.

Cons

  • Interactive by design: It isn't intended to function as a bulk exporter or product-embedded enrichment engine.
  • Outreach constraints: InMail allowances can feel restrictive for teams running heavy outbound motions.
  • Workflow dependence: Value falls if reps don't consistently save leads, review alerts, and act on relationship context.

Choose Sales Navigator when your primary job is finding and validating prospects through a professional graph. Don't choose it as a substitute for live API delivery, automated enrichment, or a programmable signal pipeline.

LinkedIn Sales Navigator

3. ZoomInfo SalesOS

ZoomInfo SalesOS is built for larger organizations that want broad contact, company, and workflow coverage under one commercial relationship. Its feature set includes a large contact and firmographic database, mobile numbers, org charts, buying-committee mapping, buyer intent, CRM integrations, and the Engage engagement layer. Salesforce, HubSpot, and Creatio connections make it easier to distribute intelligence across sales, marketing, and operations.

The strength is breadth. A mature revenue organization can justify a wider platform when several teams need the same account records, contact coverage, intent layers, and engagement tools. The weakness is that breadth increases buying friction. Pricing is quote-based, SMB affordability can be a concern, and users report that data accuracy varies by region and ICP. Those trade-offs make a pilot more important than a compelling demo.

Validate coverage before signing

Ask the vendor to test the exact personas, industries, countries, and account sizes your team targets. Mobile-number coverage that works well for one geography may not justify an enterprise package for another. The same applies to org charts and buying-committee data, which only create value when they reflect the accounts your sellers pursue.

A company lookup API may be a better complement when your product needs a focused company-resolution workflow rather than a broad sales suite.

Pros

  • Broad account context: Contacts, firmographics, org charts, intent, and engagement can sit in one ecosystem.
  • Mobile coverage: Direct numbers can justify the investment for phone-led teams.
  • Cross-functional reach: Sales, Marketing, Operations, and Talent teams can share the platform.

Cons

  • Opaque pricing: Quote-based packaging makes total cost difficult to estimate early.
  • Potential overbuying: Smaller teams may pay for modules they won't operationalize.
  • Regional variability: Coverage and accuracy should be tested against the target ICP before commitment.

ZoomInfo is recommended for established revenue organizations with budget, data-operations support, and a clear need for workflow consolidation. It's a poor first purchase for a lean team that needs only targeted lookups or a developer-ready data layer.

ZoomInfo SalesOS

4. Apollo.io

Apollo.io combines prospecting, enrichment, sequencing, and engagement for lean teams that want fewer point tools. Its contact and company search, filters, paid-tier intent topics, email sequencing, warmups, dialer add-ons, visitor identification, CRM connections, and published API cover the path from discovery to outreach. That breadth makes Apollo a workflow platform, not a substitute for every data layer.

The self-serve model makes testing easier. A free tier supports initial evaluation, while credits provide a visible control for exports and contact reveals. As usage grows, per-seat costs, phone credits, and export limits require oversight. Reported data quality also varies at scale, so teams should validate records against their ICP before treating Apollo as a primary source.

Where Apollo fits

Apollo is strongest when the job is prospecting plus outbound execution. Its API and enrichment features can support connected workflows, but teams needing live, application-embedded extraction should assess a dedicated data provider instead. Apollo is less differentiated for account-level intelligence or advanced intent prioritization than platforms built around those functions.

Use operating rules from the start: define which records qualify for export, restrict phone-data access, resolve duplicates, and require approval for credit-intensive workflows. A small team can move quickly, but unmanaged usage turns convenience into avoidable data and licensing waste.

Pros

  • Fast trial: Self-serve pricing and a free tier support quick evaluation.
  • Consolidated workflow: Search, sequences, CRM connections, and engagement reduce tool sprawl.
  • Flexible motion: The platform supports early outbound tests and structured mid-market workflows.

Cons

  • Seat expansion: Per-user pricing can rise as the team grows.
  • Credit governance: Phone reveals and exports need monitoring.
  • Scale variability: Check data quality by geography, persona, and industry rather than assuming database size indicates coverage.

Choose Apollo for SMB and mid-market teams testing outbound or replacing several point tools. Choose another layer when the primary requirement is live API-based extraction or advanced account-level intent modeling.

5. Demandbase Sales Intelligence

Demandbase Sales Intelligence fits organizations that already run an account-based marketing motion. Its core job is account intelligence and signal activation, not live API-based extraction or basic prospect discovery. The platform combines account context, buying signals, engagement insights, a browser extension, CRM and marketing integrations, plus optional advertising and DSP capabilities. That breadth can connect targeting, seller priorities, and campaign activity, but it also raises the implementation threshold.

The main dependency is shared operating logic. Sales and marketing need agreed account definitions, campaign priorities, routing rules, and measurement. Before rollout, assign each account tier a signal policy, an owner, and a response. Otherwise, real-time alerts become an unowned queue rather than a change to seller or campaign behavior.

Where Demandbase fits

Demandbase is most useful when the SaaS or GTM stack needs coordinated ABM execution across account intelligence, advertising, and sales workflows. It can reduce separation between account and contact context, but it is excessive for a small team seeking only a prospecting database or focused enrichment feed. Quote-based pricing and custom configuration make implementation ownership part of the business case, alongside license cost.

Pros

  • Unified ABM context: Sales and marketing can use shared account intelligence.
  • Signal activation: Engagement insights can guide routing, campaigns, and seller priorities.
  • Stack coordination: Advertising and DSP capabilities connect account targeting with sales activity.

Cons

  • Implementation complexity: Teams must define account tiers, routing, and ownership.
  • Quote-based cost: The package may exceed the needs of teams without a broader ABM program.
  • Adoption risk: Sellers may ignore signals if marketing owns the system without a clear handoff.

Choose Demandbase for enterprise sales and marketing teams coordinating ABM campaigns and measurement. Choose a prospecting database for contact discovery, or a dedicated data provider for live API-based extraction.

Demandbase Sales Intelligence (formerly InsideView)

6. 6sense

6sense belongs in the prioritization layer of a SaaS or GTM stack. Its 6AI predictive models classify buying stage and account scores, while the platform connects account intelligence with sales intelligence, orchestration, and integrations. The resulting value is prioritization: deciding which accounts deserve coordinated attention before sellers spend time on outreach.

That role separates 6sense from a prospecting database, enrichment feed, or live API for extracting contact data. It helps teams act on signals and coordinate plays, but it does not replace basic coverage or structured data delivery. Its fit is strongest when an organization already has an account-based motion and needs a shared operating layer for sales and marketing.

The implementation requirement is substantial. Teams must agree on target-account definitions, buying stages, signal interpretation, and follow-up actions. CRM and marketing-automation data also needs enough consistency for scores to inform workflows rather than add another unverified dashboard.

A practical rollout starts with the accounts that matter most, then tests scoring inputs against defined actions. Each stage should map to an owner and a next step. If an SDR cannot tell what to do after an account changes stage, the system is producing prioritization without operational value.

Pros

  • Focus over volume: Predictive scoring helps SDRs concentrate on accounts with stronger buying-stage evidence.
  • Cross-functional reach: Sales, marketing, and revenue operations can work from a shared account model.
  • Orchestration: Integrations support activation across workflows, rather than limiting signals to one dashboard.

Cons

  • Quote-based pricing: The cost can exceed that of a focused point solution.
  • Data dependency: Weak CRM or marketing-automation hygiene limits practical value.
  • Alignment requirement: Teams must define stages and plays before scores become actionable.

Choose 6sense when sales and marketing can connect account predictions to defined actions. Start with a simpler database or API when the immediate need is coverage or reliable data delivery.

7. Cognism

Cognism deserves attention from teams whose prospecting motion depends on international coverage, especially EMEA phone data and compliance-conscious sourcing. Its positioning centers on GDPR-aligned data sourcing, DNC filtering, the Sales Companion extension, prospecting workflows, CRM integrations, and optional data, outbound, and intent modules.

The practical advantage isn't a longer feature list. For an EMEA-heavy ICP, the decisive question is whether direct-dial and mobile coverage is usable in the countries and segments that generate pipeline. A regulated organization may also value a vendor that makes compliance processes part of the buying conversation, but that positioning still needs verification against the organization's own lawful-basis and outreach requirements.

Annual, sales-led contracts and add-ons make Cognism less approachable for a small US team seeking occasional contact reveals. There's no public price list, so the evaluation should compare total cost with actual regional coverage, not with a generic database count.

Pros

  • EMEA orientation: Direct-dial and mobile coverage can be more relevant than broad global claims for European ICPs.
  • Compliance focus: GDPR-aligned sourcing and DNC filtering support regulated outreach programs.
  • Workflow access: The browser extension and CRM integrations help reps use data where prospecting happens.

Cons

  • Sales-led buying: No public price list makes early budget planning harder.
  • Contract commitment: Annual terms and add-ons may exceed the needs of smaller teams.
  • Coverage variance: Validate the exact countries, industries, and personas before signing.

Cognism is recommended for international or regulated organizations where EMEA coverage and compliance processes are decisive. It's less compelling for a small US team that prioritizes self-serve pricing and lightweight experimentation.

Cognism

8. Lusha

Lusha is a lightweight prospecting option for SMB and mid-market SDR teams that want quick contact reveals without a heavy implementation. Its browser extension supports one-click email and phone reveals, while people and company search, filters, pooled team credits, and volume scaling give managers a simple way to distribute usage.

The product's economics revolve around credits. Moderate usage can remain manageable, but heavy dialing changes the calculation because phone reveals consume more of the team's allocation and higher tiers or overages may become necessary. That makes Lusha a good operational fit for targeted prospecting, not necessarily for broad account intelligence or an embedded product workflow.

Test the coverage that matters

Before expanding seats, run a controlled sample against the team's actual ICP. Compare regional availability, mobile coverage, seniority, and company-size fit. A tool that works well for direct-dial prospecting in one market may produce a different result for another, and a browser workflow won't solve the need for live structured data inside a SaaS application.

Pros

  • Easy onboarding: Self-serve plans support quick adoption.
  • Rep-friendly workflow: The extension makes contact reveals available during browser-based research.
  • Shared economics: Team credits can support moderate-volume SDR programs.

Cons

  • Credit planning: Heavy dialers may need higher tiers or overage budget.
  • Variable coverage: Regional and mobile performance must be tested by ICP.
  • Limited strategic depth: It isn't designed for predictive account prioritization or complex embedded workflows.

Choose Lusha when fast onboarding and moderate prospecting volume matter more than deep account intelligence. It's a practical first tool for a small SDR team, but not a complete sales intelligence architecture.

9. Clearbit, a HubSpot company

Clearbit is an enrichment-centered option for teams that already run HubSpot as the operational center of their GTM stack. Its capabilities include company and person enrichment, batch enrichment, a credit model, downstream integrations, visitor identification, and documented workflows for routing and scoring.

That makes Clearbit different from Apollo or Sales Navigator. Its strongest use case is moving firmographic and person data into downstream decisions, such as assigning records, improving qualification, or adjusting score logic. Teams choosing it for general prospect discovery may be paying for infrastructure they won't use.

Govern fields and refresh behavior

The free products were sunset in 2025, making more capabilities pay-walled. Some users also report rising costs and stale data after the acquisition. Those reports don't establish universal performance, but they do justify a careful review of field ownership, refresh behavior, enrichment triggers, and credit controls before broad activation.

A HubSpot-centered team should compare Clearbit's workflow with a focused company enrichment API, especially when it needs company resolution or live data outside HubSpot.

Pros

  • HubSpot alignment: It fits teams that already use HubSpot for CRM, routing, and scoring.
  • Operational enrichment: Batch mechanics and documented workflows support repeatable data movement.
  • Visitor context: Visitor identification can connect anonymous company activity with downstream action.

Cons

  • Reduced free access: Free products were sunset in 2025.
  • Cost management: More capabilities are pay-walled and credit usage requires oversight.
  • Freshness concerns: Some users report stale data after the acquisition, so validation matters.

Clearbit is recommended when HubSpot is already the system of record and enrichment decisions are tightly connected to routing and scoring. It's not the natural choice for a standalone outbound team or a SaaS product needing vendor-neutral API delivery.

10. Bombora

Bombora is an intent specialist, not a general contact database. Its Company Surge topics and account-level research intensity help teams identify accounts showing increased interest, while APIs and partner integrations make activation possible across CRM and marketing systems. Visitor Insights can connect first-party website activity with third-party intent, giving teams a broader account-prioritization layer.

The signal alone won't create pipeline. Teams need disciplined topic curation, defined account targeting, routing rules, and follow-up plays. Without that operating model, sales reps may receive noisy account alerts that don't explain what to do next.

Intent requires activation discipline

Bombora's value is highest for mature ABM teams that already have account definitions and want an additional prioritization layer. Quote-based pricing and potentially meaningful spend make it sensible to define the activation plan and measurement framework before purchase. Decide which topics matter, which accounts qualify, how long a signal remains actionable, and who owns the response.

Pros

  • Specialist signal layer: Company Surge topics provide account-level research context.
  • Stack flexibility: APIs and partner integrations support activation across CRM and ABM tools.
  • First-party connection: Visitor Insights can combine website activity with broader intent.

Cons

  • Quote-based pricing: The investment may be significant for teams without an established ABM motion.
  • Signal hygiene: Poor topic curation can create noise.
  • Execution dependency: ROI depends on targeting, routing, and timely follow-up.

Bombora is recommended for mature ABM teams that already have contacts and account definitions but lack an intent activation layer. If the immediate need is fresh professional or company data, start with enrichment rather than intent licensing.

Top 10 B2B Sales Intelligence Tools Comparison

Solution Core capabilities Freshness & performance (★) Pricing & value (💰) Target audience (👥) Unique selling point (✨)
🏆 Fetchin Profile & Company endpoints; Posts/Comments/Reactions; sync/async JSON; 100+ profile attrs ★★★★★ median ~1s; P95 ~1.5s; failed-request credits protected 💰 Free 1k credits; per-1k tiers, PAYG & enterprise; transparent dashboard 👥 Product teams, AI automation, recruiters, GTM systems ✨ Live per-call fetching; integration-ready JSON; reduces stale-records
LinkedIn Sales Navigator Advanced search, saved leads, TeamLink, InMail, CRM integrations ★★★★ Precise filters; interactive prospecting, not bulk API 💰 Seat-based subscriptions; limited export for high-volume needs 👥 Sales/account execs focused on relationship-driven prospecting ✨ Best-in-class professional graph & warm-intros
ZoomInfo SalesOS Large contact DB, firmographics, org charts, intent, Engage ★★★★ Broad coverage; strong US mobile data; enterprise-grade 💰 Quote-based; can be costly for SMBs; consolidated contracts 👥 Large revenue orgs needing consolidated workflows ✨ Deep mobile/direct-dial coverage & buying-committee mapping
Apollo.io Contact & company DB, enrichment, sequencing, dialer, API ★★★★ Fast adoption; variable accuracy at scale 💰 Self-serve with free tier & credits; per-seat growth considerations 👥 SMBs & mid-market outbound teams testing outbound motions ✨ All-in-one, trial-friendly stack with sequencing
Demandbase Sales Intelligence Account intelligence, buying signals, CRM/marketing integrations, DSP pairing ★★★★ Real-time account signals; enterprise implementation complexity 💰 Quote-based; part of broader ABM stack 👥 ABM-focused sales & marketing teams ✨ Unified account context + ad/DSP coordination
6sense Predictive models (6AI), account scoring, orchestration, integrations ★★★★ Strong predictive prioritization; reliant on clean CRM/MA data 💰 Quote-based enterprise pricing 👥 Cross-functional GTM teams aligning sales & marketing ✨ Predictive buying-stage scoring & orchestration
Cognism GDPR-aligned sourcing, DNC filtering, Sales Companion, CRM integrations ★★★★ Praised EMEA phone accuracy; compliance-focused 💰 Annual, sales-led contracts; add-ons; no public price list 👥 Regulated or EMEA-heavy prospecting teams ✨ EMEA mobile/direct-dial coverage with compliance controls
Lusha Chrome extension, people/company search, pooled team credits ★★★ Easy onboarding; variable global/mobile coverage 💰 Published self-serve plans; credit-based scaling 👥 SMB/mid-market SDR teams needing quick reveals ✨ One-click contact reveals via extension; fast onboarding
Clearbit (HubSpot) Company/person enrichment, batch ops, visitor ID, HubSpot integrations ★★★★ Smooth HubSpot-centric enrichment; some reports of staleness 💰 Credit model; free products sunset; paywalled capabilities 👥 HubSpot-centric ops teams needing operational enrichment ✨ Seamless HubSpot workflows and batch enrichment
Bombora Company Surge intent, APIs, Visitor Insights, partner integrations ★★★★ Strong intent signals; ROI depends on disciplined activation 💰 Quote-based; meaningful spend for activation & measurement 👥 Mature ABM teams needing intent overlay ✨ Company Surge topics + Visitor Insights for account prioritization

Choose the Data Layer That Matches the Motion

There isn't one universal winner among B2B sales intelligence tools because the products solve different jobs. A database helps a rep discover contacts. An enrichment service improves CRM records. An intent platform prioritizes accounts. An engagement system turns a chosen audience into sequences and tasks. A live API gives a product or internal workflow structured data at the moment it needs it.

Choose Fetchin when a SaaS product or internal system needs live, structured professional and company data through an API. Its profile, company, posts, comments, and reactions endpoints make it especially relevant to AI agents, recruiting platforms, talent intelligence products, and GTM systems that need current public professional data rather than periodic snapshots. The free tier, per-1,000-credit plans, pay-as-you-go options, and failed-request credit protection also make early testing easier to budget.

Choose Apollo or Lusha when self-serve prospecting and engagement are the priority. Apollo is the broader all-in-one option, with search, sequencing, CRM connections, and a published API. Lusha is lighter and more focused on fast contact reveals. Both require credit governance, and neither should be assumed to deliver the same workflow as a live application API.

Choose ZoomInfo or Cognism when coverage, direct dials, or regional requirements justify a sales-led contract. ZoomInfo is better suited to established organizations that want broad contact, account, intent, and engagement coverage. Cognism is more compelling when EMEA coverage and compliance-conscious sourcing are central. In both cases, test actual ICP coverage by geography and persona before accepting a large package.

Choose Demandbase or 6sense when account-based coordination and predictive prioritization are central. Demandbase fits organizations connecting account intelligence with ABM and advertising. 6sense fits cross-functional teams that can align on buying stages, scoring inputs, and follow-up plays. Neither platform fixes unclear ownership or weak CRM data by itself.

Choose Clearbit when HubSpot enrichment is the operational center. Its value comes from routing, scoring, batch enrichment, and visitor workflows inside an established HubSpot environment. Choose Bombora when intent activation is the missing layer and the team already has account definitions, targeting discipline, and a process for converting signals into action.

Before signing, run five checks:

  • Test coverage: Use real target accounts, personas, regions, and industries rather than vendor-provided examples.
  • Calculate total cost: Include seats, credits, phone reveals, exports, add-ons, implementation, and overages.
  • Confirm integration limits: Review API access, CRM sync behavior, rate limits, retries, and provisioning requirements.
  • Assign refresh ownership: Decide who controls field updates, deduplication, stale-record handling, and data retention.
  • Define signal actions: Document how hiring, engagement, intent, job changes, or account-stage movement becomes a routed sales task.

The market's expansion makes tool selection more consequential, not easier. Independent category tracking lists 98 sales intelligence tools as of September 4, 2026, with an average rating of 4.37 out of 5 across 73 rated tools, and 39% offering a free tier, according to Toolradar's sales intelligence statistics. More choice means buyers need sharper job definitions. The best stack is usually the smallest combination that delivers trusted data, clear prioritization, and an action in the system where work already happens.

Fetchin offers a real-time B2B data API that turns professional profile and company URLs into structured JSON, with profile, firmographic, and engagement endpoints for SaaS and GTM workflows. Visit Fetchin to test whether live, integration-ready public professional data fits your enrichment, automation, recruiting, or sales intelligence product.