On this page
- Four models for delivering intent-data services
- What to establish before selling the service
- How MarketPulse can support client work
- Current subscription allowances
- Example: pricing a defined client service
- Client billing should describe the work purchased
- Keep client data and reports separate
- Report useful evidence, not guaranteed pipeline
- Frequently asked questions
For an agency offering intent-data services, the important comparison is between business models: referring a client, operating a subscription for client work, reselling licensed data or delivering a white-label platform. These arrangements differ in billing, support, permitted use and what the client receives.
A branded report is not the same as a white-label software portal. Before promising either, document the service, the permissions you have and the work your team will own. Compare a defined scope rather than a collection of partner-program labels.
Four models for delivering intent-data services
Referral
You introduce the client to a product. The product provider generally owns the subscription relationship. Any referral payment, discount or eligibility depends on the applicable program; do not assume it exists because a product supports agencies.
Managed client service
Your team uses available Intent Scans and permitted exports to produce research, reports or appropriate follow-up work for clients. You charge for the defined deliverable and expertise. This does not automatically give clients their own software login or unrestricted rights to every record.
Licensed resale
You sell a specifically permitted data product or service under the governing agreement. Confirm the rights to transfer records, allowed client uses, retention rules and commercial terms before making a promise.
White-label platform
Clients use software presented under your brand. Branding, custom domains, access separation, billing and support need explicit scope. None of those features follows automatically from an agency subscription.
What to establish before selling the service
- Deliverable: A topic report, a reviewed audience, a campaign service or platform access.
- Permission: Which data and derived outputs can be provided, to whom and for which uses?
- Client access: Who can see records, reports and connected accounts?
- Billing: Who invoices the client and handles failed payments or refunds?
- Support: Who responds to data corrections and service questions?
- Exit: What happens to records, access and work in progress when the service ends?
Keep licensing and service design distinct. An agency can create a useful research report without owning the underlying dataset. Conversely, a license that permits certain client work does not establish that a portal or automatic billing feature is included.
How MarketPulse can support client work
MarketPulse helps you find people researching topics relevant to what a business sells, apply ICP filters and review available matches. Agencies and other service businesses can build deliverables around their available pulls and permitted exports.
- Define one client’s offer, target companies and relevant roles.
- Search the topic catalog and inspect available topic choices.
- Apply ICP filters and review matching people and companies.
- Remove unsuitable or duplicate records and check the proposed use.
- Prepare a client-specific report or an authorized next action.
- Review outcomes and adjust the scope before the next delivery.
Keep client scope, permissions and service fees clear. A MarketPulse subscription is not a promise of a white-label platform, exclusive audiences or every downstream integration. Growth and Scale include AIMEE for the initial user to research and prepare next steps through configured tools.
Current subscription allowances
- Starter: One topic, weekly refreshes and 25,000 monthly contact exports.
- Growth: Three topics, daily refreshes and 100,000 monthly contact exports.
- Scale: Ten topics, daily refreshes and unlimited contact exports.
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. Counts and fields vary, and audiences may overlap. Refreshes stop at the plan limit without overage charges.
Connected products, channel usage and fulfillment may cost extra. An eligible early-access discount is separate from these standard prices and depends on the recipient’s offer.
Example: pricing a defined client service
This is an original hypothetical calculation, not a recommended price or earnings promise. Suppose an agency charges $800 for a monthly research service. It allocates $250 in subscription cost, $200 in operator time and $50 in delivery costs to that client.
The direct cost is $500 and the contribution before other overhead is $300, or 37.5% of revenue. If corrections add $100 in labor, contribution falls to $200, or 25%. Include support and review time before calling the package profitable.
When a subscription supports several clients, use a documented allocation method and respect the available allowances. Do not count the same capacity as fully available to every client. Setup work, campaign spend and optional execution can be separately scoped.
Client billing should describe the work purchased
An invoice can distinguish a recurring research fee, setup work and separately authorized execution. The client should know the reporting period, deliverable and limits. Avoid presenting raw record count as a guaranteed number of qualified leads.
For usage-based work, define what counts as a billable unit. An export retry should not silently become a second delivery charge. Reconcile the actual completed work against the scope before invoicing.
Keep client data and reports separate
Use appropriate access controls for each client’s files and connected accounts. Review exports before sharing them, and remove access when the work ends. Do not let a reused report template expose another client’s contacts, campaign results or credentials.
The FTC’s business data-security guidance emphasizes keeping only needed information, limiting access and establishing a retention policy. Apply those principles to the systems your agency uses for client delivery.
A mobile number in an enriched record is not an SMS opt-in. Contact availability, client authorization and the recipient’s permission are separate questions. Record the appropriate basis for the intended action rather than assuming a subscription resolves it.
Report useful evidence, not guaranteed pipeline
A concise client report can show the topics reviewed, pull dates, records accepted under the agreed criteria, completed actions and observed outcomes. Explain overlap, incomplete fields and other limitations that affect interpretation.
Keep data delivery, response and sales results separate. An audience match is not a sale. If a client already had an opportunity with an account, do not credit the entire opportunity to a new topic report.
Frequently asked questions
Does white labeling mean I own the data?
No. Presentation and data rights are separate. Confirm the permitted use and transfer of records under the applicable agreement.
Can I charge for research based on Intent Scans?
A service business can package permitted client work around available pulls and exports. Define the deliverable, permissions, capacity and fees before selling it.
Should my client buy a subscription directly?
Direct access may suit a client that wants to operate the workflow. A managed service may suit one that wants your team to handle the work. Explain who will operate, support and pay for each arrangement.
See MarketPulse’s demo and current plans to build a service around a clear topic, a useful audience and a deliverable you can support.
Reviewed and updated October 2, 2026.
MarketPulse plans are starting at $500/mo. Review current package scope, usage and any separate product or service costs before purchase.
Written by
