B2B Customer Development Vetting and Outreach Workflow

Problem

B2B export sales workflows often start with keywords, company names, and email lists, but the harder part is turning public signals, customer profiles, and outreach drafts into a reusable process without leaking private data, API keys, contracts, or internal lead lists into public artifacts.

How It Works

The skill structures the workflow into concrete steps. First, it helps define a target customer profile, including product category, region, buyer type, high-value buying signals, and exclusion signals. Next, it builds keyword groups such as product, use-case, channel, compliance, and risk. Leads are then evaluated with public evidence: business fit, company authenticity, purchasing capability, contact feasibility, risk signals, and data confidence. The result is routed into A/B/C/D tiers or T1/T2/T3 research depths. Outreach drafts must include a public research signal, a supportable value proposition, a low-friction CTA, sender placeholder, and opt-out language, while avoiding fake urgency, false familiarity, unverifiable claims, and mass-spam tone. Feedback from replies, non-replies, bounces, rejections, and referrals is converted into reusable buyer signals, subject-line tests, exclusion rules, or org-structure clues.

Boundaries

This is best used as a controlled B2B development workflow. It does not bypass CAPTCHAs, paywalls, access controls, or anti-abuse systems, and it does not provide final legal, sanctions, credit, or fraud determinations. Public examples should remain fictional or generic, and private records, secrets, real customer names, and internal data should stay out of repos, templates, and sample files.