Intent-Data Service Proposal: Scope Template, Costs and Exit

Define the client decision and acceptance

The proposal is not a capability deck. It is a shared operating contract in plain language. A buyer should be able to see what comes in, what the agency does, what the client must do, what counts as delivered, what can vary, what is prohibited, and how both parties decide whether to renew.

Use seven proposal-review steps

1. 1. Complete qualification and freeze the business decision.
2. 2. Define the market, topics, signals, identity states, fields, and exclusions.
3. 3. Specify agency and client owners, approvals, SLA, and escalation.
4. 4. Describe each deliverable, module, cadence, and acceptance criterion.
5. 5. Write pricing, setup, usage, overage, payment, term, and change rules.
6. 6. Add data, security, privacy, channel, export, deletion, and incident responsibilities.
7. 7. Define the scorecard, attribution limits, stop rule, renewal, and offboarding.

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: Complete qualification and freeze the business decision. The final control is: Define the scorecard, attribution limits, stop rule, renewal, and offboarding. 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 might otherwise be mistaken for performance improvements. It also gives account teams a plain-language explanation when volume, acceptance, cost, or outcomes move between reporting periods.

Include fourteen scope and responsibility sections

1. Executive decision

Name the decision the service is intended to inform and the current cost of delay.

Watch-out: Avoid broad transformation language.

2. Who this is for

State the ideal client, prerequisites, and disqualifiers.

Watch-out: Do not hide maturity requirements.

3. Outcome and non-guarantee

Promise the maintained process and deliverables, not guaranteed buyers or revenue.

Watch-out: Explain factors outside the agency’s control.

4. Market and topic scope

List eligible markets, topics, included concepts, exclusions, and change cadence.

Watch-out: Topic names alone are insufficient.

5. Signals and identity

Define sources, units, match states, fields, freshness, and uncertainty.

Watch-out: Do not merge account and person evidence.

6. Qualification policy

Document fit, recency, recurrence, confidence, suppression, and review.

Watch-out: A score needs reason codes.

7. Activation boundary

List allowed destinations and required approvals.

Watch-out: No external action should be implied by delivery alone.

8. Deliverables

Describe reports, portal, exports, evidence cards, meetings, and training.

Watch-out: Specify format and acceptance.

9. Roles and SLA

Assign agency and client owners, response windows, and escalation.

Watch-out: Client inaction must be visible.

10. Pricing and usage

State setup, recurring fee, included usage, overages, tax, payment, and suspension.

Watch-out: Avoid unlimited language.

11. Measurement

Define baselines, windows, metrics, attribution limits, and data return.

Watch-out: Signal volume is not ROI.

12. Data responsibilities

Cover purpose, access, retention, suppression, deletion, security, and incidents.

Watch-out: Obtain counsel for the actual workflow.

13. Change and renewal

Define scope changes, repricing, review cadence, renewal, and termination.

Watch-out: Align retail exposure with wholesale commitments.

14. Exit and portability

State exports, deletion, credentials, documentation, and transition.

Watch-out: Avoid client lock-in surprises.

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 company context through configured tools. Custom portals, CRM implementation, outreach and agency-managed delivery require separately verified scope, rights and fees.

Use the current plan table above for standard topic, refresh and export allowances. Eligible early-access pricing is separate. Quote actual agency setup, review, support and channel usage separately from the software subscription.

Scope the service around defined inputs, human review, a client action and actual outcome return. MarketPulse supplies research; custom integrations, managed delivery and branded interfaces require separate implementation. A product subscription does not establish those agency capabilities.

Price full delivery and contract exposure

Separate setup fees, recurring service fees, actual software and channel costs, included labor, billable usage and taxes. Define invoice timing, payment, suspension, minimum term and cancellation. Record the full supplier commitment and who bears it if the client leaves. State margin assumptions internally; proposed economics are not guaranteed results. Count shared tools once and require written approval for work beyond the cap.

Use a stop-or-expand scorecard

Include only metrics the client can define and return: accepted signals, time to action, qualified meetings, opportunities, progression, corrections, opt-outs, adoption, cost, and margin. State when small samples or attribution overlap prevent a strong conclusion.

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 rights and proposal boundaries

Proposal risks include unlimited scope, guaranteed leads, universal identity, implied consent, hidden annual exposure, unqualified exclusivity, vague data ownership, and performance fees without a defensible causal definition.

Review actual source rights, necessary fields, access, retention, destinations and exit responsibilities. NIST SP 1305 addresses specifying supplier cybersecurity requirements. Apply that technical reference to the actual supplier relationship; it does not supply a ready-made commercial agreement, resale right or BrandWell certification. Have qualified reviewers check the actual proposed terms.

• 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 proposal-review brief

AIMEE can prepare an approved proposal draft through configured connected tools. Preserve missing evidence and conflicting requirements. A named owner approves actual capabilities, commercial terms and client delivery; a draft does not establish licensing rights or approval to send.

Objective: Draft proposal sections only from approved discovery, product terms, topic scope, workflow, pricing, and legal language. Mark every unknown and conflicting requirement. Do not invent capabilities, terms, benchmarks, or guarantees. Stop before client delivery and request commercial and legal 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.

Keep approved sources, actual capabilities, missing evidence, proposed terms and reviewer together. Reconcile the proposal against current scope and source agreements. An assistant comparison is not legal approval or evidence of guaranteed client outcomes.

Answers to ten proposal questions

What should an agency decide before writing an intent-data service proposal, and what client outcome can it responsibly promise?

The proposal is not a capability deck. It is a shared operating contract in plain language. A buyer should be able to see what comes in, what the agency does, what the client must do, what counts as delivered, what can vary, what is prohibited, and how both parties decide whether to renew.

What workflow, owners, SLA, quality checks, approvals, and client handoff does an intent-data service proposal require?

Assign a named agency owner, client owner, operator, and technical or CRM owner. The operating sequence is: 1) Complete qualification and freeze the business decision. 2) Define the market, topics, signals, identity states, fields, and exclusions. 3) Specify agency and client owners, approvals, SLA, and escalation. 4) Describe each deliverable, module, cadence, and acceptance criterion. 5) Write pricing, setup, usage, overage, payment, term, and change rules. 6) Add data, security, privacy, channel, export, deletion, and incident responsibilities. 7) Define the scorecard, attribution limits, stop rule, renewal, and offboarding. Set the response SLA, log exceptions, preserve uncertainty, and require a client handoff with permitted next steps and ownership.

Which platforms, tools, templates, calculators, and integrations best support writing an intent-data service proposal?

Start with the operating resources described in this guide: Executive decision, Who this is for, Outcome and non-guarantee, Market and topic scope, Signals and identity, Qualification policy, Activation boundary. 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 fixed-scope, modular, usage-based, custom, and pilot-first approaches compare for writing an intent-data service proposal?

A fixed-scope proposal defines included outputs and a change process. A modular proposal prices separable service units with their own limits. A usage-based proposal defines the billable unit, counting rule and cap. A custom proposal requires explicit implementation, acceptance and support responsibilities. A pilot-first proposal limits term, cost and work while evaluating fit. Compare actual delivery, rights, adoption, full costs and exit terms; the format alone does not establish value.

How should a proposal present setup fees, recurring price, usage, wholesale cost, margin assumptions, and billing terms?

Separate setup fees, recurring service fees, actual software and channel costs, included labor, billable usage and taxes. Define invoice timing, payment, suspension, minimum term and cancellation. Record the full supplier commitment and who bears it if the client leaves. State margin assumptions internally; proposed economics are not guaranteed results. Count shared tools once and require written approval for work beyond the cap.

Which acceptance, adoption, meeting, opportunity, pipeline, cost, and margin metrics should the proposal define?

Include only metrics the client can define and return: accepted signals, time to action, qualified meetings, opportunities, progression, corrections, opt-outs, adoption, cost, and margin. State when small samples or attribution overlap prevent a strong conclusion.

Which clients are ready for an intent-data service proposal, and which prospects should the agency exclude?

Agency sellers, account directors, operators, and legal or finance reviewers building a reusable proposal for a recurring intent-data service; any client branding requires verified rights and actual implementation. Best-fit clients also have a clear ICP, sufficient addressable market or qualified traffic, relevant commercial topics, a named action owner, measurable CRM outcomes, conservative economics, and privacy readiness. Exclude clients demanding guaranteed leads, universal identity, prohibited use, or automation without review.

Which signal sources, identity checks, qualification rules, activation steps, and outcome evidence matter most for an intent-data service proposal?

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 an intent-data service proposal?

Proposal risks include unlimited scope, guaranteed leads, universal identity, implied consent, hidden annual exposure, unqualified exclusivity, vague data ownership, and performance fees without a defensible causal definition.

Which commercial, data, measurement, change, renewal, and exit terms belong in the proposal?

A recurring package should connect the client decision to the operating path described in fourteen sections in an intent-data agency proposal template. 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 Write an Intent Data RFP: Requirements, Scorecard, and Vendor Shortlist, Intent Data Contract Checklist: Clauses and Data Rights to Review Before Signing, and Intent-Data Sales Pitch: A Practical Framework for Agencies.