QA

RevOps

Quality assurance — the systematic process of checking copy, targeting, tracking, and compliance before a campaign goes live.

What is QA?

Quality assurance, or QA, in the context of B2B outbound and marketing operations is the process of reviewing outputs against defined standards before they are used in production. QA covers outreach copy review, data accuracy checks on enrichment before it enters the CRM, sequence testing before launch, and reporting validation before it is shared with clients or leadership.

In outbound specifically, QA prevents errors from reaching prospects. A personalised first line that references incorrect information about a prospect, a sequence with a broken unsubscribe link, or a campaign that emails contacts whose accounts are marked do-not-contact are all QA failures with real commercial consequences. The cost of a QA process is a fraction of the cost of a campaign failure.

QA should be structured and repeatable rather than ad hoc. Define checklists for each output type: what to check, in what order, and who is responsible. A launch checklist for a new email sequence should include: copy review, technical testing of sending setup, list quality verification, unsubscribe mechanism test, and deliverability warm-up confirmation. Without a checklist, reviewers check different things each time and errors slip through inconsistently.

RevOps terms matter because they sit underneath routing, reporting, and accountability. When the operating rule is vague, the visible symptom is usually bad reporting, but the real damage is broken handoffs and wasted response time. It usually becomes more useful when it is defined alongside SOP, Guardrails, and Conversion tracking.

QA — example

An outbound agency introduces a 12-point QA checklist before every campaign launch. Previously, three campaigns in six months had launched with errors: one had broken links, one sent to a suppression list that was not uploaded correctly, and one had a template variable that failed to populate, sending emails that opened with 'Hi {FirstName}'. After implementing the checklist, the agency runs 18 consecutive campaigns with zero critical launch errors.

A scaling B2B team formalizes QA because manual workarounds stopped working once volume increased. They identify the owner, lock down where changes can happen, and remove side spreadsheets that were hiding the true process state. They also make sure it connects cleanly to SOP and Guardrails so the definition is not trapped inside one team.

Frequently asked questions

What should be on a QA checklist for a cold email campaign launch?

At minimum: copy reviewed by a second person, all personalisation variables tested with real data, unsubscribe link functional, suppression list uploaded and active, sending domain health checked, list source and quality verified, and a test send completed to a personal inbox for visual review.

How do I decide what level of QA is appropriate for each type of output?

Match QA intensity to consequence. Customer-facing outreach and public-facing content warrant thorough QA with a second reviewer. Internal reports and drafts for human editing can be reviewed by the creator alone. High-volume automated sequences deserve the most rigorous QA because errors multiply at scale.

Should QA be done by the person who created the output or someone else?

A second-pair-of-eyes review catches more errors than self-review. Creators miss their own errors because they see what they intended to write rather than what they wrote. For critical outputs, always have a different person complete the QA review. For lower-stakes outputs, at minimum complete a structured self-review against a checklist after a time gap.

How do I measure QA effectiveness over time?

Track the number of post-launch errors discovered per output type and per quarter. If errors are decreasing, QA is working. If certain error types recur, add a specific check for that error type to your checklist. A declining error rate over time is evidence that QA is improving.

What happens when QA catches a problem just before a campaign launch?

Delay the launch. The cost of a delay is always lower than the cost of a mistake reaching prospects. Use the delay time to fix the issue, re-run the QA check on the fixed element, and update the checklist if the error type was not previously covered.