25 Jul 2025
Developer Tools

Defence Procurement solution to fix the rough interface between design ...

...engineering and procurements

Confidence
Engagement
Net use signal
Net buy signal

Idea type: Swamp

The market has seen several mediocre solutions that nobody loves. Unless you can offer something fundamentally different, you’ll likely struggle to stand out or make money.

Should You Build It?

Don't build it.


Your are here

Your idea for a Defence Procurement solution targeting the interface between design engineering and procurement falls into a crowded space. Our analysis places it firmly in the "Swamp" category, meaning there are already several solutions available, but none have achieved significant traction or user love. The existence of 7 similar products (n_matches = 7) signals high competition. Adding to this, the engagement levels of these existing products are low, with an average of only 1 comment per product (n_comments = 1), indicating that they may not be solving the problem effectively or resonating with users. Given this context, it's crucial to carefully consider whether you can offer a fundamentally different and significantly better solution to justify entering this market.

Recommendations

  1. Begin by thoroughly researching why existing procurement solutions haven't succeeded in bridging the gap between design engineering and procurement in the defense sector. Focus specifically on understanding the pain points and unmet needs of both design engineers and procurement teams. Don't just look at the features; dig into the underlying workflows and communication challenges.
  2. Given the low engagement with existing solutions, consider pivoting to focus on a very specific niche within the defense procurement process or a particular type of defense product. Identify a clearly defined group of users who are demonstrably underserved by current tools. This level of focus can help you stand out and build a loyal user base.
  3. Explore the possibility of building specialized tools or integrations that enhance existing procurement platforms rather than attempting to replace them. Many companies seem to be adding GPT as a feature in existing tools. Collaborate with established providers or develop add-ons that address specific pain points in the design-procurement interface. This would allow you to get quick wins, and market feedback before tackling the entire procurement lifecycle.
  4. Since AI is a trending topic, thoroughly evaluate whether incorporating AI into your solution can truly offer a distinct advantage. Avoid simply adding AI for the sake of it. Ensure any AI features directly address user pain points or improve efficiency in a measurable way. Be wary of "AI-washing" as users will see through superficial integrations.
  5. Given the challenges in the core defense procurement space, consider exploring adjacent problems that might be more promising. Could you focus on supply chain optimization, risk management, or compliance within the defense sector? These areas might have fewer established players and offer a greater opportunity for innovation.
  6. Based on the current market landscape, carefully consider whether to proceed with building a full-fledged solution. The low engagement and the existence of multiple similar products suggest a difficult path ahead. It might be prudent to save your resources and energy for a more promising opportunity, especially if your research indicates that the fundamental problems are not easily solved with technology.

Questions

  1. What are the non-technical barriers (e.g., organizational culture, entrenched processes, regulatory hurdles) preventing effective collaboration between design engineering and procurement in defense, and how can your solution address them?
  2. What specific metrics will you use to measure the success of your solution in improving the design-procurement interface, and how do these metrics align with the overall goals of defense organizations?
  3. Considering the low engagement with existing solutions, what innovative approaches will you take to drive user adoption and ensure your solution becomes an indispensable part of the defense procurement workflow?

Your are here

Your idea for a Defence Procurement solution targeting the interface between design engineering and procurement falls into a crowded space. Our analysis places it firmly in the "Swamp" category, meaning there are already several solutions available, but none have achieved significant traction or user love. The existence of 7 similar products (n_matches = 7) signals high competition. Adding to this, the engagement levels of these existing products are low, with an average of only 1 comment per product (n_comments = 1), indicating that they may not be solving the problem effectively or resonating with users. Given this context, it's crucial to carefully consider whether you can offer a fundamentally different and significantly better solution to justify entering this market.

Recommendations

  1. Begin by thoroughly researching why existing procurement solutions haven't succeeded in bridging the gap between design engineering and procurement in the defense sector. Focus specifically on understanding the pain points and unmet needs of both design engineers and procurement teams. Don't just look at the features; dig into the underlying workflows and communication challenges.
  2. Given the low engagement with existing solutions, consider pivoting to focus on a very specific niche within the defense procurement process or a particular type of defense product. Identify a clearly defined group of users who are demonstrably underserved by current tools. This level of focus can help you stand out and build a loyal user base.
  3. Explore the possibility of building specialized tools or integrations that enhance existing procurement platforms rather than attempting to replace them. Many companies seem to be adding GPT as a feature in existing tools. Collaborate with established providers or develop add-ons that address specific pain points in the design-procurement interface. This would allow you to get quick wins, and market feedback before tackling the entire procurement lifecycle.
  4. Since AI is a trending topic, thoroughly evaluate whether incorporating AI into your solution can truly offer a distinct advantage. Avoid simply adding AI for the sake of it. Ensure any AI features directly address user pain points or improve efficiency in a measurable way. Be wary of "AI-washing" as users will see through superficial integrations.
  5. Given the challenges in the core defense procurement space, consider exploring adjacent problems that might be more promising. Could you focus on supply chain optimization, risk management, or compliance within the defense sector? These areas might have fewer established players and offer a greater opportunity for innovation.
  6. Based on the current market landscape, carefully consider whether to proceed with building a full-fledged solution. The low engagement and the existence of multiple similar products suggest a difficult path ahead. It might be prudent to save your resources and energy for a more promising opportunity, especially if your research indicates that the fundamental problems are not easily solved with technology.

Questions

  1. What are the non-technical barriers (e.g., organizational culture, entrenched processes, regulatory hurdles) preventing effective collaboration between design engineering and procurement in defense, and how can your solution address them?
  2. What specific metrics will you use to measure the success of your solution in improving the design-procurement interface, and how do these metrics align with the overall goals of defense organizations?
  3. Considering the low engagement with existing solutions, what innovative approaches will you take to drive user adoption and ensure your solution becomes an indispensable part of the defense procurement workflow?

  • Confidence: High
    • Number of similar products: 7
  • Engagement: Low
    • Average number of comments: 1
  • Net use signal: 0.0%
    • Positive use signal: 0.0%
    • Negative use signal: 0.0%
  • Net buy signal: 0.0%
    • Positive buy signal: 0.0%
    • Negative buy signal: 0.0%

This chart summarizes all the similar products we found for your idea in a single plot.

The x-axis represents the overall feedback each product received. This is calculated from the net use and buy signals that were expressed in the comments. The maximum is +1, which means all comments (across all similar products) were positive, expressed a willingness to use & buy said product. The minimum is -1 and it means the exact opposite.

The y-axis captures the strength of the signal, i.e. how many people commented and how does this rank against other products in this category. The maximum is +1, which means these products were the most liked, upvoted and talked about launches recently. The minimum is 0, meaning zero engagement or feedback was received.

The sizes of the product dots are determined by the relevance to your idea, where 10 is the maximum.

Your idea is the big blueish dot, which should lie somewhere in the polygon defined by these products. It can be off-center because we use custom weighting to summarize these metrics.

Similar products

Top