Illustrative walkthrough
From client brief to reviewed outreach
This fictional example explains the workflow. Names, companies, and messages are illustrative; they are not customer endorsements, live activity, or measured results.
The client brief
Example client: Cedar Studio, a fictional agency offering website accessibility reviews to US B2B software companies. Its approved audience is founders of small software businesses. The sender must belong to this client’s workspace.
The prospect evidence
Suppose a current public profile confirms that Alex is the founder of a US software company in the target size range. That makes Alex a potential fit. Without a verified post or explicit request, there is no evidence of an active accessibility project or buying intent.
The proposed message
Hi Alex — I work with B2B software teams on website accessibility reviews. Is that something you handle yourself, or does someone else on your team own it?
The draft states the offer and asks a relevant question. It does not invent a pain point, imply prior contact, or promise results. A connection-based message would wait for acceptance.
The review decision
A reviewer checks the evidence, recipient, client, sender, and copy. If the role or location cannot be confirmed, hold the prospect. Approving a campaign authorizes only its configured actions and limits.
The next action depends on what happens
- Invitation pending: hold the first connection-based message.
- Accepted: consider the approved first message within the account’s limits.
- Reply received: stop the no-reply sequence and review the response.
- Opt-out: suppress further outreach.
- Uncertain send result: investigate before another attempt; do not blindly resend.
What this example establishes
This walkthrough explains a review process. It does not establish a reply rate, time saving, booking rate, or guaranteed outcome. Evaluate actual workspace behavior in a product demonstration.