I don't think you understood what Alfred said. I believe he meant that people that pay for this would "protest" worse than they have in the past for any errors. IMO, his assumption is valid. Picture the outcry if it turns out the 1st Marine Div. has cheeseburgers as rations when it should have been bacon cheeseburgers...
No, I "get" Alfred's post. I'm just not as polite as he is.
Any folks here who work in business or law, as opposed to, say, IT or engineering, understand at a deck-plate level the concept of warranty. A product is only required to meet certain (minimum) legal standards of performance, OR what you yourself say it will meet. If a 1942 scenario is not warrantied to be exact, perfect, or otherwise without defect, the seller is under no obligation to respond or even listen to carping by purchasers.
However, I don't think the for-pay idea is very interesting to Matrix. I doubt the volume/revenue model is compelling versus the management time that would be consumed. Better to focus on a WITP 2.
I have been doing some noodling on the idea of a volunteer team doing such a scenario though. It's been a long time since I ran a big project, but I have run them. I was also married to a pretty good Big 5 consultant who taught me a lot about running very large IT integration projects.
I think a large-scale May 1942-start AE scenario could be wrangled by a team of no more than four leads, using the Net and the world-class WWII library collectively owned by forumites. The key proviso would be, however: "90% is good enough. All others, see the Editor." Using the Editor, Tracker's exporting and stratifying capabilities, and a clean Scenario 1 file, such a team (Air, Sea, Land, Bases/Economy) could use the excellent existing OOB as a starting point. Post-May 1, 1942, let the units arrive/be structured as now. Withdrawn units to that point, whack 'em. Build a sharable spreadsheet, put it in public with the team czars having sole editing power and the 90% decision-making power, and ask the community to fill in the Who, What, Where. Establish norms such as no CO debates below division level/CA-size ships. Let each side have ten (10) historical air unit COs and assign the others. Establish bands of dispruption, experience, etc. for LCUs where the historical record is unclear (Expert, Veteran, Trained, Recruit) and just assign them. The key is no more than four people, and ultimately the subject team lead if necessary, decides and they move on.
The key is asking for community help, but not being hamstrung by it. Distributed labor load. Accepting it won't be perfect, but only 90%. Making team T-shirts is vital. Seriously, sell them on eBay and pay the devs.
There are probably tech savvy young guys here who would love a resume stuffer for project management. If there are firm up-front rules and assumptions, and the community is brought in to help, but not control, it could get done in a few months. Perhaps if a working May 1, 1942 OOB and map could be produced, at that point the devs (Andy) or Matrix with some money could be persuaded to help write AI scripts, so long as the scope were restricted (no Quiet China, Ironman, Scenario 2, etc. One size fits all.)
Anyway, just some ideas. It could be done by amateurs using the professional grade OOB we already have, plus a collective attitude of 90% and four czars.