How to Use This Fieldbook
Agency teams can use this fieldbook when an end-client campaign needs specialized B2B audience work, managed demand execution, or a more consistent Sales handoff. It is a practical planning aid, not a claim that a particular agency or technology vendor already uses the process. Select one client, one approved offer, and one delivery period. Ask the client and prospective specialist to complete the worksheets jointly before any commercial commitment.
The suggested workshare reflects three published Intent Amplify service areas: Buyer Intelligence for audience decisions, Managed Demand Generation for approved activation and response validation, and Pipeline Activation for a documented next action [1], [2], [3]. The sequence is useful as a design reference, but the precise delivery model depends on a written scope and data terms. A partnership label alone cannot settle who owes what to the end client.
Worksheet 1: Define the End-Client Decision
Decision: What will the technology client be able to decide after the program? Write the current business need, approved offer, target markets, relevant content, and intended action. Distinguish awareness, information requests, Marketing acceptance, Sales acceptance, and opportunity creation. Record a sponsor for each decision. A demand activation partner should not inherit a vague objective such as “more leads” without agreeing what a valid response means.
Required fields: Client sector, offer, campaign dates, audience objective, primary buyer function, qualifying action, owner, and exclusions. Review test: Give two reviewers the brief and ask whether the same response would be counted. If one calls a download an SQL and the other calls it a content response, the outcome definition must be reconciled before launch.
Worksheet 2: Build the Account and Role Map
Decision: Which companies and people are suitable for this client campaign? Write the market boundaries, industry requirements, account-size criteria when supplied, role groups, exclusions, source dates, and validation method. The audience map should distinguish a verified current role from an inferred buying-committee assignment. Intent Amplify’s Buyer Intelligence description supports building a source-aware account and role decision [1].
Required fields: Source account ID, company name, segment, geography basis, role, validation source, checked date, and suppression result. Review test: Introduce one duplicated company, one old title, and one unverified parent-company relationship. Each reviewer must reach the same inclusion outcome, with a recorded reason. A large list should not be described as ready-to-send merely because the names are relevant.
Worksheet 3: Specify the Agency and Specialist Workshare
Decision: Who is responsible for the promise, the content, the execution, and the data? A simple workshare can assign the agency to client strategy, brand approval, and executive reporting, while a specialist handles only agreed audience research, distribution, validation, or handoff tasks. Avoid implying that the specialist has permission to represent the client or operate under the agency’s name without a signed arrangement.
Required fields: Task, accountable party, responsible operator, approving party, evidence produced, and escalation route. Review test: Ask who acts when a client wants a late content change, a recipient opts out, or a reported lead is disputed. Intent Amplify’s published five-stage operating model separates scope, audience, delivery, validation, and handoff approvals [8]. Treat that as a reference structure rather than an automatic contract.
Worksheet 4: Create the Acceptance and Replacement Rules
Decision: What makes an individual response acceptable? Specify the permitted channels, campaign-specific forms or events, account and role checks, mandatory fields, uniqueness logic, consent or communication restrictions, and source records. Google Analytics recommends separate generate_lead and qualify_lead events when an organization instruments those actions [4]. Event labels can assist reporting but do not themselves certify commercial fit.
Required fields: Event ID, contact identifier if known, asset, action, timestamp, validation status, rejection reason, reviewer, and decision date. Review test: Apply the policy to a repeated download, an invalid role, a wrong geography, and a direct meeting request. Record any permitted replacement rule in the client scope rather than assuming every rejected record must be replaced.
Try a Five-Record Acceptance Exercise
Before scaling a program, compare five sample responses against the account, identity, and engagement rules in Worksheets 1 through 4. Use the documented delivery model to clarify which decisions belong to the agency, specialist, and client.
Review the Delivery Model
Worksheet 5: Plan the Content and Channel Path
Decision: Which content belongs at each stage and who approves the message? A new-category technology vendor may need an introductory guide before a product comparison. An existing-category vendor might need customer questions or a webinar follow-up. Match topics to the approved audience and avoid implying that an individual who consumed one resource is ready to buy. The 4As’ 2026 survey observes the continuing role of relationship-based agency development among its respondents [9]; the client relationship remains a strategic asset during specialist execution.
Required fields: Content owner, asset ID, audience, channel, approved destination, campaign tracking tags, legal review path, and follow-up rule. Review test: A recipient sees the wrong brand, an outdated offer, or an unapproved external link. Can the agency determine who approved the asset and which records were affected? Keep the client’s brand requirements visible across the entire chain.
Worksheet 6: Define Sales Acceptance and the Next Action
Decision: What will the technology client’s Sales function accept, review, and do? Preserve the original request along with validation context, owner assignment, and explicit Sales disposition. Salesforce documents configurable assignment rules that direct leads to a user or queue [6]. A routed record is not proof that the receiving person reviewed it. HubSpot separately describes Marketing Qualified Lead and Sales Qualified Lead lifecycle stages according to the qualifying function [5].
Required fields: Receiving owner, acceptance timestamp, approved criteria, buyer-stated issue when known, agreed next action, and decline or nurture reason. Review test: A contact asks for a guide but never requests a discussion. Report the educational response accurately, even if a score favors the account. Under a conservative proposed policy, an SQL requires buyer-confirmed need and an accepted next step.
Worksheet 7: Build a Client-Readable Reconciliation View
Decision: Which outcomes appear on the end-client report, and what source substantiates each number? Track program reach, unique accepted responses, qualified responses, Sales reviews, Sales acceptances, held meetings, and opportunities separately. Keep the reporting window, numerator, denominator, and rule version beside each figure. A projected campaign target must be labeled as a target until observed results are available.
Required fields: Metric, definition, source system, cohort, reporting date, owner, exception count, and evidence pointer. Review test: Take five reported results and reconstruct their history from the original source, including invalid or repeated responses. A report that passes this test is easier for an agency account lead to explain without promising that execution automatically creates revenue.
Five Practice Scenarios
Case A: The agency proposes a new SaaS audience but lacks current title verification. Preserve the market hypothesis, then verify eligible roles before direct outreach.
Case B: A webinar registrant submits the same form twice. Preserve both actions, apply the agreed unique-person rule, and do not double-count a qualified response.
Case C: The specialist finds a strong account match with no evidence of immediate demand. Treat it as an account suitable for research, not a known buyer.
Case D: A client-side seller rejects an otherwise valid response because the person only wanted an educational guide. Retain the accepted Marketing output and record the Sales disposition separately.
Case E: A recipient uses a permitted channel to ask for a call. Record the request, agree the next step, and let the receiving Sales owner determine qualification.
In every case, respect applicable contact-use restrictions; the FTC confirms that commercial email requirements also apply to business-to-business messages [7].
A 30-Day Practice Plan
Days 1–5: Agree the client decision, eligible audience, and commercial scope.
Days 6–10: Approve the workshare, content responsibilities, acceptance rules, and communication restrictions.
Days 11–15: Run a small controlled sample and review the source records.
Days 16–20: Check duplicate handling, validation outcomes, and returned records.
Days 21–25: Test client-side Sales acceptance and appropriate follow-up.
Days 26–30: Reconcile results by source and publish a lessons-learned review.
This is a planning example, not an implementation guarantee.
The Intent Amplify Perspective
Buyer Intelligence can support an agency’s client with a clearer account and role map [1]. Managed Demand Generation can support coordinated distribution, validation, and accepted-response reconciliation [2]. Pipeline Activation can help the client’s Sales team receive source-aware context, an accountable owner, and an appropriate next action [3]. The agency remains responsible for agreeing how these services fit the end-client engagement. A signed scope, not a general article, determines actual services and commitments.
Fieldbook Completion Standard
The seven worksheets are complete when another reviewer can determine which client decision the program serves, which people may be approached, who owns the deliverables, why a response is accepted, and what the receiving Sales team is expected to do. Preserve unanswered questions as questions. Record a valid educational response without declaring it a sale. The value of a specialist execution arrangement lies in an explicit, testable workshare.
Evidence Notes and References
Numbered citations identify the sources supporting particular statements. Official service descriptions establish publisher-described scope, not measured Intent Amplify client outcomes. Survey findings retain the publisher’s sample boundaries. Practice cases and frameworks are editorial synthesis, not observed campaign performance. Sources reviewed November 11, 2026.
- 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
- Intent Amplify, Pipeline Activation (Official Service Description). https://www.intentamplify.com/solutions/pipeline-activation
- Google Analytics Help, Recommended Events for Lead Generation. https://support.google.com/analytics/answer/9267735?hl=en
- HubSpot Knowledge Base, Use Contact and Company Lifecycle Stages (Official Documentation). https://knowledge.hubspot.com/records/use-lifecycle-stages
- Salesforce Help, Set Up Assignment Rules (Official Documentation). https://help.salesforce.com/s/articleView?id=sf.creating_assignment_rules.htm&language=en_US&type=5
- Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business (Official U.S. Guidance). https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- Intent Amplify, How It Works (Official Delivery Model). https://www.intentamplify.com/how-it-works
- 4As, New Business Activity & Resources Survey 2026 (Based on 2025 Survey Data). https://www.aaaa.org/resource/new-business-activity-resources-survey-2026/
