Understanding Customer Expectations for Defense Integrators

Stop building defence startups without understanding defence markets. This may sound harsh, but it needs to be said. I meet many innovators and founders who want to “enter defence.” The ambition is there. The pitch decks are polished. But the strategy often isn’t there. Too many solutions are built with a single local market or own idea in mind. The assumption is that if something works in one country, it will naturally translate elsewhere. It rarely does. Defence markets are shaped by different doctrines, procurement systems, command structures, policies, industrial ecosystems, security requirements, and CULTURES. What resonates in one country can fall completely flat in another. Without understanding how to bridge those differences, market entry attempts almost always fall short. Another challenge is funding. Much of the funding available to early-stage defence innovators is still very local. Many investors have limited understanding of what building a defence capability for international markets actually requires. Questions often focus on familiar local startup metrics that simply do not apply. Defence is not a burger joint. It's a long game built on credibility, trust, integration, survivability in environments where failure has real consequences. Which leads to another recurring problem: positioning. “We build drones.” “We do AI.” “We provide autonomy.” That is not a capability description. Who is the operator? What mission problem are you solving? Where does the system integrate? How does it survive electronic warfare? How is it secured, governed, sustained, and supported? And most importantly: Why should anyone trust it when lives depend on it? Vagueness does not survive contact with defence reality. Commanders don't want snake oil. They want systems that work inside real operational ecosystems. That often means partnerships, integrations, logistics chains, doctrine alignment, years of credibility-building. This is where expectations frequently collide with reality. Access is not automatic. Trust is not immediate. Adoption does not happen in quarters. It takes years. What works today isn't automatically what another military is looking. Every environment has its own operational constraints, political context, integration requirements. Which means building for defence requires something many startup ecosystems underestimate: homework. Understanding the environment, the user, the system you are entering. Defence is never a one-way street. Collaboration is never a one-way street either. To receive access, insight, partnership, you also have to bring something meaningful to the table. The innovators who succeed are rarely the loudest but ones who listen first, ask the hard questions, spend time understanding operators, integration realities, mission constraints, the broader ecosystem before building the narrative. Because in defence, buzzwords don't matter. Survivability does. #DefenceInnovation #DefenceTech #NoBuzz

For technical founders in the defense space: how you communicate matters as much as what you build. Brilliant technology doesn’t win defense contracts on its own. Clear, disciplined communication does. A few patterns I see again and again with strong technical teams: 1. Lead with the mission, not the architecture. Decision-makers care first about what problem you solve and why it matters. Technical depth is essential, but it comes after relevance. 2. Translate performance into operational impact. “Lower latency” is interesting. “Faster decision-making in contested environments” is compelling. Always connect technical capability to real-world outcomes. 3. Show you understand risk, compliance, and constraints. Defense buyers want confidence that you understand the environment they operate in, security, certification, timelines, and accountability included. 4. Be precise, not verbose. Clarity signals maturity. Over-explaining often signals uncertainty. Say less, mean more. 5. Speak to today’s need and tomorrow’s integration. Defense organizations invest in platforms, not point solutions. Show how your technology fits into existing systems and scales responsibly. The founders who succeed aren’t the ones who “dumb it down.” They’re the ones who translate complexity into trust. If you’re building in defense, your communication is part of your product.

Last week I was listening to senior United States Air Force leaders talk openly about how they are rethinking requirements, industry engagement, and the pace of capability development. What caught my ear wasn’t a new program or a new acronym. It was a long overdue mindset shift by requirements generators. There was repeated emphasis on defining the operational problem first, then bringing industry in earlier to help shape solutions before requirements become overly prescriptive. Less “here is the exact widget we want” and more “here is the mission thread we need to enable, help us figure out the best way to do it.” That is a meaningful change in tone from the traditional process most of us grew up with. Another theme was continuous evolution. Leaders acknowledged that static requirements and long development cycles do not match the speed of threat adaptation. They talked about spiral development, modular architectures, and the expectation that capabilities will evolve after fielding, not freeze in time. That has big implications for how we design systems, structure contracts, and think about sustainment and upgrades. “Open architectures” came up again and again. Not as a buzzword, but as a practical enabler. The goal is to allow components, software, and subsystems to be swapped and improved over time without tearing down the entire system. From an industry perspective, that changes how we think about integration, IP boundaries, and long term value. The AI discussion was also refreshingly grounded. There was recognition that algorithms alone are not the limiting factor. Access to operationally relevant, contextualized data and the ability to build trust with operators are just as important. That reinforces the need for tight collaboration between operators, requirements owners, and industry, not just at Milestone B, but much earlier. For those of us in the aerospace and defense ecosystem, this is more than process talk. It signals that the Air Force wants partners who can operate in an iterative, collaborative, and modular environment. Companies that can move fast, integrate well, and evolve capability over time will be better aligned with where the customer is heading. It is encouraging to see this level of candor and self reflection from senior leaders. It creates space for better dialogue and, hopefully, better outcomes for the warfighter. Curious how others are seeing these shifts play out in their own engagements? #DefenseIndustry #AerospaceAndDefense #NationalSecurity #DefenseInnovation #OpenArchitecture #AIinDefense #Leadership #AirForce #CymSTAR

🛑 Stop Talking About Your Tech - nobody cares! 🛑 This week I gave a keynote at the RUAG innovation conference dedicated to the defence sector and then I helped judge the startup competition. While the tech presented was mind boggling, all companies made the same mistake: they fell into the trap of making their start-up pitch a technology showcase. Bad idea! Unfortunately, I see that mistake been made by a lot of startups & their CEOs! Sure, your innovation might be groundbreaking, but here’s the hard truth: investors and stakeholders don’t fund technology—they fund solutions that create value for customers (and beneficiaries in the defence sector). That sounds trivial, but when I listen to startup pitches I rarely see CEOs showcasing their intimate customer knowledge. They generally focus on highlighting how brilliant their tech is and limit themselves to a high-level market study that shows the size of a market. Dead wrong! A common "excuse" is that they are only starting to talk to customers, now that the tech works. Worse, even, some say that they don't have direct access to customers, only to resellers. Framed in another way: you're telling me that you made the technology work, but are only now really figuring out if customers care enough to pay? Not a good way to convince me as a potential investor. Let me break the news: You don't need a functioning prototype (nor an MVP) to prove that customers care and are willing to pay. The best startups constantly iterate between developing the tech (R&D) and testing customer needs and willingness to pay (business R&D). To win over investors and stakeholders in companies you need to showcase a deep understanding of the customer/beneficiary and their willingness to pay. Showcase the evidence that supports your idea/tech, not your tech. Here are the type of questions I ask at a startup or corporate innovation competition to judge customer understanding: 1) What is your customer's/beneficiary's #1 job and what is your evidence to prove that? How many customers/beneficiaries have you talked to? 2) How did you test if your customers/beneficiaries deeply care about your solution? How did you test if they care enough to pay? 3) What is the buying process of your customers? What are their buying criteria and how does that benefit your solution? That understanding is crucial in particular in slow sales cycles like in defence or government purchasing in general. With these type of questions and others I try to figure out how deeply/intimately a startup management understands their customers. At the end of the day the customer is every company's judge, jury, and executioner. Back to the basics: without a customer a startup will run out of money... it's as simple as that! ------------ The other startup competition judges were Colonel Dominik Winter (responsible for innovation at the Swiss Armed Forces) and RUAG CEO Ralph Mueller. #innovation #startup #defence #defencesector #armedforces

Key Account Management in Defense What makes a plan in defense industry anyway? Management (KAM) requires everything a traditional Key Account Plan entails—plus additional layers of rigor, compliance, risk management, and long-term partnership-building—given the high stakes, long sales cycles, political oversight, and mission-critical nature of defense sector work. 1. Clear Strategic Goal Setting • Define long-term objectives (e.g., multi-year procurement programs, lifecycle support contracts) • Align with national defense priorities, customer mission outcomes, and political context. • Include growth goals that go beyond revenue (e.g., footprint expansion, partnerships) • Identify milestones for customer value delivery, not just internal wins. 2. In-Depth Situation Review a) Customer Landscape • Understand their strategic defense objectives, procurement roadmap, funding cycles, and capability gaps. • Know the key decision-makers, influencers (military, civilian, political), and stakeholders • Track relevant legislation, budgets, and geopolitical developments that could impact defense spending or program priorities. b) Your Organization’s Position • Review past performance, delivery credibility, and strategic relevance to the customer’s evolving needs. • SWOT analysis of your offering vs. competitors—especially local champions or politically aligned suppliers. • Assess your compliance standing (ITAR, export controls, cybersecurity standards, etc.) 3. Strategic Formulation • Develop a co-creation strategy with the account: be a partner, not just a vendor. • Create solution roadmaps linked to current and future defense requirements. • Build alignment with customer innovation needs • Identify partnership opportunities (local defense firms, SMEs, academia). 4. Resource Allocation • Assign the right mix of technical, commercial, and strategic resources: program managers, engineers, policy experts • Ensure alignment with capture teams, business development, and proposal writers early. • Allocate budget for long-term capture efforts, demonstrations, or pilot programs. 5. Performance Metrics & Governance • Measure more than revenue: include customer satisfaction, program delivery success, new capability adoption. • Use leading indicators • Regularly review and adjust the plan quarterly—not annually—with the customer where possible. 6. Customer Collaboration & Buy-in • Validate your plan with customer input • Ensure there’s a shared understanding of joint goals and mutual investment. • Maintain transparency on roadblocks and enablers for delivering mission success. 7. Risk & Compliance Planning • Account for political shifts, security risks, policy changes, or export regulation shifts. • Include a plan for managing obsolescence, tech refresh, and through-life support. Trust you are doing well in KAM Defense planning!