BrandWell Agency Service: Product Scope, Dependencies and 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 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.

Map products to separately scoped work

Map actual current product functions to the work being proposed. Treat research, own-site audiences, available fields, validation checks and activation as planning categories. Confirm whether each field or action exists in the purchased product and separately implemented workflow.

Swipe the table to see all columns.

The table is a service overview, not a catalog of guaranteed products. A privacy notice can establish that a processing category exists in the company’s disclosed practices; it cannot establish that the category is generally available, standard, or licensed to a particular client. Likewise, public technical material from an underlying provider cannot establish a BrandWell API, rate limit, webhook, service level, or white-label right.

Check dependencies before packaging

The families form a dependency graph rather than a row of independent switches. Topic monitoring can produce a company hypothesis without naming a person. Visitor identification can add context without establishing interest in a specific topic. Enrichment can make a record actionable without proving consent. Validation can reduce delivery errors without confirming buying intent. Activation can move data reliably while still producing a poor client outcome if the qualification rules are weak.

Map each proposed output backward:

1. Outcome: What client decision will change – account selection, research follow-up, audience creation, sales prioritization, or reporting?
2. Evidence: Which downstream observation will show that the decision was used and useful?
3. Activation: Which destination receives what fields, after whose approval, under which channel policy?
4. Qualification: Which ICP, geography, recency, completeness, confidence, and suppression rules apply?
5. Identity: Is the decision at market, account, domain, household, or person level?
6. Signal: What was observed, during which window, under which topic definition?
7. Entitlement: Which purchased provision authorizes the field, client, site, volume, destination, and use?

If one node is unresolved, do not sell the downstream output as complete. This is the most important service implementation rule: dependencies should constrain the package before they become exceptions in client delivery.

Research topics with MarketPulse

The purpose of topic monitoring is to turn research activity into an account-prioritization hypothesis. A useful configuration defines the topic tightly enough to be meaningful, the market broadly enough to contain a viable population, and the observation window narrowly enough to match the intended action. It also exposes how an account entered the report and when the observation occurred.

The buyer should request topic definitions, exclusions, available granularity, timestamps, scoring interpretation, geographic applicability, and a representative sample. Do not rely on a precise public count of topics or signals: reviewed public materials contain volatile or inconsistent totals, and totals do not establish usable coverage for one agency’s ICP.

MarketPulse supplies relevant topic research, saved ICP filters and available match details. Verify separately scoped agency reporting, client interfaces, integrations, branding, data rights, usage and fees. A research subscription does not establish multi-client white-label capacity.

Expansion trigger: add another topic only after the first topic has a stable definition, sufficient eligible accounts, acceptable evidence quality, and an owner who reviews drift. More topics do not repair weak qualification.

Keep TrafficID own-site audiences distinct

Visitor identification can help a client understand otherwise anonymous business traffic, but match coverage is not universal and identity level matters. A domain or account-level inference is not evidence that a specific employee visited. Even a person-level match remains probabilistic and does not prove intent, eligibility, or readiness to buy.

Before this family enters a package, document the eligible sites, installation owner, geography, notice and consent analysis, retention, suppression, identity levels, confidence rules, excluded traffic, and permitted downstream uses. Measure eligible visits, match attempts, accepted matches, and activations separately. A single “identification rate” without a denominator and threshold is not decision-grade evidence.

Treat TrafficID or any visitor-resolution scope as optional until the Order Form confirms it for the relevant client and site. Do not imply every agency plan includes identity resolution for every client. A suitable first use is aggregate account-level prioritization with human review; a poor first use is automatic person-level outreach triggered by any visit.

Expansion trigger: broaden the destination or identity level only after false-positive review, suppression testing, and client approval show the narrower workflow is stable.

Verify available fields and company context

Enrichment connects a signal to business context the agency can evaluate: company attributes, roles, contact details, or other purchased fields. The quality question is not “How many records exist?” It is “For the client’s eligible population, which required fields are present, current enough, attributable to an allowed source category, and correct enough for the intended decision?”

The entitlement worksheet should list every field, match key, identity threshold, null behavior, source-category note, permissible use, and timestamp. Sample known customers, known non-customers, hard-to-match firms, subsidiaries, and each intended region. Review entity collisions, job changes, generic domains, and stale titles. Measure completeness by required field and segment rather than using a blended record count.

Inspect actual available fields and source context in the supported workspace. A separately implemented enrichment or routing path requires a verified field map, credential owner, deduplication rule, destination response, correction route and export rights.

Expansion trigger: add fields only when they change a qualification or activation decision. Extra data increases cost, review work, and governance surface without necessarily improving the service.

Define each validation test

Validation is valuable only when the agency defines what is being validated. Syntax, domain state, deliverability prediction, phone reachability, identity recency, and role relevance are different tests. A “valid” result for one purpose may still be unusable for another.

BrandWell’s public privacy material mentions validation as a processing or product category, but that does not prove contact validation is a standard named agency-portal module. Ask product and contracting teams to confirm the current entitlement, fields, codes, timing, limits, and support. Then build a test set containing known good, known bad, ambiguous, catch-all, changed-role, and suppressed records.

Do not use validation as a substitute for permission or channel compliance. A technically deliverable address can still be inappropriate to contact. The agency should apply purpose, geography, notice, suppression, client policy, and platform rules after validation and before activation.

Expansion trigger: introduce validation into production when failure codes are interpretable, timestamped, preserved through routing, and tied to a clear accept/review/reject action.

Specify actual actions and approvals

Activation turns an accepted record into work. A complete design specifies the trigger, input schema, transformations, destination, deduplication key, approval state, retry behavior, error queue, suppression check, audit evidence, and rollback procedure. “Send it to the CRM” is not an implementation specification.

Choose the minimum necessary destination first. A reviewed export may be safer for a pilot than a real-time push. A queue for analyst approval may be safer than automatic advertising or outreach. Once the agency can reconcile source and destination counts, it can consider shorter latency or more automation.

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.

Expansion trigger: automate only after the manual path has stable acceptance rules, reproducible evidence, and a named exception owner.

Maintain an entitlement worksheet

For every capability family, complete one row per client:

Swipe the table to see all columns.

This worksheet prevents a service demo from silently becoming the contract. It also makes documentation gaps visible. Useful service documentation includes current terms, privacy material, the actual Order Form, data dictionaries, sample outputs, technical specifications for the purchased path, security material, implementation plan, and support or escalation terms. Marketing articles can illustrate a workflow; they do not override those documents.

Test representative inputs and failures

Use one representative client scenario and ask the seller to show the complete path from signal to report. Bring a frozen test set, required fields, suppressions, and expected destination. The evaluation checklist should score:

• source and topic definition;
• identity level and confidence;
• coverage by required segment;
• observation, processing, and delivery timestamps;
• required-field completeness;
• false positives and ambiguous records;
• portal or export separation between clients;
• routing, deduplication, retries, and rejection handling;
• suppression and deletion propagation;
• documentation and change ownership;
• downstream acceptance, action, and evidence;
• offboarding and portability.

Run the path with missing data, duplicate accounts, a changed topic, an expired credential, and a record that must be suppressed. Happy-path interface fluency is not the same as operational readiness. For service evidence, preserve the input, configuration, output, reviewer decision, and exception – not only the final dashboard.

Compare the same complete workflow

Service alternatives include enterprise ABM suites, specialist point tools, agency-managed operations, and an in-house stack. Compare them on intended use, signal coverage and freshness, identity and validation, integrations and activation, implementation effort, privacy and governance, verified price and total cost, measurement, proof, limitations, and best fit.

An enterprise suite may offer broad account-based workflows but demand more implementation and adoption. A point tool can excel at one step while leaving the agency to integrate reporting and governance. A managed operator can supply labor but must define staffing, approvals, and support. A custom build can create proprietary control while transferring permanent sourcing, engineering, observability, privacy, and maintenance duties to the agency.

A fair service comparison does not count BrandWell capability families on one side and isolated competitor features on the other. It compares the whole path needed for one client outcome. Request matched scopes and samples, and do not infer reseller or white-label rights from a general product page.

Count full package and replacement costs

Service pricing should be modeled per entitlement and cost driver, not divided evenly across five labels. Include platform or data fees, usage, configuration, integration, analyst review, client reporting, support, governance, third-party destinations, exception work, and offboarding. service total cost should also include the cost of replacing a capability and the revenue delay created by an unresolved dependency.

Verify actual agency and client contracting, billing, support and operating responsibilities in the agreement. Define limits for topics, sites, records, destinations, revisions, meetings and analysis before pricing a service.

Do not promise ROI. Create a measurement plan instead: cost per eligible signal, accepted record, successful activation, qualified response, opportunity, and attributable revenue. Show the influence of sales execution, media, offer quality, and market size.

Measure each evidence layer separately

Use a balanced scorecard:

Swipe the table to see all columns.

Service accuracy requires a defined task and truth set. service coverage requires the eligible denominator and segment. service freshness requires event and delivery timestamps. Report them independently; combining them into one quality score can hide the reason a workflow failed.

Check prerequisites and limitations

Service operating prerequisites include a repeatable B2B service, an identifiable U.S.-business market, enough data for a representative test, technical ownership, client governance, and a specific activation outcome. service end-client prerequisites include a usable account market, a functioning CRM or destination, responsive sales or media operators, and a willingness to measure the full funnel.

Service use cases are weaker when traffic or market size is too small, the desired geography has not been validated, the client lacks a destination or operator, identity certainty is mandatory, or the contract depends on a fixed quantity of qualified leads. Those are reasons to narrow the scope, choose a point solution, or pause – not reasons to inflate a topic list.

Service limitations include probabilistic identity and intent, incomplete coverage, scope-dependent entitlements, external dependencies, and unresolved public specifics around an intent API or service level. service privacy review must cover purpose, roles, notice, permissions, suppression, retention, deletion, and channels. service security review must obtain current evidence instead of assuming SSO, RBAC, audit logs, tenant design, backups, RTO, RPO, or certification. service compliance cannot be presented as a guarantee.

Review an available MarketPulse topic, saved ICP and actual preceding-24-hour matches for the approved research purpose. Keep uncertain company context visible. AIMEE can organize supplied context through configured tools; named owners approve actual exports, messages, audience uploads and CRM writes.

Scope a recurring agency service

Create three client-facing layers rather than selling every family at once:

1. Signal brief: an agreed topic and market, a branded report, qualification notes, and a client review. This tests usefulness with minimal activation risk.
2. Qualified account workflow: adds identity or enrichment fields, acceptance rules, suppression, and a controlled CRM or export route where purchased.
3. Activation and learning loop: adds an approved destination, response capture, evidence review, and periodic threshold changes.

Publish a responsibility matrix for the actual agreement. Verify product supply, agency implementation, client approvals, destinations, support, reporting, data rights and outcome feedback. Custom staffing, branding and client interfaces need separately contracted scope.

Map every promised output to a verified product function, each function to its prerequisites and every conclusion to inspectable evidence. A list of capability labels or marketing terms is not an implementation plan.

That is what a white-label service should include. Not the maximum number of switches, but the smallest complete chain an agency can contract, operate, explain, and improve.

Review MarketPulse and current plans, starting at $500/mo. Evaluate a relevant topic, approved ICP, actual match details and operating effort. Review current guarantee conditions before testing; sample acceptance does not establish future pipeline or revenue.