<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Quinten Vandermeulen on Medium]]></title>
        <description><![CDATA[Stories by Quinten Vandermeulen on Medium]]></description>
        <link>https://medium.com/@quintenvandermeulen?source=rss-67679fc973b1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dk-LoxalYygXDLP3kn2AQQ.jpeg</url>
            <title>Stories by Quinten Vandermeulen on Medium</title>
            <link>https://medium.com/@quintenvandermeulen?source=rss-67679fc973b1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 14 Nov 2026 18:24:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@quintenvandermeulen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[19 reasons that killed our app startup — a post mortem]]></title>
            <link>https://medium.com/@quintenvandermeulen/19-reasons-that-killed-our-app-startup-a-post-mortem-a68c0e43235b?source=rss-67679fc973b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a68c0e43235b</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[failure]]></category>
            <dc:creator><![CDATA[Quinten Vandermeulen]]></dc:creator>
            <pubDate>Tue, 17 Sep 2019 05:56:01 GMT</pubDate>
            <atom:updated>2022-01-11T13:03:29.597Z</atom:updated>
            <content:encoded><![CDATA[<h3>19 reasons that killed our app startup — a post mortem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhJL0VLWkRPQwRu0MXx6oA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@download-a-pic-donate-a-buck-8721?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Download a pic Donate a buck! ^ </a>from <a href="https://www.pexels.com/photo/black-and-white-man-young-lonely-48566/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>After almost 2 years, our app startup Moovle failed.</p><p>There were a lot of factors that gave us an advantage. We were ambitious, had a great idea, very complementary skill sets, learned from our competitors, won a startup competition and we got along pretty well.</p><p>So where did it all go wrong?</p><p>These are the lessons from the post-mortem autopsy of our app startup:</p><ol><li>Don’t care too much about the product. Care as much about your distribution</li><li>Release… now. If you don’t feel ashamed when you release, then you released too late.</li><li>Co-founders must have the same risk appetite. Ask them on a scale of 1–10 how risk-taking they are. Their score should be close to yours.</li><li>Don’t strategize too much about things too far away in the future. You are not there yet. You just need to hustle and go fast until you reach product/market fit</li><li>Watch out for feature creep. Don’t compete on the number of features, compete on user experience</li><li>Technical people need to have an obsession with the problem you’re solving. When things get messy, obsession will make that well-paying corporate job less attractive</li><li>Without a goal, you can’t score. Repeat your vision and big goal over and over again. It’s hard to remain inspired if you forget what you’re striving for</li><li>Talk with your co-founders about the team’s failures and confidence level. Don’t ignore it or the bubble will burst</li><li>Starting on the side is great, but don’t wait too long to go fulltime. At a certain moment, you have to jump. I’d say 6 months is a milestone</li><li>Don’t lose yourself in marginal A/B testing and UX optimizations as long as you haven’t reached product/market fit. A green or red button won’t make your product must-have, they will only make a must-have even better</li><li>If your team works remotely, make sure to check-in often enough with the whole team. It’s hard to build a culture without seeing each other</li><li>Developers are not just executors. In an early-stage team, everyone should do everything</li><li>Use SCRUM. Don’t start writing a single line of code without first having a Definition of Ready</li><li>Build discipline, there’s already enough chaos in a startup. Following frameworks frees up time and brain space</li><li>Focus on what matters. Define your One Metric That Matters and track it. That will be your north star</li><li>Co-founders must be optimistic realists. Not every app has an Instagram-like growth curve from day 1. Manage expectations</li><li>Surveys are fake. They don’t work unless you have more than 300 (good) responses. Don’t invest your time in this</li><li>Products are real. Don’t release anything without tracking data. Even with 50 users, there’s a ton to learn from your data</li><li>Use design sprints and build prototypes. Building and testing a prototype takes 10% of the time of making an actual product but delivers 80% of the same learnings</li></ol><p>This is advice for every first-time founder out there.</p><p>Or as Warren Buffet says: <em>“You want to learn from experience, but you want to learn from other people’s experience when you can”</em></p><p><em>If you enjoyed this post, then please give it some claps and share it with your friends.</em></p><p><em>I’m a trilingual product strategist and banking consultant. Failed an app startup but learned a ton. I’m passionate about consumer startups and the future of banking. Connect with me on </em><a href="https://www.linkedin.com/in/quintenvandermeulen/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a68c0e43235b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to (re)design an app in 2 weeks — a UI/UX Case Study]]></title>
            <link>https://medium.com/mytake/how-to-re-design-an-app-in-2-weeks-a-ui-ux-case-study-36d3313d19a4?source=rss-67679fc973b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/36d3313d19a4</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Quinten Vandermeulen]]></dc:creator>
            <pubDate>Sun, 15 Sep 2019 22:06:01 GMT</pubDate>
            <atom:updated>2019-10-11T18:23:23.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to (re)design an app in 2 weeks — a UI/UX Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAnDI17Dfc17FD-vfQOrpQ.png" /><figcaption>Our redesigned football matchmaking app</figcaption></figure><h3>0. Introduction</h3><p>Over a year ago, our startup Moovle launched its app to the public. Our first MVP functioned well and we received a lot of useful feedback. But we went a little quick and dirty in the development without taking any scalability or design guidelines into account. As a side project, we decided to entirely redesign our app. The people who worked on this were <a href="https://www.linkedin.com/in/quinten-verniers/">Quinten Verniers</a>, <a href="https://www.linkedin.com/in/joris-saenen/">Joris Saenen</a> and <a href="https://www.linkedin.com/in/quintenvandermeulen/">myself</a>.</p><h4>The product</h4><p>Moovle is a football (or soccer, for our American friends) matchmaking app that helps you find football games, teams &amp; players in your city. Our mission is to connect football players and help them save tons of time in organizing their games. Call it the “Tinder for football”.</p><p>(<em>Note: as I publish this article, Moovle does no longer exist. We ceased operations and wanted to show a little ‘behind the scenes’ with this article)</em></p><h4>The challenge</h4><p>Completely redesign the old app in 2 weeks. We worked after-hours of our corporate job.</p><h4>The process</h4><p>These were the steps we followed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*abIt2dXhLKLMTvFHWv3tew.png" /></figure><h3>1. Research</h3><p>Start with the problem, not the solution. To fully understand the problems our users were facing, we took a deep dive into all the received feedback, organized the pain points and made user personas.</p><h4>Pain points of the football experience</h4><p>I experienced it myself, so I know how frustrating it is to find enough football players for a casual game. To understand the problem even better, I went to parks and football venues and started talking to people playing football. I was quickly added to many Facebook and WhatsApp groups of people fancying a game. Proposals to play quickly ended up in endless conversations like these:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nspwpYnnFJ5Y_oIR6VsuPA.png" /></figure><p>Both the face-to-face conversations and the group chats quickly exposed the following key issues:</p><ul><li>Finding enough football players for a game is frustrating</li><li>People don’t know where nearby football activity is going on</li><li>It is a hassle to find available football venues</li><li>It takes a lot of time to organize and inform attendees</li><li>Facebook and WhatsApp groups are inefficient alternatives and not tailored to football needs</li></ul><h4>Pain points of the old app</h4><p>We already had an app to solve the problems above. That app also had its problems:</p><ul><li>Users joined games but didn’t <em>create</em> enough games</li><li>First-time users needed a push to join their first game. Once they played a game via the app, they became recurring users</li><li>We launched during the Cambridge Analytica scandal and our app only offered sign up via Facebook. Many people didn’t want to use Facebook authentication</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPi1nIJiC8BUdl3aVdnUsw.png" /><figcaption>This is how our old app looked like, before the redesign</figcaption></figure><h4>Personas</h4><p>Based on the research, we created user personas. They help to increase empathy and put the entire team in the shoes of the user. This was one of them:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_MZful3CGocf52hXw5sQg.png" /></figure><h4>Objectives of the redesign</h4><ul><li>Create a frictionless onboarding to activate first-time users</li><li>Improve the game creation experience to increase the supply of games</li><li>Apply a consistent look and feel that is aligned with our image</li></ul><h3>2. Ideate &amp; sketch</h3><h4>Inspiration board</h4><p>Instead of trying to reinvent the wheel, we looked at other, non-related apps to get some inspiration. They all did a specific thing extremely well. Either a call-to-action, an animation, design style, conveying a feeling,…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*jKPVN2eZDcA7YmYXrdoAPg.png" /></figure><h4>Exploring scenarios</h4><p>Then we started brainstorming, playing around with ideas and sketching multiple scenarios. You want to consider your options before committing to a final scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djBppiBOjHBLJ69WgUzhYw.png" /></figure><h4>Deciding the scenario</h4><p>Having concrete, visual sketches makes it easier to estimate a feature’s chances of success. We used silent dot voting to decide on our favorites and avoid debate. This is a hard part because you feel like you are letting go of a lot of good ideas. Document those for later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cciHW5PE10eNZUsZdYNIPA.png" /></figure><h3>3. Prototype</h3><p>After sketching, it’s time for prototyping. We made clickable mockups with the Figma tool (which I highly recommend!). One of the objectives was to apply a consistent look and feel. Therefore, we first made a design style guide or library.</p><h4>Icon style</h4><p>Moovle is a social football app, focusing on team spirit and the fun of the game. We are about people, so we needed a joyful image. Flat design gives that informal touch. Monocolor, linear icons keep the design clean. Non-filled icons make the view less heavy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*kW42Np6q_wMT0_csBr07oQ.png" /><figcaption>Icons on <a href="https://www.flaticon.com/home">Flaticon</a></figcaption></figure><h4>Font style</h4><p>In line with our icon style, we chose a font with soft corners. Dosis is a free Google font that is informal, yet readable. We created a font library to avoid a cacophony of different font sizes and types.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*QB4vwBuxXA-hN2Z9VfvBaw.png" /></figure><h4>Color palette</h4><p>Football is passion. Passion is red. To avoid an aggressive tone, we took a soft red and compensated it with a calming blue and grass green as secondary colors. We used black for text, grey for icons and white as a clean background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EM6AA8WT1zD-Wc99dMyzMQ.png" /></figure><h4>Design iterations</h4><p>Using our top voted sketches as a base, we started creating prototypes. We had 2 internal design feedback sessions to refine the prototype before testing it with users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KkiJt0BxAZ6c_E1LYvpbDg.png" /></figure><h4>Final designs</h4><p>We redesigned the 3 most crucial user flows: getting the user onboard, letting him search for a football game and giving the option to create a game.</p><p><em>Onboarding flow</em></p><ul><li>As we saw during our app launch, fewer and fewer people want to sign up for an app via Facebook. Phone number and email signup are on the rise so we needed to offer multiple authentication options.</li><li>Increasing public awareness around privacy and mental health is moving people to disable location access and push notifications for apps. Answering these concerns required a clear call-to-action, providing the necessary context on why we needed to have location access and when we would send notifications.</li><li>We removed the onboarding walkthrough to focus on speed. People are annoyed by walkthroughs and skip them. If your app is straightforward, you also don’t need one</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4uaGimhIecZFw_5ORUVvA.png" /></figure><p><em>Search game</em></p><ul><li>The most crucial decision factors to join a game are <em>time</em> and <em>location</em>. These factors needed to stand out from the other data when scanning the list of games</li><li>To push the user to the aha-moment of participating in a fully booked game, he needs to find a suitable game fast. Therefore, we included directly accessible filters (no extra click required) and a map view to easily customize their view</li><li>Nearly fully booked games need to have some extra promotion to avoid disappointment when a game falls short of just 1–2 players. We stressed the scarcity for games with less than 3 spots left</li><li>Virality is crucial for a hyper-local social network like Moovle. So we included a sharing feature</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xFIeaCXaIljoIshXef84Tw.png" /></figure><p><em>Create game</em></p><ul><li>People who create games provide the supply side of the app. They will define our app’s success. The challenge was to find the sweet spot between asking enough game information so other people would join, and not overcomplicating the process</li><li>Our objective was that a user could create a game in less than 60 seconds. We limited the number of clicks and the text input</li><li>We used a step-by-step flow instead of a fill-in list to give the feeling of progress and speed</li><li>The flow needed to be personal and conversational, so we asked questions (‘When will this amazing game take place?’) instead of impersonal commands (‘Enter date’)</li><li>Remember that 1 of our 3 objectives was to improve the experience for first-time users? We added a little personalization for these people by addressing them with their first name</li><li>To increase the supply of games, we created an option to let a game automatically recur every week since many people play weekly on a fixed moment</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDF1rsecPb5aS-9kiuHOfQ.png" /></figure><h3>4. User test</h3><h4>Recruiting</h4><p>According to Jakob Nielsen, <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">you need 5 user tests to get to 85% of your product’s insights</a>. I recruited both existing users from the old app and new people via Facebook groups about football. Both groups fitted the target audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*lXCflQo4_b8EZ9_xm6SZJg.png" /></figure><h4>Tasks</h4><p>I started the user test by letting the tester talk about his background, then I proceeded to the following 3 user tasks. I observed the tester’s actions very closely and kept on drilling down on topics until I fully understood the tester’s reasoning.</p><ol><li>Can you sign up for the app? What signup method do you prefer and why?</li><li>Can you join a game that you are interested in? What factors make a game interesting for you?</li><li>Can you create a game? In which situation would you decide to create a game?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*ISDkyJR2XOdG9h9o.gif" /><figcaption>I recorded the user tests so my team members could learn as well. This tester agreed to be featured in this article.</figcaption></figure><h3>5. Conclusion</h3><h4>Learnings from user tests</h4><ul><li>The list view and map view with all the games were very well understood. Participants could find a suitable game very efficiently</li><li>Surprisingly, an important decision factor was the number of comments on a game. Comments increased the credibility of the game and showed engagement</li><li>People were overwhelmed by information on the details page of the game</li><li>It was unclear where the entry point was to create a game</li></ul><h4>Next steps</h4><p>A next UX refinement should be organized to take up the usability issues and validate the new UX with an extra wave of user tests. We will continue to test and refine iterations until we reach a certain level of saturation. Once we have that, we should start coding.</p><h4>Final notes</h4><p>This case study was an excellent mix between product strategy, creativity and actual hustling. I was surprised about how efficient we were. In a matter of 2 weeks, working after-hours, we managed to completely redesign and radically improve our app. Personally, the most fun part for me was the user testing. Meeting with users is so incredibly powerful. It keeps you going to see you’re solving relevant problems in people’s lives!</p><p>Thanks for reading!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*wXIaeSQLp07nP47M.gif" /></figure><p><em>If you enjoyed this post, then please give it some claps and share it with your friends.</em></p><p><em>I’m a trilingual product strategist and banking consultant. I’m passionate about consumer startups and the future of banking. Connect with me on </em><a href="https://www.linkedin.com/in/quintenvandermeulen/"><em>LinkedIn</em></a><em>.</em></p><p><em>Our startup failed but if you have the dream of connecting football players yourself, then please contact me. I truly hope someone can fix this problem for those millions of football players out there and I would be more than happy to help.</em></p><p><em>Special thanks to the authors of the icons and illustrations I used in the designs!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36d3313d19a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mytake/how-to-re-design-an-app-in-2-weeks-a-ui-ux-case-study-36d3313d19a4">How to (re)design an app in 2 weeks — a UI/UX Case Study</a> was originally published in <a href="https://medium.com/mytake">MyTake</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Big Belgian Banks (or How Revolut disrupts by starting with the basics)]]></title>
            <link>https://medium.com/@quintenvandermeulen/big-belgian-banks-or-how-revolut-disrupts-by-starting-with-the-basics-c664b3d05908?source=rss-67679fc973b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c664b3d05908</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[banking]]></category>
            <dc:creator><![CDATA[Quinten Vandermeulen]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 09:21:01 GMT</pubDate>
            <atom:updated>2019-10-21T18:39:13.510Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the best indicators to see how thoughtful a company is about their customer experience is to look at their onboarding flow.</p><p>Onboarding flows are too often underestimated. It’s the most crucial flow in your whole product.</p><p>Mess up the onboarding and your activation rates will plummet.</p><p><strong>So I put the onboarding flows of 4 Belgian banks to the test. Then I compared them with Revolut.</strong></p><ul><li>Mobile bank of incumbent A: “mobile” bank but not possible to onboard via their app. A courier came by to scan my ID card, wrongly scanned it, then didn’t show up for a new appointment. Eventually sent a scan of my ID by email after a long debate with customer support. <br><strong>Onboarding time: 2 months</strong></li><li>Incumbent B: asked to send a paper copy of my ID by post. The last envelope I’ve sent was 5 years ago. Decided I wouldn’t invest my time in this.<br><strong>Onboarding time: DNF</strong></li><li>Online bank C: went through the eID flow 3 times because it kept blocking, received my card and PIN 3 weeks later. If I wanted to change my PIN, I needed to go to an ATM. That’s truly “online”<br><strong>Onboarding time: 1 month</strong></li><li>Incumbent D: fairly easy online authentication. Got my debit card the week after. Overall good job.<br><strong>Onboarding time: 1 week</strong></li><li>Revolut: took a picture of my ID card and created PIN myself. Could immediately pay with Apple Pay and received my card 2 days later. Oh, the card also came in great packaging. Made me smile.<br><strong>Onboarding time: 6 minutes</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8FtFuwssWAgEBP3MI950cg.png" /><figcaption>Icons from <a href="https://www.flaticon.com/free-icon/bank_189056">Roundicons</a>, <a href="https://www.flaticon.com/free-icon/smartphone_148998">Smashicons</a> and <a href="https://www.flaticon.com/free-icon/computer_164998">Freepik </a>on <a href="https://www.flaticon.com/home">Flaticon</a></figcaption></figure><p>See the difference? That’s the start of a disruption that will only spread.</p><p>Revolut understands well where to start the disruption. In a user flow that matters.</p><p>The onboarding.</p><p><em>If you enjoyed this post, then please give it some claps and share it with your friends.</em></p><p><em>I’m a trilingual product strategist and banking consultant. Failed an app startup but learned a ton. I’m passionate about consumer startups and the future of banking. Connect with me on </em><a href="https://www.linkedin.com/in/quintenvandermeulen/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c664b3d05908" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we won Belgium’s top startup competition for students]]></title>
            <link>https://medium.com/@quintenvandermeulen/how-we-won-belgiums-top-startup-competition-for-students-41ff5db168a1?source=rss-67679fc973b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/41ff5db168a1</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[pitching]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Quinten Vandermeulen]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 14:01:02 GMT</pubDate>
            <atom:updated>2019-09-09T14:01:02.027Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s September, that time of the year when students go back to college.</p><p>It reminds me of my last year at Ghent University, in 2017, when I got bitten by the startup bug.</p><p>I was writing my thesis about Silicon Valley, wrote a business plan for a class on entrepreneurship and then decided to enter the <a href="https://www.start-academy.be/">Start Academy for Young Entrepreneurs</a> competition. With past jury members such as Marc Coucke, Martine Reynaers and many others this was a great way to see where we would stand.</p><p>Against all expectations, we made it through the first 3 selection rounds to eventually end up in the big final, where we went home with the 1st prize and a cheque of a few thousand euros.</p><p>Winning Belgium’s finest student startup competition was no matter of luck. It was a matter of mastering the basics.</p><p>This is how we did it:</p><h4>1. Show you’re making progress</h4><p>The jury can quickly filter the “wantrepreneurs” from the entrepreneurs based on how much they already accomplished in a certain frame of time. Every selection round, we analyzed the jury’s feedback, decided what was worth improving and then went to work on that. In the next round, they would see we were not only good listeners, but we could also get things done.</p><h4>2. Be energetic</h4><p>I once talked to a VC who told me they paid attention to the energy level of the pitching founders. Energy translates drive and passion. Those are crucial ingredients to get a startup off the ground and through down moments.</p><h4>3. Pay attention to the economics</h4><p>Don’t show any ridiculous hockey stick growth curves. Everyone knows they are useless. Instead, show that you thoroughly thought through your financials. Also, don’t dive into deep details here or you’ll lose your audience. Detailed tables and numbers are for your annexes. High-level revenue streams and basic numbers are for your pitch.</p><h4>4. Your pitch is everything</h4><p>You absolutely need to nail this part. You might have the best business idea and be great executioners, you’ll never convince investors or partners if your pitch is just moderate. In short: show you have a great team and sell the problem, not the solution. Do this while telling a story. It was no coincidence that next to the overall victory, we also won the prize for the best pitch.</p><h4>5. Enjoy the journey</h4><p>You’ll meet great people and interesting guest lecturers. Being around likeminded people with a dream is something very empowering. Enjoy the conversations with other contestants. Remember those awesome guest talks. Relish the deadline rushes. Heck, even enjoy the moments when a coach tells you your idea is worthless!</p><p>Master these elements, and it will get you far.</p><p>Start Academy was the kick-off of my entrepreneurial journey and I’m super grateful I participated. Even though our startup failed afterwards, the journey shaped me to become a better entrepreneur.</p><p>A big thank you to <a href="https://www.linkedin.com/in/tjorvendenorme/">Tjorven Denorme</a> for the mentoring, <a href="https://www.linkedin.com/in/thomasdhooge/">Thomas D’hooge</a> for constructively destroying our pitch so we could build it back up again properly, <a href="https://www.linkedin.com/in/kennywillems01/">Kenny Willems</a> for telling us how to build a financial plan, <a href="https://www.linkedin.com/in/ruben-monballieu-3787294/">Ruben Monballieu</a> for bringing us back to the essence, <a href="https://www.linkedin.com/in/lothardekeyne/">Lothar De Keyne</a> for teaching us how to pitch and of course <a href="https://www.linkedin.com/company/vlajo/">Vlajo</a> for organizing the competition. Even after 2 years, I’m still reaping the benefits of your advice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V8qd9YW3BFRLEdHk_3N0Qw.png" /><figcaption>Proudly posing with the jury members and our victory cup</figcaption></figure><p>Watch the after movie from the final <a href="https://www.youtube.com/watch?v=7dGCff4yfDc">here</a>!</p><p>If you enjoyed this post, then please give it some claps and share it with your friends.</p><p><em>I’m a product strategist and banking consultant. Failed an app startup but learned a ton. I’m passionate about consumer startups and the future of banking. Connect with me on </em><a href="https://www.linkedin.com/in/quintenvandermeulen/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41ff5db168a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>