1. The dated outside-in signal
Meridian Fab sees customers tightening traceability requirements for bid packages. The evidence record keeps the source URL, observation date, affected customer segment, and the demand it may imply.
2. The likely business priority
The source chain supports a working hypothesis: scale traceable bid-package assembly. This is an agenda item for discovery, not a verified fact and not an AI project.
3. Discovery validates where the pressure lands
Interviews and internal evidence confirm that RFQ-to-quote work depends on scarce senior-estimator judgment, quote and final-cost history, and manual compliance attachments. The team identifies an owner, measurable turnaround pain, accessible records, and a required human sign-off.
4. A grounded opportunity moves up
An estimator copilot already exists as a candidate because internal evidence supports it. The accepted demand hypothesis applies a bounded, visible ranking adjustment; it cannot invent the candidate or override missing feasibility evidence.
5. The build gates still apply
The opportunity must clear a blueprint, eval suite, mock execution, human-pilot plan, and production-handoff gate. Unsafe actions, missing approvals, or weak eval coverage stop progression even when demand is urgent.
What the sponsor can fund
The final package connects urgency to implementation: a source-linked business case, an internally validated workflow, a scoped copilot, golden and edge cases, human approval points, pilot success metrics, rollback criteria, and starter code engineering can own.
Run an outside-in company scan or read the demand-intelligence method.