Build a campaign intake, QA, and launch checklist system

Start by mapping how campaigns actually move today from request to post-launch review. In Airtable or a shared working doc, list stages for request, brief, asset production, list setup, landing page, form, UTM creation, approvals, routing, launch, monitoring, and retrospective. Add the common failure points your team already knows, such as missing suppression logic, broken thank-you pages, no sales alert, or unclear owner. QA check: review the map with demand gen, marketing ops, sales ops, and the campaign owner before building the intake form.

Map a campaign operations process for our marketing team.

Campaign types:
{{campaign_types}}

Team roles:
{{team_roles}}

Tools used:
{{tools_used}}

Common launch issues:
{{common_launch_issues}}

Output:
1. Campaign stages
2. Required inputs per stage
3. Owner for each stage
4. Approval points
5. QA checks
6. Reporting checks
7. Common failure points
8. Suggested intake fields

Keep this based on a practical marketing ops workflow, not an idealized enterprise process.

Create an Airtable form or intake table with the fields needed to launch without repeated clarification. Include campaign name, requester, objective, audience, offer, CTA, channels, launch date, budget, landing page need, form need, list or suppression requirements, sales follow-up, CRM campaign, reporting owner, approval owner, and risk notes. Mark truly launch-critical fields as required and leave optional fields for context that should not block submission. QA check: submit one fake campaign request and confirm the record gives marketing ops enough information to decide next steps.

Use Claude to create a reusable QA checklist in Google Sheets or Airtable. Include checks for landing page URL, mobile rendering, form submission, hidden fields, thank-you page, email confirmation, UTM links, CRM campaign association, suppression lists, sales alerts, lifecycle updates, reporting events, accessibility basics, and owner signoff. Add fields for status, owner, evidence link, screenshot or test contact ID, blocker, and resolved date. QA check: no item should be marked complete without evidence, because a checked box without proof is where launch mistakes hide.

Create a campaign launch QA checklist for these campaign types: {{campaign_types}}.

Tools involved:
{{tools_used}}

Known failure points:
{{common_launch_issues}}

Include checks for:
- Landing pages
- Forms
- Thank-you pages
- UTMs
- CRM campaign association
- Lists and suppressions
- Email assets
- Routing and sales alerts
- Analytics events
- Mobile QA
- Approval signoff

For each checklist item, return item name, owner, evidence required, pass/fail criteria, and blocker severity.

Create campaign statuses such as requested, brief approved, assets in progress, QA ready, blocked, approved, scheduled, launched, monitoring, and reviewed. Add owner, due date, next action, blocker reason, risk level, approval status, and launch date fields. Build saved views for campaign owner, marketing ops, blockers, launches this week, and post-launch review. QA check: every campaign record should show who owns the next action and what is blocking launch without needing a Slack thread.

Use Zapier to notify owners when a campaign request is submitted, QA is ready, a blocker is added, an approval is needed, or launch status changes. Keep the first automation simple: Airtable trigger, Slack or email notification, and a link back to the campaign record. Add approval gates for brief approval, asset approval, QA approval, and launch approval so the team knows which decisions are final. QA check: test each notification with a dummy campaign before connecting it to real launch work.

For each campaign, run a launch test using a test contact and a QA URL before public launch. Confirm HubSpot campaign association, form fields, hidden UTM capture, lifecycle or list updates, sales routing, confirmation email, thank-you page, and GA4 event or conversion tracking. Add the test contact ID, test URL, screenshot, and pass/fail notes to the QA checklist. QA check: do not approve launch until form submission, CRM routing, and reporting attribution have all been tested end to end.

After launch, record issues found, launch delays, missed checks, broken links, tracking problems, list errors, sales feedback, and campaign owner feedback. Use Claude to convert those issues into checklist updates, intake-field changes, automation fixes, and training notes. Review the changes monthly so the checklist gets sharper instead of becoming a static template nobody trusts. QA check: every recurring launch mistake should become either a required intake field, a QA item, an automation alert, or a documented exception.

Analyze this campaign launch review and improve our operations system.

Launch issues:
{{launch_issues}}

QA checklist results:
{{qa_results}}

Campaign owner feedback:
{{campaign_owner_feedback}}

Sales or RevOps feedback:
{{sales_revops_feedback}}

Output:
1. Intake fields to add or revise
2. QA checklist items to add or revise
3. Automation alerts to add or revise
4. Approval gates to clarify
5. Training notes for campaign owners
6. Checks to remove because they do not add value
7. Priority changes before the next campaign