Speaker: Mike Wilner, Startup Business Development, Amazon Web Services
Is raising venture capital right for you? Join this session to learn about the process that serial founders execute with fundraising. Discover how to prospect the right investors, make contact and frame a fundraising narrative, and generate a sense of urgency with investors to close your round as quickly as possible. Make sure you can fundraise like the most experienced founders to avoid dragging it out.
Moderator: Jerrod Hill, VC Business Development, Amazon Web Services
Panelists: Nyla Koncurat, Managing Partner, Karlani Capital
Elizabeth D. Sigety, Esq., Director, Co-Founder, Delaware Crossing Investor Group
There's no perfect pitch deck. However, there are elements every investor will be looking for, and that your deck better have. If you are in the school of, “Why do I need a pitch deck at all?” it's time to change your thinking. A spiffy series of slides won't magically get you investors, customers, or those critical early hires. But it's a way in, especially for novice entrepreneurs. In this talk we'll cover what’s critical in a deck, what’s best left out, and how to combine everything to tell a compelling story about yourself and your startup.
The document discusses the importance of customer development for startups. It emphasizes the need to discover customers' problems through interviews and validate any product ideas before building. The key steps outlined are customer discovery, where the focus is on understanding customer needs without demos; and customer validation, which involves testing solution concepts and business models directly with customers. Throughout, it stresses really listening to customers, getting outside the building to conduct interviews, and making reversible decisions quickly through a process of continuous learning and iteration.
Speaker: Alejandra Novack, Developer Relations, Amazon Web Services
Early stage startups are time and resource constrained and they need to quickly get to product market fit. In this session you’ll get an overview of how startups build MVPs using services like Amazon API Gateway, AWS Amplify, AWS Lambda, Amazon EKS, Amazon Lightsail, and database options. After this session, you’ll be able to pick the right technologies and use pre-configured architectures to speed up your development.
The document discusses best practices for creating effective pitch decks to present startup ideas to investors. It provides examples of pitch decks from successful companies like Airbnb and LinkedIn that emphasize clearly explaining the problem, solution, and business model. It also stresses the importance of demonstrating growth and traction as well as having a strong founding team. Common pitfalls to avoid include not having a clear thesis, including too much unrelated content, and failing to address typical concerns about the business. The key is to iterate the pitch deck while focusing on conveying the core of the startup idea rather than overly focusing on design.
The document discusses tools for building minimum viable products (MVPs) on Amazon Web Services (AWS). It recommends starting with the simplest possible solution, such as a static single-page web application using AWS Amplify. It also provides guidance on building microservices architectures and monolithic applications on AWS, emphasizing the ability to start small and scale easily. The document cautions against overengineering and emphasizes continuous delivery of working software to users.
The document discusses strategies for efficiently raising a seed round of funding. It begins by establishing ground rules for fundraising, such as dedicating one person to fundraising full-time and fundraising in parallel rather than sequentially. It also discusses crafting an effective fundraising narrative in 20 seconds or less that communicates what the company does, its most compelling feature, progress to date and future milestones. The document then covers prospecting an initial funnel of potential investors by working backwards from an ideal cap table structure.
This document provides an overview of databases, data warehouses, and data lakes on AWS. It discusses Amazon RDS for relational databases, Amazon Redshift for data warehousing, and data lakes on AWS. The presentation covers topics like database engines supported by RDS, high availability and scalability features, database backups and monitoring. It also summarizes Amazon Aurora which provides faster performance than traditional databases and Amazon Redshift which is optimized for analytics workloads.
AWS Initiate - A Cultura de Inovação da Amazon direcionada ao sucesso do ClienteAmazon Web Services LATAM
Amazon fosters innovation through a culture of customer obsession, hiring builders and empowering small teams to invent and experiment quickly. It uses mechanisms like working backwards from customer needs and embracing failure. Amazon's architecture supports this with microservices and self-service platforms. Together, Amazon's organizational structure, culture, mechanisms, and architecture multiply its innovative output.
Moderator: Jerrod Hill, VC Business Development, Amazon Web Services
Panelists: Nyla Koncurat, Managing Partner, Karlani Capital
Elizabeth D. Sigety, Esq., Director, Co-Founder, Delaware Crossing Investor Group
There's no perfect pitch deck. However, there are elements every investor will be looking for, and that your deck better have. If you are in the school of, “Why do I need a pitch deck at all?” it's time to change your thinking. A spiffy series of slides won't magically get you investors, customers, or those critical early hires. But it's a way in, especially for novice entrepreneurs. In this talk we'll cover what’s critical in a deck, what’s best left out, and how to combine everything to tell a compelling story about yourself and your startup.
The document discusses the importance of customer development for startups. It emphasizes the need to discover customers' problems through interviews and validate any product ideas before building. The key steps outlined are customer discovery, where the focus is on understanding customer needs without demos; and customer validation, which involves testing solution concepts and business models directly with customers. Throughout, it stresses really listening to customers, getting outside the building to conduct interviews, and making reversible decisions quickly through a process of continuous learning and iteration.
Speaker: Alejandra Novack, Developer Relations, Amazon Web Services
Early stage startups are time and resource constrained and they need to quickly get to product market fit. In this session you’ll get an overview of how startups build MVPs using services like Amazon API Gateway, AWS Amplify, AWS Lambda, Amazon EKS, Amazon Lightsail, and database options. After this session, you’ll be able to pick the right technologies and use pre-configured architectures to speed up your development.
The document discusses best practices for creating effective pitch decks to present startup ideas to investors. It provides examples of pitch decks from successful companies like Airbnb and LinkedIn that emphasize clearly explaining the problem, solution, and business model. It also stresses the importance of demonstrating growth and traction as well as having a strong founding team. Common pitfalls to avoid include not having a clear thesis, including too much unrelated content, and failing to address typical concerns about the business. The key is to iterate the pitch deck while focusing on conveying the core of the startup idea rather than overly focusing on design.
The document discusses tools for building minimum viable products (MVPs) on Amazon Web Services (AWS). It recommends starting with the simplest possible solution, such as a static single-page web application using AWS Amplify. It also provides guidance on building microservices architectures and monolithic applications on AWS, emphasizing the ability to start small and scale easily. The document cautions against overengineering and emphasizes continuous delivery of working software to users.
The document discusses strategies for efficiently raising a seed round of funding. It begins by establishing ground rules for fundraising, such as dedicating one person to fundraising full-time and fundraising in parallel rather than sequentially. It also discusses crafting an effective fundraising narrative in 20 seconds or less that communicates what the company does, its most compelling feature, progress to date and future milestones. The document then covers prospecting an initial funnel of potential investors by working backwards from an ideal cap table structure.
This document provides an overview of databases, data warehouses, and data lakes on AWS. It discusses Amazon RDS for relational databases, Amazon Redshift for data warehousing, and data lakes on AWS. The presentation covers topics like database engines supported by RDS, high availability and scalability features, database backups and monitoring. It also summarizes Amazon Aurora which provides faster performance than traditional databases and Amazon Redshift which is optimized for analytics workloads.
AWS Initiate - A Cultura de Inovação da Amazon direcionada ao sucesso do ClienteAmazon Web Services LATAM
Amazon fosters innovation through a culture of customer obsession, hiring builders and empowering small teams to invent and experiment quickly. It uses mechanisms like working backwards from customer needs and embracing failure. Amazon's architecture supports this with microservices and self-service platforms. Together, Amazon's organizational structure, culture, mechanisms, and architecture multiply its innovative output.
The Pitch - Essentials for Success, and Blunders to AvoidAmazon Web Services
The document discusses key elements of a successful startup pitch deck. It identifies problem, solution, business model, growth and traction, and team as particularly important sections. It provides examples of good and bad ways to present these sections. Additionally, it outlines seven common pitfalls to avoid, such as burying the main point or pretending to have no competition. The presentation emphasizes that the focus should be on clearly conveying your business idea rather than overly designing the presentation.
AWS Initiate - Security Framework Shakedown: Mapeie sua jornada com as melhor...Amazon Web Services LATAM
The document discusses best practices for security in cloud adoption and the AWS Well-Architected Framework. It covers defining a security strategy as part of cloud adoption, delivering a security program, operating robust security, controlling identity and access, enabling traceability, protecting the network layer, applying security across layers, and automating security checks and management. Specific AWS services referenced include AWS Organizations, IAM, GuardDuty, VPC, WAF, Config, and automation tools.
The document discusses strategies for efficiently raising a seed round of funding. It recommends establishing ground rules for fundraising including dedicating one person to the full-time role and fundraising in parallel rather than sequentially. The document also advises crafting an ideal cap table structure to create scarcity and urgency for investors. Additionally, it emphasizes the importance of developing a concise fundraising narrative that outlines company progress, future milestones, and vision in under 20 seconds.
This document discusses why startups choose to build on AWS. It notes that AWS allows startups to pay only for the resources they use without upfront costs, focus on their core business instead of infrastructure, and launch faster by having new IT resources available in a few clicks. This enables startups to experiment more and fail fast if ideas don't work. The document also shares statistics on the pace of innovation on AWS and lists some of the programs and resources available to help startups on AWS.
DevOps is currently one of the most sought after engineering models. One reason is that it helps enterprise transformations. The Amazon transformation to DevOps was born out of the desire to be even more customer obsessed, more agile, and more innovative. Come and learn from our journey as we share the playbook that helped us successfully implement and adopt DevOps as well as the lessons we learned the hard way.
The document discusses a general purpose serverless IoT platform for builders created by SoftChef Corporation. It addresses issues with traditional IT like costs, time constraints, and lack of resources. The platform aims to provide fully serverless IoT applications that are plug and play with easy expansion between central and edge computing. It also benefits from partnerships in a Joint Innovation Center and support from AWS.
This document discusses how a Taiwanese real estate startup called Leju used AWS to accelerate development of their MVP for property price queries and registration of actual transaction prices. It describes Leju's goals of increasing transparency of property prices and making information easier to read. It then outlines some of Leju's key milestones and features, including providing community average price maps, school district data, restoring address numbers, and integrating listings. The document also notes that AWS provided startups like Leju with infrastructure architects, subsidies, and other support important for non-technical founding teams.
The document discusses tools for building minimum viable products (MVPs) on Amazon Web Services (AWS). It recommends starting with the simplest possible solution, such as a static single-page web application using AWS Amplify. It also provides suggestions for building monolithic applications on AWS Elastic Beanstalk or decomposing them into microservices. The document outlines options for different data storage needs including relational, key-value, document, in-memory, graph, time-series, and ledger databases. It emphasizes measuring everything and designing with few components to get an MVP built quickly.
Amazon prioritizes innovation through a culture of customer obsession, long-term thinking, and a willingness to fail. They organize into small, empowered teams and provide mechanisms like working backwards to focus on customers' needs. Their architecture supports rapid growth through microservices and self-service platforms. This allows experimentation without constraints while empowering others.
OwlTing is a leading blockchain startup based in Taiwan that provides blockchain services and solutions. It has offices globally and strategic partnerships with large companies. OwlTing's services include OwlNest for hotel property management on the blockchain, OwlMarket for local products, and OwlExperiences for tour guides. These services provide benefits like preventing overbooking, enabling product traceability, and building trust. OwlTing has seen increasing use of Amazon Web Services for its flexibility, security, and performance.
The document discusses strategies for enterprises to transition to more frequent innovation and change like technology companies. It outlines several anti-patterns of traditional enterprise IT and new patterns that can help speed up delivery including: breaking up monolithic applications into microservices; investing in reskilling the workforce to be more customer-centric; automating security and compliance processes to match the speed of cloud; and building resilience by experimenting with failures instead of just planning for anticipated disasters. The overall goal is for enterprises to become "high-frequency" at delivering value through IT.
AWS Initiate Day Dublin 2019 – The Culture of Innovation at AmazonAmazon Web Services
The document discusses Amazon's culture of innovation and how it drives customer success. It emphasizes that Amazon prioritizes customer obsession, long-term thinking, willingness to fail, and being misunderstood for long periods of time. It also highlights how Amazon organizes for innovation through experimentation in small teams, a working backwards process from the customer, microservices architecture, and self-service platforms without gatekeepers. The goal is to decentralize innovation throughout the company and empower all employees to invent on behalf of customers.
AWS Initiate Day Dublin 2019 – Breaking down the MonolithsAmazon Web Services
The document discusses monolithic applications and microservices. It defines monoliths as traditional applications developed to best practices at the time that were not designed to be distributed. Microservices are defined as independently deployable services that work together and are modeled around business domains. The document discusses how Amazon transformed from monoliths to microservices and describes benefits of microservices like improved modularity, scalability, and faster release cycles. It also covers microservice design principles like bounded contexts and messaging patterns to connect microservices using services like SNS and SQS.
Paua Ventures is a Berlin-based venture capital firm that invests in B2B software companies addressing large markets with strong technical foundations. The presentation identifies four key trends in B2B software: 1) Everything is moving to the cloud, which provides challenges for large enterprises migrating systems; 2) Employees expect consumer-like experiences from enterprise software; 3) A growing cloud infrastructure opens more opportunities for cyber attacks; 4) Demand for microprocessors will increase dramatically with new devices like autonomous vehicles and drones.
The document discusses Amazon's approach to DevOps. It explains that Amazon needed to innovate rapidly to support thousands of teams making millions of deployments per year using microservices and continuous delivery practices. Amazon broke processes into fine-grained units and assigned them to autonomous two-pizza teams. These teams adopted agile methodologies and learned to work together across functions like development, operations, security, and quality assurance using a DevOps approach. Amazon also built shared tools, services, and best practices to support these teams in their DevOps journey.
The document discusses iVideosmart, a company that offers a smart video widget to easily integrate video content into any website. Their widget can automatically recommend relevant videos based on page content and convert views to video views. iVideosmart has over a billion pageviews and 200 million video views per month from their large network of premium video publishers globally. They utilize Amazon Web Services to scale their infrastructure and quickly prototype and process large amounts of data.
Why serverless will revolutionize your software process.James Beswick
Serverless fundamentally changes software development for both enterprises and startups - here's how it impact your process and how you can benefit. Presented at ITNext Summit, Amsterdam in 2019.
Security Framework Shakedown: Chart Your Journey with AWS Best PracticesAmazon Web Services
As with everything in life there is an easy way and a hard way when it comes to adopting security framework recommendations. Featuring the AWS Well-Architected and Cloud Adoption Frameworks, we will walk you through a complete security journey. We'll start with identification of requirements, then move through a series of how-tos from classifying your data, automating controls, to running fun incident response game days.
The document discusses Amazon Go, a cashier-less convenience store developed by Amazon, as a case study for using machine learning and IoT on AWS. It provides an overview of the challenges in building Amazon Go, including identifying customers and items taken for purchase without traditional checkout methods. It then discusses retail trends driving the need for AI and IoT solutions. The remainder of the document offers tips for developing AI and IoT projects, including focusing on business outcomes, considering related AWS services, and learning through hands-on projects to avoid prolonged analysis.
The document discusses Amazon's AI and machine learning journey, highlighting six key lessons learned: (1) maintain a sense of urgency and customer obsession as if it is still day one, (2) act with agility to stay ahead of or keep up with changes, (3) modernize applications using microservices and automation, (4) recognize that general artificial intelligence has not been achieved and specific models are needed, (5) determine when to build custom models versus using pre-trained ones, and (6) apply a continuous machine learning flywheel of data collection, model training, evaluation and improvement. The document emphasizes Amazon's focus on customers, innovation, and using AI/ML to enhance operations.
AWS Startup Day Bogotá - Fundraising Essentials: Raising a Seed Round Efficie...Amazon Web Services LATAM
This document discusses strategies for efficiently raising a seed round of funding. It recommends establishing ground rules for fundraising and drafting an ideal cap table structure to create scarcity. A key rule is to fundraise in parallel rather than sequentially to generate competition. It also stresses the importance of crafting a concise fundraising narrative that explains what you do, what's compelling, progress made, and future plans in 20 seconds or less. Backing the narrative with a financial model is also suggested. Prospecting a large initial funnel that narrows is a recommended approach to efficiently raising a seed round within a month.
The document provides guidance on efficiently raising a seed round of funding. It discusses that seed funding comes from both venture capital and non-VC sources. An experienced founder can raise a seed round in as little as a month by generating competition among investors. The secret is to establish clear fundraising rules, draft an ideal capital table, craft a concise fundraising narrative, build an initial funnel of prospects, and efficiently stack meetings to pitch to investors and close funding. The goal is to cultivate a sense of urgency for investors and put yourself in a position to turn investors away.
The Pitch - Essentials for Success, and Blunders to AvoidAmazon Web Services
The document discusses key elements of a successful startup pitch deck. It identifies problem, solution, business model, growth and traction, and team as particularly important sections. It provides examples of good and bad ways to present these sections. Additionally, it outlines seven common pitfalls to avoid, such as burying the main point or pretending to have no competition. The presentation emphasizes that the focus should be on clearly conveying your business idea rather than overly designing the presentation.
AWS Initiate - Security Framework Shakedown: Mapeie sua jornada com as melhor...Amazon Web Services LATAM
The document discusses best practices for security in cloud adoption and the AWS Well-Architected Framework. It covers defining a security strategy as part of cloud adoption, delivering a security program, operating robust security, controlling identity and access, enabling traceability, protecting the network layer, applying security across layers, and automating security checks and management. Specific AWS services referenced include AWS Organizations, IAM, GuardDuty, VPC, WAF, Config, and automation tools.
The document discusses strategies for efficiently raising a seed round of funding. It recommends establishing ground rules for fundraising including dedicating one person to the full-time role and fundraising in parallel rather than sequentially. The document also advises crafting an ideal cap table structure to create scarcity and urgency for investors. Additionally, it emphasizes the importance of developing a concise fundraising narrative that outlines company progress, future milestones, and vision in under 20 seconds.
This document discusses why startups choose to build on AWS. It notes that AWS allows startups to pay only for the resources they use without upfront costs, focus on their core business instead of infrastructure, and launch faster by having new IT resources available in a few clicks. This enables startups to experiment more and fail fast if ideas don't work. The document also shares statistics on the pace of innovation on AWS and lists some of the programs and resources available to help startups on AWS.
DevOps is currently one of the most sought after engineering models. One reason is that it helps enterprise transformations. The Amazon transformation to DevOps was born out of the desire to be even more customer obsessed, more agile, and more innovative. Come and learn from our journey as we share the playbook that helped us successfully implement and adopt DevOps as well as the lessons we learned the hard way.
The document discusses a general purpose serverless IoT platform for builders created by SoftChef Corporation. It addresses issues with traditional IT like costs, time constraints, and lack of resources. The platform aims to provide fully serverless IoT applications that are plug and play with easy expansion between central and edge computing. It also benefits from partnerships in a Joint Innovation Center and support from AWS.
This document discusses how a Taiwanese real estate startup called Leju used AWS to accelerate development of their MVP for property price queries and registration of actual transaction prices. It describes Leju's goals of increasing transparency of property prices and making information easier to read. It then outlines some of Leju's key milestones and features, including providing community average price maps, school district data, restoring address numbers, and integrating listings. The document also notes that AWS provided startups like Leju with infrastructure architects, subsidies, and other support important for non-technical founding teams.
The document discusses tools for building minimum viable products (MVPs) on Amazon Web Services (AWS). It recommends starting with the simplest possible solution, such as a static single-page web application using AWS Amplify. It also provides suggestions for building monolithic applications on AWS Elastic Beanstalk or decomposing them into microservices. The document outlines options for different data storage needs including relational, key-value, document, in-memory, graph, time-series, and ledger databases. It emphasizes measuring everything and designing with few components to get an MVP built quickly.
Amazon prioritizes innovation through a culture of customer obsession, long-term thinking, and a willingness to fail. They organize into small, empowered teams and provide mechanisms like working backwards to focus on customers' needs. Their architecture supports rapid growth through microservices and self-service platforms. This allows experimentation without constraints while empowering others.
OwlTing is a leading blockchain startup based in Taiwan that provides blockchain services and solutions. It has offices globally and strategic partnerships with large companies. OwlTing's services include OwlNest for hotel property management on the blockchain, OwlMarket for local products, and OwlExperiences for tour guides. These services provide benefits like preventing overbooking, enabling product traceability, and building trust. OwlTing has seen increasing use of Amazon Web Services for its flexibility, security, and performance.
The document discusses strategies for enterprises to transition to more frequent innovation and change like technology companies. It outlines several anti-patterns of traditional enterprise IT and new patterns that can help speed up delivery including: breaking up monolithic applications into microservices; investing in reskilling the workforce to be more customer-centric; automating security and compliance processes to match the speed of cloud; and building resilience by experimenting with failures instead of just planning for anticipated disasters. The overall goal is for enterprises to become "high-frequency" at delivering value through IT.
AWS Initiate Day Dublin 2019 – The Culture of Innovation at AmazonAmazon Web Services
The document discusses Amazon's culture of innovation and how it drives customer success. It emphasizes that Amazon prioritizes customer obsession, long-term thinking, willingness to fail, and being misunderstood for long periods of time. It also highlights how Amazon organizes for innovation through experimentation in small teams, a working backwards process from the customer, microservices architecture, and self-service platforms without gatekeepers. The goal is to decentralize innovation throughout the company and empower all employees to invent on behalf of customers.
AWS Initiate Day Dublin 2019 – Breaking down the MonolithsAmazon Web Services
The document discusses monolithic applications and microservices. It defines monoliths as traditional applications developed to best practices at the time that were not designed to be distributed. Microservices are defined as independently deployable services that work together and are modeled around business domains. The document discusses how Amazon transformed from monoliths to microservices and describes benefits of microservices like improved modularity, scalability, and faster release cycles. It also covers microservice design principles like bounded contexts and messaging patterns to connect microservices using services like SNS and SQS.
Paua Ventures is a Berlin-based venture capital firm that invests in B2B software companies addressing large markets with strong technical foundations. The presentation identifies four key trends in B2B software: 1) Everything is moving to the cloud, which provides challenges for large enterprises migrating systems; 2) Employees expect consumer-like experiences from enterprise software; 3) A growing cloud infrastructure opens more opportunities for cyber attacks; 4) Demand for microprocessors will increase dramatically with new devices like autonomous vehicles and drones.
The document discusses Amazon's approach to DevOps. It explains that Amazon needed to innovate rapidly to support thousands of teams making millions of deployments per year using microservices and continuous delivery practices. Amazon broke processes into fine-grained units and assigned them to autonomous two-pizza teams. These teams adopted agile methodologies and learned to work together across functions like development, operations, security, and quality assurance using a DevOps approach. Amazon also built shared tools, services, and best practices to support these teams in their DevOps journey.
The document discusses iVideosmart, a company that offers a smart video widget to easily integrate video content into any website. Their widget can automatically recommend relevant videos based on page content and convert views to video views. iVideosmart has over a billion pageviews and 200 million video views per month from their large network of premium video publishers globally. They utilize Amazon Web Services to scale their infrastructure and quickly prototype and process large amounts of data.
Why serverless will revolutionize your software process.James Beswick
Serverless fundamentally changes software development for both enterprises and startups - here's how it impact your process and how you can benefit. Presented at ITNext Summit, Amsterdam in 2019.
Security Framework Shakedown: Chart Your Journey with AWS Best PracticesAmazon Web Services
As with everything in life there is an easy way and a hard way when it comes to adopting security framework recommendations. Featuring the AWS Well-Architected and Cloud Adoption Frameworks, we will walk you through a complete security journey. We'll start with identification of requirements, then move through a series of how-tos from classifying your data, automating controls, to running fun incident response game days.
The document discusses Amazon Go, a cashier-less convenience store developed by Amazon, as a case study for using machine learning and IoT on AWS. It provides an overview of the challenges in building Amazon Go, including identifying customers and items taken for purchase without traditional checkout methods. It then discusses retail trends driving the need for AI and IoT solutions. The remainder of the document offers tips for developing AI and IoT projects, including focusing on business outcomes, considering related AWS services, and learning through hands-on projects to avoid prolonged analysis.
The document discusses Amazon's AI and machine learning journey, highlighting six key lessons learned: (1) maintain a sense of urgency and customer obsession as if it is still day one, (2) act with agility to stay ahead of or keep up with changes, (3) modernize applications using microservices and automation, (4) recognize that general artificial intelligence has not been achieved and specific models are needed, (5) determine when to build custom models versus using pre-trained ones, and (6) apply a continuous machine learning flywheel of data collection, model training, evaluation and improvement. The document emphasizes Amazon's focus on customers, innovation, and using AI/ML to enhance operations.
AWS Startup Day Bogotá - Fundraising Essentials: Raising a Seed Round Efficie...Amazon Web Services LATAM
This document discusses strategies for efficiently raising a seed round of funding. It recommends establishing ground rules for fundraising and drafting an ideal cap table structure to create scarcity. A key rule is to fundraise in parallel rather than sequentially to generate competition. It also stresses the importance of crafting a concise fundraising narrative that explains what you do, what's compelling, progress made, and future plans in 20 seconds or less. Backing the narrative with a financial model is also suggested. Prospecting a large initial funnel that narrows is a recommended approach to efficiently raising a seed round within a month.
The document provides guidance on efficiently raising a seed round of funding. It discusses that seed funding comes from both venture capital and non-VC sources. An experienced founder can raise a seed round in as little as a month by generating competition among investors. The secret is to establish clear fundraising rules, draft an ideal capital table, craft a concise fundraising narrative, build an initial funnel of prospects, and efficiently stack meetings to pitch to investors and close funding. The goal is to cultivate a sense of urgency for investors and put yourself in a position to turn investors away.
This document contains slides from a presentation given by Francisco Ruiz on creating successful pitches and avoiding common mistakes. The presentation discusses key elements to include in a pitch deck such as clearly presenting the problem, solution, business model, growth and traction, and team. It also identifies some common pitches sins to avoid like burying the main point, having an unclear thesis, including too much information, pretending there is no competition, and unrealistic assumptions about the market. The presentation emphasizes iteratively refining the pitch deck but notes the presenter's role is not as a "PowerPoint master."
This document contains slides from a presentation given by Francisco Ruiz on creating successful pitches and avoiding common mistakes. The presentation discusses key elements to include in a pitch deck such as the problem, solution, business model, growth and traction, and team. It also identifies some "deadly sins" to avoid like burying the main point, lacking focus, including irrelevant information, pretending the company has no competition, and unrealistic projections. The presentation emphasizes iteratively refining the pitch deck but notes the presenter's role is not as a "PowerPoint master."
The document discusses setting up accounts on AWS for different purposes as part of operating at scale. It recommends starting with a single AWS Organizations master account and then creating additional accounts for core services, shared services, security, billing/tools, internal audit, developer sandboxes, and business/product environments. Each account type has a specific purpose, access level, and relationship to the master account and other account types. The goal is to establish security, isolation, and control as the environment grows in complexity and size.
The document discusses best practices for creating effective pitch decks to present startup ideas to investors. It provides examples of pitch decks from successful companies like Airbnb, LinkedIn, and Square that emphasize clearly explaining the problem, solution, and business model. It also stresses the importance of demonstrating growth and traction as well as having a strong founding team. Common pitfalls to avoid include not grabbing attention quickly, lacking a clear thesis, including too much unrelated content, and failing to address typical concerns about the business. The overall message is that an effective pitch focuses on problem, solution, business model, growth, and team while avoiding vague, disorganized presentations.
성장하는 스타트업을 위한 아마존 이야기: Lean Innovation and Culture - Gaurav Arora, APAC 스타트업 ...Amazon Web Services Korea
The document discusses innovation at Amazon. It explains that Amazon fosters innovation through its organizational structure, architecture, culture and mechanisms. The company organizes into small independent teams and keeps systems loosely coupled. Its culture emphasizes customer obsession and leadership principles like bias for action and inventing. Teams follow practices like developing minimum viable products and iterating quickly based on customer feedback. This lean approach has allowed Amazon to continuously innovate while growing at scale.
The document discusses customer development and validation techniques for startups. It emphasizes the importance of getting out of the building to learn directly from customers through interviews and other techniques. Good questions for interviews focus on problems from the customer's perspective rather than products, and aim to elicit stories and pain points. Validation ensures the right problems are understood and that customers will pay for the proposed solution. Customer development should overlap with and inform product development to achieve product-market fit.
Culture of Innovation at Amazon - AWS Startup Day Johannesburg.pdfAmazon Web Services
In this session, we cover some of the mechanisms and best practices that help us innovate at Amazon. You'll get insights on how we structure our teams for autonomy and speed, how we 'work backwards' from our customers when deciding where to focus engineering efforts and how these mechanisms can be applied to running your startup.
How do I grow with my organization and meet my organization's needs? How do I rise to the new challenges before me? In this session we discuss the differences in preparing to operate in the cloud, what your operational priorities need to be, how to start designing for operations, and building your operational readiness. We will walk you through the process of how to launch your new life in the cloud. You will learn to make the early choices that lay the foundations for a successful adoption of cloud services. At the end of this session you will understand the key considerations when planning your personal journey to the cloud. This session is for leaders, operations, service owners and anyone interested in how to get started in the cloud to ensure successful business outcomes.
The Culture of Innovation at Amazon Driving Customer SuccessesAmazon Web Services
The document discusses Amazon's culture of innovation. It highlights that Amazon starts with the customer and works backwards to drive innovation. Amazon embraces failure as an important part of experimentation and invention. The company organizes for innovation through two pizza teams that work autonomously, microservices architectures, and self-service platforms without gatekeepers. Amazon's leadership principles like customer obsession and bias for action also support its culture of distributed innovation across the organization.
AWS Initiate - Inovação Rápida: O caso de negócio para desenvolvimento de apl...Amazon Web Services LATAM
The document discusses best practices for enabling rapid innovation through modern application development techniques. It advocates decomposing monolithic applications into microservices to improve agility, experimentation, and scalability. Other recommendations include using serverless technologies for infrastructure management, automating security to address vulnerabilities, and establishing continuous delivery practices through DevOps. The document uses Amazon's approach to building applications as an example, highlighting how techniques like microservices, serverless computing, and DevOps have allowed Amazon to rapidly innovate and evolve its business.
AWS Initiate Day Manchester 2019 – The Culture of Innovation at AmazonAmazon Web Services
The document discusses Amazon's culture of innovation and how it drives customer success. It emphasizes that Amazon prioritizes customer obsession in its approach to innovation. It highlights key beliefs such as thinking long-term, being willing to fail, and being willing to be misunderstood for a long time. The document also outlines Amazon's mechanisms for innovation including working backwards from the customer and having self-service platforms without gatekeepers. It notes Amazon's architectural approach of using micro-services and loosely coupled applications. Finally, it discusses how Amazon organizes for innovation through experimentation, small teams, and a culture of builders and entrepreneurs.
Initiate Edinburgh 2019 - The Culture of Innovation at AmazonAmazon Web Services
Customers often ask us how they can innovate "like Amazon". From its humble beginnings as a startup in a garage, Amazon has not only innovated across e-commerce, but also introduced new, diverse businesses beyond e-commerce. Over the years, Amazon has improved its ability to take on hard problems and find innovative ways to solve them. AWS is one such example. We have taken something as central and specialized as operating a datacenter, and pushed it to the edge as a utility. When technology becomes a utility, it becomes ubiquitous, allowing more people to participate in innovation. This talk will discuss how Amazon approaches innovation, with its mechanisms, architecture, culture, and organization, with an emphasis on how some of these factors can help other organizations. Our customer will also share how this approach has helped them inspire change within their businesses.
The document discusses Amazon's culture of innovation. It emphasizes that Amazon organizes for innovation through its culture of customer obsession, by hiring builders and letting them build with autonomy on small teams. It also facilitates innovation through mechanisms like working backwards, and through architectural structures that support rapid growth, like microservices and self-service platforms. The culture and these organizational approaches have enabled Amazon to successfully innovate in many areas over the years.
스폰서 발표 세션 | 클라우드 세상에서 CIO로 살아남기
이한주 대표이사, Bespin Global
클라우드 세상에서 CIO로 살아남기 위해서는 어떻게 해야 할까요? 클라우드를 도입하는 건 더이상 선택의 문제가 아닙니다. 우리 삶에 이미 스며들어 비즈니스 연속성을 갖기 위해서 취해야 할 당연한 환경입니다. 이제 클라우드는 얼마나 빨리 최신 기술을 적용하여 시장에 내놓을 수 있는지, 비즈니스 확장과 스피드의 관점으로 바라봐야합니다. 기업에서는 클라우드를 어떻게 접근해야 할까요? 개발자, 운영자 CIO로서 나가야 할 방향과 디지털 트랜스포메이션을 주도해야 하는 CDO로서의 방향은 어떻게 되어야 할까요?
High frequency enterprises embrace cloud computing as a flywheel for frequent value delivery. This requires tighter alignment with business unit stakeholders to increase agility and pace of innovation. In this session, we explore the potential for transformation that comes with cloud adoption and discuss how some of the world’s leading enterprises were able to transform and quickly deliver business value outcomes. We also explore organisational and technology best practices that you can implement to become a high frequency enterprise.
AWS SSA Webinar 4 - Building out your multi-account infrastructureCobus Bernard
Takes you through setting up multiple accounts with AWS Organisations, adding IAM policies, roles, groups and users. Also covers how to set up account switching, use profiles with the AWS CLI. Lastly, it cover which resources should be created in which accounts, and how to reason about those.
Understanding Complexity and How it Impacts Innovation - AWS Summit SydneyAmazon Web Services
Creating new products and services for customers is an increasingly complex challenge – technology trends are changing rapidly, industries are being disrupted, team dynamics are intricately impulsive, and customer behaviour is highly unpredictable. Albert Einstein famously said “the thinking that got us to where we are is not the thinking that will get us to where we want to be.” What would it take to rethink complexity, and nudge your behaviours to operate more successfully in this complex world? What if you could learn to use experimentation to create better products, high-performing teams, and a culture that is truly innovative? Come and learn how to thrive within the complex and uncertain world of modern business.
We uncovered a lot of information in our 2019 Expansion SaaS Benchmarks survey. What's keeping founders up at night, what the fundraising landscape looks like and how a product led growth strategy can help you narrow your focus to see better results.
Similar to Fundraising Essentials for Every Entrepreneur (20)
Come costruire servizi di Forecasting sfruttando algoritmi di ML e deep learn...Amazon Web Services
Il Forecasting è un processo importante per tantissime aziende e viene utilizzato in vari ambiti per cercare di prevedere in modo accurato la crescita e distribuzione di un prodotto, l’utilizzo delle risorse necessarie nelle linee produttive, presentazioni finanziarie e tanto altro. Amazon utilizza delle tecniche avanzate di forecasting, in parte questi servizi sono stati messi a disposizione di tutti i clienti AWS.
In questa sessione illustreremo come pre-processare i dati che contengono una componente temporale e successivamente utilizzare un algoritmo che a partire dal tipo di dato analizzato produce un forecasting accurato.
Big Data per le Startup: come creare applicazioni Big Data in modalità Server...Amazon Web Services
La varietà e la quantità di dati che si crea ogni giorno accelera sempre più velocemente e rappresenta una opportunità irripetibile per innovare e creare nuove startup.
Tuttavia gestire grandi quantità di dati può apparire complesso: creare cluster Big Data su larga scala sembra essere un investimento accessibile solo ad aziende consolidate. Ma l’elasticità del Cloud e, in particolare, i servizi Serverless ci permettono di rompere questi limiti.
Vediamo quindi come è possibile sviluppare applicazioni Big Data rapidamente, senza preoccuparci dell’infrastruttura, ma dedicando tutte le risorse allo sviluppo delle nostre le nostre idee per creare prodotti innovativi.
Ora puoi utilizzare Amazon Elastic Kubernetes Service (EKS) per eseguire pod Kubernetes su AWS Fargate, il motore di elaborazione serverless creato per container su AWS. Questo rende più semplice che mai costruire ed eseguire le tue applicazioni Kubernetes nel cloud AWS.In questa sessione presenteremo le caratteristiche principali del servizio e come distribuire la tua applicazione in pochi passaggi
Vent'anni fa Amazon ha attraversato una trasformazione radicale con l'obiettivo di aumentare il ritmo dell'innovazione. In questo periodo abbiamo imparato come cambiare il nostro approccio allo sviluppo delle applicazioni ci ha permesso di aumentare notevolmente l'agilità, la velocità di rilascio e, in definitiva, ci ha consentito di creare applicazioni più affidabili e scalabili. In questa sessione illustreremo come definiamo le applicazioni moderne e come la creazione di app moderne influisce non solo sull'architettura dell'applicazione, ma sulla struttura organizzativa, sulle pipeline di rilascio dello sviluppo e persino sul modello operativo. Descriveremo anche approcci comuni alla modernizzazione, compreso l'approccio utilizzato dalla stessa Amazon.com.
Come spendere fino al 90% in meno con i container e le istanze spot Amazon Web Services
L’utilizzo dei container è in continua crescita.
Se correttamente disegnate, le applicazioni basate su Container sono molto spesso stateless e flessibili.
I servizi AWS ECS, EKS e Kubernetes su EC2 possono sfruttare le istanze Spot, portando ad un risparmio medio del 70% rispetto alle istanze On Demand. In questa sessione scopriremo insieme quali sono le caratteristiche delle istanze Spot e come possono essere utilizzate facilmente su AWS. Impareremo inoltre come Spreaker sfrutta le istanze spot per eseguire applicazioni di diverso tipo, in produzione, ad una frazione del costo on-demand!
In recent months, many customers have been asking us the question – how to monetise Open APIs, simplify Fintech integrations and accelerate adoption of various Open Banking business models. Therefore, AWS and FinConecta would like to invite you to Open Finance marketplace presentation on October 20th.
Event Agenda :
Open banking so far (short recap)
• PSD2, OB UK, OB Australia, OB LATAM, OB Israel
Intro to Open Finance marketplace
• Scope
• Features
• Tech overview and Demo
The role of the Cloud
The Future of APIs
• Complying with regulation
• Monetizing data / APIs
• Business models
• Time to market
One platform for all: a Strategic approach
Q&A
Rendi unica l’offerta della tua startup sul mercato con i servizi Machine Lea...Amazon Web Services
Per creare valore e costruire una propria offerta differenziante e riconoscibile, le startup di successo sanno come combinare tecnologie consolidate con componenti innovativi creati ad hoc.
AWS fornisce servizi pronti all'utilizzo e, allo stesso tempo, permette di personalizzare e creare gli elementi differenzianti della propria offerta.
Concentrandoci sulle tecnologie di Machine Learning, vedremo come selezionare i servizi di intelligenza artificiale offerti da AWS e, anche attraverso una demo, come costruire modelli di Machine Learning personalizzati utilizzando SageMaker Studio.
OpsWorks Configuration Management: automatizza la gestione e i deployment del...Amazon Web Services
Con l'approccio tradizionale al mondo IT per molti anni è stato difficile implementare tecniche di DevOps, che finora spesso hanno previsto attività manuali portando di tanto in tanto a dei downtime degli applicativi interrompendo l'operatività dell'utente. Con l'avvento del cloud, le tecniche di DevOps sono ormai a portata di tutti a basso costo per qualsiasi genere di workload, garantendo maggiore affidabilità del sistema e risultando in dei significativi miglioramenti della business continuity.
AWS mette a disposizione AWS OpsWork come strumento di Configuration Management che mira ad automatizzare e semplificare la gestione e i deployment delle istanze EC2 per mezzo di workload Chef e Puppet.
Scopri come sfruttare AWS OpsWork a garanzia e affidabilità del tuo applicativo installato su Instanze EC2.
Microsoft Active Directory su AWS per supportare i tuoi Windows WorkloadsAmazon Web Services
Vuoi conoscere le opzioni per eseguire Microsoft Active Directory su AWS? Quando si spostano carichi di lavoro Microsoft in AWS, è importante considerare come distribuire Microsoft Active Directory per supportare la gestione, l'autenticazione e l'autorizzazione dei criteri di gruppo. In questa sessione, discuteremo le opzioni per la distribuzione di Microsoft Active Directory su AWS, incluso AWS Directory Service per Microsoft Active Directory e la distribuzione di Active Directory su Windows su Amazon Elastic Compute Cloud (Amazon EC2). Trattiamo argomenti quali l'integrazione del tuo ambiente Microsoft Active Directory locale nel cloud e l'utilizzo di applicazioni SaaS, come Office 365, con AWS Single Sign-On.
Dal riconoscimento facciale al riconoscimento di frodi o difetti di fabbricazione, l'analisi di immagini e video che sfruttano tecniche di intelligenza artificiale, si stanno evolvendo e raffinando a ritmi elevati. In questo webinar esploreremo le possibilità messe a disposizione dai servizi AWS per applicare lo stato dell'arte delle tecniche di computer vision a scenari reali.
Amazon Web Services e VMware organizzano un evento virtuale gratuito il prossimo mercoledì 14 Ottobre dalle 12:00 alle 13:00 dedicato a VMware Cloud ™ on AWS, il servizio on demand che consente di eseguire applicazioni in ambienti cloud basati su VMware vSphere® e di accedere ad una vasta gamma di servizi AWS, sfruttando a pieno le potenzialità del cloud AWS e tutelando gli investimenti VMware esistenti.
Molte organizzazioni sfruttano i vantaggi del cloud migrando i propri carichi di lavoro Oracle e assicurandosi notevoli vantaggi in termini di agilità ed efficienza dei costi.
La migrazione di questi carichi di lavoro, può creare complessità durante la modernizzazione e il refactoring delle applicazioni e a questo si possono aggiungere rischi di prestazione che possono essere introdotti quando si spostano le applicazioni dai data center locali.
Crea la tua prima serverless ledger-based app con QLDB e NodeJSAmazon Web Services
Molte aziende oggi, costruiscono applicazioni con funzionalità di tipo ledger ad esempio per verificare lo storico di accrediti o addebiti nelle transazioni bancarie o ancora per tenere traccia del flusso supply chain dei propri prodotti.
Alla base di queste soluzioni ci sono i database ledger che permettono di avere un log delle transazioni trasparente, immutabile e crittograficamente verificabile, ma sono strumenti complessi e onerosi da gestire.
Amazon QLDB elimina la necessità di costruire sistemi personalizzati e complessi fornendo un database ledger serverless completamente gestito.
In questa sessione scopriremo come realizzare un'applicazione serverless completa che utilizzi le funzionalità di QLDB.
Con l’ascesa delle architetture di microservizi e delle ricche applicazioni mobili e Web, le API sono più importanti che mai per offrire agli utenti finali una user experience eccezionale. In questa sessione impareremo come affrontare le moderne sfide di progettazione delle API con GraphQL, un linguaggio di query API open source utilizzato da Facebook, Amazon e altro e come utilizzare AWS AppSync, un servizio GraphQL serverless gestito su AWS. Approfondiremo diversi scenari, comprendendo come AppSync può aiutare a risolvere questi casi d’uso creando API moderne con funzionalità di aggiornamento dati in tempo reale e offline.
Inoltre, impareremo come Sky Italia utilizza AWS AppSync per fornire aggiornamenti sportivi in tempo reale agli utenti del proprio portale web.
Database Oracle e VMware Cloud™ on AWS: i miti da sfatareAmazon Web Services
Molte organizzazioni sfruttano i vantaggi del cloud migrando i propri carichi di lavoro Oracle e assicurandosi notevoli vantaggi in termini di agilità ed efficienza dei costi.
La migrazione di questi carichi di lavoro, può creare complessità durante la modernizzazione e il refactoring delle applicazioni e a questo si possono aggiungere rischi di prestazione che possono essere introdotti quando si spostano le applicazioni dai data center locali.
In queste slide, gli esperti AWS e VMware presentano semplici e pratici accorgimenti per facilitare e semplificare la migrazione dei carichi di lavoro Oracle accelerando la trasformazione verso il cloud, approfondiranno l’architettura e dimostreranno come sfruttare a pieno le potenzialità di VMware Cloud ™ on AWS.
1) The document discusses building a minimum viable product (MVP) using Amazon Web Services (AWS).
2) It provides an example of an MVP for an omni-channel messenger platform that was built from 2017 to connect ecommerce stores to customers via web chat, Facebook Messenger, WhatsApp, and other channels.
3) The founder discusses how they started with an MVP in 2017 with 200 ecommerce stores in Hong Kong and Taiwan, and have since expanded to over 5000 clients across Southeast Asia using AWS for scaling.
This document discusses pitch decks and fundraising materials. It explains that venture capitalists will typically spend only 3 minutes and 44 seconds reviewing a pitch deck. Therefore, the deck needs to tell a compelling story to grab their attention. It also provides tips on tailoring different types of decks for different purposes, such as creating a concise 1-2 page teaser, a presentation deck for pitching in-person, and a more detailed read-only or fundraising deck. The document stresses the importance of including key information like the problem, solution, product, traction, market size, plans, team, and ask.
This document discusses building serverless web applications using AWS services like API Gateway, Lambda, DynamoDB, S3 and Amplify. It provides an overview of each service and how they can work together to create a scalable, secure and cost-effective serverless application stack without having to manage servers or infrastructure. Key services covered include API Gateway for hosting APIs, Lambda for backend logic, DynamoDB for database needs, S3 for static content, and Amplify for frontend hosting and continuous deployment.
This document provides tips for fundraising from startup founders Roland Yau and Sze Lok Chan. It discusses generating competition to create urgency for investors, fundraising in parallel rather than sequentially, having a clear fundraising narrative focused on what you do and why it's compelling, and prioritizing relationships with people over firms. It also notes how the pandemic has changed fundraising, with examples of deals done virtually during this time. The tips emphasize being fully prepared before fundraising and cultivating connections with investors in advance.
AWS_HK_StartupDay_Building Interactive websites while automating for efficien...Amazon Web Services
This document discusses Amazon's machine learning services for building conversational interfaces and extracting insights from unstructured text and audio. It describes Amazon Lex for creating chatbots, Amazon Comprehend for natural language processing tasks like entity extraction and sentiment analysis, and how they can be used together for applications like intelligent call centers and content analysis. Pre-trained APIs simplify adding machine learning to apps without requiring ML expertise.
Amazon Elastic Container Service (Amazon ECS) è un servizio di gestione dei container altamente scalabile, che semplifica la gestione dei contenitori Docker attraverso un layer di orchestrazione per il controllo del deployment e del relativo lifecycle. In questa sessione presenteremo le principali caratteristiche del servizio, le architetture di riferimento per i differenti carichi di lavoro e i semplici passi necessari per poter velocemente migrare uno o più dei tuo container.
[introduce yourself]
Slides will be available after the talk
This is advice on fundraising from founders. There’s a lot of fundraising advice from VCs, and it’s usually pretty self-serving. We’re going to talk about some fundraising best practices today that VCs are very unlikely to share
NOTE
[talk about the different types of fundraising and how deciding on funding sources depends on your goals for the business]
Today, we’re going to talk about fundraising as efficiently as possible, which raises the question, “how long should fundraising take?”
…now personally, my first round took around 6 months – which is more aligned with the experience of first-time founders. So today, we’re going to talk about to go about how to fundraise like a serial founder. So what’s the secret of serial founders?
….and today we’re going to talk about how to do that.
If you’re bootstrapping, you have true autonomy over your business. Other than customers and teammates, you don’t have anyone to answer to. When you fundraise, you then have a fiscal responsibility to your investors and have an entirely new group of people to answer to.
When you’re bootstrapping, a $2M exit or slowly growing a passive, profitable business can be great outcomes. If you raise outside money, those are not good outcomes. As we’ll discuss today, depending on who you take money from, the bar for good outcomes is a lot higher.
[Tell bootstarp story of convertkit]
For example, Fanduel, the category leader of daily fantasy sports, was acquired for $465M. Sounds like an amazing victory, right? Well, the company had raised $416M across seven funding rounds, at one point valuing the company at over $1B.
- Avoid the gray area of “kind of” fundraising. It’s easy to say yes when someone offers to introduce you to an investor, and the next thing you know, you’re “kind of fundraising” – this is no way to successfully raise money, so avoid it. Keep it black and white.
- Investors are incentivized to help when you’re not fundraising; they want to wait as long as possible when you are fundraising
- When you’re “not fundraising” you can stack the deck in your favor by building relationships with investors who you may be able to go to once you do fundraise.
- One person owning fundraising prevents it from distracting others
- The fundraiser needs to spend 80% of their time fundraising. This is easier said than done, but is one of the ways that fundraises fail before they begin. You’ll need to delegate most of your operational responsibilities before diving into a fundraise.
- You should have a single person handling all meetings and communications with investors. If you show up to a meeting with your entire founding team, investors are going to wonder who is steering the ship!
- You’re selling the precious, scarce equity in your company, not asking for money
- There’s a fine line between confidence and arrogance, [share personal anecdote]
- Every interaction during a fundraise can positively impact your business and career [share personal anecdote]
Bob Moore from crossbeam pitched first round capital twice. They passed on two of his past companies. On his third company, they ended up investing because he was respectful throughout the process.
One of the biggest mistakes founders make it they try to get one investor at a time and await an answer. Today we’re going to talk a lot about the 3x1 rule – the idea that you should be in final diligence with three investors simultaneously for every spot you have available in your round.
One way to understand this rule: if you run a fundraise effectively, you will absolutely need to say no to at least one investor who wants to invest. A lot of what we’ll talk about today is about putting you in that position.
Another common mistake founders make is trying to artificially create urgency by telling an investor that “the round is going to close in the next two weeks.” This rarely creates any FOMO, but it frequently backfires. Investors hear this all the time so they can usually see through it. And if two weeks go by and you haven’t closed your round, that’s a negative signal and you’ll lose credibility with the investor.
Instead, investor urgency comes from authentically having more investors deeply interested in your deal than spots available.
When fundraising, you want to be “in market” for as little time as possible. If you’re fundraising for a long time, it becomes a negative signal for investors. At the same time, if you give investors an unlimited amount of time to evaluate your deal, they will usually find reasons to say no. An investor I worked with once told me a story about a founder he wanted to invest in who gave him unlimited time for diligence. While he liked the company at first, the more he dug, the more he found reasons to say no and eventually. In retrospect, he wished that he would have invested and said he probably would have if he was pressed to act faster.
….if you want to raise $2M, the idea of just hitting the fundraising trail and scrapping together 2M in checks is daunting and paralyzing. Therefore, one of the first things you need to do before fundraising is draft how you want your round to be composed.
…This is just one example, in order to draft how you want your round to be composed, we need to better understand the different types of investors and their motivations.
…This is just one example, in order to draft how you want your round to be composed, we need to better understand the different types of investors and their motivations.
One of the best things you can do as a founder is have empathy for investors and see things from their perspective
Being a successful VC is hard. Imagine a VC who makes 33 $300K investments from a $10M fund, and has these outcomes….
[run through outcomes]
That VC is doing just ok!
….which means they’re looking for founders to 50x their company.
[talk about how newer VCs are incentivized for you to continue raising capital]
[talk about my personal anecdotes with some of the motivations of my angel investors]
[talk about how 3x can be a “great” outcome for an angel, contrast to how that’s a write-off for a VC]
This is both good and bad – they’re not going to have voting rights and can’t force you to do anything, but also may not be that helpful.
[Talk about Sparktoro raising a $1.3M seed round from 35 angels and why they did it]
If you share your fundraising narrative with an investor, they should be able to recite it to others verbatim even after talking to ten other startups
…..an investors should be able to go hear 10 other pitches, and then repeat these things to
…..an investors should be able to go hear 10 other pitches, and then repeat these things to
…..an investors should be able to go hear 10 other pitches, and then repeat these things to
This is why on Y Combinator’s application the first two questions are to explain your company in 50 characters or less and to simply describe what you’re going to make. The quickest way to get disqualified here is to use buzzwords
[read aloud]
First of all, when I read this I still don’t really know what you do.
Second of all, there’s no way an investor can remember this.
This is great. I know what you do (though I don’t know the gritty details yet), and I can easily remember this.
Other examples I’ve seen:
“A new regulation forces universities to send us customers, and the universities pay us too.”
“We have $20K in MRR with 3 straight months of 40% MoM growth”
At the seed stage, it’s less about vanity metrics – it’s about the derisking you’ve done. This is how some startups are able to raise money with less traction.
Progress to date: What have you already figured out?
Next Milestone: What are you going to figure out with this round?
The Future: How will achieving the next milestone put you on the path to your long-term vision?
Ask the audience to answer some of these questions
…This is just one example, in order to draft how you want your round to be composed, we need to better understand the different types of investors and their motivations.
3x1: Be in final diligence with 3 investors at the same time for every spot available
10x1: Have initial conversations with 10 investors at the same time for every spot available
20x1: Start with 20 prospects for every spot available
…when we look at this, we can see why fundraising becomes a full-time job. This means that if we have 8 total spots available in the round, we should start with 160 prospects.
3x1: Be in final diligence with 3 investors at the same time for every spot available
10x1: Have initial conversations with 10 investors at the same time for every spot available
20x1: Start with 20 prospects for every spot available
…when we look at this, we can see why fundraising becomes a full-time job. This means that if we have 8 total spots available in the round, we should start with 160 prospects.
3x1: Be in final diligence with 3 investors at the same time for every spot available
10x1: Have initial conversations with 10 investors at the same time for every spot available
20x1: Start with 20 prospects for every spot available
…when we look at this, we can see why fundraising becomes a full-time job. This means that if we have 8 total spots available in the round, we should start with 160 prospects.
3x1: Be in final diligence with 3 investors at the same time for every spot available
10x1: Have initial conversations with 10 investors at the same time for every spot available
20x1: Start with 20 prospects for every spot available
…when we look at this, we can see why fundraising becomes a full-time job. This means that if we have 8 total spots available in the round, we should start with 160 prospects.
Talk about how you should think about the people you have access to in addition to the firms you want to work with. Note that people have different focuses. For example, two different partners at the same VC firm may invest in entirely different areas.
[talk about how you can use Crunchbase to find investors]
[talk about how founders who are a year ahead of you have already done a lot of this work and can refer you to investors they know]
[talk about how founders like being scouts for investors (even those who didn’t invest in them). Use Erik Torenberg as an example]
[talk about how I still refer companies to my previous investors]
[talk about how associates thrive on referring deals to each other. Share my anecdote of an associate friend referring me to other investors who were a good fit]
…we’ll talk about this in a 4-step process
[talk about building relationships with investors before you turn fundraising mode on. Talk about how your can be working on fundraising in this way even though you’re not messaging that you’re “in fundraising mode”]
…Not having these things when you start will slow down the process.
There’s a big difference between turning fundraising mode on and having no investors and turning fundraising mode on with at least one investor. Talk to some of the people who you already have close relationships with (it could even be small angels) to get some commitments before you turn fundraising mode on – that way, your fundraise will feel more real from the start. When turning fundraising mode on, you should be leveraging your network and existing connections to get introductions to your prospects as quickly as possible. If you can’t find an introduction to the person you want to meet, then note that…(next slide)
[talk about how you’ll get referred to new people during this process, and you need to take advantage of those introductions and add new people to the funnel]
…With these goals in mind, there are a few rules for initial meetings
[talk about the typical investment process]
[Talk about how you only have so much energy. If an investor is out, then it’s better to know that so you can spend your energy elsewhere. ]
…now personally, my first round took around 6 months – which is more aligned with the experience of first-time founders. So today, we’re going to talk about to go about how to fundraise like a serial founder. So what’s the secret of serial founders?