SVC-03 · Service
Proposal preparation and technical volume review for aerospace bids
Goujon Systems supports aerospace, space and defence teams preparing competitive bids: ESA and national-agency tenders, prime-to-supplier proposals, and EU-funded calls. The work covers win-theme definition, technical volume structure and writing, compliance and traceability against the customer’s requirement set, and adversarial peer review: reading the proposal the way the evaluator will, and finding what will cost you points before the evaluator finds it for free.
Clément Goujon has sat on both sides of this: as lead system architect on a bid worth over €1 billion that was won, and as a technical reviewer inside the System, Functional & Avionics Architecture Committee of a large space integrator. Support scales from a single red-team pass on a near-final volume to involvement from the bid/no-bid decision onward.
What gets support
Scoped to what the bid needs. Very few teams need all of this; almost every team needs more than the red-team pass they were planning to ask for.
- Bid / no-bid technical input: an honest read of whether the technical requirement set is winnable with the solution you actually have, before the bid budget is committed.
- Win themes and technical discriminators: identifying what genuinely separates your solution from the obvious alternative, and making sure it appears where the evaluator is looking rather than only in the executive summary.
- Compliance matrix and traceability: every customer requirement mapped to the section that answers it, so that formal compliance is demonstrable rather than merely true.
- Technical volume architecture: the storyline and section structure, built around the evaluation grid rather than around your internal organisation chart.
- System architecture and justification content: writing the architecture sections directly, including the rationale that turns a design description into a defensible argument.
- Risk, margin and TRL narrative: a maturity and risk story that is credible precisely because it acknowledges what is not yet mature, rather than claiming uniform TRL 6.
- Adversarial red-team review: reading the volume as a hostile expert evaluator would, scoring it against the customer's own grid, and reporting what loses points.
- Clarification and negotiation rounds: support on written clarification responses, where a careless answer can undo a strong proposal.
How evaluators actually read a technical volume
Most losing proposals are not technically inferior. They are technically fine and badly evaluated, because they were written for a reader who does not exist.
- Evaluators score against a grid, not against your enthusiasm. Anything the grid asks for that is not findable scores zero, regardless of whether you did the work.
- Compliance is checked before quality is judged. A brilliant section that sits outside the required structure can be marked down before anyone reads it properly.
- Unjustified assertions are discounted entirely. “Our architecture is robust” contributes nothing. The trade-off that produced it, and the margin that demonstrates it, contribute everything.
- Margins that are not stated are assumed absent. An experienced evaluator reads an unquantified margin as no margin, and prices the risk accordingly.
- Your reader is on their tenth volume that week. Structure, signposting and a findable answer to each grid line are not courtesies: they are a scoring mechanism.
- Acknowledged weakness reads as competence. A stated risk with a credible mitigation scores better than an unstated one the evaluator spots unaided.
The red-team pass
What an adversarial review produces
Against the customer's grid
The volume is scored line by line against the evaluation criteria as published, not against a generic quality checklist. Findings are ranked by points at risk.
Find the load-bearing claims
Every claim carrying weight is tested: is it justified, quantified, traceable, and consistent with the rest of the volume? Inconsistency between sections is the most common and most costly defect.
Prioritise against the clock
A ranked list of fixes matched to the time actually remaining before submission, so effort goes where it changes the score rather than where it is easiest.
Frequently asked
Questions people ask before getting in touch
When in the bid cycle should outside support come in?
Two points give the best return. The first is immediately after the requirement set is released, when the win themes and volume architecture are still changeable and correcting them is nearly free. The second is a red-team pass roughly two weeks before submission, when there is still time to act on what it finds. The worst moment is three days before submission, when a review can only produce anxiety.
Can you write the technical volume, or only review it?
Both. Writing the system architecture and justification sections directly is common, particularly where the architecture argument is the discriminator. Reviewing is cheaper and often sufficient when the team is strong and simply too close to the text.
Do you work under NDA?
Always, and as a matter of course before any bid material is shared.
What kinds of bids does this cover?
ESA and national space agency tenders, prime-to-supplier proposals inside large programs, EU-funded calls, and defence procurement where the technical volume carries a defined share of the score. The common factor is a system-level technical argument that has to be evaluated by an expert reader.
Is there a conflict of interest if you work with our competitors?
Conflicts are declared before an engagement is accepted, and a bid engagement excludes working on a competing bid for the same procurement. This is stated in writing, not assumed.
What if the proposal is nearly finished?
Then the useful work is a triage pass: compliance gaps first, because an unmet formal requirement can cost more than a weak technical argument; then unjustified assertions; then structure. Expect a prioritised list of what to fix in the time remaining, not a wish list.
Related services
Book a free intro call.
Thirty minutes, no commitment, in English, French or Italian. Tell me about the program and I will tell you honestly whether I am the right person for it.
Last updated: