Build vs Resell vs Refer Intent Data: Rights and Full Costs

Choose a sustainable operating responsibility

Choose the model by client ownership, delivery responsibility, technical capacity, gross-margin target, contract rights, and exit risk. The responsible promise is a defined service outcome and governed workflow. No model makes the underlying signals certain or guarantees client demand.

Use seven model-review steps

1. 1. Define the client outcome, buyer, and revenue event before evaluating technology.
2. 2. Map who owns branding, billing, implementation, data rights, support, activation, and measurement.
3. 3. Test representative topics, markets, identity states, exports, and client separation.
4. 4. Model total cost for platform, engineering, operations, sales, support, and unused capacity.
5. 5. Review reseller, OEM, referral, multi-client, derived-data, deletion, and termination terms.
6. 6. Use a bounded paid validation to test client demand and delivery burden.
7. 7. Select the model only after an evidence-backed stop, revise, or expand decision.

Preserve the versioned evidence log

Use one versioned record to show why each intent-platform operating model decision was made. Capture the eligible market, topic definition, source, observed time, identity state, validation result, suppression, reviewer, approved action, downstream disposition, and fully loaded cost. Preserve rejected, expired, duplicated, and corrected records with reason codes rather than overwriting them. This makes client explanations and later comparisons reproducible.

Open the log with Define the client outcome, buyer, and revenue event before evaluating technology. Close each review cycle with Select the model only after an evidence-backed stop, revise, or expand decision. If a topic, source, identity rule, activation path, outcome definition, price, or policy changes, record the approver, affected records, and whether prior periods remain comparable.

Compare five contract and delivery models

1. Build a proprietary service layer

The agency owns the client experience, logic, integrations, reporting, and roadmap. Control depends on actual source licenses and contracts; fund engineering, security, support and maintenance as ongoing capabilities.

Watch-out: Do not treat the first integration as the full cost. Observability, permissions, deletion, incident response, billing, and vendor changes remain ongoing work.

2. Resell a complete white-label service

The agency buys a defined wholesale capability, applies its brand and commercial packaging, and owns end-client billing and delivery within written reseller rights.

Watch-out: Verify topic availability, client capacity, usage, export, support, data rights, termination, and what happens to client records if the agreement ends.

3. Refer the client to a provider

The agency introduces the client and may receive a referral fee while the provider owns the software agreement and much of the operating relationship.

Watch-out: The provider handles its contracted product relationship. Verify referral payment, client-contact boundaries and any separately scoped agency work.

4. Manage a client-owned enterprise platform

The client licenses the platform and the agency sells implementation, operations, media, analytics, or enablement around that deployment.

Watch-out: This can fit a mature client but does not automatically create a reusable multi-client reseller product for the agency.

5. Combine licensed inputs with agency operations

The agency licenses selected signals or data, then supplies its own identity, qualification, activation, reporting, support, and client interface.

Watch-out: A modular stack can avoid unused suite features, but every connector, permission boundary, service failure, and reconciliation rule becomes the agency’s responsibility.

Copyable operating-model worksheet

Use this field set during discovery, onboarding, and the first client review. It turns an intent-platform operating model into a reproducible decision record instead of an informal promise. Replace every bracketed prompt with written evidence and leave unknowns visible.

INTENT-PLATFORM OPERATING MODEL DECISION WORKSHEET
Client decision: [one decision this service must improve]
Eligible market and exclusions: [written ICP, geography, lifecycle, customers, competitors]
Evidence required: [source, observed time, topic rule, identity state, validation]
Path being evaluated: [Build a proprietary service layer; Resell a complete white-label service; Refer the client to a provider; Manage a client-owned enterprise platform; Combine licensed inputs with agency operations]
First operating control: [Define the client outcome, buyer, and revenue event before evaluating technology.]
Final operating control: [Select the model only after an evidence-backed stop, revise, or expand decision.]
Owners and approvals: [agency, client, data, CRM, activation, privacy, billing]
Fully loaded monthly cost: [platform + usage + labor + support + risk reserve]
Evidence of use: [accepted, rejected, corrected, acted on, downstream disposition]
Stop, revise, or expand rule: [threshold, reviewer, next action]

Scope the recurring client operation

Translate the workflow into a client scope for an intent-platform operating model: the decision being improved, eligible market, topic set, branded deliverable, portal or export, action SLA, review cadence, usage boundary, support path, change control, and stop rule. Mark records as eligible, review, suppressed, expired, or unresolved so the client knows what can happen next.

Assign named owners for sales, client success, data operations, identity review, CRM, activation, privacy, security, analytics, and billing. Attach evidence to every handoff. Review the first month as an operating test by comparing accepted, rejected, corrected, suppressed, and acted-on records with delivery hours, outcome return, and contribution margin. Narrow or stop the service when the client cannot use the evidence reliably.

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 use. AIMEE can organize supplied company context through configured tools. Custom interfaces, reseller agreements, CRM implementation and managed delivery need separately verified scope, rights and fees.

Use the current plan table above for standard topic, refresh and export allowances. Eligible early-access pricing is a separate offer. Include actual agency implementation, support and channel usage when pricing a client service.

AIMEE can prepare an approved research brief through configured connected tools. Preserve source rights, missing fields and unresolved client responsibilities. Named owners approve destinations and external actions. Do not describe a standard subscription as a custom API, private-label portal or reseller contract.

Budget full operating and switching costs

Compare total service economics rather than record price. A build includes engineering, observability, security, integrations, exception handling, billing, and maintenance. A resale model includes wholesale minimums, usage, support, and client capacity. A referral model includes acquisition and qualification costs, actual payment terms and any separate support work. A direct enterprise model includes implementation and adoption burden.

The intent-platform operating model stop-or-expand scorecard

Track sales-cycle length, validation-to-plan conversion, implementation time, accepted-signal cost, delivery hours, support load, contribution margin, client adoption, expansion, renewal, concentration, and switching cost. Use the same client decision to compare models.

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 source rights and exit terms

Risks include assuming resale rights, underestimating engineering, allowing a vendor to own the client, hiding minimum terms, creating data lock-in, omitting deletion and export paths, and mistaking a referral fee for a durable agency asset. Obtain written commercial and legal review.

Review actual source rights, necessary fields, retention, destinations and exit arrangements for each model. NIST SP 1305 addresses defining supplier cybersecurity requirements. Apply it to that technical responsibility; it does not grant resale rights, certify a provider or validate an agency margin forecast. Obtain actual written commercial and legal review for the proposed relationship.

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

Copyable assistant model-comparison brief

Objective: Compare build, reseller, referral, managed, and direct-enterprise models for a named agency use case. Use identical fields for rights, client ownership, signals, identity, activation, branding, implementation, cost, support, evidence, risk, and exit. Mark unknowns and stop before a recommendation until a human reviews written terms.
Inputs: approved ICP, topic dictionary, signal source and time, identity state, client lifecycle, suppressions, permitted-use policy, outcome definitions, 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 actual terms, missing evidence, permitted use, proposed action and reviewer together. An assistant comparison does not establish licensing rights or client demand. Check the recommendation against written contracts, current capabilities and full operating costs before approval.

Maintain current sources and scope

This guide evaluates an intent-platform operating model through one defined client decision, a seven-step operating workflow, consistent option criteria, a fully loaded cost model, an outcome scorecard, and explicit limitations. The workspace image illustrates the interface; example counts do not establish service profitability or client outcomes. Current contracts, official product documentation, platform policies, and scope-matched written quotes control volatile facts.

Recheck the relevant claim before a client quote and whenever a provider changes pricing, modules, permitted uses, reseller rights, retention, export, support, platform policy, or contract terms. Revise the affected statement and workflow rather than carrying an old assumption into a new engagement.

Related agency operating guides

Use these companion guides to move from the current decision into the next operating layer without collapsing distinct buyer questions into one oversized page.

• Intent-Data Service Models for Agencies: Resell vs Build vs Enterprise
• How to Choose an Intent-Data Vendor for an Agency Service
• Best White-Label Intent Client Portals for Agencies

Answers to ten operating-model questions

What should an agency decide before choosing whether to build, resell, refer, or directly implement an intent platform, and what client outcome can it responsibly promise?

Make a go, revise, or stop decision before delivery begins. The governing test is: Choose the model by client ownership, delivery responsibility, technical capacity, gross-margin target, contract rights, and exit risk. The responsible promise is a defined service outcome and governed workflow. No model makes the underlying signals certain or guarantees client demand.

What workflow, owners, SLA, quality checks, approvals, and client handoff does an intent-platform operating model require?

Assign a named agency owner, client owner, operator, and technical or CRM owner. The sequence is: 1) Define the client outcome, buyer, and revenue event before evaluating technology. 2) Map who owns branding, billing, implementation, data rights, support, activation, and measurement. 3) Test representative topics, markets, identity states, exports, and client separation. 4) Model total cost for platform, engineering, operations, sales, support, and unused capacity. 5) Review reseller, OEM, referral, multi-client, derived-data, deletion, and termination terms. 6) Use a bounded paid validation to test client demand and delivery burden. 7) Select the model only after an evidence-backed stop, revise, or expand decision. 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 choosing whether to build, resell, refer, or directly implement an intent platform?

Start with the operational resources in this guide: Build a proprietary service layer, Resell a complete white-label service, Refer the client to a provider, Manage a client-owned enterprise platform, Combine licensed inputs with agency operations. Use the client CRM as the outcome system of record, a permissioned review queue or database for evidence, the copyable worksheet in this guide, a topic dictionary, qualification scorecard, cost calculator, responsibility matrix, client report, and approval checklist. Add integrations only after field IDs, permitted writes, owners, retries, deletion, and exception handling are documented for an intent-platform operating model.

How do build, white-label resale, referral, managed service, and direct enterprise compare for choosing whether to build, resell, refer, or directly implement an intent platform?

Compare build, white-label resale, referral, managed service, and direct enterprise against the same client decision, market, evidence, owners, SLA, implementation time, fully loaded cost, governance, outcome scorecard, and exit path. The right approach to choosing whether to build, resell, refer, or directly implement an intent platform is the one the client can adopt and the agency can deliver repeatedly without hiding labor, rights, uncertainty, or risk.

How should an agency price an intent-platform operating model, and which setup, usage, labor, support, and risk costs determine gross margin?

Build a client-level cost model before setting price. Compare total service economics rather than record price. A build includes engineering, observability, security, integrations, exception handling, billing, and maintenance. A resale model includes wholesale minimums, usage, support, and client capacity. A referral model includes acquisition and qualification costs, actual payment terms and any separate support work. A direct enterprise model includes implementation and adoption burden. Put usage overages, client work, exception handling, and out-of-scope activation in writing.

Which quality, adoption, meeting, opportunity, pipeline, cost, margin, and retention metrics show whether an intent-platform operating model is working?

Use a baseline and one review cadence. Track sales-cycle length, validation-to-plan conversion, implementation time, accepted-signal cost, delivery hours, support load, contribution margin, client adoption, expansion, renewal, concentration, and switching cost. Use the same client decision to compare models. Do not call correlation incremental impact without an appropriate comparison.

Which clients are ready for an intent-platform operating model, and which prospects should the agency exclude?

A client is ready for an intent-platform operating model when it has a clear ICP, sufficient market or qualified traffic, relevant commercial topics, a named action owner, measurable outcomes, conservative economics, privacy readiness, and a way to return dispositions. Require this first control: Define the client outcome, buyer, and revenue event before evaluating technology. 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-platform operating model?

For an intent-platform operating model, combine topic or first-party behavior with fit, recency, recurrence, identity state, validation, suppressions, human acceptance, the approved activation path, and returned outcomes. Apply the specific controls in this workflow: Map who owns branding, billing, implementation, data rights, support, activation, and measurement. Test representative topics, markets, identity states, exports, and client separation. Keep evidence types separate so an inference never becomes a false fact.

Which data-quality, privacy, security, scope, billing, delivery, and client-trust risks must the agency control for an intent-platform operating model?

Maintain a risk register owned by the agency and client. Risks include assuming resale rights, underestimating engineering, allowing a vendor to own the client, hiding minimum terms, creating data lock-in, omitting deletion and export paths, and mistaking a referral fee for a durable agency asset. Obtain written commercial and legal review. Record the control, owner, evidence, exception path, and next review for every material risk.

What should the final build, resell, refer, or direct-platform decision document include?

The decision document should name the selected model, actual contract parties, client-contact and billing terms, permitted data use, service scope, implementation cost, ongoing capacity, support owner, reporting, cancellation and exit. Record unknown rights as unresolved, not assumed. Compare actual client adoption and cost against the agreed pilot before expanding.

Review one supported research use

Review an available MarketPulse topic, saved ICP and actual preceding-24-hour matches for the agreed research use. AIMEE can organize supplied company context through configured tools. Custom interfaces, reseller agreements, CRM implementation and managed delivery need separately verified scope, rights and fees.