# Adam Call D9688 Class: Customer Recording: https://drive.google.com/file/d/127Kap2AMbuPGT7dfJ1C59kdOCSd65UeG/view?usp=share_link # Call Plan 1. Introduce scope of call. 1. I am making a service to make it easy for startups to develop online apps. By online apps, I mean apps where users can sign up, sign in, save to and read from a database in the cloud, message one another, and get push notifications from the server. Unlike apps that run within a single device, such online apps run on a system of multiple services, such as a frontend client, a web server, and a database. I learnt it’s taking even technical founders 3 to 6 months to build their first version of their apps, because even people who studied CS for years in college, or even worked as a software engineer at a large company, don’t get to learn the full stack. Unlike a course assignment or a company project where they can focus on writing one feature, and all the other parts are set up by others, startups need to make everything on their own. So I want to give a centralized infrastructure to multiple startups so that they can focus on app’s unique features, rather than reinventing the same database and the same server that thousands of other founders are reinventing every year. 2. Ethan let me know that you are a founder working on an app yourself! I wanted to hop on a call, first of all, to get to know you, so we can each have more founder friends, then to understand what you are making, what your journey has been so far, and to get your feedback on how Junwon App Platform will work. 3. Is there anything else you want to add to our agenda? 2. First, I want to make sure I understand Vestr correctly. I read your landing page and tried out your app. 1. My current understanding is that Vestr is a social media for investors. A user can get news about companies, but more importantly, subscribe to creators who share what they are investing, and maybe news articles they want to relay to their followers. I imagine a user will pay some membership fee every month to follow a user, like Substack, and you will take a cut of this fee. Is my understanding correct? 2. What stage are you in today? How many users do you have? 3. How did you make the current app? What is the tech stack? 1. How long did it take you to get there? 2. What is next milestone? 4. What engineering problems are you facing today? What is your mitigation plan? 1. What problems do you expect to face on your way to your next milestone? What is your mitigation plan? 2. What problems do you expect to face a year later? Multiple years down the road? 5. Junwon App Platform lets developers focus on writing React components that users see and touch, such as pages and buttons, instead of spending time configuring, deploying, and integrating all the other parts, like backend servers and real-time databases. It is a CLI tool. Developer runs, junwon create APPNAME to make a new git repository. In the git repository, there are two folders: app and platform. In the platform folder are the files that provide a skeleton for the frontend to route the user, files to work with the database, files that abstract away cloud services to make it possible for developer to easily send push notifications to users, or deliver messages from one user to another. Developer works just in the app folder. The developer can write React components to be on the frontend, and server-side functions to run on the backend, and, right out of the box, authenticate users, send push notifications, save to the cloud database, without setting anything up separately. Does this make sense so far? 1. The immediate value prop is that developers can launch in a day as opposed to in 3 to 6 months. But the more important value prop is what happens after that. Developers don’t have to hire infrastructure teams, because I am combining infrastructure needs of many companies, and solving it once really well for all the customers there are and there will be. Kind of like the Shopify model. For example, if I can combine demands of 100 companies, I can negotiate a favorable term with the database providers, and distribute cost savings to the customers while also taking a healthy profit myself. Repeat this for web servers. I can make mobile apps and add features like offline mode. I can make it once really well, maybe using 10 times the capital that a single startup may be able to, since 100+ startups can share the benefits of that great mobile app client and features, so after all is said and done, I can spend 10 times the cost and still generate 10 times cost savings in total. Any questions? 2. Finally, I flip the cash flow to let developers make money first. Today, a startup first makes an app without making any money from the users. During this time, the startup is spending money, either founder’s time or by hiring engineers, and making no money. Hopefully, the app will take off, and the startup will be able to find a good revenue model, and the months or years of pain will pay off. I want to flip it so that developers can give app to users on day one. Then instead of paying 100,000 on a frontend engineer and another on backend, pay just 1 cent per user per day, so if the app does not take off, developers do not lose a ton of money, and if the app does grow, then developer can make that much more money before making the larger payment. This way, developer pays more, but has made more, so developers have nothing to lose. 3. Would this be a solution to your problem? 6. Invite to Advance Engagement. # Call Review - $50K over 6 months for engineers in India.