Intent Data Pricing: Starting at $500/mo and Total Costs

MarketPulse intent-data plans are starting at $500/mo. To compare a program fairly, add setup, review, activation and measurement costs to the subscription, then divide by a clearly defined usable outcome.

This guide explains current MarketPulse allowances, cost per pull, pricing models and a total-cost workbook. BrandWell publishes this article about its own product. The budget examples are fictional, not a claim that every business incurs the same costs or results.

MarketPulse plans and cost per pull

• Starter: One topic, weekly pulls and up to 25,000 contact exports per month.
• Growth: Three topics, daily pulls and up to 100,000 contact exports per month.
• Scale: Ten topics, daily pulls and unlimited contact exports.

To calculate effective cost per pull, divide the subscription cost by the Intent Scans actually used during the same period. A pull retrieves available data from the previous 24 hours for one topic. Unused allowances increase the effective cost per consumed pull; fields, counts and audience overlap vary.

To calculate effective cost per pull, divide the subscription cost by the Intent Scans actually used during the same period. A pull retrieves available data from the previous 24 hours for one topic. Unused allowances increase the effective cost per consumed pull; fields, counts and audience overlap vary.

Audience size, available fields and overlap vary. A pull does not guarantee a minimum number of usable prospects or purchases. Growth and Scale include AIMEE for the initial user. Channel usage, fulfillment and additional products may cost extra.

Review the current MarketPulse plans and terms before purchase. An early-access promotion is a separate, time-limited offer for an eligible recipient. Do not substitute its price for the standard public plan in a general cost comparison.

Five pricing models to normalize

1. Fixed subscription: Compare the included topics, refreshes, exports, users and selected products.
2. User-based pricing: Count the actual access needed, minimum seats and expansion rules.
3. Usage-based pricing: Define the billable unit, included allowance, failed work and applicable limits.
4. Managed service: Separate the platform from implementation, operations, reporting and media.
5. Custom scope: Obtain a written price schedule for the defined coverage and workflow.

These are comparison categories, not statements about named providers. A quote-required result is useful when the exact scope is unknown. Record evidence separately from an analyst’s estimate and retain the date of each quote.

Calculate the workflow’s full cost

Begin with one defined revenue workflow and its units: accounts monitored, topics, regions, users, records enriched, audiences activated, client tenants, and qualified outcomes. Price the system that produces the outcome. A vendor may quote by platform, user, topic, credit, record, API call, media percentage, service, or a mix; the invoice alone does not reveal comparable cost.

Use this planning equation: total operating cost = fixed platform and license + variable data and usage + setup and integration + services and support + media and activation + internal labor + governance and risk + renewal and exit exposure. Convert every quote to the same time horizon, scope, expected usage, and adoption scenario.

Build a comparable pricing workbook

Create a pricing workbook with inputs, vendor evidence, buyer assumptions, formulas, sensitivity cases, and decision notes. Keep public fact, written quote, BrandWell-provided planning, and analyst assumption in separate columns. Record units, included allowance, overage, minimum, billing cadence, term, renewal, change right, and source for every line.

1. Freeze the ICP, use case, accounts, topics, geographies, users, modules, integrations, destinations, support, and outcome.
2. Test representative coverage, freshness, identity, required fields, validation, activation acceptance, and operational effort.
3. Request a written price schedule, order form, implementation statement, data terms, support scope, renewal language, and exit obligations.
4. Normalize fixed and variable charges into base, expected, high-usage, low-adoption, expansion, and exit scenarios.
5. Add internal roles and hours for setup, data, RevOps, media, sellers, analytics, QA, training, privacy/security, support, and procurement.
6. Calculate coverage-adjusted cost, qualified-outcome cost, contribution or gross-profit sensitivity, and stop thresholds before selecting.

Platform, service or in-house work

A platform shifts more configuration and operation to the buyer but may create reusable internal capability. A managed service bundles expert labor and can shorten time to value, but scope, transparency, portability, and margin must be examined. Building in-house can make sense with proprietary first-party signals, engineering/data maturity, strict control needs, and enough scale to fund ongoing identity, policy, security, support, and product maintenance.

A manual or non-intent approach is the baseline for small markets and unsettled ICPs. Price researchers, list building, enrichment, rep time, missed timing, and quality control honestly. In-house is not free, and managed service is not automatically expensive; compare the same outcome and include opportunity cost.

Fees and quote requirements

Hidden costs most often appear in seats, topics, credits, account universes, exports, phone/email fields, validation, APIs, connectors, implementation, migration, professional services, support tiers, advertising fees, media, client tenants, data storage, overages, training, QA, privacy/security, renewal increases, minimum terms, and exit support. Ask which features in the demo are not in the quote.

Build sensitivity cases. The base case uses expected accounts, users, signals, match, action, and support. The high-usage case adds topics, enrichment, exports, audiences, clients, and overages. The low-adoption case keeps the contract cost but reduces active users and seller action. The expansion case adds a region or business unit. The exit case includes data return, deletion, migration, replacement overlap, and lost workflow capacity.

Request a current written scope and price schedule. Distinguish a public list price, an eligible promotion, a quote and your own budget assumption. Do not infer a universal price or contract term from an anecdote.

Connect cost to usable findings

Price must be joined to signal quality. Track fit coverage, relevant-topic coverage, freshness, account resolution, person or role coverage, field completeness, validation, permitted-use yield, destination acceptance, match, rep adoption, qualified outcomes, and corrections. A low license can have a high cost per usable account; an expensive platform can be economical if it replaces several tools and the team uses it.

Use gates before weighted scores. If a provider cannot cover a required geography, supply a permitted field, integrate with the system of record, or meet security requirements, a lower price should not compensate. For tradeoffs, weight only business-relevant dimensions and show how the decision changes under conservative assumptions.

When the cost may make sense

Intent data is easiest to justify when deal value and volume can fund prioritization, topics map to actual buying problems, the addressable market is large enough for data coverage, teams can act quickly, and outcomes are reliably recorded. Multi-product, enterprise, expansion, advertising, and agency-reseller motions can benefit when timing and coordination matter.

It is harder to justify for a tiny market, very low contract value, undefined ICP, no action capacity, weak CRM, sparse signals, sensitive uses, or leadership expecting certainty. Start with a coverage assessment and manual baseline. Decline a long, high-minimum contract if the team cannot define what it will do with one qualified signal.

Measure outcomes and full cost

Calculate cost per raw record only for data operations. For the commercial decision, calculate cost per usable account, activated account, rep-accepted account, accepted opportunity, win, and incremental gross profit. Show the numerator and denominator, observation window, segment, adoption, and confidence. Compare with the baseline and include all channels that touched the account.

ROI should use incremental gross profit when a credible holdout, randomized test, or staged comparison supports it: (incremental gross profit − total operating cost) ÷ total operating cost. Platform-attributed or influenced pipeline can support diagnosis but is not automatically causal. A short pilot may prove coverage, integration, and adoption without proving revenue.

Budget for operating risk

Contract risk includes auto-renewal, notice windows, price changes, minimums, non-cancellable commitments, seat floors, lost credits, restricted exports, data deletion, transition support, service dependencies, and unclear remedies. Procurement should model the expected and downside cases and assign an owner to every renewal trigger.

Include the cost of reviewing the actual data use, access, retention, suppression, security, service providers and incident handling. Obtain qualified review where needed. A budget worksheet is not a legal or compliance determination.

Data-quality and adoption risks include wrong companies, stale employment, invalid contacts, broad topics, opaque scores, model drift, duplicate workflows, seller distrust, unused seats, and poor outcome capture. Price monitoring and remediation rather than assuming quality remains fixed for the contract term.

Price an agency service

An agency can quote distinct services: a coverage assessment, setup, approved data use, operations, quality review, activation, reporting, media and custom work. Budget only the rights and usage established by the actual subscription and client scope. Include labor, exceptions, management and support when pricing the service.

Reconcile subscription usage and client scope each billing cycle. Show topics, usable findings, actions, qualified outcomes, full cost, limitations and the next decision. A proposed service package does not establish white-label, wholesale or resale rights.

Common questions

Why do many intent-data providers use custom quotes?

Scope varies by accounts, topics, data products, users, credits, geography, integrations, support, services, and activation. Custom pricing is not automatically bad, but it makes a normalized written workbook and contract review essential.

Should annual value be divided by twelve?

That can normalize the license for comparison, but it does not turn an annual commitment into a cancellable monthly plan. Preserve payment timing, non-cancellable amount, renewal, implementation, usage, and exit exposure.

What is the most important hidden cost?

Usually the largest unmodeled category is internal adoption and operation: data work, integration, seller behavior, QA, reporting, and change. The answer varies, so price each role and hour instead of applying a generic percentage.

Can a public price replace a quote?

No. A public amount can anchor a line item, but the current offer, rights, limits, term, services, and buyer scope need a written quote and order. If a page is inconsistent or promotional, preserve the uncertainty.

A fictional monthly cost worksheet

For a hypothetical pilot budget, use a $500 software allocation, four hours of setup at $60/hour, six hours of operating review at $60/hour and $300 of separate activation spending. First-month cost is $500 + $240 + $360 + $300 = $1,400. Without repeated setup, the assumed ongoing month is $1,160. These are fictional planning inputs, not a product quote.

If the first month produces 1,000 reviewed records, 200 unique usable accounts and 20 accepted opportunities, the respective allocations are $1.40 per reviewed record, $7 per usable account and $70 per accepted opportunity. They measure different stages. Deduplicate accounts and keep the observation window consistent.

To calculate effective cost per pull, divide the subscription cost by the Intent Scans actually used during the same period. A pull retrieves available data from the previous 24 hours for one topic. Unused allowances increase the effective cost per consumed pull; fields, counts and audience overlap vary.

Stress-test low adoption: if only 100 accounts are usable at the same $1,400 cost, cost per usable account doubles to $14. More raw records do not necessarily make the program more economical.

Start with a bounded research workflow

In MarketPulse, select relevant topics, apply the saved ICP and review available findings before activation. Keep the source, observation time, filters and action with your operating record. Prepare an Outreach or Direct Mail workflow only when it fits the approved use; include its separate costs.

AIMEE can help prepare account research and connected tasks according to configured tools and access. It does not replace cost accounting, outcome validation or an accountable decision owner.

Explore MarketPulse and its current plans or review the BrandWell product directory to scope the workflow before committing.

Reviewed and updated October 3, 2026.

Written by

Farnaz Kia