Solving the Podcast Puzzle: How Dumi Mabhena Built Hilite's Unified Editing Platform
There’s a particular kind of frustration that comes from having a great idea but being blocked by broken infrastructure. That’s exactly what Dumi Mabhena experienced when he started Zimbabwe in Voices, a podcast dedicated to sharing positive stories from his home country.
The concept was meaningful. The execution was painful.
During COVID, Dumi launched his podcast with genuine purpose: to counter the overwhelmingly negative narratives coming out of Zimbabwe by highlighting the people doing good work in his community. But as he began recording remote interviews across the globe, editing audio, and publishing episodes, he hit a wall that had nothing to do with storytelling ability.
“The tools were incredibly fragmented,” Dumi explains. “I’d record on Zoom or Riverside, edit in one product, remove background noise in another, and publish somewhere else entirely. For someone without an audio engineering background, it was just cumbersome.”
That friction became the seed for an idea that would eventually become Hilite—a unified platform designed to make podcast production as simple as telling a story.
Validating the Problem Before Writing Code
Here’s what’s remarkable about Dumi’s approach: he didn’t immediately start building. Instead, he validated market demand the scrappy way.
Before a single line of code was written, Dumi created a landing page on Wix. He wrote copy highlighting the core value proposition: streamline workflow, record, edit, publish, and monetize in one place. Then he ran small Facebook ad experiments—$50 at a time—driving traffic to the page with a critical question at the bottom: “Which of these features matters most to you?”
The response data became his north star. People were signing up and selecting specific features they actually wanted. Dumi would iterate on the messaging, tweak the variables, run another experiment, and track which positioning resonated most.
“I did three or four experiments and went back to the one with the best result,” he recalls. “That validated market demand before we even thought about architecture or engineering.”
This is classic lean startup methodology, but it’s worth emphasizing because so many founders skip it. Dumi had the conviction to test his hypothesis cheaply and quickly, letting real user behavior—not his assumptions—guide the product direction.
The MVP Tradeoff: Picking Your Lane
Once Dumi had validation, the real challenge emerged: what should the first version actually do?
The podcast production workflow involves multiple distinct jobs—recording, editing, hosting, publishing, and monetization. Building all of those simultaneously would have been a recipe for mediocrity across the board. So Dumi and his team made a deliberate choice: focus on the highest-friction point first.
That was editing.
“If editing is cutting words and removing background noise, those were the recurring pain points we kept hearing,” Dumi explains. “But the tradeoff was clear—if we’re only building editing, we’re not solving recording or hosting. That works for some people, but it creates a gap for others.”
And that gap was real. Creators who already had a podcast in motion could use Hilite for editing. But someone starting from scratch hit a dead end: “Where do I record?” This fragmentation defeated the original problem Hilite was meant to solve.
It’s a reminder that early-stage product decisions are inherently about tradeoffs. You can’t solve everything at once. The key is being conscious about what you’re choosing to solve and what you’re consciously deferring.
“We knew we could get some validation, learn from customers, and then determine what to build next,” Dumi says. “That’s how you build a complete product over time, not all at once.”
Building the Roadmap With Real Data
With validation in hand and a focused MVP, Dumi faced another critical decision: how do you prioritize what to build next?
This is where his co-founder Paul became invaluable. While Dumi excelled at customer discovery and understanding pain points, Paul brought technical product thinking. Together, they did something simple but powerful: they extracted user stories and pain points from all the customer interviews Dumi had conducted.
They clustered these insights, identified patterns, and built documentation around specific features and requirements. That data-driven roadmap became their North Star—a clear sequence of what to build with limited resources while they pursued funding.
“We had editing first, then publishing, then recording, with a few other core elements,” Dumi explains. “But the main constraint was always: what can we build with the resources we have while we raise money and grow the user base?”
This disciplined approach prevented the classic founder trap of chasing every shiny idea. Instead, every feature decision traced back to customer feedback and strategic sequencing.
The Trust Factor in Building Teams
As Hilite evolved from an MVP to a real product, Dumi needed to build a team. His first hire was obvious: Paul, his co-founder from grad school. But they’d actually known each other since undergrad in Scotland—a friendship forged years before they ever considered building a company together.
“Trust is the core element of great teams,” Dumi emphasizes. “That was number one. Secondary to that was complementary skillsets.”
The team structure emerged naturally from their gaps. Dumi owned customer conversations and market understanding. Paul focused on product definition and engineering leadership. They hired front-end and back-end engineers, spending months finding the right people who both had strong technical skills and fit the team’s culture.
The lesson here is subtle but important: founding teams aren’t built on resume optimization. They’re built on trust, complementary strengths, and shared conviction about the problem. Dumi could have hired the most brilliant engineer he found in week one. Instead, he spent months finding people who understood the mission and could work together effectively.
From Personal Frustration to Creator Infrastructure
What started as Dumi’s personal pain point—wanting to tell stories without wrestling with broken tools—evolved into a platform that’s now helping creators across the world.
The journey from Zimbabwe in Voices to Hilite illustrates something important about startup founding: the best ideas often come from genuine problems you’ve experienced yourself. Dumi didn’t theorize about podcast production friction. He lived it. He felt it. And that conviction carried him through the hard work of validation, iteration, and team building.
Whether you’re building creator tools, SaaS infrastructure, or anything in between, there’s a lesson in Dumi’s approach: start with real problems, validate before you build, make conscious tradeoffs, and surround yourself with people you trust.
Want to hear the full story? Listen to the complete episode with Dumi Mabhena on Code Story to dive deeper into how Hilite is architecting frictionless creator infrastructure, the early scaling challenges they faced, and what’s next for social commerce in the creator economy.