Paid Intent-Data Pilots: Agency Scope, Credits and Scorecards

Define the pilot decision and limits

A paid pilot should answer a commercial decision, not imitate a full production deployment. The agency needs to learn whether target topics produce usable reports, whether prospects understand the offer, whether the sales playbook creates qualified conversations, and whether conservative client economics justify moving forward.

Use seven scoped pilot steps

1. 1. Write the pilot decision, buyer, topics, geography, and excluded use cases.
2. 2. Agree the agency pilot fee, deliverables, dates and acceptance rule in writing; buy only the product allowance actually required.
3. 3. Gather approved client context and verify the actual report format, rights and implementation.
4. 4. Review the agency-prepared research deliverable for relevance, coverage, uncertainty and intended use.
5. 5. Use an approved agency sales playbook with a bounded set of eligible prospects.
6. 6. Log replies, objections, proposed commitments, missing proof, and delivery concerns.
7. 7. Choose stop, revise, or sign a full plan based on written commitments and conservative economics.

Preserve the versioned decision log

Maintain one versioned record from the first client question through the final commercial decision. Record the eligible market, topic definition, signal source, observed time, identity state, validation state, fit decision, suppressions, reviewer, approved next action, downstream disposition, and fully loaded cost. Do not overwrite rejected, expired, duplicated, or corrected evidence. Preserve the original record and add a reason-coded disposition so the agency can explain what changed. Review the log with the client at an agreed cadence, then use the evidence to tighten qualification, remove noisy topics, revise service scope, and decide whether to stop or expand. This operating record is also the source for renewal reporting, exception handling, and any claim about adoption or outcomes. A polished dashboard without this audit trail can hide weak process quality instead of improving it.

The first control for this workflow is: Write the pilot decision, buyer, topics, geography, and excluded use cases. The final control is: Choose stop, revise, or sign a full plan based on written commitments and conservative economics. Those bookends keep the service tied to a buyer decision rather than raw signal volume.

Add a short review note whenever the policy, topic definition, client scope, source, identity rule, activation path, or outcome definition changes. The note should identify who approved the change, which records or clients it affects, and whether earlier results remain comparable. This helps expose process changes that could be mistaken for performance improvements. It also gives account teams a plain-language explanation when volume, acceptance, cost, or outcomes move between reporting periods.

Compare four paid pilot models

1. Low-cost sales-readiness pilot

Tests the offer, branded report, prospect response, and commitment path before full-plan signup. An agency can use this model when its own written pilot scope supports it.

Watch-out: It does not include every full-plan capability and cannot guarantee commitments.

2. Fixed-fee delivery pilot

Tests one client workflow with real operator effort and a defined deliverable.

Watch-out: The agency must cap data, integration, support, and revision scope.

3. Credited pilot

Applies some or all pilot fees toward a later contract when written conditions are met.

Watch-out: Credits can hide the actual cost of validation and should not pressure a poor-fit purchase.

4. Performance-contingent pilot

Ties fees to an agreed output or outcome.

Watch-out: Attribution, buyer behavior, sales execution, and small samples make outcome guarantees risky.

Current MarketPulse research workflow

BrandWell MarketPulse: intent data starting at $500/mo. Find people researching topics relevant to what you sell, apply saved ICP filters, and review available contact details before taking action.

MarketPulse plans are starting at $500/mo. Verify current package scope and offers on the product page.

MarketPulse standard monthly plans

Plan	Topics and refreshes	Monthly exports
Starter	1 topic, weekly	25,000 contacts
Growth	3 topics, daily	100,000 contacts
Scale	10 topics, daily	Unlimited contacts

Swipe the table to see all columns.

A pull retrieves available data from the previous 24 hours for one topic. Daily use across all included topics provides 90 Growth pulls or 300 Scale pulls in a 30-day month. Weekly Starter pulls vary by calendar month. Available audience size and contact fields vary, and audiences may overlap. Refreshes stop at the plan limit without overage charges.

• Find and qualify: search the topic catalog, save your ICP, and review the people and companies that match.
• Act on the research: export qualified contacts or prepare an Outreach or Direct Mail workflow. Connected products, channel usage, and fulfillment may cost extra.
• Get help from AIMEE: Growth and Scale include AIMEE for the initial user to research accounts and prepare the next step through connected tools.

Agencies and other service businesses can build client deliverables around their available Intent Scans and exports. Keep each client’s scope, permissions, and service fees clear. A subscription is not a promise of a white-label platform or exclusive access to a market.

Explore MarketPulse and watch the demo or compare plans starting at $500/mo. Any early-access discount is a separate, time-limited offer shown to an eligible recipient.

Separate product and agency responsibilities

BrandWell MarketPulse is topic-based intent-data software for businesses and agencies. Choose relevant research topics, apply saved ideal-customer-profile filters, review available names, roles, companies and contact details, and export the audience or prepare a connected workflow. Plans start at $500/mo. TrafficID identifies visitors to your own website and is a separate product. A MarketPulse subscription does not by itself promise a white-label portal, custom API implementation, exclusive topics, or managed client delivery.

Review an available MarketPulse topic, saved ICP and actual preceding-24-hour matches for the agreed research purpose. AIMEE can organize supplied context through configured tools. Name the reviewer, action approver, destination, feedback owner and deadline. A client pilot, branded report and sales playbook require separately verified agency scope and implementation.

Use the current table above for standard topic, refresh and export allowances. Eligible early-access offers are separate. Agency evaluation fees, credits, reports, playbooks, managed delivery and custom interfaces are not established by these subscription allowances; verify any proposed scope and written terms separately.

Scope the pilot around reviewed research, named owners, approved actions and actual outcome return. MarketPulse supplies research. Custom reports, CRM joins, portals and agency-operated execution need separately verified implementation, rights and fees.

Price the pilot and any conversion credit

Put actual pilot deliverables, period, fee, usage cap, client tasks and acceptance in writing. Budget setup, allocated software, review, support, corrections and channel usage. Credit only the documented amount under agreed conditions; a credit does not erase the original delivery cost. MarketPulse standard subscriptions are starting at $500/mo. Do not present a separate agency pilot fee or supplied sales assets as BrandWell product terms.

Use a stop-or-expand scorecard

Track report relevance, qualified prospects contacted, positive sales conversations, objections, written commitments, expected monthly retail revenue, projected contribution margin, confidence in delivery, and unresolved compliance needs. Do not use report volume alone as the success metric.

Important: Intent signals are probabilistic evidence. They do not prove identity, consent, need, authority, budget, stage, qualification, purchase, pipeline, or revenue. Report association and uncertainty honestly.

Review evidence and action boundaries

The pilot can fail if the agency targets weak-fit prospects, promises results before delivery is designed, treats verbal interest as contracted revenue, or overlooks data rights and activation limits. Record what the pilot does not include and who must approve every client-facing claim.

Review actual source rights, necessary fields, permitted purposes, access, retention and destinations. Keep action approvals and client responsibility separate from a research subscription. Resolve missing prerequisites before exports or activation.

• Preserve source, observed time, identity state, confidence, and validation status.
• Separate known people, candidate people, companies, domains, and unresolved visitors.
• Apply customer, employee, competitor, duplicate, geography, consent, and opt-out suppressions before action.
• Require a named human approval before CRM writes, audience uploads, spend, or outreach.
• Give clients correction, export, deletion, escalation, and offboarding paths.

Copyable assistant pilot-review brief

AIMEE can prepare a pilot brief through configured connected tools. Preserve actual inputs, missing evidence, assumptions and action boundaries. Named owners approve the scope and external actions; a proposed pilot does not establish native product capability.

Objective: Prepare pilot sales assets from the approved agency positioning, branded reports, qualification criteria, pricing assumptions, and playbook. Summarize objections and proposed commitments. Do not treat interest as a contract, promise cost recovery, expose private behavior, or send outreach without approval.
Inputs: approved ICP, topic dictionary, signal source and time, identity state, CRM lifecycle, suppressions, permitted-use policy, and current written commercial scope.
Rules: preserve provenance and uncertainty; never infer budget, authority, consent, or purchase readiness; never expose private behavior in messaging; stop before external action.
Output: decision, reason codes, missing evidence, recommended next step, and audit log.

Design the measurement before launch. The UK Magenta Book distinguishes process, impact and value-for-money evaluation. Apply that distinction to delivery, causal claims and costs; this government guidance does not validate a MarketPulse pilot.

Answers to ten pilot questions

What should an agency decide before structuring a paid intent-data pilot, and what client outcome can it responsibly promise?

A paid pilot should answer a commercial decision, not imitate a full production deployment. The agency needs to learn whether target topics produce usable reports, whether prospects understand the offer, whether the sales playbook creates qualified conversations, and whether conservative client economics justify moving forward.

What workflow, owners, SLA, quality checks, approvals, and client handoff does a paid intent-data pilot require?

Review an available MarketPulse topic, saved ICP and actual preceding-24-hour matches for the agreed research purpose. AIMEE can organize supplied context through configured tools. Name the reviewer, action approver, destination, feedback owner and deadline. A client pilot, branded report and sales playbook require separately verified agency scope and implementation.

Which platforms, tools, templates, calculators, and integrations best support structuring a paid intent-data pilot?

Start with the operating resources described in this guide: Low-cost sales-readiness pilot, Fixed-fee delivery pilot, Credited pilot, Performance-contingent pilot. Support them with a qualification scorecard, topic dictionary, evidence card, cost model, proposal, CRM disposition fields, client report, and approval checklist. Software should support the workflow rather than define it.

How do paid-pilot, free-trial, proof-of-concept, credited, and full-contract approaches compare for structuring a paid intent-data pilot?

A paid pilot compensates defined evaluation work and needs a capped scope. A free trial still consumes review and support capacity and needs actual offered terms. A proof of concept tests a specific technical or fit question, not necessarily recurring delivery. A credited pilot needs a written credit amount, expiry and conversion conditions. A full contract adds ongoing obligations and exit terms. Compare the decision, evidence, costs and acceptance rule; none automatically proves demand or profit.

How should an agency price a paid intent-data pilot, and which setup, usage, labor, support, and risk costs determine gross margin?

Price the written deliverable and actual setup, tools, review, channel usage, support and corrections. State the cap, acceptance, credit conditions and stop rule. A software subscription is separate from agency services; calculate the full pilot remainder before offering a credit.

Which quality, adoption, meeting, opportunity, pipeline, cost, margin, and retention metrics show whether a paid intent-data pilot is working?

Track report relevance, qualified prospects contacted, positive sales conversations, objections, written commitments, expected monthly retail revenue, projected contribution margin, confidence in delivery, and unresolved compliance needs. Do not use report volume alone as the success metric.

Which clients are ready for a paid intent-data pilot, and which prospects should the agency exclude?

Require a clear client decision, relevant topic, named reviewer and action owner, permitted destination, enough review capacity and an outcome-return plan. Defer missing approvals or evidence. Exclude universal identity promises, guaranteed revenue, prohibited uses and unreviewed automation.

Which signal sources, identity checks, qualification rules, activation steps, and outcome evidence matter most for a paid intent-data pilot?

Combine relevant topic or first-party behavior with fit, recency, recurrence, identity state, enrichment and validation, suppressions, human acceptance, an approved activation path, and outcome return. Keep every evidence type separate so an inference does not become a false fact.

Which data-quality, privacy, security, scope, billing, delivery, and client-trust risks must the agency control for a paid intent-data pilot?

The pilot can fail if the agency targets weak-fit prospects, promises results before delivery is designed, treats verbal interest as contracted revenue, or overlooks data rights and activation limits. Record what the pilot does not include and who must approve every client-facing claim.

What should the pilot agreement, scorecard, conversion rule, and stop rule include?

A recurring package should connect the client decision to the operating path described in four paid pilot models agencies should understand. Define the eligible market, topics, signals, identity states, qualification policy, branded deliverable, portal or export, action SLA, approvals, usage, pricing, scorecard, governance, support, change control, and offboarding. Expand only after the client uses the first module well.

Review a bounded research workflow

Assess the audience and the operating cost before expanding the service. Explore MarketPulse with the data, tools, and client delivery scope you need.

Related BrandWell guides: How to Run an Intent Data Proof of Concept: Test Plan, Scorecard, and 5 Platforms, Intent Data Discovery Call Checklist: Questions, Red Flags, and Pilot Fit, and How to Position an Intent-Data Service So Clients Understand the Value.