GITNUXSOFTWARE ADVICE
Sales EnablementTop 10 Best Inbound Lead Generation Services of 2026
Ranked comparison of Inbound Lead Generation Services for B2B teams, with technical notes and tradeoffs from providers like DemandScience and SmartBug Media.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
DemandScience
Configuration-driven lead lifecycle automation with an API-backed event model for tracking and handoff.
Built for fits when teams need governed inbound lead routing with API-driven integration depth..
GTMnow
Editor pickRBAC plus audit log trails for lead routing configuration and automation changes.
Built for fits when RevOps needs governed inbound routing across multiple systems and schemas..
SmartBug Media
Editor pickAutomation tied to a normalized lead data schema for API and webhook event consistency.
Built for fits when teams need controlled data model integration and governed automation for inbound routing..
Related reading
Comparison Table
This comparison table maps inbound lead generation providers by integration depth, including API and automation surface, data model schema, and provisioning workflow. It also contrasts admin and governance controls such as RBAC, audit log coverage, and configuration options that affect throughput and extensibility for routing and enrichment. Readers can use these dimensions to assess tradeoffs in API-driven automation, governance, and data consistency across providers without relying on marketing claims.
DemandScience
specialistB2B inbound demand generation and lead generation services that combine content, paid promotion, marketing automation, and sales enablement support.
Configuration-driven lead lifecycle automation with an API-backed event model for tracking and handoff.
DemandScience operationalizes inbound demand by configuring lead intake, enrichment, and lifecycle status updates across marketing and sales systems. The service supports integration breadth through an automation and API surface that can move events and field-level data between platforms instead of relying only on manual exports. The underlying data model ties together lead identity, account mapping, and campaign attribution so that handoffs are consistent across touchpoints. Configuration and provisioning are central to setup because workflows depend on schema alignment and event contracts.
A concrete tradeoff is that deeper integration and schema alignment require upfront mapping work to keep field semantics consistent across systems. Teams using complex CRM and marketing automation stacks get the most value when they need deterministic lead routing, event-driven status changes, and extensibility for additional enrichment stages. A typical usage situation is an enterprise marketing org synchronizing landing page capture and intent signals to a CRM with controlled deduplication rules and governed access for different stakeholders.
- +Event-driven automation connects inbound capture to CRM lifecycle status updates
- +API surface supports lead, account, and campaign data synchronization
- +Governance-oriented admin controls cover RBAC-aligned access patterns
- +Schema-aware data model keeps attribution consistent across systems
- –Integration depth depends on clean field mapping and schema alignment
- –Workflow configuration effort increases with additional enrichment stages
Best for: Fits when teams need governed inbound lead routing with API-driven integration depth.
More related reading
GTMnow
specialistInbound lead generation and sales enablement services that center on marketing operations, nurture programs, and pipeline reporting for B2B teams.
RBAC plus audit log trails for lead routing configuration and automation changes.
GTMnow fits marketing and RevOps groups that require more than form submissions and basic email actions. Lead events can be mapped into a consistent data model so enrichment fields, scoring signals, and routing attributes land predictably in CRM objects. The service favors an integration-first approach where configuration drives the workflow graph and API calls fill gaps when custom mapping or enrichment is needed.
Automation and API surface tend to be strongest when workflows are structured around provisioning and repeatable schemas. A key tradeoff is governance friction during early setup because RBAC, audit log review, and schema alignment add review steps before high-volume throughput. This fits teams migrating multiple inbound sources into one CRM routing policy, especially when they need controlled changes across campaigns, territories, and lifecycle stages.
- +Consistent lead data model for predictable CRM field mapping
- +Config-driven automation with an API surface for custom enrichment
- +RBAC and audit logging support controlled routing and schema changes
- +Workflow provisioning supports repeated campaign launches
- –Initial schema alignment and permissions review add setup overhead
- –Custom enrichment requires careful API and mapping design
Best for: Fits when RevOps needs governed inbound routing across multiple systems and schemas.
SmartBug Media
agencyInbound lead generation programs that integrate lifecycle marketing, content, and marketing automation with measurable pipeline outcomes.
Automation tied to a normalized lead data schema for API and webhook event consistency.
SmartBug Media work is oriented around mapping inbound lead signals into a controlled data model that travels across CRM, marketing automation, and enrichment layers. Integration depth is reflected in schema design and field normalization so attribution, lifecycle stage, and routing logic can be enforced with less manual translation. Automation is implemented around configurable flows with an API and webhook surface where available, which reduces batch dependencies for lead capture and enrichment.
A tradeoff is that stronger governance and automation usually require upfront schema decisions, including naming conventions, identity rules, and event definitions. Teams get the most value when they need reliable lead throughput with consistent routing outcomes across multiple channels, not just campaign-level reporting. Governance also matters when multiple admins, agencies, or internal teams touch the same lead operations so RBAC and change history prevent silent configuration drift.
Extensibility is supported through integration breadth and configuration-driven workflows, so additional fields, scoring events, or handoff rules can be added without rewriting the entire pipeline. This works best when there is a documented target schema for lead and account objects, plus clear provisioning responsibilities for the connected systems.
- +Integration depth across CRM and marketing automation with consistent schema mapping
- +Automation flows designed around API or webhook event ingestion
- +Governance practices include RBAC boundaries and change traceability for configuration
- +Lead, account, and engagement fields are normalized to reduce routing ambiguity
- –Schema and identity rules require upfront alignment before automation scales
- –Complex multi-system setups may increase configuration effort for admins
- –Workflow changes can depend on maintainable integration contracts and event formats
Best for: Fits when teams need controlled data model integration and governed automation for inbound routing.
Single Grain
agencyInbound demand generation and lead capture services that use SEO, content strategy, and conversion-focused landing and funnel design.
API-enabled workflow automation for lead enrichment and lifecycle routing across connected systems.
Within inbound lead generation services, Single Grain focuses on integration and operational control for marketing and sales systems. It supports lead routing and lifecycle execution through automation that can connect to CRM and marketing tooling.
The service delivery emphasizes a data model that can map lead fields into a consistent schema. Extensibility is handled via API-driven configuration patterns and workflow automation surfaces that reduce manual handling.
- +Integration-first delivery across CRM, marketing, and lead handling workflows
- +Lead data mapped into a consistent schema for downstream systems
- +Automation design reduces manual handoffs in lead lifecycle execution
- +API-driven extensibility supports workflow configuration and expansion
- –Governance controls like RBAC and audit logs need explicit confirmation
- –Schema mapping work can add upfront effort for complex field sets
- –Automation throughput constraints depend on chosen integration patterns
Best for: Fits when teams need integration depth and controllable lead automation across systems.
WebFX
agencyFull-funnel inbound lead generation services that combine SEO, content, web conversion optimization, and marketing analytics for B2B buyers.
Form-to-CRM provisioning with schema mapping and tracked attribution continuity across channels.
WebFX runs inbound lead generation programs that connect tracking, landing pages, and CRM handoff into a single acquisition workflow. The service emphasis centers on integration depth through documented schema, configurable routing logic, and clear attribution mapping across sources.
Automation coverage includes campaign workflows, form-to-CRM provisioning, and API-driven syncing between lead records and marketing events. Admin control is supported through governance steps like role-based access, change traceability, and audit-friendly process boundaries for operational reliability.
- +Integration-first setup for form-to-CRM lead routing with clear attribution mapping
- +API and schema alignment helps keep lead records consistent across systems
- +Automation workflows cover capture, enrichment, and campaign event syncing
- +Governance practices support RBAC boundaries and auditable operational handoffs
- –Automation depth depends on existing CRM and data model alignment effort
- –Extensibility may require custom configuration for atypical lead schemas
- –Throughput and job scheduling behavior can require scoping during implementation
- –Admin controls rely on client-side governance choices for access boundaries
Best for: Fits when teams need managed inbound execution with strong CRM and automation integration controls.
Thrive Internet Marketing Agency
agencyInbound lead generation services centered on SEO, content marketing, and landing page optimization tied to lead and pipeline metrics.
Lead lifecycle workflow management that links campaign activity to routed outcomes for follow-up.
Thrive Internet Marketing Agency fits teams that need inbound lead generation execution tied to real integration and data control. It emphasizes campaign-to-lead workflows across channels, with configuration for routing, targeting, and attribution that supports operational throughput.
The service is oriented around mapping lead lifecycle data into usable structures for reporting and follow-up automation. Teams get governance through documented process alignment, with operational visibility focused on what campaigns created and what outcomes they drove.
- +Campaign workflows integrate lead capture, routing, and follow-up execution
- +Lead lifecycle reporting supports attribution across inbound channels
- +Operational configuration covers targeting rules and lead handling logic
- +Process documentation supports consistent delivery across campaign iterations
- +Extensibility is practical through defined implementation steps and handoffs
- –API surface details are not consistently exposed for deep custom integrations
- –Data model mapping constraints can limit advanced schema customization
- –Governance relies on service operations more than self-serve RBAC tooling
- –Automation controls may require agency involvement for nonstandard changes
Best for: Fits when teams need managed inbound execution with measurable lead lifecycle reporting.
WebpageFX
agencyInbound lead generation services that include SEO, content, and conversion design with reporting built for sales and marketing alignment.
Lead routing configuration that maps inbound events to CRM objects and lifecycle stages.
WebpageFX differentiates with documented integration paths that support inbound lead generation workflows across marketing, sales, and analytics systems. The delivery emphasis centers on campaign setup, conversion tracking, and lead routing with an explicit data model for attribution and pipeline handoff.
Automation and API surface are positioned for extensibility, letting teams connect forms, CRM objects, and reporting schemas without manual spreadsheet processes. Admin and governance controls focus on operational oversight for campaign changes, access boundaries, and auditability of lead handling events.
- +Integration-first implementation with conversion tracking wired to lead capture events
- +Automation support for lead routing into CRM fields and lifecycle stages
- +Extensibility through API-style connectivity for forms, web events, and reporting
- +Governance emphasis with controlled campaign changes and operational visibility
- –Automation depth depends on available CRM and schema alignment
- –More complex data models require upfront configuration and mapping
- –High-volume throughput may need tuned event batching and routing rules
- –RBAC granularity can lag behind organizations needing strict role separation
Best for: Fits when teams need managed inbound lead operations with integration breadth and control depth.
Lyfe Marketing
agencyInbound lead generation programs that combine content, paid social support, and lifecycle follow-up to generate qualified leads.
Managed lead routing with schema-mapped enrichment synced into CRM objects.
Inbound lead generation delivery from Lyfe Marketing pairs campaign execution with integration-oriented operations for lead routing and list management. Reported workflows typically include CRM and marketing platform syncing, lead enrichment, and attribution handling tied to form and ad sources.
The service approach emphasizes configuration control, including reusable lead schemas and governance for who can publish, export, or modify routing rules. Integration depth is expressed through documented API and automation touchpoints that connect capture, enrichment, and follow-up with controlled throughput.
- +Integration-focused workflows that connect capture, enrichment, and CRM routing
- +Configuration control over lead schemas and field mappings across sources
- +Automation coverage for routing rules and follow-up triggers
- +Governance support with RBAC-style access boundaries for campaign operations
- +Audit-friendly operations for changes to routing and exports
- –API surface depth can depend on chosen CRM and marketing stack
- –Data model rigor may require upfront schema alignment work
- –Automation throughput tuning is constrained by client system capacity
- –Less visibility into internal pipeline details for nonstandard attribution models
Best for: Fits when teams need managed lead operations with controlled integration and automation across systems.
SmartSites
agencyInbound lead generation services that tie SEO and content programs to lead forms, conversion rates, and sales-ready reporting.
Lead lifecycle automation that routes and updates CRM records from campaign events.
SmartSites runs inbound lead generation workflows that connect CRM records to campaign channels and normalize lead attributes into a consistent schema. The service delivery emphasizes integration breadth through web-to-lead capture, CRM syncing, and analytics mapping so attribution stays traceable across systems.
Automation depth is supported via configurable lead routing and lifecycle triggers that reduce manual handoffs. The operational model includes governance controls for managing access and auditing marketing changes across environments.
- +CRM sync model with field mapping for consistent lead attributes
- +Integration breadth across web capture, campaign tracking, and analytics
- +Configurable lead routing reduces manual lead handling
- +Automation triggers align lead lifecycle stages to marketing events
- +Governance controls support RBAC-style access boundaries
- +Audit trails document changes to automation and routing logic
- +Extensibility via API-driven updates for campaign and contact objects
- +Environment separation supports safer iteration with production parity
- –Schema normalization can require upfront cleanup for legacy CRM data
- –API and automation features depend on documented data objects and events
- –Complex attribution paths may need custom tracking configuration
- –Governance coverage can vary across automation modules and connectors
- –High-throughput routing may require careful throttling and batching
Best for: Fits when teams need governed inbound automation tied to a defined CRM data model.
ZETTER
specialistInbound pipeline generation services that combine content strategy, demand capture, and marketing automation-driven lead nurturing.
API-led provisioning of lead and enrichment workflows with RBAC and audit log controls.
ZETTER fits teams that need inbound lead generation backed by a documented integration path into sales and marketing systems. Its value centers on data model alignment for lead and engagement records plus schema-driven provisioning for repeatable workflows.
Automation relies on a clear API surface for lead routing, enrichment events, and campaign attribution handoffs. Admin depth is shaped by governance controls such as RBAC scoping and audit log trails that support multi-team operations.
- +Documented API supports lead creation, updates, and routing workflows
- +Data model supports structured schema mapping for lead and activity records
- +Automation surface links routing, enrichment events, and attribution handoffs
- +Governance controls include RBAC scoping and audit log coverage
- –Integration depth may require engineering effort for complex custom schemas
- –Throughput tuning and rate controls may need platform-specific design work
- –Automation behaviors can become hard to reason about at high event volume
Best for: Fits when teams need governed inbound lead flows with deep CRM and marketing integration.
How to Choose the Right Inbound Lead Generation Services
This guide helps buyers evaluate inbound lead generation providers using integration depth, data model rigor, automation and API surface, and admin and governance controls. It covers DemandScience, GTMnow, SmartBug Media, Single Grain, WebFX, Thrive Internet Marketing Agency, WebpageFX, Lyfe Marketing, SmartSites, and ZETTER.
Each section explains what to verify during implementation work, not what to assume from marketing copy. The guide also calls out where setup effort increases when schema alignment and permissions review are not handled early.
Inbound lead generation services that route intent to CRM-ready leads with governed automation
Inbound lead generation services build capture-to-handoff workflows that turn website and campaign activity into lead records, then push those records into sales systems with consistent attribution. The best programs connect tracking, form capture, enrichment, and campaign event syncing into one operational path with an explicit lead and account data model.
DemandScience and GTMnow show this model in practice by tying inbound capture to lifecycle routing and sales handoff through configured workflows and an API or API-adjacent extensibility surface. SmartBug Media and SmartSites emphasize normalized lead and account fields so routing rules and lifecycle stage updates remain consistent across systems.
Evaluation criteria that map directly to integration depth and governance control
The primary risk in inbound lead generation is inconsistent field mapping between capture forms, enrichment services, and CRM objects. That inconsistency breaks routing logic and degrades attribution even when campaign setup looks correct.
The second risk is automation changes made without governance controls. DemandScience, GTMnow, and ZETTER place audit logging and RBAC scoping around routing and enrichment configuration so changes can be traced across teams.
Lead and account data model with schema-aware mapping
DemandScience uses a schema-aware lead, account, and campaign data model so attribution and lifecycle events stay consistent across systems. SmartBug Media and SmartSites normalize lead and engagement fields into a consistent schema so routing ambiguity drops as workflows expand.
API-backed event model for lifecycle tracking and handoff
DemandScience runs configuration-driven lead lifecycle automation with an API-backed event model for tracking and handoff. ZETTER similarly supports API-led provisioning for lead creation, updates, routing workflows, and enrichment events.
Automation and workflow extensibility through documented integration surface
GTMnow supports config-driven automation with an API surface for custom enrichment and controlled routing changes. Single Grain and WebpageFX describe API-style connectivity patterns that reduce manual handling during lead enrichment and lifecycle routing.
Admin governance controls with RBAC-aligned permissions and audit trails
GTMnow pairs RBAC with audit log trails for lead routing configuration and automation changes. DemandScience and ZETTER also center governance inputs on RBAC-aligned access patterns and audit log coverage for operational reliability.
Form-to-CRM provisioning with tracked attribution continuity
WebFX provides form-to-CRM provisioning with schema mapping and tracked attribution continuity across channels. WebpageFX and SmartSites emphasize lead routing configuration that maps inbound events to CRM objects and lifecycle stages while keeping campaign event history auditable.
Operational throughput control via routing workflow configuration
ZETTER highlights throughput tuning and rate control requirements at high event volume so automation behaviors remain explainable. WebpageFX calls out high-volume routing needs event batching and tuned routing rules so capture spikes do not flood CRM updates.
A decision framework for selecting the right inbound lead generation provider
The right provider is the one that can make the capture-to-CRM path deterministic using a shared data model and a controlled automation workflow. Buyers should select providers that can explain how lead fields, identity rules, and lifecycle states move between systems.
The next filter is governance. RBAC scoping and audit logging should cover routing and enrichment configuration changes so multi-team operations do not create silent drift.
Validate the lead and account schema mapping approach before build work starts
Ask DemandScience, SmartBug Media, or SmartSites how lead, account, and engagement fields are normalized into one schema for routing and attribution. Require an upfront field mapping plan because multiple providers flag schema and identity alignment as the setup work that determines how well automation scales.
Confirm the automation event model and integration surface used for lifecycle updates
Request a walkthrough of the event types used for lead capture, enrichment, and campaign event syncing for providers like DemandScience and WebFX. Favor providers such as DemandScience and ZETTER that tie automation to an API-backed event model for lifecycle tracking and handoff.
Test extensibility through custom enrichment and routing configuration paths
For RevOps-led teams, require GTMnow or WebpageFX to show how custom enrichment can be added through their API surface and mapping design. For teams with atypical lead schemas, check whether the workflow configuration effort increases because providers like WebFX and Single Grain note custom configuration complexity when schemas deviate.
Demand governance coverage for routing and automation changes
Require RBAC-aligned permissions and audit log trails for configuration changes from GTMnow, DemandScience, or ZETTER. If RBAC tooling is not self-serve, clarify what governance steps exist for access boundaries and traceability so nonstandard changes still produce auditable outcomes.
Stress test high event volume behavior for batching and job scheduling assumptions
Ask WebpageFX and ZETTER to describe rate controls and throughput tuning patterns for high inbound spikes. WebFX and SmartSites also note that throughput and job scheduling behavior may require scoping during implementation.
Which teams get the most from governed inbound lead generation execution
The strongest match is teams that need deterministic routing from inbound capture into CRM lifecycle fields with documented automation behavior. These are usually RevOps teams or marketing operations teams that must coordinate schema changes across multiple systems.
Buyers also need to match governance depth to team structure. Providers with audit trails and RBAC scoping work best when multiple stakeholders change routing logic over time.
RevOps teams needing governed inbound routing across multiple systems and schemas
GTMnow fits because it pairs RBAC with audit log trails and supports config-driven automation with an API surface for schema-safe routing changes. DemandScience also fits when teams need event-driven automation that keeps lifecycle handoffs aligned with CRM status updates.
Marketing ops teams prioritizing schema normalization for consistent lifecycle attribution
SmartBug Media and SmartSites fit because they normalize lead, account, and engagement fields into consistent schemas for routing and webhook or event ingestion. Single Grain also fits when integration-first schema mapping is the central operational requirement.
B2B teams that want API-led provisioning and workflow automation extensibility
ZETTER fits because it provides documented API-led provisioning for lead routing, enrichment events, and campaign attribution handoffs with RBAC scoping and audit log trails. DemandScience fits when the team needs an API-backed event model for tracking and sales handoff through configured workflows.
Teams that need managed form-to-CRM execution with attribution continuity
WebFX fits because it emphasizes form-to-CRM provisioning with schema mapping and tracked attribution continuity. WebpageFX also fits when lead routing configuration must map inbound events into CRM objects and lifecycle stages without spreadsheet-based operations.
Pitfalls that break inbound lead automation even when capture traffic looks healthy
Mistakes cluster around schema alignment and governance coverage. When lead identity rules and permissions are not defined early, automation changes become harder to audit and routing becomes inconsistent.
Another recurring issue is assuming automation extensibility without testing throughput at high event volume. Multiple providers flag event batching, rate controls, or implementation scoping as necessary to keep lead lifecycle execution stable.
Skipping upfront schema and identity alignment for lead routing fields
SmartBug Media and SmartSites highlight that identity and schema rules need upfront alignment before automation scales. DemandScience and GTMnow also rely on a schema-aware lead and campaign model, so buyers should require a concrete field mapping plan before workflows go live.
Treating the integration surface as a black box instead of defining the event model and API contracts
If the provider cannot clearly describe the event types used for capture, enrichment, and campaign syncing, lifecycle handoffs will drift. DemandScience and ZETTER provide API-backed event modeling and API-led provisioning, which makes custom routing and enrichment changes easier to reason about.
Allowing routing configuration changes without RBAC and audit log trails
GTMnow and DemandScience focus governance around RBAC-aligned access and audit logging for routing changes and configuration updates. ZETTER also includes RBAC scoping and audit log coverage, which buyers should insist on when multiple teams will modify automation.
Ignoring throughput behavior during campaign spikes
WebpageFX notes that high-volume throughput may require tuned event batching and routing rules. ZETTER points to throughput tuning and rate control design work, so buyers should run a volume rehearsal or define throttling expectations during implementation.
How We Selected and Ranked These Providers
We evaluated DemandScience, GTMnow, SmartBug Media, Single Grain, WebFX, Thrive Internet Marketing Agency, WebpageFX, Lyfe Marketing, SmartSites, and ZETTER on capabilities, ease of use, and value, then built an overall score as a weighted average where capabilities carries the most weight and ease of use and value each contribute the same share. Each provider is ranked by how directly its inbound lead generation workflows connect capture to CRM-ready lifecycle updates using an explicit data model and an automation surface.
DemandScience separated itself from lower-ranked providers by combining configuration-driven lead lifecycle automation with an API-backed event model for tracking and handoff. That specific capability lifts performance in the capabilities category because it makes integration depth and lifecycle execution more deterministic than purely managed routing steps.
Frequently Asked Questions About Inbound Lead Generation Services
How do inbound lead generation services handle lead, account, and campaign data models across CRM and marketing tools?
Which providers expose an API or integration surface for lead lifecycle events and automation workflows?
What setup steps typically exist for wiring inbound forms or ad sources to CRM lead objects?
How do providers control access for admins and route changes across teams?
What audit and monitoring artifacts help teams troubleshoot incorrect routing or stale enrichment data?
How do these services support extensibility for new lead fields, new sources, or new routing rules?
Which provider fits best when lead routing must be governed across multiple systems and schemas in parallel?
How do services handle data migration or mapping when a team changes CRM fields, object structure, or environments?
What common technical failure points occur with inbound lead generation services, and how do providers mitigate them?
Conclusion
After evaluating 10 sales enablement, DemandScience stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Sales Enablement alternatives
See side-by-side comparisons of sales enablement tools and pick the right one for your stack.
Compare sales enablement tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.