Will AI Agents Kill the Lead List? (2026)

AI agents autonomously monitor and score live intent signals before a lead enters your CRM.

Static lists capture a single point-in-time snapshot that cannot detect changes after export.

The choice between them determines your cost-per-lead, data decay exposure, and compliance risk.

You've been pitched AI agents by three vendors this quarter.

Each one claims static lead lists are dead, but none showed you the** actual cost-per-lead math** or what happens when an agent mis-scores a new market.

That gap between vendor promise and operational reality is where most teams get stuck.

The real answer isn't "agents or lists": it's matching your approach to your pipeline stage and data maturity. A validated, scaling sales motion with 100+ historical conversions? Agents justify their cost.

New market, thin conversion history, tight budget? Static lists are safer and more predictable. Most teams need both, layered differently.

This guide gives you the framework to decide. Not another vendor pitch: the actual trade-offs, break-even math, and a decision tree for your team's stage.

Why Is Everyone Talking About AI Agents for Lead Gen Right Now?

AI agents moved from pilot to mainstream in B2B sales because intent-signal processing crossed a cost threshold that static lists can't match.

Enterprise adoption accelerated when vendors embedded scoring directly into existing CRM and sequencing workflows.

An AI agent for lead generation is software that autonomously monitors intent signals, scores prospects against your ICP in real time. It then triggers enrichment or outreach actions, without requiring manual list refreshes between cycles.

The early wins are real: 54% of B2B sales teams now use some form of AI agent for prospecting workflows, and those teams report a 34% reduction in prospect-research time on average.

The momentum is undeniable.

LinkedIn (Sales Navigator AI), Apollo.io (Apollo AI), and Hunter.io have each launched or expanded AI-powered lead-scoring and outreach automation features since 2024, making agent functionality table stakes across the major prospecting stacks.

Every platform now promises to "let AI do the digging."

But here's what's missing from the conversation: a real framework for when AI agents actually outperform a well-curated, exported lead list.

Most vendors and articles treat AI agents and static lists as equivalent, or they'll tell you agents are always better because they're "always learning" or "always working." That's incomplete.

What Just Changed to Make This Possible

Four technical shifts converged in 2024 to move agents from pilot to production scale:

Real-time intent APIs dropped below $0.02 per lead when combined with LLM reasoning, making continuous re-scoring cheaper than one-off static enrichment.

Compound lead-scoring agents now continuously re-score prospects using first-party website behavior plus funding/hiring triggers instead of static firmographic snapshots.

Agent frameworks now output structured stakeholder data that plugs directly into Outreach, Salesloft, and Apollo sequences.

Autonomous stakeholder-mapping agents analyze a target account's buying committee, tag pain points per role (CFO, VP Eng, champion), and route each contact into a tailored orchestration sequence, without requiring manual rep research.

Persistent signal-monitoring agents can watch funding rounds, exec hires, and tech-stack changes, then auto-re-engage cold leads only when intent spikes.

Nurture agents no longer rely on a rep-owned "check back in 6 months" task; they trigger reactivation autonomously.

Conversational LLM agents can now conduct BDR-style discovery and write structured outputs to CRM fields without human triage.

Qualification agents triage inbound leads via chat or email, ask discovery questions, and route to the right rep in under four hours.

I'll walk you through the real trade-offs: where agents win, where static lists still dominate, and how to know which one (or both) fits your process.

What Do AI Agents and Static Lead Lists Actually Do Differently?

AI agents continuously monitor and score live intent signals before a lead enters your CRM; static lists capture a single point-in-time snapshot that cannot detect changes after export.

Here is what each approach actually does.

What an AI Agent Does to a Lead Before It Hits Your CRM

Platforms like Evaboot, are designed using agents to do what static lists can't: watch intent signals continuously.

Job changes, company funding, hiring sprees, industry mentions, the agent catches them all and scores each lead against your ICP in real time.

The agent tracks engagement velocity too. Engagement velocity is the rate at which a prospect advances through research behaviors, page visits, content consumption, competitor tracking, within a defined time window.

How fast is the prospect moving through research? What content have they consumed? Which competitors are they tracking?

The moment an intent signal fires, the agent flags it, enriches it with context (recent role change, budget clue, competitor research), and qualifies it before it touches your CRM.

The lead arrives pre-scored: fit confidence, intent confidence, recommended next action. Because agents work autonomously, they scale across hundreds or thousands of leads without you lifting a finger.

If a lead's status changes, the agent re-qualifies it automatically.

What a Static List Does, and Doesn't, Track

A static list is a snapshot. You build your search filters in Sales Navigator, add emails, clean titles, check for duplicates, and download the CSV.

That list can't detect job changes after you export it. It can't sense when a prospect suddenly starts researching your category, and it can't flag intent signals, only demographics and historical data.

To match what an agent does, you'd need to re-export and re-enrich that same search every week or two. Then manually compare new results to the old list and flag only the changes.

At scale, that's structurally impossible. Static lists capture no velocity, no real-time intent, and no autonomous qualification, only point-in-time fit.

ROI Breakdown: When Do AI Agents Pay, and When Do Static Lists Win?

AI agents break even in months 4–6 for a 10-rep team once you account for infrastructure costs, data refresh cycles, and deliverability erosion from stale lists.

Static lists never break even because they lose value every quarter.

The real gap between AI-agent claims and list-based reality? Cost structure and data decay. I'll show you when each approach wins, and the hidden costs most benchmarks ignore.

Industry data indicates that sales teams using AI agents report higher average revenue growth (approximately 83%) compared to teams relying on traditional list-based motions (approximately 66%).

Note that these figures reflect the proportion of teams reporting growth, not absolute growth rates.

But that upside depends entirely on data maturity and realistic ramp costs. Once you account for agent licensing, setup, and ongoing maintenance against list purchase, enrichment, and refresh cycles, the economics shift dramatically.

The Cost-Per-Qualified-Lead Math: A Worked Example

Let's say you're running a 10-rep SDR team with a 1,000-contact outbound motion quarterly. An AI-agent setup costs roughly $2,000–$4,000 in licensing, initial data cleaning, and integration.

Maintenance runs ~$500/month. That's $8,000–$10,000 annually for agent infrastructure.

A static-list approach costs $1,200 for the initial list, $800 for email enrichment (to get beyond the ~30% of on-profile emails), and $400 every three months for refresh.

B2B data decays at a significant rate each month, compounding to meaningful annual losses in list quality.

Total: $3,600–$6,000 annually.

Here's where it breaks down: stale data creates hidden drag. Email deliverability on aged lists drops materially; bounce rates spike and throttle your sender reputation.

A 10-rep team sending 4,000 quarterly outbound emails faces hundreds to over a thousand extra bounces on decayed lists. Each one erodes domain authority and forces more re-list purchases.

When you calculate cost-per-qualified-lead, the agent cost stabilizes immediately. The list cost explodes as data ages.

You hit break-even on the agent once you've sent ~2,500 qualified touches. The list never breaks even: it requires constant replacement.

Break-Even Timeline: How Long Before Agents Outperform?

A 10-rep team sees break-even in months 4–6 if agents hit even 15% of the promised open and reply lift. That's conservative.

Smaller teams (3–5 reps) break even later (around month 9–12) because fixed infrastructure costs spread across fewer touches.

Static lists never hit break-even. They lose value every quarter.

The decay cost compounds: each refresh cycle adds labor (re-upload, re-cleaning, re-enrichment). Every bounce degrades sender reputation and forces offline mitigation: domain warming, IP rotation, list scrubbing.

Timing matters: if you're already managing a static list and planning to scale in H2, model agent costs against your current refresh and bounce budgets.

If refresh cycles consume 15–20% of your annual tool spend, agents break even faster.

CAC Reduction and Time-to-Qualification: The Two Missing ROI Metrics

Cost per qualified lead is half the ROI story. Buyers justify agent spend to finance with customer acquisition cost (CAC) and qualification speed, because both tie directly to sales capacity and payback period.

CAC reduction ranges:

Agents that score and route leads cut wasted rep time on unqualified contacts. Peers report 20–30% CAC reduction when agents replace manual list-building and first-pass qualification. The savings come from two places:

Track CAC monthly. If it's flat after 90 days of agent deployment, your agent isn't filtering, it's passing through the same low-quality volume your static list delivered.

Time-to-qualification benchmarks:

Qualification speed matters when your reps are capacity-constrained.

An agent that routes hot leads to the top of the queue and deprioritizes cold contacts cuts qualification time by 40–60%, measured as days from lead-create to SQL.

The time savings show up in two places:

Measure time-to-SQL in your CRM. Compare the 90 days before agent deployment to the 90 days after.

If the median hasn't moved, your agent is scoring everyone medium and routing nothing, a config problem, not a model problem.

Why these matter for your CFO: CAC and time-to-qualification translate directly to sales capacity. A rep who qualifies leads 50% faster can carry a 50% larger territory without adding headcount.

That's the ROI case that gets budget approved.

What Does Data Decay Actually Cost You, and Who Pays for It?

Data decay costs the average B2B team a meaningful share of its annual list spend in rework, bounced email remediation, and lost pipeline velocity, and the cost falls almost entirely on the SDR and marketing ops functions.

B2B contact data doesn't stay fresh: it degrades at a measurable, predictable rate.

A list exported today will have lost a meaningful percentage of valid contacts within a year due to job changes, email bounces, and company moves that compound without active maintenance.

That erosion compounds across your teams and budget. A sales rep working with a stale list chases dead emails and outdated job titles instead of reaching active prospects.

Marketing automation sends campaigns into the void. Revenue cycles slow because pipeline velocity tanks.

And your compliance team inherits duplicate, conflicting, or outdated records, each one a remediation cost.

But data decay isn't inevitable. It's a consequence of how we export.

When I pull a list from LinkedIn Sales Navigator, I get a snapshot, a moment frozen in time. It doesn't update when a contact changes jobs, gets promoted, or leaves the company.

Without a refresh cadence, that moment just sits there, getting staler. The industry feels this.

74% of teams name data hygiene as a top priority. Even AI-forward organizations see decay as the root blocker, not a nice-to-have concern.

There are two levers. First, enrich what you export: cleaned names, company data, validated email addresses reduce where decay takes hold.

Second, establish a refresh rhythm. Re-export and re-validate key lists every 3–6 months using tools like Evaboot's URL enrichment to re-check old LinkedIn profiles against current snapshots and flag what shifted.

Without that cycle, decay runs silent. With it, you recapture pipeline velocity and eliminate the hidden tax of rework.

Where Do AI Agents Break Down, and What Are the Real Failure Modes?

AI agents break down in three specific scenarios: hallucination from thin training data, cold-start mis-scoring in new markets, and runaway spend before precision metrics stabilize.

Each failure mode is predictable and preventable with the right guardrails.

Hallucination and Model Drift in Lead Scoring

An AI agent trained on thin or biased historical data confidently mis-scores leads, assigning high intent to prospects who don't fit your ICP.

The drift gets worse when the training set over-represents one customer segment or lacks diversity across deal sizes.

Two guardrails work.

First, enforce a human review threshold: agents should flag candidates for review rather than fire unsupervised outreach. Second, audit scoring decisions quarterly by sampling mis-scored leads and retraining on real outcomes.

Without these checks, model confidence masks systematic error, and runaway low-quality touches degrade your sender reputation long before you notice the decay.

Cold-Start Problems and Runaway Spend

A cold-start problem occurs when an AI agent lacks sufficient historical conversion data to calibrate its scoring signals, causing it to default to volume-over-precision guesses that burn deliverability and budget.

The result is predictable: high-volume, low-quality touches that burn deliverability, waste budget, and train the model on poor feedback loops.

A prospect who ignores a poorly targeted message isn't a bad fit: they were never targeted correctly.

Seed the agent with curated seed lists of known good customers and lost deals, and enforce spend caps during the first 60–90 days while precision metrics stabilize.

Early volume is not an asset. Early accuracy is.

Static Lists: Decay, No Adaptation, and the Compounding Miss

Static exported lists don't hallucinate, but they degrade silently. B2B data decays at a measurable rate each month: job changes, email bounces, and company moves compound without adaptation.

Unlike agents that retrain on live signals, a static list from three months ago carries measurable staleness that only accelerates.

Refresh exported lists every 3–6 months, and cross-check against your CRM before re-engagement to catch the biggest changes.

Static lists also cannot respond to shifts in your ICP. If your ideal buyer profile sharpens mid-year, an old export cannot adapt.

Honest assessment: agents win on flexibility, but only if their scoring guardrails are tight.

Training-Data Bias: When Your Agent Systematically Excludes Valid ICP Segments

An agent trained on historical wins will replicate the biases in your past pipeline.

If your first 50 deals skewed enterprise because you had one whale account, the agent will underweight mid-market leads, even when your 2026 strategy targets them.

Common bias patterns:

How to catch it: Run a weekly report of leads the agent scored below threshold. Look for patterns in industry, company size, or geography.

If an entire segment scores low but matches your documented ICP, your training data is biased.

The fix is manual: tag those leads as "high-value" in your CRM and retrain.

Most platforms let you override agent scores for specific cohorts, which reweights the model without discarding the original training set.

How to Build a Feedback Loop That Keeps Your Agent Current

An agent without a feedback loop decays. Reps accept or reject leads every day; closed-won data arrives every month.

If none of that flows back into the model, you're running last quarter's ICP against this quarter's market.

The mechanics:

Why now: Most CRMs (HubSpot, Salesforce, Pipedrive) added agent-feedback APIs in 2024–2025. You no longer need a data-engineering team to close the loop, it's a workflow config, not a build.

Without this loop, your agent becomes a static scoring model that ignores everything your reps learn after deployment. You'll retrain quarterly, notice the model hasn't improved, and blame the vendor.

The model didn't fail, you starved it.

Which Approach Fits Your Pipeline Stage? A Decision Framework for 2026

Stage 1, New Market or Early ICP: Why Static Lists Win Here

Without conversion history, AI agents hallucinate. They over-fit, chase false patterns, and burn budget along with your sender reputation.

Static lists with tight ICP criteria are faster to validate and cheaper to run.

You define your ideal customer profile once, apply a cleaning algorithm (like Evaboot's double-filter validation), and ship a predictable cohort with zero model retraining.

Entering a new vertical or geography? Under 50 closed deals? Static lists are your safer bet.

Stage 2, Validated ICP, Scaling Volume: Where Agents Start to Pay

Agent ROI flips positive when you have the right foundation: 50–100+ historical conversions, enrichment infrastructure already in place (email finder, phone appends, intent signals), and one person watching agent performance weekly.

Now agents learn from your past wins and losses. They catch ICPs your static rules missed. They scale volume without hiring headcount.

Clean, enriched historical data and the bandwidth to monitor drift? Agents justify their cost and unlock gains static lists can't touch.

The Hybrid Path: Using Static Lists as Agent Training Data

Here's what we've seen work: run static lists as your feeder and validation layer for agent training.

Curated, enriched static lists become your agent's initial training set: less cold-start hallucination, and you keep list-level predictability.

Ship a static list in month one. Agents use that list's conversion outcomes to learn in parallel.

By month two, the agent is tuned and you run both together: static list as your baseline, agent as your upside.

This bridges early-stage predictability with later-stage agent gains.

Research on multichannel outreach shows reply rates can improve significantly when list type and channel strategy align, so layering a static baseline with agent-driven outreach compounds your edge.

How Do You Define the ICP Your AI Agent Will Learn From?

An agent is only as good as the pattern it trains on.

Before you configure a single filter, you need a documented ICP that your agent can use to recognize good leads and ignore noise.

Start with your last 50 closed-won deals. Not leads. Not opportunities. Closed revenue. Pull firmographics, behavioral signals, and disqualifiers from those accounts.

Questions to Answer Before You Build

Answer these for every agent deployment. Skip one and the agent will drift or hallucinate within weeks.

Why this matters: An agent trained on "50+ historical conversions" without documented disqualifiers will score leads that look right on paper but die in discovery.

You're teaching it what worked, not what failed, and both matter.

Write the ICP as a checklist, not a narrative. Your agent (and your reps) need binary yes/no decision points, not interpretive guidance.

Which Tools Support Each Approach, and What Does the Stack Actually Look Like?

Static List Stack: Sales Navigator + Enrichment + Evaboot

We built this stack around a simple workflow: search Sales Navigator (job title, company, location, skills), export with Evaboot, enrich in bulk, and ship to your outreach tool or CRM.

Here's how it works. You install the Evaboot Chrome extension, run your search in Sales Navigator, and click the Export button we add to the interface.

Evaboot adds verified emails automatically, so you download the cleaned CSV and you're done.

Our cleaning algorithm fixes first names, last names, company names, and job titles automatically. The "No Match Reasons" column flags leads that don't fit your criteria and tells you why.

If your data gets stale, you can re-upload old LinkedIn URLs to refresh enrichments every 3–6 months.

We see this work best for teams running 5–50 campaigns per month with tight, repeatable segments. It scales to Sales Navigator's export limits, and fits budgets under $500/month (Sales Navigator Core + Evaboot).

It works hardest when your ICP is narrow enough that a single search gives you 80%+ usable results.

The trade-off: you can't automate intent detection, trigger outreach, or real-time lead scoring. Every campaign means manual discovery and list-building.

AI Agent Stack: What You Actually Need Before You Buy

An AI agent automates discovery, prioritization, and outreach sequencing, but it demands three prerequisites that most teams skip.

CRM data quality comes first. The agent needs clean company names, accurate job titles, and recent activity logs to score and sequence reliably.

If your CRM is fragmented or full of duplicates, the agent will scale those errors.

Intent data feed comes second. The agent needs a real signal of buying intent: website visits, content engagement, earnings calls, funding news, to know which leads to target today.

Without it, you're stuck with demographic matching, which is static and weak.

Human oversight capacity comes third. The agent generates hundreds of leads and threads per week.

You need a person or process to validate decisions, tune rules, and catch drift.

If you can't commit 5–10 hours per week to agent work, the tool will degrade within 30 days.

When all three are in place, an agent stack justifies $2,000–$5,000/month and scales to 500+ leads per week with minimal manual list-building.

The agent-versus-static-list debate masks a simpler truth: the quality of your underlying B2B data and your pipeline stage determine which approach wins, not the tool itself.

Before you adopt an AI agent, audit your current list decay rate. Pull a 500-contact export from three months ago, re-check it against LinkedIn today, and count how many job titles, company names, or email addresses have shifted.

That decay number is your hidden cost, and it's the same cost an agent will inherit if your CRM and enrichment foundation aren't clean.

If decay is running high, fix your refresh cadence first. If your ICP is validated (50+ historical conversions) and your enrichment infrastructure is solid, agents justify their cost.

If you're entering a new market or validating fit, static lists with tight filtering are safer and cheaper.

Start here: measure your list decay this week. Then use automated lead list building and bulk LinkedIn URL enrichment to close the gap between your current refresh cadence and what your pipeline actually needs.

How Do You Run AI Agents Without Breaking Your Pipeline?

Most AI agent deployments break on compliance exposure, CRM field-mapping conflicts, and insufficient team training, not on strategy. Here are the seven operational details that determine whether your rollout succeeds.

Deciding to use agents is the easy part. Most failed deployments die on the operational detail, not the strategy.

1. Compliance exposure, and how to mitigate it

AI agents touch more PII than a static list. They scrape, enrich, and store contact data in memory across sessions. That surface area matters if you operate in GDPR or CCPA jurisdictions.

The risk isn't the agent itself: it's how the platform handles data residency, retention, and consent.

Most AI prospecting agent vendors, including LLM-based tools built on OpenAI or Anthropic APIs, host memory in US cloud regions and retain conversation history indefinitely by default unless you explicitly configure retention limits.

If you're prospecting European leads, that's a compliance gap on day one.

Mitigation checklist:

Static lists let you control retention and residency because the data sits in your CRM. Agents centralize data in the vendor's environment, which shifts compliance ownership. Budget legal review time before you deploy.

2. Why agent integrations break, and what to test first

AI agents promise "plug and play" with your CRM and MAP. In practice, most early deployments fail on data sync, not intelligence.

Common failure modes:

Test these before production:

Static lists integrate via CSV upload or native connector. The failure surface is smaller because you control timing and field mapping in a single batch operation.

If your stack uses custom objects, middleware (Zapier, Workato), or legacy MAP infrastructure, add two weeks to agent integration timelines. The "setup in minutes" marketing assumes greenfield Salesforce + HubSpot.

3. How to map agent types to pipeline stages

Not every AI agent does the same job. Vendors bundle different capabilities under "AI agent," which makes comparison hard. Here's how to map agent types to where they actually help.

Research and prospecting agents scrape intent signals, enrich ICP fit scores, and build target account lists. They replace manual LinkedIn searches and technographic lookups.

Use these at top-of-funnel when you need more accounts that match a profile.

• Good for: seed-stage outbound, new market entry, account-based prospecting.
• Weak at: understanding your existing pipeline. They don't read CRM history or past email threads.

Qualification agents score inbound leads, ask discovery questions via chat or email, and route to the right rep. They replace BDR triage work.

Use these when inbound volume exceeds your team's capacity to respond in under four hours.

• Good for: SaaS free-trial funnels, high-velocity SMB motions, event lead follow-up.
• Weak at: complex enterprise deals where qualification needs a live conversation.

Engagement agents write personalized emails, follow up on opens/replies, and book meetings. They replace outbound cadence execution. Use these when your reps spend more time on sequence logistics than actual selling.

• Good for: high-volume outbound (500+ touches/week per rep), multi-threaded account campaigns.
• Weak at: deals that need video, voice, or demo-first outreach. Email agents can't record a Loom.

Nurture agents monitor buying signals (funding news, job changes, tech stack adoption) and re-engage cold leads when intent spikes. They replace manual "check back in six months" tasks.

Use these for long-cycle deals where timing matters more than your pitch.

• Good for: enterprise sales, seasonal buying windows, post-churn win-back.
• Weak at: creating urgency. If the signal isn't real, the agent just adds noise.

Most teams start with one agent type and add others as they prove ROI. Trying to deploy all four at once creates integration chaos and makes attribution impossible.

4. What it costs to train your team

AI agents fail when reps don't trust the output. That trust gap isn't technical: it's training.

The hidden cost: onboarding your team to work alongside an agent takes longer than teaching them a new tool.

Reps need to learn what the agent can decide, what it escalates, and when to override it. Most vendors ship a 30-minute product walkthrough and call it done.

What actually breaks:

Training budget for a 10-person sales team:

Static lists need zero behavior change. You upload, you call.

Agents require reps to shift from "I own this lead" to "I own this lead and I'm training the system." That's a muscle most teams don't build until after the pilot fails.

If your org has never run a structured sales enablement program, double the agent adoption timeline. The tech is ready faster than the people.

5. Which intent signals actually matter

AI agents tout "intent-driven prospecting." In practice, intent signal quality varies by three orders of magnitude.

Intent signal types, ranked by reliability:

Explainability is the filter. A good intent feed tells you why the signal fired: "Visited pricing page twice, spent 4min on Enterprise tier comparison, returned from [competitor.com] referrer." A bad feed gives you a score and no context.

Questions to ask your agent vendor:

Static lists don't use intent signals: you build the list from firmographic fit and manually check for triggers. Agents live on intent feeds, which means bad signals = bad prospecting at scale.

If you can't explain to a rep why the agent picked a lead, the rep won't work it. Prioritize platforms that surface signal provenance in the UI.

6. What guardrails keep agents from breaking your pipeline

AI agents make decisions. Without constraints, they'll make bad decisions at scale.

Guardrails you need on day one:

The failure mode: agents optimize for activity (emails sent, leads scored, meetings booked) without understanding business context.

A prospecting agent will happily email your CEO's golf buddy if the ICP fit score is high enough.

Static lists don't need guardrails because a human reviewed every name before upload. Agents prospect autonomously, which means you're trading speed for control.

The guardrails let you get the speed without losing your brand.

7. How agents fit into sales orchestration

Sales orchestration platforms coordinate multi-channel outreach (email, LinkedIn, phone, direct mail) across a buying committee. AI agents add a research layer before the sequence launches.

The agent then routes each stakeholder into a tailored sequence. The CFO gets ROI-focused emails. The VP Eng gets a technical whitepaper and a calendar invite to a live demo.

The champion gets a LinkedIn message referencing a mutual connection.

This only works if:

Where it breaks:

Static lists treat every contact the same. Orchestration + agents let you treat each stakeholder as a distinct sub-campaign.

That's powerful for enterprise deals with 6+ decision-makers. It's overkill for SMB sales where one person signs the contract.

If your average deal involves fewer than three contacts, skip stakeholder research agents. The complexity costs more than the lift.

Conclusion

No, AI agents are not killing the lead list. They are changing what the list is for.

A static export is still the cheapest way to reach a known ICP, and it is still the thing that keeps an agent from hallucinating its way through a cold start.

What agents kill is the manual refresh cycle around that list.

Run the hybrid: curate the list, let the agent watch it, and re-check the split every quarter as your data decays and your motion changes.

Frequently asked questions