How to Use the Fieldbook
This fieldbook is a working instrument for campaign and revenue teams, not a benchmark report. It assumes that a B2B technology vendor has a list of candidate accounts but needs to decide which organizations, business units, and buying roles are suitable for a specific offering. Its worksheets are designed to be completed in order: define the market, resolve identity, validate fit, map roles, authorize activation, and confirm handoff. Each worksheet produces a decision artifact with a named owner.
The 60-day schedule is illustrative, not a statement about the time needed in every organization. Data-source contracts, privacy rules, product complexity and CRM implementation determine real feasibility. Do not assign scores based on an anticipated future data check. Validate the current sample first.
Worksheet 1: Write the Account Eligibility Contract
Purpose: agree precisely which companies are addressable for this campaign. Record the product line, buyer problem, territory, intended company types, required technical context, supported deployment models and exclusions. Give each requirement a source and an owner. For a hypothetical developer-tools vendor, the audience might include companies building and deploying their own applications, while excluding consulting-only businesses if the product does not serve them.
Fields to complete: offering and use case ____; target region ____; qualifying industries ____; operating characteristics ____; prohibited or unsupported segments ____; required evidence fields ____; approving Marketing owner ____; Sales territory owner ____; rule version and date ____.
Acceptance test: provide six positive and six negative account examples. Ask two independent reviewers to decide eligibility without a live explanation. Record disagreements and amend the rules. The goal is a repeatable rule, not unanimous optimism. Intent Amplify Buyer Intelligence emphasizes scope, buying roles, validation fields and exclusions as the starting point [1].
Worksheet 2: Resolve Company Identity and Ownership
Purpose: prevent one organization appearing in multiple ways while protecting legitimately separate divisions. Preserve the supplied company name and source key, canonical domain, legal or trading entity, parent ID, relevant subsidiary and CRM owner. Salesforce’s parent-child hierarchy guidance shows why an account structure can contain multiple distinct records [2]. HubSpot’s deduplication guidance documents common company-domain and contact-email matching methods [3]. These software behaviors do not establish the correct business interpretation on their own.
Fields to complete: supplied company ____; canonical record ____; parent entity ____; business unit ____; country ____; source URL or reference ____; check date ____; duplicate-review status ____; Sales coverage owner ____.
Acceptance test: examine one renamed business, one acquisition, one shared-domain subsidiary and one unrelated same-name company. Log whether each should be merged, related, separated or sent for manual review. Keep the original IDs so a reviewer can reconstruct the decision.
Worksheet 3: Score Fit without Pretending to Predict Buying
Purpose: create a transparent, non-predictive eligibility assessment. Score four evidence dimensions from 0 to 2 as an internal working rubric: product/use-case relevance; company-type match; geography and serviceability; required operational or technology environment. Use 0 for not established, 1 for supported with limitations, and 2 for supported against approved evidence. Maximum score is 8. Mandatory exclusions overrule the sum.
Example: a firm operating in the target country with the right business model but no evidence of the required deployment environment earns no automatic activation approval. The unknown must be resolved or its consequences explicitly accepted by the business owner. The score is not a purchase probability and should not be compared with external industry benchmarks.
Fields to complete: each dimension ____; evidence reference ____; last-check date ____; exclusion override ____; final eligibility judgment ____; reviewer ____. Report how many sampled accounts have enough evidence, and how many need additional research.
Worksheet 4: Map Real Buying Tasks to Actual People
Purpose: replace the “one senior title equals one buyer” assumption with role-specific content relevance. Document the business problem, expected evaluator, operating user, finance or economic approver, security/privacy reviewer and procurement participant as applicable. Salesforce’s contact-role documentation differentiates evaluators and decision makers in opportunity context [4]. That is a model for defining separate roles, not confirmation of roles in your list.
Fields to complete: task or decision ____; original title ____; normalized department ____; proposed buying role ____; evidence for interpretation ____; uncertainty flag ____; appropriate content ____; permitted response ____.
Acceptance test: inspect five accounts where a senior executive has no visible connection to the technology purchase. Can the team articulate a plausible relevance path without inventing budget authority? If not, choose another role or educational approach. Multiple legitimate buying roles do not imply that every role is already engaged.
Worksheet 5: Approve Source Rights and Activation Plan
Purpose: determine whether a valid target record can be used in the proposed channel. Capture source permissions, applicable consent or lawful-use basis, country, suppression status, communication policy, retention owner and approved campaign purpose. For US commercial email, the FTC explains that the CAN-SPAM Act applies to B2B commercial messages and requires appropriate opt-out treatment [5]. Other jurisdictions may have different rules; seek appropriate review.
Fields to complete: personal-data elements ____; collection source ____; approved purpose ____; email eligibility ____; social-message eligibility ____; exclusion/suppression timestamp ____; privacy owner ____; remediation path ____.
Acceptance test: use one verified contact who opted out, one contact with missing source, and one contact whose regional treatment is unclear. The account may remain on the market map, but the person must not be activated through a prohibited or unapproved channel.
Worksheet 6: Define Delivery Acceptance and Sales Handoff
Purpose: make the next action explicit before the campaign runs. Record the accepted engagement types, required campaign and asset IDs, validation checks, qualification information actually captured, rejection and replacement rules, CRM mapping fields and receiving owner. Intent Amplify Managed Demand Generation describes a managed audience, content and evidence pathway [6]; Pipeline Activation describes an accountable CRM handoff [7]. Both depend on an agreed engagement scope.
Fields to complete: accepted response types ____; disallowed substitutions ____; mandatory fields ____; quality sample ____; acceptance reviewer ____; replacement terms ____; CRM owner/queue ____; next-action types ____; Sales disposition codes ____.
Acceptance test: a registration with no attendance must remain a registration; a mismatched persona must retain that exception; an opted-out contact must not enter a prohibited sequence; and an accepted content interaction cannot become an SQL without Sales qualification. The destination CRM team must validate any real field routing before activation.
A Hypothetical Worked Example
Suppose a B2B cloud operations vendor receives a file of 1,000 candidate companies. This is an illustrative starting inventory, not a real campaign or performance case. The first task is not to claim a particular conversion rate. The team selects a stratified sample: large and midmarket companies, different countries, legacy customers, high-priority accounts and the accounts Sales already disputes.
The team discovers that some entries refer to regional brands owned by the same parent, some have no relevant cloud operations function, and others match the ICP but have no confirmed contact. Rather than guessing final totals, the team records every disposition, updates the definitions and then runs them against the rest of the file. Its final report distinguishes the universe, verified eligible accounts, excluded records, open identity questions and verified contact-role coverage.
The Illustrative 60-Day Plan
Days 1–10: approve the market question, product use case, owner and exclusions. Output: audience eligibility contract.
Days 11–20: reconcile canonical records and account hierarchy; preserve source and check dates. Output: identity decision ledger.
Days 21–30: test fit and buying-role rules on positive and negative examples. Output: validated sample with documented disagreements.
Days 31–40: verify data rights, suppression, content relevance and acceptance definitions. Output: controlled activation brief.
Days 41–50: run a bounded pilot only where authorized, preserving distinct engagement evidence and correcting exceptions. Output: delivery and validation ledger.
Days 51–60: review Sales dispositions with RevOps and revise the rules. Output: the next-version audience specification and executive decision summary. The schedule is conditional on actual approvals.
An Internal Readiness Rubric with No Invented Benchmarks
Score each of six worksheet outputs on a 0–3 scale: 0 absent; 1 drafted; 2 approved with evidence; 3 implemented and sampled. A total of 18 is possible. This score is an original planning tool, not a certified measure of pipeline performance. It is inappropriate to award 3 for an activity that exists only in a project plan. Display the scored evidence and the decision owner beside the numeric total.
For management reporting, show eligible-account share with a documented denominator, percent of records with traceable identity, buying-role coverage, channel-permission coverage, acceptance/rejection reasons and Sales disposition completeness. Recalculate these measures by audience-rule version. Never turn engagement counts into opportunity counts without the CRM’s authoritative record.
Guide to Reviewing a Batch Before Wider Activation
The review group should draw records from every original data source and account tier, rather than only from the cleanest segment. Include records that were previously rejected by Sales. Ask reviewers to keep a reason-code sheet with examples, not just pass/fail totals. If new errors cluster in one source, narrow that source’s allowed use or run additional validation before distribution. Where outcomes differ between products or territories, record separate eligibility versions. This avoids treating one campaign’s decision as permanent truth for the entire CRM.
Intent Amplify Perspective
The service path can be tailored around the six worksheets. Buyer Intelligence supports audience and role requirements; Managed Demand Generation can run agreed content or event activity and validation; Pipeline Activation can prepare a permitted, contextual handoff. The client retains decisions about market ownership, privacy, CRM fields, Sales acceptance, and commercial opportunity stages.
A smaller, explainable universe may be a better operating asset than a larger file that no one can defend. The output worth taking into a campaign review is the evidence-backed decision about where to focus, not the total that fits on the slide.
Use the Fieldbook before the Next Campaign Brief
Complete the six worksheets with your own source evidence and owner sign-offs, then run the negative-case tests on a representative sample. If additional help is useful, bring the completed results into an exploratory audience-scoping conversation with Intent Amplify.
Evidence Notes and References
References below support their specifically cited factual statements. Example workflows, criteria, matrices and test cases are proposed editorial frameworks, not verified client results. The availability of any Intent Amplify service component depends on agreed engagement scope. All links were reviewed during preparation on October 23, 2026.
- Intent Amplify, Buyer Intelligence. https://www.intentamplify.com/solutions/buyer-intelligence
- Salesforce Help, Create Parent and Child Account Relationships (April 2, 2026). https://help.salesforce.com/s/articleView?id=000391142&language=en_US&type=1
- HubSpot Knowledge Base, Deduplicate Records in HubSpot (updated October 2, 2026). https://knowledge.hubspot.com/records/deduplication-of-records
- Salesforce Help, Contact Roles. https://help.salesforce.com/s/articleView?id=sf.sales_core_contact_roles.htm&language=en_US&type=5
- US Federal Trade Commission, CAN-SPAM Act Compliance Guide for Business. https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- Intent Amplify, Managed Demand Generation. https://www.intentamplify.com/solutions/managed-demand-generation
- Intent Amplify, Pipeline Activation. https://www.intentamplify.com/solutions/pipeline-activation
