Skip to main content

​
Operating Context & Funnels

Use this step to review your funnel baselines and configure per-product operating context so WisePilot prioritizes the right work for each product line.

​
When to Use

After product classification is complete and integrations are connected (GA4, HighLevel CRM, ad platforms).

​
Prerequisites

  • Product lines created (if multi-product)
  • At least one integration connected (GA4, HighLevel, Google Ads, or Meta Ads)

​
The Prompt

​
What Claude Does

  1. Checks data health using get_data_health — reviews data freshness and completeness per source
  2. Reviews onboarding status using get_onboarding_status — confirms integrations are configured
  3. Shows detected funnels — lists what stages are active based on connected integrations

​
Auto-Detected Funnel

WisePilot automatically builds your funnel from connected integrations: A website with only Google Analytics gets a 1-stage funnel (traffic). A website with GA4 + HighLevel gets a full 4-stage funnel from traffic through revenue.

​
Weekly Baselines

Every Monday, WisePilot computes:
  • 30-day and 90-day trailing averages for each funnel stage
  • Current week vs previous week comparison
  • Deviation from baseline — how far current performance is from normal
  • Trend direction — improving, stable, or declining
New data sources start in a warming up state until there are at least 7 days of data, ensuring baselines are reliable before they influence AI decisions.

​
Per-Product Baselines

When multi-product mode is enabled, baselines are computed at two levels:
  1. Website-wide — aggregated across all products (unchanged)
  2. Per product line — filtered to entities tagged with that product
This means each product gets its own constraint detection and priority multipliers.

​
Constraint Detection

WisePilot walks your funnel from top (revenue) to bottom (traffic), looking for the first stage significantly below its baseline:
  • Warning — Performance 15%+ below baseline for 1+ weeks
  • Critical — Performance 25%+ below baseline for 2+ weeks
  • Healthy — All stages performing within normal range

​
How Constraints Affect Prioritization

When a product has its own constraint, work items for that product use the product-specific multiplier. If no product-specific constraint exists, the website-wide constraint applies.

​
Product-Specific Overrides

Each product line can optionally have:
  • Primary KPI — which metric matters most for this product
  • Disabled stages — exclude stages from constraint detection
  • Funnel overrides — custom thresholds per stage
Configure these in Settings > Operating or ask Claude:

​
Viewing Your Operating Context

Navigate to Settings > Operating to see:
  • Operating Profile Card — detected vertical, funnel stages, data sources
  • Baseline Dashboard — current values, deviations, trend indicators
  • Per-product baselines — when multi-product is enabled
Most users never need to change anything. The auto-detected funnels and baselines work well for the vast majority of businesses. Only configure overrides if a product has a fundamentally different funnel shape.

​
Common Edge Cases

  • New product with no data — baselines show “warming up” until enough data accumulates
  • Products with very different funnels — use per-product overrides to disable irrelevant stages
  • Single-product websites — operating context works the same way, just without product-level splitting