Sub-tier DIB suppliers handling FCI only

You are a defense industrial base research analyst helping me qualify a CMMC Level 1 prospect.

Company: {{company}}
Website: {{website}}

Research and produce a one-page brief with:

1. Defense business signals
   - Active or recent DoD prime/sub awards (search USAspending.gov and SAM.gov by recipient name and DUNS/UEI).
   - NAICS codes they self-report and which map to DoD spend categories.
   - Any Capability Statement, GSA Schedule, or SBA set-aside designations (8(a), SDVOSB, HUBZone, WOSB).

2. CMMC Level 1 relevance
   - Likelihood they handle Federal Contract Information (FCI) but NOT Controlled Unclassified Information (CUI) — explain why.
   - If they likely handle CUI, flag them as a Level 2 prospect instead and stop.

3. Trigger events in the last 90 days
   - New contract awards
   - News of prime supplier-portal changes
   - Cyber incidents or breach disclosures
   - Funding, M&A, or new exec hires (especially in IT, ops, contracts)

4. Buying committee
   - Likely owner/president (LinkedIn URL)
   - Office manager / controller / contracts admin
   - IT lead or external MSP (if discoverable)

5. Outreach hook
   - One sentence tying a specific trigger to the Opsfolio CMMC Level 1 self-assessment.

Return as markdown with section headers. Cite every external claim with the source URL.

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.

Build me a list of 25 US small businesses that are strong candidates for CMMC Level 1 self-attestation.

Filters:
- Active DoD prime or sub award in the last 24 months (use USAspending.gov as the source)
- Employee count 10–100
- NAICS: 332710, 332999, 333515, 336411, 336413, 541330, 541512, 541611, 541715, 561210
- Geography: {{state_or_region}}
- NOT currently appearing in the Cyber AB Marketplace (so unlikely to already be engaged)
- NO public mention of holding a current SPRS score above 88

For each company, return:
| Company | UEI | NAICS | Est. employees | Most recent DoD award (date, amount, prime) | Owner/President name | LinkedIn URL | Best opening hook |

Sort by most recent award descending.

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.

Write a 3-touch cold email sequence to {{first_name}} ({{title}}) at {{company}}.

Context:
- {{company}} is a small DoD supplier in {{naics_industry}}.
- Trigger event: {{trigger_event}} (e.g. "won a $1.2M sub from Lockheed last month").
- They are likely Level 1 (FCI only).
- Sender: {{partner_name}}, {{partner_title}} at {{partner_company}}.

Constraints:
- Touch 1: ≤90 words, plain text, one CTA = "worth a 15-minute look?"
- Touch 2 (day 3): ≤60 words, reframe around the prime's expectations.
- Touch 3 (day 7): ≤40 words, break-up note.
- No "I hope this finds you well." No "circling back."
- Reference the trigger event specifically.
- CTA in every touch points to: {{affiliate_link}} for a self-service Level 1 readiness check.

Return as three labeled blocks: SUBJECT + BODY for each.

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.

Draft a LinkedIn outbound cadence to {{first_name}} ({{title}}, {{company}}).

Cadence:
1. Connection note (≤300 chars, no pitch): mention {{trigger_event}} or a mutual context.
2. Day-1 DM after acceptance (≤500 chars): one specific observation about their DoD work + one question about CMMC L1 readiness.
3. Day-5 DM (≤300 chars): share the link {{affiliate_link}} framed as "a 17-control self-check, not a sales call."
4. Day-12 DM (≤200 chars): polite break-up.

Tone: peer-to-peer, founder-friendly, never patronizing. Avoid jargon like "synergy," "leverage," or "circle back."

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.

Generate a 15-minute discovery call script for a CMMC Level 1 prospect: {{company}}, contact {{first_name}} ({{title}}).

Structure:
1. Opening (60 sec) — confirm time, state the one reason for the call (their DoD subcontract exposure), ask permission to ask 5 questions.
2. Five qualifying questions:
   - Which DoD primes are you currently subbing to?
   - Has any prime sent you a CMMC flow-down letter or supplier survey in the last 6 months?
   - Do you have a current SPRS score on file? When was it last updated?
   - Who handles your IT today — internal or an MSP? Have they spoken to you about FCI/CUI handling?
   - If a prime asked tomorrow for your Level 1 affirmation, how long would it take you to produce it?
3. Bridge to demo (60 sec) — based on answers, frame the self-service Level 1 assessment as "a guided 90-minute exercise, not a 3-month consulting engagement."
4. CTA — book a working session OR send the {{affiliate_link}} so they can start themselves.

Include branching logic: if they handle CUI, route to a Level 2 conversation instead.

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.

Act as a senior CMMC consultant. The prospect ({{company}}, {{title}}) just said:

"{{objection}}"

Respond in 2–4 sentences. Rules:
- Acknowledge the concern in their words.
- Cite the relevant authority (FAR 52.204-21, 32 CFR Part 170, DFARS 252.204-7012 / -7021) by section.
- End with a question that moves the conversation forward, not a pitch.
- Never sound defensive. Never say "actually" or "to be fair."

Rules:
- Be concrete and specific to {{company}}; no generic compliance fluff.
- Cite the regulation by section number where relevant.
- If you don't know, say so — do not invent contract numbers, names, or dates.