Pricing FAQ
Questions Demand Gen,
Sales,
and procurement ask
before they start.
Which tier should I start with?
Start with the lowest evidence depth
that answers the question
your current Sales motion needs answered.
Use IA Demand for qualified response,
IA Verified when Sales needs inspectable evidence,
IA Intent when account priority matters,
and IA Buying Group when stakeholder coverage
becomes operationally necessary.
Why does CPL increase by tier?
The commercial object changes by tier.
Higher tiers add additional evidence,
account context,
and buying-unit requirements
rather than selling the same delivery event
at four prices.
Why pay $55 when another vendor quotes a lower CPL?
Compare the commercial object delivered
and the cost of leads Sales actually accepts,
not headline CPL alone.
Use your CRM acceptance definitions
to evaluate the economics.
What is included in the program minimum?
The minimum covers the contracted activation scope,
audience requirements,
campaign execution,
qualification,
reporting,
and evidence configuration
relevant to the selected tier.
Can CPL vary from the prices shown?
Yes.
Geography,
audience scarcity,
seniority,
account density,
volume,
evidence requirements,
integrations,
and buying-group complexity
can change final pricing.
Does Intent Amplify guarantee Sales acceptance?
No.
Sales acceptance depends on
the customer's agreed operating definition,
qualification criteria,
CRM process,
and Sales workflow.
Does engagement automatically create an SQL?
No.
Engagement is evidence,
not automatic qualification.
SQL eligibility should remain governed
by the customer's agreed ICP,
evidence,
commercial,
and CRM criteria.
Does Intent Amplify guarantee pipeline or revenue?
No.
Pricing represents contracted program scope
and evidence depth.
Downstream outcomes depend on
market conditions,
audience,
offer,
Sales execution,
CRM definitions,
and program design.
Are the Zendesk numbers actual customer results?
No.
The quantitative figures shown
in this pre-live build
are modeled placeholders.
They must be replaced with
verified CRM-backed outcomes
and approved customer usage rights
before public publication.
