Interactive tools and plain-language guides to help customers build better requirements before they reach the contracting officer.
Most delays and rework in contracting trace back to the requirements package. These tools meet customers where they are — walking them through what a good package looks like, what the CO needs, and why.
Ollie the axolotl walks customers through intake, market research, evaluation factors, justification, funding, and a routing-slip package summary. Exports PDFs at every step.
Answer structured questions before the package hits the CO's desk. Flags missing requirement documents, funding and schedule risk, justification gaps, COR/QASP issues, and next steps.
Candid, plain-language answers to the questions program offices keep asking: clearly defined requirements, sole source, GSA, market research, why the CO pushes back, small business, and how to get past a stonewalled package.
Pick an appropriation and period. Tool explains what the money can and cannot buy, and when it expires.
Short customer-facing lessons that map directly to the gaps Preflight finds. Live cards reuse KTHQ tools and CO trainings where they already fit.
What the CO needs before the acquisition can move. Could be a little, could be a lot — depends on what you're buying. Covers the spectrum from micro-purchases to major systems and lists everything that could go in the file.
Helps customers separate outcomes, constraints, minimum requirements, preferences, and accidental brand-name lock-in.
Three different dates that look the same, what you can do to compress the timeline, when the schedule genuinely flexes for real emergencies, and how to track your own contracts so the next buy isn't a panic.
How to define measurable "done" for products, services, and construction. Covers inspection vs. acceptance, the delayed-install trap, how acceptance gets documented (including WAWF for DoD), and what happens when something fails.
How to define reports, meetings, data, and closeout artifacts so they survive contact with reality. Includes a deeper dive on CDRLs — codes you'll actually see, common DIDs, distribution statements, and the data-rights clauses that decide what the Government can do with the data later.
Use the PWS training as the deeper dive on outcomes, tasks, standards, surveillance, and why services packages need an administration plan before award.
How to turn "best value" into specific questions, useful evidence, and fair ways to compare contractors. Includes a menu of common factors, the evaluator vocabulary you'll hear if you serve on a team, and the source-selection-sensitivity rules that come with the seat.
Explains how to support brand-name or brand-name-or-equal needs with minimum characteristics, market facts, and a justification story that survives review.
An estimate is just market research with a number on it. Covers what the FAR actually requires (less than you think), why the IGE matters more when competition is weak, and the bad-optics trap of writing one after the proposals come back.
Use the existing market research training to gather prior buys, known vendors, quotes, capability statements, constraints, and incumbent context.
A plain-language entry point for fund type, fiscal year posture, bona fide need, crossing fiscal years, and why funding timing changes acquisition timing.
Shows what evidence helps a single-source or brand-name claim and what statements collapse when the CO, legal, or competition advocate reads the file.
The old file is a map, not a template. Covers what probably changed, how to use incumbent performance as evidence, the package sections that need fresh review, the customer's side of transition, and the bridge-contract trap.
A customer-friendly way to spot supervision, tasking, workspace, and control patterns that can turn a services contract into a legal problem.
Use contract-specific COR training to help customers understand who will inspect performance, what the COR owns, and why "we will name someone later" is a package risk.
Shows customers why scope, funding, schedule, and contract language have to flow through the CO instead of informal direction to the contractor.
Use the cure notice training as the CO-side deep dive, with a customer focus on documenting facts, notifying the COR/CO, and avoiding informal direction.
Anyone in a program office, requiring activity, or resource shop who has to hand a requirement to a contracting officer — whether that is a shiny new purchase request or a complex services recompete.
No contracting background assumed. No acronyms that aren't defined. The tools ask what you actually know and translate it into something the CO can act on.