Six weeks. That is the number every Tier-1 automotive tooling builder cites when describing a standard feasibility cycle for a new program from Ford, General Motors, or Stellantis. From RFQ arrival to final quote submission, the average cycle runs five-and- a-half to six-and-a-half weeks. Some run longer for cross-zone programs. Few run shorter without sacrificing quality. The number is so consistent across builders that it has become an industry norm - assumed by OEM procurement teams, baked into program timelines, treated as a fixed constraint.
It is not fixed. It is the sum of specific activities, each with its own duration, each with its own bottleneck, each with its own opportunity for compression. When you decompose the six weeks carefully, what you find is that approximately 60-70% of the cycle time is mechanical work - document reading, similarity matching, specification cross-referencing, layout extraction - and only 30-40% is the actual engineering judgment work that requires senior expertise.
This brief decomposes the six-week cycle week by week, identifies where the time actually goes, and shows what compresses to days when AI handles the mechanical 60-70%. The compression is real and measurable. The implication for builder competitiveness - and for OEM-side procurement expectations - is structural.
Week 1: The Senior Engineer Read
A new RFQ from Ford BME, GM GMW, or Stellantis MS arrives in the builder's inbox on Monday morning. By Tuesday, the most senior estimator has been assigned. Their week is structured around getting through three documents: the layout PDF (typically 48 x 36 inches at 200 DPI), the requirements document (typically 50 pages of dense technical specification), and the 2D or 3D product models (the actual cargo door, underbody, body-in-white panel being built).
Day 1 of Week 1 is initial scan. The senior engineer reads the program identification (vehicle code, plant, production rate, JPH target), the cell scope summary (which cells the builder is being asked to quote), and the process requirements section. They form an initial mental model of what is being asked.
Days 2-3 are deep read. The senior engineer goes through the specifications section line by line. They extract every cited BMS, GMW, MS, or PWA standard. They cross-reference against the specifications used in past programs they remember as comparable. They flag the deltas they catch and miss the deltas they do not. This is the part of the week where the missed-spec-delta failure mode activates.
Days 4-5 are similarity identification. The senior engineer searches the builder's historical job database for past cells that match the new RFQ's profile. Most builders use document-control systems where this search is largely manual - opening past job folders, reading the cell summaries, judging similarity. The senior engineer identifies three to five candidate past cells for the Frankenstein process.
Total Week 1 senior engineer time: typically 25-35 hours, which consumes most of the senior engineer's available bandwidth that week. They cannot run three of these in parallel - the cognitive load of switching between RFQs is too high.
Week 2: Junior Engineer Cross-Check
Week 2 begins with the senior engineer handing the candidate past cells to a junior engineer for cross-reference validation. The junior engineer pulls the historical files from document control, reads the past cell summaries in detail, and cross-references the cited specifications against the new RFQ's spec list.
Day 6-7 of Week 2 is file retrieval. The junior engineer requests the historical files from document control. Depending on the builder's document management maturity, this can take anywhere from a few hours (modern PLM-integrated systems) to several days (legacy folder structures on shared network drives). Many builders still operate at the slower end of this range.
Days 8-10 are spec validation. The junior engineer reads each past cell's specification documentation and validates that the cited specs match the new RFQ's. They produce a delta list - what is the same between past and new, what has changed. This is the document that the senior engineer will use in Week 3 to start Frankensteining.
Throughout Week 2, the senior engineer is consulted on ambiguous deltas. The junior engineer flags items they cannot confidently categorize. The senior engineer makes the call. Each consultation is a 15-30 minute interruption. Across a week, these add up to 5-8 hours of senior engineer time that is productive but not high-leverage.
Total Week 2 effort: 30-40 hours junior engineer, 5-8 hours senior engineer. The senior engineer's bandwidth begins to free up for parallel programs, but the Week 1 program is still consuming meaningful attention.
Week 3: The Frankenstein Synthesis
Week 3 is when the actual quote starts to take shape. The senior engineer takes the past cells, the spec delta list, and the new RFQ requirements and begins the Frankenstein process: mashing sections of past cells into a baseline concept for the new cell.
Day 11-12 is initial Frankenstein. The senior engineer drafts a first-pass cell concept. Which past cell's door panel section? Which past cell's hem assembly? Which past cell's weld sequence? The choices are made based on similarity ranking and the senior engineer's judgment about which sections are most adaptable.
Day 13-14 is adjustment. The senior engineer adjusts the Frankenstein for the new RFQ's JPH target, alloy mix, and any spec deltas that affect cycle time or cell architecture. This is the highest-judgment work of the entire cycle - the senior engineer's accumulated expertise is being directly applied here.
Day 15 is internal review. The senior engineer presents the Frankenstein baseline to the program lead, the layout team lead, and sometimes the customer-facing sales engineer. The review surfaces questions, gaps, and judgment calls that need resolution before moving to Week 4.
Total Week 3 senior engineer time: 30-40 hours, the heaviest week of the cycle. The senior engineer's focus is now concentrated on this program because the Frankenstein synthesis cannot easily be parallelized with another program's similar synthesis phase.
Week 4-5: Layout Team Adjustment and Simulation
Weeks 4 and 5 see the cell concept move from the senior engineer to the layout team. The layout team takes the Frankenstein baseline and adjusts it for the specific plant where the program will run.
Day 16-18 is plant constraint extraction. The layout team reads the plant layout PDF for column grid, conveyor topology, utility access, and ceiling clearance. They validate that the Frankenstein baseline fits the plant envelope. This is where the plant-layout- mismatch failure mode activates - if the baseline assumes a 30-foot grid and the plant has a 24-foot grid, the cell has to be redesigned.
Day 19-22 is cell layout simulation. The layout team uses simulation software (typically Tecnomatix Process Simulate, Delmia, or Visual Components) to validate the cell's cycle time, robot reach, part flow, and station-to-station transfer. The simulation produces a refined cell concept with detailed robot positions, conveyor configurations, and cycle time decompositions.
Day 23-25 is iteration. The simulation reveals gaps in the baseline. A robot cannot reach a weld point. A conveyor transfer exceeds the cycle budget. A station has insufficient operator access. The layout team iterates with the senior engineer to resolve each gap. Each iteration costs 1-2 days of layout team time and 2-4 hours of senior engineer time.
Total Weeks 4-5 effort: 60-80 hours layout team, 15-25 hours senior engineer. The senior engineer's role shifts from primary synthesis to consultative, freeing bandwidth for the next program's Week 1 read.
Week 6: Pricing and Customer Review
The final week takes the refined cell concept and converts it into a customer-facing quote. Pricing pulls labor costs from the engineering bill of materials, material costs from the cell BOM, and risk reserves based on the senior engineer's confidence assessment. The sales engineer reviews the quote with the senior engineer for technical defensibility before sending to the customer.
Day 26-27 is pricing assembly. The pricing team compiles labor hours, material costs, capital equipment costs (robots, conveyors, tooling, automation controllers), and overhead allocation. They apply the company's standard margin structure.
Day 28-29 is review and submission. The sales engineer walks through the quote with the senior engineer to ensure the technical narrative aligns with the customer's RFQ. Any final adjustments are made. The quote is formatted and submitted.
Day 30 (and any additional days) is customer questions. The customer's BME/GMW/MS engineering team typically asks 5-10 clarification questions over the following week. Each question requires a 1-3 hour response from the senior engineer.
Total Week 6 senior engineer time: 15-20 hours, including post-submission customer Q&A. Total cycle time across all six weeks: 30 calendar days, plus 5-7 days of post-submission clarification.
Where the Mechanical Work Hides
When you decompose the six weeks of senior engineer time, approximately 60-70% is mechanical work that does not require senior judgment.
Week 1's document reading and spec extraction (25-35 hours of senior time) is largely mechanical. The senior engineer is reading a 50-page document to find cited specs and identify cell scope. A junior engineer could do this if they had perfect recall of past programs - but they do not, so the senior engineer does it.
Week 1's similarity identification (8-12 hours of senior time) is mechanical pattern matching. The senior engineer is searching a database for past cells that match the new RFQ profile. This is exactly the kind of task that AI is good at.
Week 2's spec validation consultation (5-8 hours of senior time) is mechanical cross-referencing. The senior engineer is confirming or denying judgments the junior engineer cannot confidently make.
Week 3's Frankenstein synthesis is mostly judgment - but the first-pass section selection (which past cell's door panel to start from, which past cell's hem assembly) is mechanical similarity matching. Maybe 8-12 hours of the Week 3 effort is mechanical work that AI could compress.
Week 4-5's plant constraint extraction is partly mechanical (the column grid, conveyor topology, and utility access can be extracted directly from the layout PDF) and partly judgment (the layout team's iteration on cell topology is real engineering work). Maybe 6-8 hours of senior time per week is mechanical constraint validation.
Adding up: roughly 55-75 hours of senior engineer time per quote is mechanical work. The total senior time per quote is roughly 90-115 hours. The mechanical fraction is 60-65% of senior engineer effort.
The Compression Math
When AI handles the mechanical 60-65% of senior engineer time at 80% accuracy, the senior engineer's contribution shifts from original work to verification. Verification is roughly five times faster than original work. The compression math:
55-75 hours of mechanical work compresses to 11-15 hours of verification. The senior engineer's total time per quote drops from 90-115 hours to 36-55 hours. The cycle time compresses from six weeks to roughly two weeks.
The specific week-by-week compression looks like:
Week 1 (senior engineer read) compresses from 25-35 hours to 4-7 hours. The AI extracts specs, identifies similarity, and flags deltas. The senior engineer verifies in a half-day rather than spending the full week.
Week 2 (junior cross-check) is largely eliminated. The AI has already done the spec cross-reference. The junior engineer's role shifts to reviewing the AI's delta list, which takes 1-2 days instead of a full week.
Week 3 (Frankenstein synthesis) compresses from 30-40 hours to 15-20 hours. The AI has provided the first-pass section selection. The senior engineer does the judgment adjustment but not the mechanical pattern matching.
Weeks 4-5 (layout team simulation) compress modestly. The plant constraint extraction is automated. The actual simulation work still requires the layout team. Cycle compression: 60-80 hours to 40-55 hours.
Week 6 (pricing and review) is largely unchanged. The pricing team still needs to compile costs. The sales engineer still needs to review with the senior engineer. Cycle time: unchanged at about a week.
Total compressed cycle: 14-18 days instead of 30-35 days. The six-week cycle becomes a two-week cycle. Quotes go out faster. Senior engineer bandwidth multiplies.
What This Unlocks at the OEM Procurement Level
The cycle compression matters beyond the builder's internal productivity. It changes what OEM procurement teams can demand.
Today, OEM BME, GMW, and MS teams structure their procurement cycles around a six-week assumption. Programs go out to bid with six weeks of response time. The first round of bid review then triggers follow-up RFQs to refine scope, which take another three weeks. The total procurement cycle from initial RFQ to signed contract is typically 12-16 weeks.
When builders can respond in two weeks instead of six, the OEM procurement cycle can compress to 4-6 weeks. This is not a hypothetical - the most progressive OEM procurement teams are already restructuring their cycles to take advantage of faster supplier responses. The slower suppliers are being filtered out of consideration before pricing even matters.
The competitive dynamic this creates is asymmetric. Builders that have integrated AI-assisted cycle compression can respond to more RFQs per year, win more programs, and deepen relationships with OEMs who value response speed. Builders that have not are seeing their RFQ invitations decline as procurement teams pre-filter to faster responders.
What VPs of Engineering Should Track
If you are VP of Engineering or COO at a Tier-1 automotive tooling builder, the metrics that actually matter for cycle compression are not the standard productivity dashboards.
Track senior engineer hours per quote. If this number is above 80 hours per quote, you have meaningful compression opportunity. If it is below 40 hours, you are already at AI-assisted leverage and your competitors are about to catch up.
Track cycle time from RFQ arrival to quote submission. The industry baseline is 30-35 days. Best-in-class is 14-18 days. Where you sit on this curve directly correlates with your market share trajectory.
Track senior engineer parallel program capacity. How many programs can each senior estimator have active simultaneously? At pre-AI leverage, the answer is typically 2-3. At post-AI leverage, it should climb to 5-7.
Track post-submission clarification volume. OEMs typically ask 5-10 questions per quote. Quotes from AI-assisted workflows often have lower clarification volume because the upstream document analysis is more complete. This is a quality signal that compounds into customer trust.
The Industry Endpoint
Six weeks has been the assumed quote cycle for fifty years. It is becoming two weeks at the leading edge of the industry. By 2028, the OEM-side procurement teams will have restructured around the two-week assumption. The builders that have not compressed will be operating outside the new norm and will progressively lose competitive position.
This is not a productivity improvement. It is a market restructure. The builders that move first will gain market share that becomes structural over time. The builders that move last will face a tightening procurement window they cannot meet without the same cycle compression.
The six-week feasibility cycle was always sixty percent mechanical work that did not require senior engineering judgment. Recognizing that and compressing it is not optional. It is the defining operational shift for Tier-1 automotive tooling builders over the next 36 months.
See the six-to-two week compression on your own RFQ.
Before your competitors do.
We will walk through one of your recent RFQs on screen and show exactly which week-by-week steps compress with AI. No marketing math. Just the actual cycle decomposition and where your senior engineer time can be reclaimed.
Book a 30-Minute Demo →