On this page
An intent-data RFP should define the business task, required evidence, permitted uses, delivery test and total operating cost before asking for proposals. Give every respondent the same requirements and sample criteria. Separate mandatory conditions from scored features so a large dataset cannot offset a failed essential requirement.
For a small team testing one topic, a written pilot brief may be enough. A formal request for proposal is more useful when several stakeholders, integrations, significant commitments or client delivery responsibilities need a common decision record.
Write the business question first
Specify the market, ICP, geography, exclusions and action the data should support. Name the operator and the destination. Define the outcome you can observe during the evaluation.
Here is an original fictional example: “Our payroll software team wants to investigate organizations researching relevant payroll topics. We need current company context, clear topic definitions and a reviewable record that an assigned researcher can use. The pilot will measure relevant records accepted, review time and qualified follow-up outcomes.”
This brief asks for an operating result. It does not assume that research activity proves an active buying project or that every available contact performed the observed action.
An original RFP requirements template
For each requirement, ask the respondent for an answer, supporting document, relevant limitation and owner. Mark an unanswered item as “not established.”
- Use case: the decision, audience, action and success criteria.
- Data definition: source categories, topic meaning, identity level and field dictionary.
- Time: observation, processing and delivery timestamps, refresh behavior and historical availability.
- Coverage: relevant industries, locations and roles, plus missing or unresolved records.
- Quality: duplicate handling, stale data, disputed matches and correction procedures.
- Delivery: supported export or connection, field mapping, failures and reconciliation.
- Use and control: permitted purposes, client scope, access, suppression, retention and deletion.
- Commercial scope: fees, limits, extra services, implementation, renewal and exit.
Ask for evidence relevant to your requirements rather than accepting a general demonstration as proof. Keep the proposed package and the demonstrated capability aligned.
Separate mandatory gates from scored criteria
A mandatory requirement might be an acceptable data-use agreement, a necessary destination, required fields or a workable correction process. Decide these before seeing responses. A failed gate should be resolved or recorded as a failure, not hidden inside a high average score.
The following is an original illustrative weighting model. Adapt it to your task before issuing the RFP; it is not an industry standard.
- Topic relevance, provenance and recency: 25%.
- Sample coverage and usable-record quality: 25%.
- Delivery and operating effort: 20%.
- Controls, correction and reporting: 15%.
- Total cost and commercial fit: 15%.
For a 0-to-5 scoring scale, define what each score means. For example, zero means the requirement is not established; three means it is demonstrated with documented limitations; five means the full stated requirement is demonstrated. Attach evidence to the score.
If a category has a 25% weight and scores four out of five, its contribution is 20 points out of 100. That arithmetic does not make the judgment objective by itself. Review the evidence and unresolved risks alongside the total.
Run three practical tests
1. Evidence to usable record
Use a defined sample that reflects your ICP. Inspect topic meaning, timestamps, company and person associations, required fields, duplicates and exclusions. Record the original sample size and each reduction so acceptance rates have a clear denominator.
2. Record to action
Move a small approved sample through the intended destination. Check field mapping, ownership, failure visibility and review. Test a correction or suppression request as well as successful delivery.
3. Action to outcome
Record what the operator accepted and did, then reconcile subsequent responses, qualification and opportunities where available. A successful export is not a sales outcome. A later opportunity associated with a record is not automatically incremental revenue caused by the data.
Keep the current process as a comparison where practical. Explain differences in fit, treatment, timing and sample size rather than forcing a winner from limited evidence.
Normalize the full cost
Request a quote for the same scope: topics, refreshes, exports, users, connections, client use, implementation and term. Separate the recurring fee from setup work and other channel costs.
Include internal research, review, administration and reporting time. In a fictional example, a $500 monthly fee, $300 in operator time and $100 in other workflow costs total $900. If 150 records pass the defined acceptance criteria during that month, the operating cost is $6 per accepted record.
These numbers illustrate the calculation, not expected results or recommended pricing. Define “accepted” before measuring it, and keep costs and records within the same time window.
Evaluate the current MarketPulse workflow
MarketPulse plans are starting at $500/mo. Search the available topic catalog, apply your ICP and review the matching people and companies for a task relevant to your market.
An Intent Scan retrieves available data from the previous 24 hours. Review the plan’s topic, refresh and export allowances against your operating needs. Counts, fields and coverage vary, and audiences can overlap.
AIMEE can assist through configured tools and workflows. Confirm the supported destination and permissions for the action you need. An export allowance does not automatically establish client redistribution or ad-platform activation rights.
If you plan to rely on the first-purchase three-day satisfaction guarantee, review its conditions first: no data exports and no more than two Intent Scans. A limited evaluation can establish some aspects of fit, but cannot prove future pipeline.
Review controls and keep a decision record
The NIST Privacy Framework is a voluntary privacy risk-management resource. Use it to help structure relevant questions about data processing and responsibility; it is not a certification of a particular supplier or a replacement for applicable requirements.
Assign owners for commercial scope, security, data use, delivery and reporting. Confirm access, corrections, retention, deletion and exit responsibilities in the actual agreement. Keep each client’s scope and data separate in agency work.
At the end, record passed gates, evidence-based scores, cost assumptions, unresolved items and the reason for the decision. “More testing needed” is a valid result when the sample or workflow does not answer the question.
Use AI to organize evidence
AIMEE or another permitted drafting workflow can help arrange approved documents into a requirement-and-evidence matrix. Give it the requirement IDs and source documents, and instruct it to preserve limitations and mark missing evidence.
Verify the matrix against the originals. Do not let a generated summary invent a price, supported connection, data right or contract term. The accountable people should review the sections they own and approve the final record.
Frequently asked questions
Do we need a formal RFP for a small pilot?
Not necessarily. A concise written brief with scope, criteria, costs and review responsibilities can be suitable for a bounded test.
Should the lowest price win?
Compare the full operating cost and requirements passed. A lower fee can still require more labor or fail the task your team needs to perform.
Can a high total score override a mandatory failure?
Keep mandatory requirements separate. Resolve the failure explicitly rather than allowing unrelated features to offset it.
What should we preserve after the evaluation?
Keep the requirements, responses, sample definitions, test results, quotes, score evidence, limitations and final rationale in a dated decision record.
Reviewed and updated October 2, 2026.
Written by
