What "good" looks like here

• All three messages are under the 300-character hard cap (verified: 258 / 257 / 251).
• Each opens with the relevance anchor (industry day attendance) -- not the capability pitch.
• Single ask per message: capability brief intro / cap statement send / brief intro slot. No combining.
• No banned marketing words. No "let's connect to explore opportunities."
• First name salutation (LinkedIn norm), not "Dear Ms. [Last]."
• Three meaningfully different angles: post-event follow-up, certification-led, NAICS-vehicle-curious.

Example 2: DM Follow-Up to a Prime BD Lead After a Conference Panel (300-500 char range)

Template Used: Template 1 -- Prime Contractor BD Lead (executed as dm_followup surface, since the connection has been accepted)

Inputs Used:

• {{recipient_name}}: Marcus
• {{recipient_title}}: VP, Federal Civilian BD
• {{recipient_organization}}: Booz Allen Hamilton
• {{your_name}}: Diane Halvorsen
• {{your_company}}: Larkspur Civic Strategy
• {{your_capability_one_line}}: HHS data engineering for public-health data platforms
• {{relevance_anchor}}: HRSA workforce panel at NDIA Health
• {{surface}}: dm_followup
• {{template_category}}: Prime BD
• {{call_to_action}}: 15-minute introductory call
• {{shared_experience}}: NDIA Health 2026, HRSA workforce panel (Marcus on the panel)
• {{recent_post_reference}}: (blank)
• {{mutual_connection_name}}: (blank)

Output

TEMPLATE 1: Prime Contractor BD Lead (dm_followup surface)
SURFACE: dm_followup
CHARACTER COUNT: 423

MESSAGE:
Hi Marcus -- thanks for connecting. Your contribution on the HRSA workforce panel at NDIA Health stayed with me, particularly the point on rural-health workforce shortages and the limits of current data infrastructure. I lead BD at Larkspur Civic Strategy (HHS data engineering for public-health data platforms). Would value 15 minutes to compare notes on what your civilian-health team is shaping for the next IDIQ window.

VARIANT A (specific-data-point-extension-led):
CHARACTER COUNT: 339

Hi Marcus -- glad we connected after NDIA Health. The HRSA workforce panel landed for me, particularly your framing of data-integration gaps as a workforce-visibility problem. Larkspur Civic Strategy builds the data-engineering side of that picture for HHS programs. Could I get on your calendar for a 15-minute call in the next two weeks?

VARIANT B (mission-impact-led with concrete reference offer):
CHARACTER COUNT: 339

Marcus -- thanks for the connect. NDIA Health's HRSA workforce panel was the strongest session of the day, and your point on integrating CMS and HRSA data is the exact problem Larkspur Civic Strategy works on for federal civilian-health clients. Open to 15 minutes whenever it's useful -- happy to come with one concrete reference example.

WHEN TO USE: First DM follow-up 24-48 hours after a prime BD lead accepts your connection, when you have a substantive shared touchpoint to reference.

What "good" looks like here

• All three messages fall in the 300-500 character DM range (verified: 423 / 339 / 339).
• Each opens by referencing the specific panel and a substantive idea from it -- not "great panel" or generic congratulations.
• Single ask per message: 15-minute call / calendar slot / 15 minutes with a reference example. No multi-asking.
• Variants vary by angle: contribution-recall / data-integration-framing / mission-impact-with-reference-offer. Not word swaps.
• Tone is professional-federal-warmer, appropriate for a post-acceptance DM.
• No banned words. No "let's circle back" or "leverage."

Example 3: Empty Relevance Anchor -- Warning + Generic-But-Honest Fallback

Template Used: Template 3 -- Contracting Officer / Contract Specialist (run with {{relevance_anchor}} left blank)

Inputs Used:

• {{recipient_name}}: Lin
• {{recipient_title}}: Contract Specialist
• {{recipient_organization}}: NAVSEA
• {{your_name}}: Maya Okafor
• {{your_company}}: Sentinel Strand Cyber
• {{your_capability_one_line}}: CMMC L2 cybersecurity for DoD program offices
• {{relevance_anchor}}: (blank)
• {{surface}}: connection_request_300
• {{template_category}}: Contracting Officer / Contract Specialist
• {{call_to_action}}: (blank -- defaults to capability brief intro)
• {{shared_experience}}: (blank)
• {{recent_post_reference}}: (blank)
• {{mutual_connection_name}}: (blank)

Output

TEMPLATE 3: Contracting Officer / Contract Specialist
SURFACE: connection_request_300

WARNING: {{relevance_anchor}} is empty. Without a specific relevance anchor (mutual connection, shared event, recent post, prior contract), the message opens cold. LinkedIn BD data suggests cold-open connection requests to federal recipients see roughly half the acceptance rate of relevance-anchored ones. Strongly recommended: populate {{relevance_anchor}} before sending. Below is a generic-but-honest fallback that does not fabricate a relationship.

COMPLIANCE NOTE: Recipient is a Contract Specialist. This message is scoped to neutral capability awareness only -- no active solicitation reference, no source-selection probing. The CTA is a soft cap statement share, not a meeting request about specific procurements.

CHARACTER COUNT: 232

MESSAGE:
Hi Lin -- reaching out cold. I run BD at Sentinel Strand Cyber (CMMC L2 cybersecurity for DoD program offices) and have been tracking your office's small-business work. Would value a brief capability intro when your calendar allows.

VARIANT A (certification-led, still cold-anchored):
CHARACTER COUNT: 227

Lin -- reaching out cold. Sentinel Strand Cyber is an SDVOSB doing CMMC L2 work for DoD program offices, and I'd like to introduce the firm to your office. Open to sending our capability statement and finding a time that works.

VARIANT B (acknowledge-the-cold-reach, low-pressure parking ask):
CHARACTER COUNT: 233

Hi Lin -- cold reach, I'll be brief. Sentinel Strand Cyber delivers CMMC L2 cybersecurity to DoD program offices. If your office is taking introductory capability briefs from SDVOSBs in our NAICS, I'd value a slot when timing allows.

WHEN TO USE: Only as a last resort when no relevance anchor exists. Populate {{relevance_anchor}} -- attend the next NAVSEA industry day, engage on a recent NAVSEA OSDBU post, or get a mutual introduction first -- and rerun the template for a stronger result.

NEXT STEP: Consider attending the next NAVSEA Industry Day or NAVSEA OSDBU event before sending. Repopulating {{relevance_anchor}} with a real shared touchpoint typically doubles connection acceptance rates.

What "good" looks like here

• The prompt did NOT silently fabricate a relevance anchor. It produced a warning AND a fallback that openly acknowledges the cold reach.
• The CO/CS compliance guardrail engaged automatically (Template 3): the CTA defaulted to a soft cap statement share, NOT a procurement-specific meeting request.
• All three fallback messages are under 300 characters (232 / 227 / 233).
• The user gets a usable message AND clear coaching to strengthen the next attempt -- which is more valuable than a polished-but-fake "we share so much in common" cold open.
• This is the load-bearing test of the pack's anti-fabrication posture: a cheaper / lower-quality tool would have invented a mutual or claimed a shared event. This pack does not.