· revenue engine
A SaaS outbound campaign is ready when the team can explain why each account belongs, what the product can support and who owns every decision after a reply.
The go-or-hold sheet puts the release evidence in one view. Use the actual campaign version that would launch.
Go-or-hold evidence sheet
| Evidence gate | Required record | Owner | Go, hold or exclude | Review note |
|---|---|---|---|---|
| Use case | Approved customer job and product capability | |||
| ICP | Must-have conditions and exclusions | |||
| Account evidence | Current source and fact-to-fit reasoning | |||
| Technical fit | Supported environment and known constraints | |||
| Buyer group | Workflow, technical and commercial responsibilities | |||
| Claims | Approved proof for every product or outcome claim | |||
| Qualification | States, questions and stop conditions | |||
| Reply operation | Owner, timing and CRM record | |||
| Data controls | Purpose, fields, source, retention and suppression |
A campaign stays on hold while a mandatory record is missing. The hold needs an owner and an exact review action.
Confirm one use case
Name the job the software changes, the current process, the required capability and the environment the product cannot support. Keep the campaign narrower than the whole product.
Give product or implementation specialists the technical-fit row. Sales language should follow the approved capability record. A plausible integration is still unconfirmed until product evidence supports it.
Check account evidence and exclusions
Every account needs a current observation, the source, a fit interpretation and an exclusion check. The record should also say what remains unknown.
Typical exclusions might concern workflow absence, unsupported geography, required integrations, implementation capacity or an existing suppression. The exact list comes from the product and commercial plan.
Map the buyer group
Define responsibility before contact names:
- workflow owner;
- business sponsor;
- product user;
- IT or security reviewer;
- procurement or finance route.
Some accounts combine the roles. The campaign brief should show the confirmed responsibility and any role still assumed.
Minimise campaign data
ICO data-minimisation guidance says personal data should be adequate, relevant and limited to what is necessary for the stated purpose. Apply that test to every contact field and research note. Record why a field is needed and remove fields collected only because a provider makes them available.
ICO B2B guidance also says personal-data duties can apply to business contacts and rules vary by channel and subscriber type. The current guidance is under review. Recheck the live position before release.
Fictional example
A fictional example concerns software that routes service exceptions for review. The campaign has an approved use case and clear account conditions. Research found current evidence for the target workflow. The product team has not confirmed an integration mentioned in the draft.
The account evidence passes. The claims gate stays on hold. The team can remove the integration claim or wait for product approval. The unsupported statement keeps the campaign on hold until removal or approval.
Run the cold-read test
Give the evidence record and draft to someone outside the build. The reviewer should be able to identify:
- the subject of every sentence;
- the source behind every account claim;
- the product evidence behind every capability claim;
- the route for a reply;
- the condition that should stop contact.
The reviewer records findings. The campaign owner resolves them and supplies a new version for approval.
Control the release version
Give the campaign a version identifier that connects the account rules, source records, approved claims, message, suppression file and reply process. Approval applies to that version. A change to product claims, exclusions, channel or audience creates a new review item.
Record who can release, pause and amend the campaign. The campaign owner should be able to show which version ran, which accounts were included and which approval covered the work. This prevents a correct review record being attached to different production content.
Define the first learning decision
Write the decision the initial cohort will inform. The decision might concern account fit, buyer responsibility or use-case language. Choose the evidence the team will review and the point at which it will pause, continue or revise. Activity volume is not the learning decision.
Release check:
- [ ] The use case and exclusions are explicit.
- [ ] Technical constraints have a product owner.
- [ ] Every account claim has a current source.
- [ ] Buying responsibilities come before contact names.
- [ ] Personal data is necessary for the stated purpose.
- [ ] Suppression and objection controls are ready.
- [ ] Qualification and reply ownership are written down.
- [ ] Final approval applies to the actual release version.
The software sales lead generation guide owns the broad strategy. To compare this release sheet with Hyper’s software approach, visit the software growth page.
Sources and further reading
- Business-to-business marketing · Information Commissioner’s Office
- Principle (c): Data minimisation · Information Commissioner’s Office