Speak their language
"Wireframe deck": Presentation version of the wireframes you're building for development, tailored to an executive audience who wants to know
x about the project.
This is a very common term among execs and other "business types" who are familiar with the concept of designing an app or site (but aren't designers or developers). It is driven by the normal cross-departmental meeting requirement of informing your partners with a short slide deck.
Slide-based presentation tools are this audience's bread and butter (for better or worse). The fear of getting caught trouble-shooting tech issues with a new format (even a web-based tool) is enough to keep the status quo.
A different kind of story
The focus of the wireframe story needs to change compared to a typical engineering/development presentation. It's about showcasing business value before system flow or function. Your presenter is going to want to tell a concise story about how the user comes into the system and quickly get to the ROI drivers.
Marcin Treader (CEO of UX Pin) says this about simple wireframes:
The design should solve certain problems for a certain group of people. Wireframes and prototypes do not present the problem that needs to be solved and do not describe a targeted group of users.
^ Applied to this context, the normal wireframe format you might deliver to a product manager or software architect will fall flat in an executive setting.
Ideally, there's a lot of material that lead to the wireframe (eg personas, user journeys, analytics, market research, etc). Adding those supporting pieces will go a long way toward explaining the value behind the wires. Keep it short, but make the thinking very clear.
This classic graphic from JJG speaks to the bigger picture that you want execs to understand.
Set up the deck
This part is more about "decks" provided to clients ...
PowerPoint is far and away the application of choice. It's worth asking if they have a standard deck template. Common elements are headings, a small logo, and a non-disclosure statement. The expectations around template usage changes from one org to the next.
I prefer to set the deck up in Google Slides so it can be privately accessed from any device (and I don't have to use PP). My deliverables are the Slides link and exports in PPT and PDF format. That covers my bases and keeps the client feeling safe. I've never had a problem with this approach; in fact, on various occasions, each of those backup formats (Slides and PDF) have gotten the client out of a jam.