Our Story
We built Deckhalo because decks were stealing our nights.
Brandon Hale spent five years in enterprise software sales watching skilled account executives lose entire evenings to PowerPoint the night before a QBR. The problem was never knowing what to say — it was not knowing how to structure it into a deck that made one clear point per slide.
It was 11pm the night before a quarterly business review. One of Brandon's account executive colleagues had three hours of meeting notes, a spreadsheet with Q3 usage data, and a blank PowerPoint open on her second monitor. She'd present in nine hours to a client facing a $400K renewal decision. She wasn't stuck because she didn't know what to say. She was stuck because she couldn't see how to break it into slides — which point led to which, where the chart went, what story the numbers were trying to tell.
That moment defined the founding question of Deckhalo: not "how do we generate AI slides?" but "how do we take what someone already knows, build the argument structure they can't see when they're inside it, and produce a deck that earns the room?"
Brandon started building in Salt Lake City in 2023, with a small team of engineers and a designer who'd spent years in enterprise software. The first version was a command-line script that took raw notes and returned a slide outline. By the third iteration, users were pasting QBR notes at midnight and exporting a polished 16:9 deck — with speaker notes — before bed.
We are still a small team and we intend to stay precise. Deckhalo does not try to replace your judgment about what to say or your strategy about how to say it. It handles the part that steals the night: turning what you already know into a structure that communicates it.
The Team
The people building Deckhalo
Brandon Hale
CEO & Co-Founder
Five years in enterprise software sales. Built Deckhalo in Salt Lake City in 2023 after too many QBR nights spent rebuilding slides instead of refining arguments.
Reina Flores
Head of Design
Previously principal designer at two growing B2B SaaS companies. Holds that a slide is a statement — one argument, one visual, one job.
Kai Nakamura
Head of Engineering
ML engineer specializing in document understanding and structured output generation. Designed the narrative architecture engine that sequences slides before writing them.
Sasha Okafor
Head of Growth
B2B SaaS growth. Three years helping PLG tools reach their first 1,000 active users through content, community, and word-of-mouth in niche professional communities.
What we believe
Three principles that guide every decision
Clarity over decoration
A beautiful slide that makes three points makes none of them. Deckhalo enforces the one-idea-per-slide discipline that we all know is right but abandon when the deadline is tomorrow morning.
Speed without sacrifice
A first draft in 90 seconds is only valuable if it's a good draft. Speed comes from a rigorous narrative structure engine — not from skipping the hard part of deciding what the deck is actually trying to say.
Slides that earn the room
The measure of a deck isn't how long it took to make. It's whether the audience left with the right decision. We build for that outcome — not for impressive-looking slides that get clicked through without being read.