How to Use This Workbook
This workbook is a planning and review instrument for enterprise teams working across multiple demand channels, vendors and internal functions. It is organized around five worksheets that connect strategic decisions to required evidence and the responsible person. The 90-day structure is illustrative; complex procurement, geographic permissions and CRM changes may require a different schedule. The worksheets do not replace contractual scope, source permissions or enterprise governance. Each should be completed with actual current information and approved through the relevant internal process before activation.
Worksheet 1: Define the Enterprise Growth Decision
Purpose and Working Instructions
Begin with one business decision rather than a broad statement such as 'more pipeline.' For example, the enterprise may need to establish whether a defined account segment is reachable with approved content, whether a regional persona strategy creates relevant engagement, or whether delivered engagement records are suitable for Sales review. The sponsor writes the question, the decision date, the audience boundary and the exact evidence needed. All fields should be assigned an owner.
-
Business question: ____________________ | Decision sponsor: ____________________
-
Target market, account classes and geography: ____________________
-
Intended buying roles and exclusions: ____________________
-
Approved program types and assets: ____________________
-
Evidence needed to make the decision: ____________________
-
Required privacy, contract and financial approvals: ____________________
-
Go/no-go criterion: ____________________ | Review date: ____________________
Illustrative Completed Example
A midmarket technology division wants to test a defined IT operations audience in one region using two educational guides. The objective is to measure eligible account reach, accepted content engagement and handoff completeness, not to promise a number of opportunities. The audience owner must define the company-size band, excluded industries and approved contact roles. The program owner records whether the segment is feasible under the actual data sources and scope. Sales agrees how accepted records will be reviewed and how rejections will be classified.
Worksheet 2: Build the Audience Evidence Contract
Required Fields and Decisions
For every chosen field, record its purpose, permitted source, update date, confidence or validation status, handling of unknowns, and owner. Common fields include canonical company domain, market segment, region, business-contact identity, role or persona, consent or permission flag, campaign identifier and interaction timestamp. Identity conflicts should be quarantined for review. An account tier derived from an internal segmentation model must be labeled as the enterprise's classification, not presented as an externally verified purchase signal.
-
Account identity fields | Mandatory/optional: ____ | Approved source: ____ | Check: ____ | Owner: ____
-
Contact and role fields | Mandatory/optional: ____ | Approved source: ____ | Check: ____ | Owner: ____
-
Engagement fields | Mandatory/optional: ____ | Source/time: ____ | Interpretation limit: ____
-
Privacy and communication permissions | Basis: ____ | Retention: ____ | Suppression: ____
-
Exclusion and replacement reasons | Codes: ____ | Reviewer: ____ | Escalation: ____
Sample Acceptance Tests
Test a correct account and role; a duplicate with competing company names; a valid person outside the intended persona; a record with an incorrect country; and a contact with unverified consent where consent is required. For each, document whether to accept, reject, hold, replace, or request more information. Ask two reviewers to apply the rule independently; if they disagree, the rule is insufficiently precise and needs clarification.
Worksheet 3: Map Content and Channels to Buyer Decisions
Build a Purpose-led Activation Grid
List the stakeholder question, the content answer, the allowed channel, the recorded interaction, and the next action that the evidence could support. An educational download may justify a nurture asset; an explicit inbound inquiry may justify a permitted sales-response workflow. Do not create a score conversion that transforms a generic content interaction directly into an SQL. Ensure the asset is reviewed for marketing claims, privacy requirements, and relevance to the program's solution scope.
-
Persona: ____ | Business question: ____ | Content asset: ____ | Channel: ____ | Approved claim source: ____
-
Observable interaction: ____ | Verification method: ____ | Responsible owner: ____
-
Permitted response or follow-up: ____ | Required consent: ____ | Exclusions: ____
-
Fallback if no usable engagement is captured: ____ | Review date: ____
A Practical Sequencing Example
For an enterprise infrastructure audience, week one might provide a planning article; week two a detailed technical evaluation guide; week three an optional executive procurement checklist. Each asset should have a distinct purpose and clear label. If a contact engages with one resource, record that interaction without assuming that the reader consumed subsequent materials. The campaign ledger should preserve channel, asset and time instead of presenting an inferred full journey.
Worksheet 4: Specify Validation, Acceptance and CRM Handoff
Acceptance Specification
Define what counts as an eligible response, the proof that must accompany it, and the cases that trigger rejection or replacement. Record each delivery as accepted, rejected, replacement requested or pending clarification. Do not count pending records as accepted. If a sample audit identifies systematic mismatches, hold the affected batch and revise the validation check rather than quietly changing the reporting denominator.
-
Delivery unit and exact definition: ____ | Excluded event types: ____
-
Mandatory acceptance fields: ____ | Quality sampling method: ____
-
Duplicate, role mismatch and geographic exclusion codes: ____
-
Acceptance reviewer and turnaround window: ____ | Replacement rule: ____
Sales Handoff Specification
Identify the CRM object, approved field mappings, receiving owner or queue, submission reference, content or event source, timestamp, qualification inputs, and next-action recommendation. Preserve source permissions. A CRM integration should not be assumed to exist merely because the asset describes a handoff model. Platform and RevOps owners must verify actual routing, consent treatment, error handling and rollback before a production change.
-
Receiving CRM owner / queue: ____ | Approved fields: ____ | Required reference ID: ____
-
Sales disposition options: accepted; rejected; needs clarification; nurture; no action (adapt to approved policy).
-
Follow-up permission and suppression check: ____ | Error/duplicate remediation owner: ____
Worksheet 5: Establish an Improvement Loop
Create a Metric Dictionary
Measure a small set of evidence-based indicators rather than starting with a composite success score. Candidate metrics include eligible account coverage, percent of accepted records meeting the full field specification, duplicate rate, rejection reasons, time to assignment, permission completeness and Sales response coverage. Each requires a definition, numerator, denominator, period, source of truth and owner. Qualified leads, opportunities and revenue should be reported only from the authorized CRM process and never inferred from the delivery ledger.
-
Metric name and definition: ____ | Numerator: ____ | Denominator: ____
-
Period: ____ | Source system: ____ | Owner: ____ | Verification sample: ____
-
Baseline: ____ | Target approved by owner: ____ | Exception threshold: ____
Retrospective Prompts
At each review, ask: Did the program reach the defined audience? Which content or channels generated verifiable engagement? What failed audience or delivery acceptance? What did Sales find usable? Which records were unqualified or had incomplete data? Which changes need a new approval? A productive review converts each problem into a named corrective action with a verification test.
The Illustrative 90-Day Plan
Days 1–15 — Frame and Scope
Appoint sponsor and operators; review current audience and source permissions; complete Worksheet 1; agree the decision and data boundaries. Output: approved decision brief and problem statement. Gate: scope and required approvals confirmed. If the objective or consent basis is unclear, do not proceed to activation.
Days 16–30 — Design and Test
Complete the audience evidence contract, asset mapping and acceptance policy. Run small positive and negative data-validation tests. Output: approved account/role specification, asset matrix and campaign measurement plan. Gate: audience feasibility and validation rules are usable by independent reviewers.
Days 31–45 — Prepare Controlled Activation
Confirm editorial clearance, channel scope, destination links, event or content references, campaign tags, consent capture, delivery ledger and replacement rules. Output: launch-ready pack. Gate: designated program owner verifies approved settings and documentation. External publication or production changes remain subject to the appropriate execution authority.
Days 46–70 — Run and Reconcile
Operate the approved pilot; sample records for fit, source and permission consistency; reconcile exceptions; prepare only accepted and authorized handoff information. Output: evidence ledger and sample QA findings. Gate: acceptance decisions reproducible; disputed records held.
Days 71–90 — Review and Prioritize
Bring Marketing, Sales and RevOps together to compare campaign evidence with CRM dispositions, identify reason-code patterns and update target, content and delivery rules. Output: retrospective, versioned improvements and the next scoped decision. Gate: leadership can distinguish completed delivery from validated business results.
Readiness Self-Assessment: Eight Domains
Score each domain from 0 to 3, solely using current evidence: 0 missing, 1 proposed, 2 documented and approved, 3 executed and sampled. Total possible: 24. Domains: accountable decision, audience definition, source and permission mapping, persona/content alignment, channel and campaign evidence, acceptance and exception handling, CRM owner/handoff design, measurement and improvement. This is an original internal planning rubric, not a certified benchmark. Do not assign 3 for a planned activity; it requires actual operating proof.
How to Work with Intent Amplify
Take the five completed worksheets into a program-scoping discussion. Intent Amplify can assess an appropriate starting point in Buyer Intelligence, Managed Demand Generation, or Pipeline Activation and identify which acceptance, validation, and handoff fields can be delivered under the agreed scope. The workbook is designed to make the conversation precise: what problem is to be solved, which evidence will be available, which party owns the next decision, and which limits remain visible.
Intent Amplify Capability Fit
Buyer Intelligence supports enterprise target audience design, account-fit rationale, buying roles and validation fields. Managed Demand Generation supports the scoped audience and content/event program, its engagement evidence, acceptance and replacement rules. Pipeline Activation structures the CRM-ready handoff, source and interaction context, approved fields and receiving owner. These responsibilities are bounded by the agreed program, available data and permission controls; they are not standalone evidence of lead qualification, opportunity creation or revenue.
Implementation and Claim Boundaries
These materials are educational operating models proposed for planning. They are not assertions that any named customer uses this workflow or has achieved a financial outcome. An intent score, click, registration, or delivery record is not intrinsically an MQL, SQL, opportunity, pipeline or revenue. Consent, identity, source coverage and CRM acceptance must be verified for each actual implementation.
References
- Intent Amplify, How It Works, https://intentamplify.com/how-it-works
- Intent Amplify, Solutions, https://intentamplify.com/solutions
- Intent Amplify, Managed Demand Generation, https://intentamplify.com/solutions/managed-demand-generation
- Intent Amplify, Pipeline Activation, https://intentamplify.com/solutions/pipeline-activation
- Intent Amplify, Buyer Intelligence, https://intentamplify.com/solutions/buyer-intelligence
