A briefing is most useful when both sides come prepared. The questions that help a defense organization get clear answers quickly.
By Skyrivet2 min read
A capability briefing is a conversation, not a sales pitch. It works best when the organization asking for it knows what it needs to find out. These are the questions we find most useful to prepare in advance.
About the requirement
- What problem are you trying to solve, and for which units?
- Where and in what conditions will the system be used?
- What is already in service, and what does the new capability need to work with?
- What is the timeline, and what is driving it?
About the system
- What has been tested, where, and under which conditions?
- How does it behave when communications are degraded or lost?
- What does it need from the user in power, logistics and maintenance?
- How long does it take to train an operator?
About the long term
- How are updates delivered, and how often?
- Which repairs can be done by users, and which by the manufacturer?
- What standards and interfaces does it support?
- Who owns the data it produces?
About the next steps
A good briefing ends with a clear view of what happens next: further technical discussions, a demonstration, or an honest conclusion that the capability is not the right fit.
Some information is only shared in a briefing and not on a public website. To start the conversation, request a briefing and tell us about your organization and requirements.
