Turn one content offer into a multi-channel demand gen engine

Capture: Collect the final content offer, target audience, primary business objective, approved CTA, destination URL, launch window, budget, regions, languages, and channel owners in one intake record.

QA: Confirm that the offer itself is approved and that any cited research, customer examples, statistics, or partner logos can be promoted publicly. Add explicit exclusions for audiences, claims, industries, geographies, and data uses that the campaign must avoid.

Scope: Name one campaign owner with final decision authority and one approver for brand, legal, or product claims.

Approval: Do not start asset production while the destination, CTA, or approval path is unresolved. Mark the intake approved only when every required owner has acknowledged the constraints.

Set up: Open Claude and create a new project or chat for this offer.

Action: Paste the approved prompt, attach the complete offer or approved transcript, and include the intake record, audience definition, CTA, and claims policy. Require Claude to return a structured source brief with evidence references, not campaign copy.

Next action: Save the output in the campaign workspace and assign it a version number that every later asset will reference. Have the content owner verify every proof point against the source material and remove anything that depends on outside model knowledge.

Approval: Do not advance until the source brief is approved as the single source of truth.

Set up: Create a Google Sheets claim ledger with claim_id, source_brief_version, proposed claim, claim type, source page or timestamp, approved wording, proof owner, permitted channels, expiry date, risk level, and approval status.

Action: Include visual proof such as charts, screenshots, customer logos, analyst quotes, or benchmark tables only when usage rights are clear. Mark statistics, comparative claims, customer results, legal statements, and forward-looking claims for specialist review.

Next action: Separate “the offer says” from “the company can claim publicly,” because those are not always identical. Link every future copy asset to claim IDs rather than copying unsupported language from drafts.

Approval: Block production for any hero claim that lacks an approved proof path.

Set up: Create a segment table for each audience the campaign will address, including segment_id, role, company profile, current pain, buying stage, awareness level, objection, relevant proof, preferred CTA, exclusion criteria, and sales owner.

Action: Use HubSpot properties that already exist wherever possible so the campaign can actually route and report by segment. Map each segment to eligible lists, suppression lists, regions, consent requirements, and lifecycle-stage rules.

Scope: Decide whether the offer should generate new demand, accelerate known leads, support active opportunities, or reactivate dormant contacts.

QA: Have RevOps validate that every planned segment can be identified reliably in HubSpot before copy is generated. Remove segments that cannot be targeted, measured, or served with a meaningfully different message.

Scope: Choose one primary campaign objective and define the conversion event that represents success.

Capture: Record baseline volume, target range, budget, expected audience size, reporting window, attribution model, sales follow-up SLA, and guardrail metrics such as unsubscribe rate, form completion rate, cost per qualified response, or lead rejection rate. Define the exact HubSpot campaign, form, list, lifecycle, and opportunity fields that will be used for measurement.

Action: Separate leading indicators such as CTR from business outcomes such as qualified meetings or influenced pipeline. Assign an owner for every metric and a deadline for data availability.

Output: Publish this as the measurement contract and require campaign-owner approval before channel planning.

Set up: Create one row per segment and channel in Google Sheets with campaign angle, reader context, problem framing, proof IDs, offer section, CTA, destination, tone, asset format, owner, and approval status.

Action: Use Claude to suggest channel adaptations only after the source brief, claim ledger, segments, and measurement contract are approved. Assign the sharpest pattern-interrupt angle to paid media, more context-rich angles to email, utility-led framing to organic, and account relevance to SDR outreach. Keep the primary CTA consistent unless the measurement contract explicitly defines a micro-conversion.

QA: Review the map for duplicated messages, unsupported claims, and channels that do not match how the audience consumes content.

Approval: Lock the approved map as the production brief for all asset owners.

Build: Turn the approved message map into a production matrix with asset_id, segment_id, channel, format, dimensions or length, source brief version, required claim IDs, owner, reviewer, due date, dependency, destination, UTM content value, and status. Include landing-page modules, forms, thank-you assets, email messages, ad variants, organic posts, SDR copy, visuals, and internal launch materials.

Action: Sequence dependencies so landing-page and routing decisions are complete before final emails and ads are approved.

Set up: Add status values for briefed, drafting, in review, changes requested, approved, built, QA passed, scheduled, live, and retired.

QA: Set a scope limit that the team can produce and review without weakening quality. Review the critical path with all owners in Slack and resolve blockers before writing begins.

Set up: Open Claude and provide the source brief, message map, approved claim IDs, segment priorities, and measurement contract.

Build: Generate a modular landing-page brief and copy blocks for hero, problem, insight summary, proof, offer preview, what the reader will learn, form value exchange, CTA, and post-conversion expectation. Require notes showing which segment and claim IDs each block serves.

Action: Save the copy in the production matrix and route it to content, product, and legal reviewers as required. Remove sections that merely repeat the asset title without increasing perceived value or reducing conversion anxiety.

Approval: Approve the narrative before building the HubSpot page.

Set up: Create or clone the approved HubSpot landing-page template and insert only approved copy and assets.

Configuration: Configure the form fields, progressive profiling, consent language, hidden campaign fields, lifecycle behavior, owner routing, list membership, thank-you behavior, and asset delivery method. Map every form field to the correct HubSpot property and document required versus optional fields in the tracker.

Build: Build the follow-up workflow for delivery, internal notification, lead scoring, segmentation, and sales handoff according to the lifecycle-routing map. Test known-contact and new-contact behavior, business and personal email addresses, duplicate submissions, suppression logic, and mobile rendering.

QA: Do not mark the asset built until the test records appear in the correct lists and workflows.

Set up: Open Claude and generate email copy from the approved source brief, message map, segment rules, and claim ledger.

Configuration: Create the invitation or nurture sequence, confirmation or delivery email, reminder if relevant, and a sales-assist follow-up for qualified contacts. Require subject line, preview text, body, CTA, segment, send timing, suppression rule, and supporting claim IDs for every message.

Action: Save approved copy in HubSpot and configure enrollment, delays, goals, exit criteria, frequency caps, and timezone behavior. Send tests to desktop and mobile clients, validate personalization fallbacks, and click every tracked link.

Approval: Route final approval to the email owner before scheduling.

Set up: Open Claude and use the approved paid-media rows from the message map to draft a controlled testing matrix.

Configuration: Create distinct tests for angle, proof type, format, or audience, but change only one major variable within each comparison where possible. Include ad_id, segment, objective, hook, intro text, headline, CTA, supporting claim IDs, creative concept, destination, UTM content value, and hypothesis. Keep copy within the current platform field limits used by your account and let the paid-media owner trim final text in the platform.

Guardrails: Exclude claims that cannot be understood without the offer’s full context.

Approval: Approve the matrix before creative production or campaign setup.

Action: Use Claude to create separate copy packages for organic LinkedIn, SDR outreach, newsletter placement, website modules, partner promotion, and the internal Slack launch. Provide the relevant message-map row and audience context for each package rather than asking for one generic repurposing batch.

Next action: Require asset IDs, approved claim IDs, destination, CTA, personalization fields, and usage notes in every output.

Action: SDR copy should explain when a rep should use the asset and when not to use it, while partner copy should identify any co-branding or approval dependency.

Output: Save each package in the production matrix and assign a human owner to personalize and approve it. Reject copy that sounds identical across channels or implies one-to-one research that did not occur.

Set up: Create a Canva campaign folder with the approved source brief version, brand kit, approved logos, image rights, and production matrix. Build a reusable visual system covering typography, color, chart style, cover treatment, CTA treatment, and required disclaimers.

Action: Produce only the approved formats, such as report cover, stat card, quote card, carousel, LinkedIn single image, document ad preview, website module, and email banner. Link every visual to its asset ID and claim IDs, and keep editable source files rather than exporting isolated images only.

QA: Review legibility at actual placement size, mobile crops, contrast, logo clear space, and disclaimer visibility.

Approval: Mark each export with version, dimensions, owner, and approval status in Google Sheets.

Build: Build a Google Sheets tracking table with asset_id, channel, source, medium, campaign, content, term where needed, segment_id, destination URL, shortened URL if used, owner, and QA status. Define one naming convention for the HubSpot campaign, LinkedIn campaign group, campaign, ad set or audience, ads, emails, workflows, lists, and Canva exports.

Execution: Generate final URLs from the approved fields rather than hand-typing UTMs inside each platform.

QA: Check for duplicate content values, inconsistent capitalization, spaces, accidental PII, and destinations that redirect away from the intended page. Paste the final tracked URL back into every production-matrix row.

Approval: Lock the naming sheet after approval and route changes through the campaign owner.

Set up: Create the HubSpot campaign using the approved naming convention and associate the landing page, form, emails, workflows, lists, CTAs, and tracked URLs.

Configuration: Configure campaign start and end dates, owner, budget where used, audience, notes, and primary goal.

QA: Verify that hidden fields, original source data, campaign membership, lifecycle updates, and owner assignments behave as documented. Build saved views or reports for submissions, qualified contacts, lifecycle progression, influenced records, source and medium, and sales disposition.

Review: Document the attribution model and any metrics that remain directional. Reconcile test submissions from Step 9 before giving the campaign a launch-ready status.

Build: Build the LinkedIn Ads campaign structure from the approved testing matrix and naming sheet. Configure objective, geography, language, company or role targeting, exclusions, matched audiences, retargeting windows, budget, schedule, bid strategy, conversion tracking, and frequency controls according to the measurement contract.

Capture: Upload only approved creative and copy, then paste the canonical tracked destination for each ad.

QA: Check estimated audience size and overlap so separate tests are not unknowingly competing for the same people. Use draft or paused status while a second person reviews targeting, budget, URLs, creative, and conversion events.

Output: Record platform IDs and launch status back in Google Sheets.

Action: Use one QA checklist in Google Sheets covering copy approval, claim IDs, visual approval, links, UTMs, forms, consent, workflows, lists, routing, suppression, mobile rendering, accessibility, targeting, budgets, conversion events, delivery assets, and rollback owners.

Scope: Assign each check to a named reviewer and require evidence such as a screenshot, test record, or preview link. Run end-to-end tests from ad or email click through form completion, asset delivery, HubSpot record creation, list membership, notification, scoring, and sales routing. Resolve all critical and high-severity issues before launch and document any accepted low-risk exceptions.

Action: Obtain final sign-off from the campaign owner, channel owners, and required claim reviewers.

Approval: Keep every campaign and ad paused until the approval gate is complete.

Scope: Post the launch plan in Slack with launch time, owners, dashboards, asset links, audience, budget, escalation contacts, and rollback criteria. Launch channels in the agreed sequence so the team can isolate technical issues rather than activating everything blindly.

Action: During the first 72 hours, monitor spend, delivery, rejected ads, broken links, form completion, workflow enrollment, email bounces, unsubscribe spikes, duplicate contacts, routing failures, and sales alerts. Log issues in the tracker with severity, owner, resolution, and time detected.

Next action: Fix technical failures immediately, but avoid broad creative conclusions before enough data accumulates.

Details: Send a concise launch-health update after the first day and again after 72 hours.

Scope: At the agreed review window, compare channel results with the measurement contract rather than selecting whichever metric looks strongest.

QA: Review reach, spend, CTR, landing-page conversion, email engagement, form completion, qualified-contact rate, sales acceptance, opportunity movement, pipeline signals, and guardrails by segment and asset ID. Ask sales to disposition leads using defined reasons and compare message angles with lead quality, not only volume.

Capture: Record findings as facts, hypotheses, data gaps, and decisions in Google Sheets. Decide which assets to scale, revise, pause, repurpose, or retire, and assign owners plus deadlines.

Approval: Feed approved learnings back into the source brief, message map, templates, and future content-offer activation backlog.