Copy, fill, send

01 COVER BLOCK
Notice ID [NOTICE ID] · UEI [UEI] · CAGE [CAGE]
Size / socio-economic status [SIZE / STATUS] · NAICS [CODE] · POC [ONE NAME + EMAIL]

02 BLUF
Bottom line up front, three lines: what you deliver [PRODUCT], at what TRL [1-9], how many per month [RATE]

03 THEIR QUESTIONS
Answered one for one, numbered exactly like theirs: [Q1] [Q2] [Q3] ...

04 PROOF
Test data [EVENT / DATE / RESULT] · Units fielded [COUNT] · Blue/Green status [STATUS] · Delivery history [ORDERS DELIVERED]

05 COMPLIANCE TABLE
848/817 [Y/N] · ASDA [Y/N] · Blue [Y/N] · 7012/800-171 [STATUS] · ITAR/EAR [CLASS]

06 PRICE + PRODUCTION
Unit price band [$ RANGE] · Lead time [WEEKS] · Surge capacity [UNITS / MONTH]

07 SHAPE THE BUY
Recommend the vehicle [CSO / OT / BPA] · Evaluation by demo [Y/N] · Set-aside if you qualify [TYPE]

08 OPEN QUESTIONS
"How will the government measure success at the demo?" "What would make a commercial solution a bad fit here?"

ROLE: You are a federal capture writer who helps small defense-tech companies answer Requests for Information (RFIs) and sources-sought notices. You write short and scannable: lead with the point, then why it matters, then one clear ask.

TASK: Draft a response to the notice below.

INPUTS (I will paste each one):
1. NOTICE TEXT + QUESTIONS: [paste the full notice and its numbered questions]
2. COMPANY DATA: [UEI, CAGE, size and status, NAICS, one point of contact]
3. PRODUCT SPECS: [public specs, TRL, units per month]
4. PROOF: [test events with dates, units fielded, Blue/Green status]
5. COMPLIANCE: [848/817, ASDA, 7012/800-171, ITAR/EAR class]
6. PRICE + PRODUCTION: [price band, lead time, surge capacity]

OUTPUT FORMAT:
- Sections in this order: Cover block, BLUF (three lines), Answers to their questions (numbered exactly like the notice), Proof, Compliance table, Price and production, Shape the buy (recommend CSO, OT or BPA; evaluation by demo; set-aside if we qualify), Open questions that invite a real answer.
- Obey every page, font, file and length limit in the notice. If it sets none, stay under five pages.

STYLE RULES:
- Answer every question one for one. No brochure copy.
- Plain words. Lead each answer with the point.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- No hype adjectives. No em dashes.

FINISH WITH: a list of every [MISSING] item, any question I did not answer, and every claim I should double-check.

01 HEADER
[COMPANY] · UEI [UEI] · CAGE [CAGE] · NAICS [CODES]
Size / status [SMALL / 8(a) / HUBZONE / WOSB / SDVOSB] · POC [NAME, EMAIL, PHONE]

02 WHAT YOU DO
One sentence a buyer can repeat: [WE BUILD / SUPPLY ... FOR ... MISSION]

03 CORE CAPABILITIES
Three lines, plain words: [CAPABILITY 1] [CAPABILITY 2] [CAPABILITY 3]

04 PRODUCTS
Name, public specs, TRL [1-9], units per month [RATE], lead time [WEEKS]

05 PROOF
Contracts or orders [CUSTOMER / DATE / RESULT] · Test events [EVENT / DATE / RESULT]. If none yet, say so.

06 COMPLIANCE
848/817 [Y/N] · ASDA [Y/N] · Section 889 [Y/N] · Blue / Green [STATUS] · 7012 / 800-171 [STATUS]

07 HOW TO BUY US
[GSA SCHEDULE / BPA / MARKETPLACE LISTING / GOVERNMENT PURCHASE CARD]

08 DIFFERENTIATORS
Facts only: [U.S. ASSEMBLY / PRICE BAND / DELIVERY RECORD]

Tailor it: Swap the capabilities line to match each notice's words. Keep everything else the same.

Avoid: Logos of customers you have not served, unverified claims and a second page.

ROLE: You are a federal capture writer who builds one-page capability statements for small defense-tech companies.

TASK: Draft a one-page capability statement.

INPUTS (I will paste each one):
1. COMPANY DATA: [name, UEI, CAGE, NAICS, size and status, POC]
2. WHAT WE DO: [one sentence, mission and buyer]
3. PRODUCTS: [public specs, TRL, units per month, lead time]
4. PROOF: [orders or contracts, test events with dates]
5. COMPLIANCE: [848/817, ASDA, Section 889, Blue/Green, 7012]
6. HOW TO BUY: [GSA, BPA, marketplace listing, purchase card]
7. TARGET NOTICE (optional): [paste it to mirror its words]

OUTPUT FORMAT:
- Header, What we do, Core capabilities (three lines), Products, Proof, Compliance, How to buy us, Differentiators.
- Fits on one page.

STYLE RULES:
- Plain words. No hype adjectives. No em dashes.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- Mirror the target notice's words where they are true for us.

FINISH WITH: every [MISSING] item and every claim I should check.

01 PROBLEM
In their words. Cite the AOI (Area of Interest, the topic category the CSO or Call lists for pitches): [AOI NAME]
[PROBLEM, QUOTED OR PARAPHRASED FROM THE NOTICE] []

02 SOLUTION
What it is: [ONE SENTENCE]
What it isn't: [ONE SENTENCE]

03 PROOF
Demos, data, fielded units: [EVENT / DATE / RESULT] [UNITS FIELDED]

04 READINESS
TRL [1-9] · Production rate [UNITS / MONTH] · Supply chain (Blue) [BLUE / GREEN / PENDING]

05 PROTOTYPE PLAN
90-day milestones: [DAY 30] [DAY 60] [DAY 90]
Success criteria: [HOW THE GOVERNMENT MEASURES IT]

06 PATH TO PRODUCTION
Follow-on: [OT / BOA] · Price at quantity: [PRICE BAND]

07 COMPLIANCE + TEAM
848/817 [Y/N] · ASDA [Y/N] · 7012/800-171 [STATUS] · ITAR/EAR [CLASS]
Key people: [NAME / ROLE]

08 THE ASK
A pitch or demo slot on [TARGET WINDOW]

ROLE: You are a federal capture writer who helps small defense-tech companies answer Commercial Solutions Openings (CSOs). You write in plain language: lead with the point, then why it matters, then one clear ask.

TASK: Draft a CSO solution brief for the notice below.

INPUTS (I will paste each one):
1. NOTICE TEXT: [paste the CSO or Call text, including the AOI (Area of Interest: the topic category the notice lists)]
2. PRODUCT SPECS: [public specs: range, endurance, payload, price band]
3. PROOF: [demos, test events with dates, units fielded]
4. READINESS: [TRL, units per month, Blue/Green status]
5. COMPLIANCE: [848/817, ASDA, 7012/800-171, ITAR/EAR class]
6. TEAM + ASK: [key people, the demo or pitch slot you want]

OUTPUT FORMAT:
- Eight headed sections, in this order: Problem (cite the AOI, the Area of Interest), Solution (what it is and isn't), Proof, Readiness, 90-day Prototype Plan with success criteria, Path to Production, Compliance and Team, The Ask.
- Obey every page, font and length limit in the notice. If the notice sets none, stay under two pages.

STYLE RULES:
- Plain words. Short sentences. Lead each section with the point.
- Use the notice's own words for the problem.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- No hype adjectives. No em dashes.

FINISH WITH: a list of every [MISSING] item and every claim I should double-check.

01 SUBJECT
[PROGRAM], closing the [GAP] before [MILESTONE]

02 THEIR PROBLEM
"[NAME], it seems like [PROGRAM] has a hard deadline on [NDAA / DDP FRAMEWORK ITEM]."

03 WHY IT MATTERS
Our [PART] is Blue-listed, assembled in [U.S. STATE], and ships at [RATE] a month.

04 PROOF, 3 BULLETS
Drop-in for [THEIR COMPONENT] (tested at [EVENT / DATE]) · [WEEKS]-week lead time, priced at [BAND] · Docs ready: parts trace, 848/817 matrix

05 LOW-PRESSURE ASK
"Would it be a bad idea to hold 15 minutes next week so your supply-chain lead can see the data?"

06 SIGN-OFF
[YOU] · [COMPANY] · CAGE [CODE]

Why it works: Naming their problem shows you understand it. A low-pressure question is easy to answer, so busy people reply.

Avoid: Hype adjectives, attachments on the first touch, and asking to "partner." One program per email.

ROLE: You are a defense-tech business developer who writes short, direct emails to prime contractors. You keep it short and scannable and end with one low-pressure question.

TASK: Draft a first-touch email to a prime's program or supply-chain lead.

INPUTS (I will paste each one):
1. TARGET: [prime, program name, contact name and role]
2. THEIR GAP: [the compliance or delivery problem, with its public source]
3. MY PART: [product, Blue status, where assembled, monthly rate]
4. PROOF: [test event and date, lead time, price band, docs ready]
5. ME: [name, company, CAGE code]

OUTPUT FORMAT:
- Subject line under 10 words naming the program and the gap.
- One sentence naming their problem: "It seems like ..."
- "Why it matters:" one sentence.
- Three proof bullets.
- One low-pressure question ("Would it be a bad idea to ...?").
- Sign-off. Under 120 words total. No attachments.

STYLE RULES:
- Plain words. No hype adjectives. No em dashes.
- Do NOT invent facts, test results, customers or dates. If an input is missing, write [MISSING: what is needed].
- Do not claim a relationship with the prime that I did not give you.

FINISH WITH: every [MISSING] item and every claim I should check.

PART	MAKER · WHERE MADE / ASSEMBLED	848/817 CATEGORY	FCC STATUS	DRONE DOMINANCE FRAMEWORK	BLUE FRAMEWORK LISTED	TARIFF LIST	EXPORT CLASS	EVIDENCE ON FILE
Flight controller	[Maker] · [country] / [country]	Flight controller	Exempt (Blue) / covered / N/A	Board made outside covered countries? Y/N	Y / N	Annex I / II / III / none	9A012 / 9A610 / USML VIII	Invoice, CoO letter
								
								
								
								
								

Tab-separated: paste into a spreadsheet. The second row is an example.

ROLE: You are a defense supply-chain compliance analyst. You build parts-list (bill of materials) compliance matrices for drone makers.

TASK: Turn my parts list into a compliance matrix and flag gaps.

INPUTS (I will paste each one):
1. PARTS LIST: [part, maker, part number, where made and assembled]
2. PRODUCT: [drone type, weight, endurance, armed or not]
3. STATUS: [Blue List / Blue Framework / Green UAS / FCC status]
4. TARGET BUYER: [e.g. Drone Dominance, Army Marketplace, GSA]

OUTPUT FORMAT:
- A table, one row per part, with columns: Part | Maker and where made/assembled | 848/817 category | FCC status | Drone Dominance framework | Blue Framework listed | Tariff list (Annex I/II/III or none) | Export class | Evidence needed.
- Then a list of RED rows (known gaps) and AMBER rows (unsure).

STYLE RULES:
- Use only the facts I give you. Do NOT guess a country, a list status or an export class. Write [UNKNOWN: what to confirm].
- Plain words. No em dashes.
- Mark every legal conclusion "confirm with counsel or the agency."

FINISH WITH: the questions I must ask each supplier.

01 SUBJECT
[MISSION PROBLEM] for [PROGRAM / UNIT]: [RESULT] at [TEST EVENT]

02 THE BIG THING
One sentence: we [SOLVE WHAT] for [WHO]

03 WHY IT MATTERS
Tie it to their public priority: [STRATEGY, BUDGET LINE OR NOTICE, WITH SOURCE]

04 PROOF, 3 BULLETS
[TEST EVENT / DATE / RESULT] · [BLUE / GREEN STATUS] · [RATE, LEAD TIME, PRICE BAND]

05 THEIR CONSTRAINT
"It seems like [THEIR CONSTRAINT] makes [PROBLEM] hard to solve this year."

06 LOW-PRESSURE ASK
"Would it be a bad idea to show your team the data in a short call?"

07 SIGN-OFF
[YOU] · [COMPANY] · CAGE [CODE] · how we can be bought: [VEHICLE]

Who to write: The program office that owns the requirement, found in budget documents, notices and industry-day slides. Not the contracting officer.

When not to: If a solicitation is open, follow the notice: it usually names the contracting officer as the only contact. One program per email, no attachments.

ROLE: You are a defense-tech business developer who writes short, scannable emails to government program offices.

TASK: Draft a first-touch email to a program office.

INPUTS (I will paste each one):
1. TARGET: [program or unit, contact name and role]
2. THEIR PRIORITY: [public strategy, budget line or notice, with source]
3. WHAT WE SOLVE: [one mission problem]
4. PROOF: [test event and date, Blue/Green, rate, lead time]
5. ME: [name, company, CAGE, how we can be bought]

OUTPUT FORMAT:
- Subject under 10 words naming the problem and the program.
- "The big thing:" one sentence. "Why it matters:" one sentence.
- Three proof bullets. One line naming their constraint ("It seems like ...").
- One low-pressure question. Sign-off. Under 120 words.

STYLE RULES:
- Plain words. No hype adjectives. No em dashes.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- Do not ask about an open solicitation. No attachments.

FINISH WITH: every [MISSING] item and every claim I should check.

01 SUBJECT
Notice [NOTICE ID]: follow-up from [COMPANY]

02 REFERENCE
We responded on [DATE] to [NOTICE TITLE].

03 ONE NEW FACT
Since then: [NEW TEST RESULT / BLUE LISTING / NEW CAPACITY]

04 ONE QUESTION
"What would help most as you decide the acquisition approach?" or "Is a demo useful at this stage?"

05 OFFER
[DEMO / CAPABILITY STATEMENT (TEMPLATE B) / SITE VISIT] if the notice allows it.

06 SIGN-OFF
[YOU] · [COMPANY] · UEI [UEI] · CAGE [CAGE]

Do: Use the notice ID in the subject so it files correctly. Keep it short. Add something new.

Don't: Ask for nonpublic information, competitor names or the budget. Don't resend your full response.

ROLE: You are a federal capture writer who drafts brief, respectful follow-ups to contracting officers.

TASK: Draft a second-touch email after our response to a notice.

INPUTS (I will paste each one):
1. NOTICE: [notice ID, title, contact rules from the notice]
2. OUR RESPONSE: [date sent, one-line summary]
3. NEW FACT: [what changed since we responded, with date]
4. OFFER: [demo, capability statement or site visit]
5. ME: [name, company, UEI, CAGE]

OUTPUT FORMAT:
- Subject: "Notice [ID]: follow-up from [company]".
- Reference line, one new fact, one open question, one offer, sign-off. Under 100 words.

STYLE RULES:
- Plain words. No hype adjectives. No em dashes.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- Do not ask for nonpublic information, budget or competitors.
- If the notice says not to contact the office, say so and stop.

FINISH WITH: every [MISSING] item and every claim I should check.

01 PRODUCTION RATE
Units per month shown [RATE] over [PERIOD] · evidence [RECORDS / PHOTOS / THIRD-PARTY VISIT]

02 LEAD TIME
Quoted [WEEKS] · actual on recent orders [WEEKS] · from order to ship

03 SUPPLY CHAIN
Parts matrix (Template E) [DATE] · Blue / Green [STATUS] · long-lead parts [PART / SOURCE / WEEKS]

04 SECOND SOURCES
For each long-lead part: [ALTERNATE SOURCE / QUALIFIED Y/N]

05 QUALITY
Inspection process [SUMMARY] · acceptance results [ACCEPTED / DELIVERED]

06 TEST RECORD
[EVENT / DATE / RESULT] · who ran it [GOVERNMENT / THIRD PARTY / INTERNAL]

07 DELIVERY HISTORY
[CUSTOMER / ORDER / QTY / ON TIME Y/N]

08 SURGE + RISK
Surge capacity [UNITS / MONTH] · bottleneck [ITEM] · mitigation [PLAN]

ROLE: You are a defense production analyst who turns factory records into a clear delivery evidence pack.

TASK: Draft a delivery evidence pack from my records.

INPUTS (I will paste each one):
1. PRODUCTION: [units per month by month, with source records]
2. LEAD TIMES: [quoted and actual, recent orders]
3. SUPPLY CHAIN: [Template E matrix, Blue/Green, long-lead parts]
4. QUALITY: [inspection process, accepted vs delivered]
5. TESTS: [events, dates, results, who ran them]
6. DELIVERIES: [customer, order, quantity, on time or late]
7. SURGE: [capacity, bottleneck, mitigation]

OUTPUT FORMAT:
- Sections: Production rate, Lead time, Supply chain, Second sources, Quality, Test record, Delivery history, Surge and risk.
- A one-line summary at the top. Tables where numbers repeat.

STYLE RULES:
- Plain words. No hype adjectives. No em dashes.
- Do NOT invent facts, numbers, dates, customers or test results. If an input is missing, write [MISSING: what is needed].
- Tag every number with its source record. Show late deliveries too; do not hide them.

FINISH WITH: every [MISSING] item and every claim I should check.