Delivery Hero is one of the largest food delivery companies in the world, partnering with over half a million restaurants in 70 countries, including Greece and Cyprus, where Evangelos Foutakoglou leads the consumer-facing product team.
Evalngelos’ team is responsible for designing, launching, and driving the adoption of key features of the Delivery Hero app. With Lovable, he’s able to streamline the traditionally lengthy process of stakeholder alignment, getting from idea to production in less than half the time.
A couple of months ago, Evangelos was heading into a meeting with one of their customers to talk about about integrating its loyalty rewards program into the Delivery Hero app. The business team briefed him on the issue a few hours beforehand: Their customers are technically allowed to redeem rewards points in Delivery Hero, but many users are unaware of this offering, leading to low adoption.
Evangelos didn't have much time. He knew what he wanted to build: a simple prompt at checkout to redeem reward points, along with a reminder for users who hadn't opted in yet.
He opened Lovable and built a working prototype in one hour.
During the meeting, he didn't just walk through the concept or a few slides; he pulled up the prototype and let his customers use it. The bank reps clicked around, saw where their logo would sit, and got the experience immediately. They provided meaningful and specific feedback, achieving directional alignment in just a matter of minutes.
Then he sent the link to internal teams. Engineering, design, and analytics could all pressure test it, see how their feedback would actually look, and spot implications that would've taken another week of document revisions and meetings to catch. "Something that would have taken about three weeks took one week," Evangelos says. "About one third of the time."
Lovable didn't only serve to speed up the process, it also made for a more delightful product. When people interact with the actual feature instead of commenting on your description of it, you get higher fidelity feedback and better products.
Getting everyone on the same page regarding a new feature usually takes weeks. Most product managers are familiar with the typical process of getting a feature into the build pipeline: You have a clear vision for what needs to be built, but before you can start, you need to obtain buy-in. So you write a painstakingly detailed PRD (product requirements document), share it with others, schedule calls, wait for feedback, revise, schedule more calls, and repeat. Engineering needs a week to review. Design has questions. Business wants clarifications. External partners need their own round of back-and-forth.
Nobody's trying to be difficult; it's just that a document fundamentally requires interpretation, and often written requirements mean something different to everyone who reads them. By the time all the stakeholders weigh in, ambiguities become blockers, weeks have passed, and nobody's entirely sure if they're still discussing the same thing.
Evangelos doesn't write docs anymore, or at least he doesn't start with them. When he kicks off a new project, he builds a working prototype with Lovable. "I might write something in a PRD, and you might understand something different," he says. "But with an interactive prototype, we have a common ground that's undisputable."
The point isn't replacing engineers or shipping prototype code to production. It's about shortening the time it takes to green-light features for development. As Evangelos puts it: "By inviting other people into my Lovable project, they had the chance to see my problems and my thought process. Not only did they have access to the solution, but also to the problem itself and how I approached it."
Lovable is how he turns lengthy product docs into something visceral that stakeholders can react to in the moment. All the PMs in his org already use Lovable to drive alignment, and Delivery Hero is exploring broader rollout across the product and partner teams.
Evangelos is enhancing the traditional PRD with Lovable. "I'm pushing an AI-first, prototype-first culture on my team," he said of the future.
