7 Intent-Data Services for SaaS Agencies: Scope and Full Costs

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.

Check actual client readiness

This guide is for:

• agency owners serving B2B SaaS clients;
• demand-generation and RevOps consultants packaging recurring services;
• strategists deciding whether intent data fits a client’s sales motion; and
• delivery leaders responsible for client value, margin, and renewal.

It is not for agencies that plan to sell the same unqualified “hot lead” export to every SaaS company. A good service adapts to the client’s product, contract value, buying group, sales cycle, data maturity, and activation capacity.

Use eight client-fit gates

Use these gates before preparing a proposal. A “no” does not always kill the opportunity, but it should change the scope.

1. Is the ICP operational?

The client should be able to define inclusion, exclusion, and priority fields in observable terms. “Innovative companies” is not operational. Industry, employee band, geography, technology, business model, use case, and explicit exclusions can be.

Acceptance gate: the client can label a sample of accounts consistently. Failure mode: vague fit turns intent into broad prospecting.

2. Is the revenue event valuable enough?

Name the event: a qualified new-logo opportunity, expansion, renewal defense, partner recruitment, or another client-approved outcome. Estimate whether the event’s value supports the full cost of data, delivery, activation, and sales follow-up.

Acceptance gate: the economics work at a downside conversion case. Failure mode: even accurate data can be uneconomic for a low-value or poorly defined event.

3. Is there enough addressable volume?

Estimate eligible accounts after geography, company size, category, current customers, partners, conflicts, and exclusions. The client also needs enough volume for its chosen channel and an evaluation design.

Acceptance gate: the available audience supports the play. Failure mode: a tiny audience may not meet advertising platform minimums and can create privacy or identification risk.

4. Can the buying evidence be observed?

Define which topics, website actions, review activity, product signals, customer events, or other evidence can be sourced and time-bounded. Store source and freshness with each record.

Acceptance gate: every signal has provenance and an expiration rule. Failure mode: broad topics create impressive volume without SaaS buying relevance.

5. Can the destination accept the data?

Validate CRM objects, field names, deduplication, account hierarchy, routing, ownership, suppression, and rollback before live delivery.

Acceptance gate: sample records land in a sandbox with the correct owner and evidence ID. Failure mode: good signals disappear into bad CRM operations.

6. Will somebody act?

Name the team, approved play, response expectation, exception path, and capacity limit. “Sales will follow up” is not ownership.

Acceptance gate: the client accepts the workload. Failure mode: unworked signals create no learning, no outcome, and no credible renewal story.

7. Is the intended use allowed?

Review the data source, purpose, transparency, legal basis or consent where applicable, privacy notice, channel rules, opt-out, suppression, and sensitive-category restrictions. Business-to-business use does not erase every privacy, advertising, or email obligation.

Acceptance gate: the appropriate privacy, compliance, legal, security, and platform reviewers approve the intended use. Failure mode: the agency activates data it was allowed to receive but not allowed to use in that way.

8. Can the client accept or reject the evidence?

Agree on event definitions, stable IDs, denominators, comparison logic, costs, and review cadence. The agency and client need the same definition of an accepted signal and a qualified opportunity.

Acceptance gate: both parties can reconcile the report to destination records. Failure mode: influenced pipeline becomes an all-purpose claim with no causal boundary.

Keep SaaS evidence types distinct

A useful intent-data services strategy separates evidence types instead of blending everything into one mystery score.

• Category research: useful for market education and account research, but often broad.
• Competitor or comparison activity: closer to vendor evaluation, but limited to the observed source and account resolution.
• Website behavior: first-party context can be valuable, but anonymous or resolved activity still requires confidence, purpose, and suppression controls.
• Product and customer evidence: can support expansion or renewal plays, but should remain inside agreed customer-data boundaries.
• Contact and account identity: makes routing possible, but identity quality must be tested separately from fit and intent.

Keep fit, intent, identity confidence, freshness, and permitted use in separate fields. Apply hard exclusions first. Then map accepted evidence to a stage-appropriate play. A return visit from a current customer should not trigger the same workflow as a new high-fit account researching a competitor category.

Scope seven agency service modules

These are service modules, not seven promises that every client should buy at once.

1. Market and topic intelligence reports

Monitor client-approved topics and markets, explain where the evidence came from, and deliver a branded report with a clear time window and exclusions. This gives a low-maturity client a view of demand without pushing records into production.

Applicable fit: market planning, content, and account research. Limitation: broad topics can produce volume without relevance. Acceptance: the client confirms the topics map to a real product and revenue motion.

2. ICP account prioritization

Combine separately stored fit and intent evidence to prioritize a client-owned account universe. Show why each account qualified and why other accounts were rejected or held.

Applicable fit: named-account sales and ABM planning. Limitation: intent should never override a hard ICP exclusion. Acceptance: a labeled account sample passes the client’s quality threshold.

3. Website visitor company identification

Identify eligible website activity at the account or person level only when the evidence supports that level. Preserve the source, page or event category, time, confidence, and no-match state.

Applicable fit: high-consideration SaaS sites with enough qualified traffic and a defined follow-up motion. Limitation: a reveal is probabilistic and is not proof of a specific person, consent, or buying intent. Acceptance: false and missed match handling is explicit.

4. Contact and buying-group enrichment

After account fit, add only the roles and contact fields the approved workflow needs. Record provenance, field date, validation state, suppression, and current-employment checks.

Applicable fit: clients with clear buying-group roles and owned follow-up. Limitation: more contacts can increase cost and risk without improving relevance. Acceptance: required fields pass sampled QA and destination validation.

5. CRM signal routing and service-level operations

Map accepted evidence to CRM fields, owners, tasks, notifications, deduplication, exceptions, and rollback. Carry an evidence ID through every write.

Applicable fit: clients with functioning RevOps and named sales owners. Limitation: unowned alerts become noise. Acceptance: sandbox records land correctly and can be reversed.

6. Intent-led audience and outreach playbooks

Translate approved signal tiers into channel-eligible audiences, messages, sequences, suppression, pacing, and human approval. Prepare the action before executing it.

Applicable fit: clients with tested offers, enough audience volume, and disciplined channel owners. Limitation: automation amplifies stale data, message fatigue, and policy mistakes. Acceptance: source, purpose, audience, creative, and stop rules receive approval.

Verify the actual destination, source, recipient, purpose, account requirements and permissions before upload. Third-party research does not become first-party customer collection through hashing or enrichment. Hold unresolved eligibility rather than uploading speculatively.

7. Branded evidence, optimization, and renewal

Reconcile signal receipt, QA, acceptance, action, response, opportunity, cost, client adoption, and agency margin. End each review with a scale, repair, or stop decision.

Applicable fit: any recurring package. Limitation: influenced pipeline is not proof of incremental pipeline. Acceptance: the client can reconcile the report and agrees on the next decision.

Assign owners and handoffs

Assign the actual responsibilities:

• an agency service owner for scope and margin;
• a data and QA operator for provenance, freshness, identity, and fit;
• a client sponsor for outcomes and commercial decisions;
• a RevOps owner for fields, routing, deduplication, and rollback;
• channel owners for outreach and advertising eligibility;
• privacy and security reviewers for source, purpose, access, retention, and rights; and
• a named human approver for consequential actions.

Run the cadence around events rather than a made-up universal schedule: intake approval, signal QA, exception handling, activation review, evidence reconciliation, and renewal. Every handoff needs an input, owner, acceptance test, and escalation path.

Keep actual source, processing, recipients, access, retention, correction, deletion and suppression routes traceable. Resolve implementation and eligibility before activation. A supplier agreement does not certify the workflow.

Compare four operating approaches

Use manual research when volume is low or the play is still being learned. It offers control and close review, but labor grows with every client.

Use a generic package only for stable primitives that truly repeat: intake, evidence fields, QA states, routing controls, reporting structure, and change management. Its limitation is that SaaS buying motions differ. A usage-led expansion play and an enterprise new-logo play do not share the same evidence or owners.

Use a SaaS-specific playbook when contract value, buying group, sales cycle, CRM objects, product evidence, metrics, or activation differ materially. Its limitation is setup work. The agency must resist turning every client variation into custom software.

An agency can separately build a client-facing report or interface. Verify actual implementation, rights, client separation, maintenance, billing, export and exit terms. Do not assume a research subscription supplies this delivery layer or eliminates operating work.

Calculate price and full costs

Build the economics from the bottom up:

Defined service cost = actual allocated product costs + setup + recurring labor + QA and corrections + client service + approved activation + reporting + other included costs. For a target remainder as a share of fee, fee = defined cost / (1 – target rate). Multiplying cost by a markup is a different calculation. State what costs are excluded.

Separate one-time discovery, ICP and topic design, integration, sandbox testing, and training from recurring monitoring, QA, activation support, evidence review, and changes. Stress-test a low-volume case, because fewer usable signals can mean more manual exception work rather than lower delivery cost.

Do not label one platform universally inexpensive. Compare the same topics, accounts, contacts, identity fields, integrations, reports, activation, media, services, users, support, term, overages, exports, and exit rights.

Measure outcomes and agency economics

Track a chain of measures:

• eligible account coverage;
• signal provenance and freshness completeness;
• accepted, held, and rejected records;
• sampled precision and error reasons;
• time to an owned action;
• CRM and sales acceptance;
• responses and qualified opportunities;
• cost per accepted signal and accepted opportunity;
• client adoption and unresolved exceptions;
• recurring scope retained or expanded; and
• agency gross margin.

Keep the actual observation unit, adjudicated labels, false matches, missed matches and unresolved records. Selected-sample results do not automatically describe every account. Do not equate list size or coverage with correct identity, qualification or business impact.

Use a holdout, phased rollout, or matched cohort when practical. Keep attribution separate from incrementality. Do not invent a benchmark because a client asks for one; establish a baseline from the client’s own accepted definitions.

Control data and action risks

Check these potential failures:

• unclear source or permitted use;
• cross-client data mixing;
• stale signals and employment data;
• false person or account matches;
• unapproved sensitive inference;
• missing correction, suppression, opt-out, or deletion handling;
• deceptive outreach or ineligible ad audiences;
• uncontrolled CRM writes; and
• reporting that cannot reconcile to source evidence.

Verify actual source, purpose, responsibilities, recipient, jurisdiction, channel and rights requirements before action. Keep correction, suppression, opt-out and deletion routes traceable. Resolve uncertainty with qualified advice.

Use supported BrandWell research

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.

MarketPulse supplies topic research and available match details. TrafficID separately supports owned-site visitor review. AIMEE can organize supplied context through configured tools. The seven agency services require their own implementation, rights, scope, owners and fees. Do not promise exclusive topics, client interfaces or custom routing from the research subscription.

Review actual audience fit, unknown cases and full operating cost before expanding. Explore MarketPulse and current plans.

AIMEE can prepare a review brief through configured connected tools. Keep proposed actions separate from actual approvals and destination acknowledgements. Confirm the implementation and permissions before execution.

BrandWell has real limits. It does not make intent deterministic, create consent, replace a CRM or ad platform, guarantee identity or outcomes, or remove product, pricing, privacy, security, compliance, legal, and platform-policy review. A broad enterprise ABM suite, a focused point tool, or an in-house process may fit a different buyer better.

Prepare a review-only pilot brief

1. Provide the approved ICP, exclusions, topic definitions, source permissions, destination schema, owners, and outcome event.
2. Ask the agent to identify missing data, stale evidence, unclear provenance, policy conflicts, and records below confidence thresholds.
3. Require reject, hold, human review, and approved-for-staging states with reasons.
4. Generate a branded topic report and a proposed action for each accepted tier without executing it.
5. Have the client and agency review quality, cost, privacy, security, compliance, legal, product, pricing, and platform rules.
6. Let the named approver authorize any consequential action.
7. Record the evidence ID, action, approver, destination result, response, opportunity, cost, and exception.
8. Finish with a scale, repair, or stop memo.

Freeze the pilot’s accounts, topics, time window, evidence, owners, costs, destinations, and acceptance thresholds before it begins. Otherwise, every disappointing result will cause the test definition to move.

Choose a bounded first service

Start with the smallest service that closes a real client gap. A reporting-first client does not need a complex activation program. A mature SaaS team does not need another unowned dashboard. Sell the connection between evidence, action, and a decision.

When you can show which accounts were eligible, why records were accepted, what the client did, which outcomes followed, what the work cost, and whether the agency can deliver it profitably, use the evidence to decide whether to renew, repair or stop the actual service.