How to Use This Fieldbook
A technology portfolio is not one buying decision. Products may serve different departments, use cases, customer segments, and purchase processes even when they share the same target account. This fieldbook is designed to help a team coordinate account selection while keeping each product’s audience, message, and commercial stage distinct. It contains six working worksheets. Complete them for a manageable subset of accounts before expanding.
Each worksheet has four practical elements: A decision to make, fields to record, a named owner, and a reproducible review test. The framework is a proposed planning method, not a description of an automatic product feature or an observed performance result. The objective is to make an ABM program easier to review, revise, and operate across teams without turning every marketing interaction into a sales claim.
Worksheet 1: Create a Shared Account Record
Decision: Should the account be in the portfolio-wide target universe? Fields: Account legal name; parent organization; subsidiary or business unit; headquarters and selling region; industry; employee-size band if supported; named exclusion; source URL; verification date; review owner. Add a confidence note that distinguishes direct company evidence from vendor taxonomy or inference. Do not call a billing-country field verified headquarters.
Review test: Have two team members classify three borderline accounts without seeing each other’s decision. If they disagree, refine the definition. HubSpot documents a Target Account company property as a way to identify companies pursued through ABM [1]. It is an organizational label, not evidence that a company has a current buying project. Owner: ABM Strategy, with Revenue Operations maintaining the record key and duplicate policy.
Output: A versioned account universe with explicit exclusions. Negative cases matter. An attractive brand that fails the agreed geography or product-market test should remain in the excluded file with a reason, not silently enter the activation list.
Worksheet 2: Set Product-Fit Rules Before Writing Copy
Decision: Which solution families are plausible for this account and why? Fields: Product family; supported business use case; eligible market; exclusion; known customer or partner relationship if verified; source of relevant evidence; owner; confidence; latest review date. Separate broad account suitability from evidence that the product category is relevant. Do not infer the use of a vendor’s competitor merely from industry membership.
Microsoft Dynamics 365 Sales describes product families as a way to categorize products and bundles within its product catalog [2]. That documents one example of portfolio organization, not a requirement to adopt Microsoft software. A campaign can maintain the same logical product-to-use-case classification in an existing planning table. For each account, permit one primary product path, secondary paths with evidence, and an explicit not-yet-relevant state.
Review test: If an account engages with a cloud operations article, would a reviewer understand why a separate data-governance offering should or should not be promoted? Owner: Product Marketing, with Sales validating which offerings can realistically be discussed in the account.
Worksheet 3: Map Buying Roles by Product Decision
Decision: Who could help answer the product-specific buyer question? Fields: Function; full Title Case designation; likely responsibility; named contact if verified; source and date; role type; evidence of actual involvement; unknown decision participant; permitted channel. Keep role hypotheses distinct from identified participants. A CMO may sponsor a portfolio campaign while a VP Engineering is an evaluator for only one product line.
Intent Amplify Buyer Intelligence frames account and buying-role criteria as inputs to a validated activation audience [3]. Use that scope to design the mapping exercise. Avoid presenting a decision-maker label, a senior title, or a LinkedIn connection as proof of procurement authority. Prefer neutral questions such as whether the area falls within the person’s responsibilities.
Review test: Give a colleague the buying-role map for a product they did not help launch. Can they explain what is known, what is inferred, and which role still needs confirmation? Owner: ABM Director. Output: Product-by-role matrix with evidence labels, not a fictional complete committee.
Worksheet 4: Match One Content Promise to One Buyer Question
Decision: What would a person learn from each asset without accepting a meeting? Fields: Asset ID; product family; reader problem; intended role; claim references; distribution placement; content owner; approved first-party destination; exclusion rule; next helpful resource. Avoid using the same general portfolio pitch for every product line. A product comparison, implementation checklist, and executive economics note can all be useful, but each serves a different reader task.
Intent Amplify Managed Demand Generation describes coordinated audience, content and event activation, validation, and reporting within an agreed program [4]. That operating model makes content-to-account mapping an explicit decision rather than a volume exercise. The content promise should remain true for a reader who is researching the topic without a current budget.
Review test: Have a neutral reviewer read the headline and first paragraph. Can the reviewer state the promised learning outcome in one sentence? If the answer changes by product, produce a separate version. Owner: Product Marketing for claim quality and Marketing Operations for asset IDs and distribution rules.
Worksheet 5: Build the Evidence and Contact-Permission Ledger
Decision: Which observed events justify a next action? Fields: Account ID; contact ID where valid; product path; content ID; observed action; timestamp; channel; source; identity connection; explicit inquiry; duplicate status; restriction; owner. A company-level impression, a named form request, and a reply describing a project belong in different event classes. Avoid turning anonymous company reach into identified personal interest.
Google Analytics documents UTM parameters for identifying campaign referral context [5]. These parameters do not, by themselves, prove who viewed a page or which product an entire account is evaluating. LinkedIn Matched Audiences describes company, contact, and retargeting audience types [6]; each depends on its own data and settings. Record only the type of engagement actually available.
Review test: Reconstruct five events from source records and verify that the product attribution, timestamp, and contact rules survived the handoff. The FTC explains that US commercial email requirements cover business-to-business marketing [8]. Owner: Campaign Operations with the responsible privacy reviewer. Output: Traceable event ledger and a separate permitted-action decision.
Worksheet 6: Define the Sales Handoff by Product
Decision: Which offer, relevant business need, and next action should the receiving seller review? Fields: CRM account key; product family; named contact; validated role; original event; buyer-stated problem if any; campaign context; channel eligibility; receiving owner; MQL rule; Sales acceptance; accepted next step; disposition date. One account can contain several distinct product conversations without making them one generic opportunity.
Intent Amplify Pipeline Activation describes assembling validated account, contact, and engagement context for a named receiving Sales owner or queue [7]. The receiving Sales team should confirm whether any specific product opportunity exists. A completed content form, matched company impression, or lead score cannot replace evidence of a business need and a mutually accepted next step.
Review test: Ask a seller who was not involved in the campaign to explain what is established and what the first reasonable question should be. Owner: Sales leadership with Revenue Operations controlling stage history. Output: An evidence-backed handoff with a visible accept, decline, nurture, or no-contact decision.
Two Negative-Case Tests That Prevent Portfolio Confusion
Case A: The same contact requests an analytics guide and later attends a security webinar. Preserve two separate interactions, then ask whether each is relevant to that person’s actual responsibilities. Do not declare a cross-sell opportunity simply because the account appears in two product dashboards.
Case B: Two business units share a parent organization, but one is excluded from a program. Resolve the legal entity before treating the parent record as blanket permission to activate both.
Case C: A marketing response is valid but suppressed for email. Preserve permitted internal evidence while excluding the prohibited action.
Case D: An existing account owner says a product discussion is not in scope this quarter. Record the disposition and adjust outreach. These cases are hypothetical controls rather than incidents or proof of campaign performance.
A Practical 30-Day Pilot
Days 1–5: Agree on the account universe, product-family definitions, and exclusion rules.
Days 6–10: Map priority roles and design one relevant content path for each primary product use case.
Days 11–15: Test event capture and approved destinations with synthetic records.
Days 16–20: Complete source and contact-permission review, then initiate a small authorized activation group.
Days 21–25: Review accepted responses and Sales dispositions by account and product.
Days 26–30: Compare evidence gaps and authorize one controlled expansion or correction.
Keep a dated decision ledger for the pilot. For every change, record the prior rule, revised rule, evidence, reviewer, and effective date. Count the same event population under the definition used at the time. The 30-day steps are an illustrative operating sequence, not evidence that campaign infrastructure has already been configured or that any form-fill goal has been reached.
Explore Managed Demand Generation
The Intent Amplify Perspective
Buyer Intelligence can support the account and role screen; Managed Demand Generation can help operate distinct product-content paths and acceptance controls; Pipeline Activation can pass the appropriate context to Sales [3], [4], [7]. The client retains its own product strategy, CRM permissions, qualification criteria, and commercial decisions. The value of a coordinated approach lies in making these boundaries understandable to every participating function.
Use the Fieldbook With Five Accounts
Complete all six worksheets for five genuinely eligible accounts with different product-fit patterns. Have ABM, Product Marketing, and Sales independently review the resulting decisions and capture where the evidence changes the proposed message. To explore a managed approach to approved activation, see Intent Amplify Managed Demand Generation at https://www.intentamplify.com/solutions/managed-demand-generation.
Evidence Notes and References
Numbered references support the factual claims beside them. Program methods, examples, definitions, and recommendations are editorial proposals, not measured campaign outcomes. Official vendor documentation describes its own products or services only. Sources reviewed November 3, 2026.
- HubSpot Knowledge Base, Set Up Account-Based Marketing in HubSpot (Official product documentation). https://knowledge.hubspot.com/branding/get-started-with-account-based-marketing-in-hubspot
- Microsoft Learn, Set Up Product Families (Official Dynamics 365 Sales documentation). https://learn.microsoft.com/en-us/dynamics365/sales/create-product-family
- Intent Amplify, Buyer Intelligence (Official service description). https://www.intentamplify.com/solutions/buyer-intelligence
- Intent Amplify, Managed Demand Generation (Official service description). https://www.intentamplify.com/solutions/managed-demand-generation
- Google Analytics Help, URL Builders: Collect Campaign Data with Custom URLs (Official product documentation). https://support.google.com/analytics/answer/10917952?hl=en
- LinkedIn Marketing Solutions, Matched Audiences (Official advertising documentation). https://business.linkedin.com/advertise/ads/targeting/matched-audiences
- Intent Amplify, Pipeline Activation (Official service description). https://www.intentamplify.com/solutions/pipeline-activation
- Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business (US federal guidance). https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
