Paste a requirement — a rough need, an existing statement of work, or a labor-hour position description. The pipeline identifies the distinct position(s) being asked for, translates contractor jargon into plain functions, and drafts a CLIN structure for each: a Firm-Fixed-Price (FFP) deliverable, a Firm-Fixed-Price, Level-of-Effort (FFP-LOE) structure, or — only when genuinely warranted — the justification required to keep it T&M. No price or dollar amount is ever suggested; pricing is left to competitive quotes.
Quick reference, before you start
- T&M
- Time-and-Materials / labor-hour. You pay for hours worked, regardless of what gets produced. FAR 16.601 says this should only be used when it truly isn't possible to estimate the extent or duration of the work in advance — it requires a signed determination, not just habit.
- FFP
- Firm-Fixed-Price. A defined deliverable, checked against a stated acceptance criterion. Best fit when the output can be described well enough that someone could say "done" or "not done."
- FFP-LOE
- Firm-Fixed-Price, Level-of-Effort (FAR 16.207). A known, capped amount of one person's time over a period — a middle ground for real advisory or support work where the output can't be fully pre-defined, but the amount of effort can be. FAR is explicit that FFP-LOE still pays for effort expended, not results achieved.
- CLIN
- A contract line item — one self-contained piece of the eventual award. One position usually needs one CLIN; occasionally a position needing ongoing presence also has a genuine, separate deliverable worth calling out, which becomes a second, companion CLIN. No CLIN this tool drafts ever carries a price — that's set later by competitive quotes among vetted candidates.
None of this is legal advice — your contracting officer makes the final contract-type determination. This tool is meant to give you a defensible first draft to bring to that conversation, not to replace it.
No classified information, CUI, export-controlled or source-selection-sensitive material.
Past runs, stored in this deployment's database. Click one to reopen it.
No saved runs yet.
This is the actual logic each pipeline stage runs on. Edit it and re-run a real input to test whether a change generalizes, not just whether it fixes one example.
Stage 1 — Identify positions
Identifies the distinct position(s) in a requirement (usually one) and translates each one's contractor jargon into a plain-language function description, without yet deciding contract type.
Stage 2 — Classify by contract type
Applies the FAR 16.601 test to recommend FFP, FFP-LOE, or (rarely) that T&M is genuinely required.
Stage 3 — Draft CLIN structure
Drafts one or more CLINs per position: a deliverable (FFP), a fraction-of-one-FTE effort structure (FFP-LOE) with an optional genuine companion deliverable, or a FAR 16.601 justification (T&M). Never includes a price.
Stage 4 — Lint
Flags boilerplate T&M justifications, vague FFP criteria, FFP-LOE structures that quietly grade outputs instead of effort, manufactured companion deliverables, and any price that leaked in where it shouldn't be.
Stage 5 — Readiness check
Checks the requirement for the six fields that gate a consultant match (clearance, citizenship, location/on-site vs. remote, price/rate ceiling, availability window, degree requirement) and drafts a plain-language reminder for anything missing.