Foundations
Part of Foundations for B2B social selling in England, from a measurable boundary to a controlled hand-off
B2B social selling market entry checklist: per-account gates
B2B social selling market entry checklist: verify each account, procurement route, recipient, data clearance and sender security before messaging.
This B2B social selling market entry checklist is for the last decision before a first social message to a specific English prospect. It checks the named organisation, a relevant procurement route where applicable, the intended recipient, contact-data clearance and the seller's sending account. Treat each as a gate for that account, not as proof that the prospect is ready to buy. Record a pass, hold or stop decision, and do not treat an unresolved check as approval.
Start with the exact account and proposed contact
Open a record for one organisation and one intended recipient, defining the account before the person.
Capture the organisation name as it appears in the record you are checking, the person's name and profile, the channel, and why this person is receiving a message. Keep the source and check date with each decision.
Also retain the proposed message or a concise description of its purpose, who will send it, and who reviewed it. This makes the approval about an actual contact and message, rather than a general permission to approach a broad account list. If the organisation or recipient cannot be identified confidently, pause before drafting outreach.
Apply five account gates before sending
Work through the checks below for the specific account. Record what supports each decision; a blank or uncertain answer means hold, not pass.
1. Match the organisation to its registration
Where the prospect is a registered company, compare its identity in Companies House with the name and organisation represented by the social profile. Check the organisation's own site or another current record if the names do not clearly match. Record enough detail to show which entity you mean, rather than relying on a similar name or logo.
A live registration does not by itself prove that an organisation is trading, has purchasing authority or is suitable for your offer. If the record and the profile point to different entities, or you cannot resolve the mismatch, hold the message until the account identity is clear.
2. Confirm the procurement route, if one is relevant
For a public-sector prospect, check whether the specific procurement context you plan to mention is supported by a notice on Find a Tender. Read the notice and its attachments, and check the organisation, location and deadline. Do not treat the organisation's name alone as evidence that a particular opportunity is open or that a social message is an invited route into it.
Record the notice you checked and what it does, and does not, support. If you refer to a notice in your outreach, make sure the message reflects its details and does not present your contact as a substitute for the published route. The publication's procurement notice checks cover how to assess such signals.
3. Check that the recipient's role fits the message
Verify the person's current role against the organisation's own site or another current record. Then ask whether the responsibility shown is relevant to the specific issue your message raises. A job title or social-platform filter can help you find a possible recipient, but it does not establish that the person controls a budget or welcomes contact.
If the role is missing, appears out of date or does not connect to the subject of the proposed message, hold rather than guess. Record the evidence for the role and any uncertainty; do not turn uncertainty into a claim about the person's authority.
4. Clear the contact data and proposed use
Before sending, check the source of the personal data you intend to use and the purpose for using it in this message. Record which details will be used, the applicable retention and deletion route, and whether the planned contact has been reviewed against ICO guidance. Check that relevant privacy information and any objection are handled before proceeding.
A public profile is not, on its own, a clearance for any use of its information. If the source, planned use or objection status is unclear, do not send until the appropriate review is complete. For the wider data-protection questions, use the publication's data-protection guidance. The UK rules guide covers the rules for private social messages.
5. Check the sending account and access
Confirm that the message will come from the intended personal or company profile and that the person sending it is authorised to use that profile for this contact. Do not send from an account whose ownership or access arrangements are unclear. If the sender's account is not secure, hold the outreach until the issue is resolved.
The NI Cyber Security Centre advises enabling two-factor authentication on social media accounts; its 2FA account advice explains this additional sign-in check. Record whether the control is in place for the account that will actually send the message.
Set a clear pass, hold or stop outcome
Pass only when the organisation is identified, any relevant procurement context is checked, the recipient's role fits, the data review is complete and the sending account is authorised and secure. A pass means this message cleared these checks; it does not show buyer intent or guarantee a response.
Hold when a check is incomplete or depends on someone else's review. State what evidence or decision is missing, who must resolve it and what must change before the message can be reconsidered. Do not let a platform view, connection or profile detail fill a gap in the record.
Stop when the identity is wrong, the proposed message cannot be supported by the evidence, an objection applies, or the sender cannot use the account securely. Record the reason so that another person does not repeat the same attempt without resolving it.
| Outcome | Trigger | What to record |
|---|---|---|
| Pass | Organisation identified, procurement context checked, role fits, data review complete, sending account authorised and secure | Any condition attached to the pass |
| Hold | A check is incomplete or depends on someone else's review | What is missing, who resolves it, what must change |
| Stop | Wrong identity, unsupported message, an applicable objection, or an insecure sender account | The reason, so the attempt is not repeated blindly |
Leave a decision trail for the first message
Keep the result with the account record, as the planning template does: the date checked, sources consulted, the proposed recipient and channel, the message purpose, each gate's outcome, and the person who approved or paused it.
Note any condition attached to a pass, such as limiting the message to the subject actually supported by the evidence. Reopen the checks if the recipient, message or relevant account information changes before sending.
Once the account passes, move the approved contact into the existing CRM hand-off, preserving the account-level decision and its limits. The record should make it possible to tell what was verified for this one contact, and what remains unknown, without mistaking a completed checklist for proof of a sale.
