For the inaugural episode of the Friday Five, we asked Travis Jarae, Liminal’s co-founder and CEO, five rapid-fire questions about the trade-offs founders and operators face every day. The format is what it sounds like: five questions, three minutes, no preamble. Travis has spent over a decade in market intelligence, watching the same trade-offs play out across identity, fraud, and cybersecurity teams. The sharpest answer in this conversation was about team composition. Not vision, not product. Team composition.
The argument is simple. The people who do strategy and the people who do execution are usually not the same people, and most companies pick one and call it a team. Both versions of that team fail, for different reasons. The version that works is the one most leaders avoid because it requires hiring against type. You need both.
Below: the video and three moments from the conversation worth pulling out.
The trade-off Travis names is the one most leaders learn the hard way. A strategy-heavy team produces decks and roadmaps but ships nothing. An execution-heavy team ships constantly but builds the wrong thing. The temptation is to fix it by hiring more of whichever side feels missing.
Travis says that’s the wrong instinct.
“Don’t try to bring people in that are either only strategy or only execution. It typically doesn’t work.”
The healthy version is a strategist with strong operators around them, or an operator with strong strategic thinkers around them. The unhealthy version is to keep stacking the same archetype because it’s the one you understand best. The fix takes humility most leaders run short on, especially in the first year of building a team.
Composing the team this way is how leaders excel at both strategy and execution. The strategy vs execution debate stops being a debate the moment you stop hiring for one side.
Travis built Liminal on the bet that competitive intelligence and market research were undervalued by the people who needed them most. That bet has held up better than he expected.
“People are always very surprised at how little people actually do competitive intelligence and research.”
The pattern he describes is familiar to anyone who has sat through a product roadmap review. Teams know their customer well. They know their internal capabilities well. They know almost nothing about what has already been tried, by whom, and why it failed. The result is a steady stream of products that re-litigate problems the market solved years ago, or revive ideas that died for reasons no one bothered to research. The bar to clear is low. Most teams still don’t clear it.
When Travis was asked what would matter most in the next 12 to 18 months, his answer was agentic AI. The framing he chose for it is the part worth catching.
“How do you get your teams AI native? Not to make it another tool that you need to learn, but rather something that’s going to make the existing tools that you use better every day.”
Most AI adoption pitches sell a destination. Travis is describing a path. The teams pulling away right now are not the ones replacing their stack. They are the ones layering AI underneath the tools their people already trust, so the learning curve is invisible and the productivity gain is not. It is a quieter way to ship the change, and the only one that survives the first month after launch.
Asked for a small hill he’d die on, Travis went straight to mustard. He hates it, and he’ll die on that hill. Welcome to the Friday Five.
