I built & sold 12 no -ode apps in 12 weeks - here's everything I learned - No Code Conf 2019 Workshop
âą
4 gefĂ€llt mirâą3,311 views
This document outlines David Adkin's experience building and selling 12 no-code apps in 12 weeks. It discusses how to find clients for no-code app projects, how to estimate the time and price to build an app, designing the app features and database, developing the minimum viable product (MVP) in iterations, and tasks for publishing and launching the app. The key recommendations are to clearly define the app features and scope of work, set proper expectations on no-code limitations, develop the app incrementally with testing, and plan for beta testing, launch, and future versions with the client.
Empfohlen
Empfohlen
Weitere Àhnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Ăhnlich wie I built & sold 12 no -ode apps in 12 weeks - here's everything I learned - No Code Conf 2019 Workshop
Ăhnlich wie I built & sold 12 no -ode apps in 12 weeks - here's everything I learned - No Code Conf 2019 Workshop (20)
Mehr von Webflow
Mehr von Webflow (19)
KĂŒrzlich hochgeladen
KĂŒrzlich hochgeladen (20)
I built & sold 12 no -ode apps in 12 weeks - here's everything I learned - No Code Conf 2019 Workshop
- 1. I BUILT & SOLD 12 NO-CODE APPS IN 12 WEEKS Hereâs Everything I Learned
- 2. David Adkin Hey No-Coders! Co-founder of Adalo @david_adkin
- 3. Agenda 1 Intro 5 Minutes 2 How to Sell No-Code Apps 15 Minutes 3 Selling Exercise 15 Minutes 4 How to Build No-Code Apps 10 Minutes 5 Building Exercise 10 Minutes 6 Top 5 Must-Dos & Wrap-up 5 Minutes
- 4. My Story Architecture UX Designer Entrepreneur 2007 - 2013 2012 - 2018 2018 - Today
- 5. 12 Apps in 12 Weeks! BuzzerBeater Book local barbers now PeriDeals Find perishable deals Tavolo Dining made easy Beyond Boundaries Track progress in program Entrees By Laura Find perishable deals Tavolo - Restaurant Dining made easy DevMarket Buy dev projects Second Street Internal feedback app CITCOR Cannabis training tracker Lifetime Performance High end workout app LucasPye BPT Drug tracker TCR Doctor chat app for Africa
- 6. Websites vs Apps No Code Conf Site Twitter
- 7. Websites vs Apps Twitter No Code Conf
- 8. The Times They Are a-Changin'
- 10. But itâs a lot more complicatedâŠ
- 12. The Perfect Client It matters even more for no-code apps.
- 13. Client Assessment Tech Experience Their Appâs Chance at Success Go With the Flow Level of Commitment
- 14. Tech Experience They can explain their app idea They understand the concept of an MVP They can barely even use an app They donât believe in the idea of an MVP Able to use the no-code tool
- 15. Their Appâs Chance at Success They have an existing audience Thereâs a plan for their app to make $ They donât really have a deïŹned idea Thereâs no business value Possible to make with a no-code tool
- 16. Go With The Flow Personal connection They have a fun attitude Uncomfortable with uncertainty They need to have ever last detail ïŹgured out before they want to commit to the project
- 17. Commitment They have a team (If startup) theyâve taken steps to make the business real Change their ideas all the time Too busy to commit Donât follow through
- 18. âAll Hat and No Cattleâ
- 19. Finding Clients Social Media Content Marketing Freelancer Groups The Traditional Ways Freelancers Find ClientsâŠ
- 20. Finding Clients Whatâs New For No-Code App Builders? New Kid on the Block Existing Clients Local Advantage
- 21. Finding Clients Startups Go to Local Startup Events Talk with Incubators & Accelerators Bid on sites like Upwork Existing Business What are they doing with spreadsheets? Always be thinking about apps. Rinse & repeat.
- 22. First Meeting(s) Whatâs their app idea? Pre-Meeting Is it worth your time? Do research on their space.
- 23. First Meeting(s) Talk about every possible feature Features Discussion Set no-code expectations Discuss native vs web app (narrow down later)
- 24. First Meeting(s) Try to ïŹgure out their budget Initial Pricing & Timeline Explain app complexities Give them a general range
- 25. What pages? Home? Pricing? Team? Website Features Blog? Ecommerce?
- 26. Do they need multiple apps for the different users? App Features Web app or mobile app? Push notiïŹcations? Payments? Marketplace? Digital goods? Chat? Booking or sending requests? Social media type features? Following? Browsing? Images? Video? Audio? Integration with external data sources?
- 27. Red Flag Features! AR/VR Algorithmic Feeds Complex Computations Mobile Games A.I. Video Tracking
- 28. Estimating the Time & Price Login, Signup, Create ProïŹle Browse Classes Book and Bid Appointments App Version 1 Chat with Teachers Weeks 1 to 3 Reviews/Teacher Ratings Admin NotiïŹcation Center Promo Coupon Code App Version 2 Weeks 4 to 5 Wanted in V1 But Moved to V2 Did a Test to ConïŹrm Possible Accurate Estimation is Key
- 29. Estimate Hours and Multiply Coming Up with a Price 40 hours * $50/hr = $2k Normally between $2k - $10k Charge less when you have no previous apps built to grow your portfolio Make sure to talk about payment works for more features after youâre done!
- 30. Making the Sale Show Them Their Future! Make a quick version of a portion of it. Itâs your secret weapon. But donât spend too much time⊠itâs risky.
- 31. Making the Sale Have a PSA & SOW! Get a Professional Service Agreement Template A clearly deïŹned Scope of Work is critical. An email is better than nothing!
- 32. Scope Creep is Real!
- 34. Designing the App Login, Signup, Create ProïŹle Browse Classes Book Classes App Version 1 Features Create Classes Overall Navigation & Organization First
- 35. 3 Overall Types of Screens List Screen Details Screen Add/Edit Screen
- 36. Designing the Database New!! Classes Class Name Class Image Class Teacher Class ProïŹciency Class Description Class Notes
- 37. Designing the Database New!! Email Users Password ProïŹle Picture Name Classes Image Description Requested Date Requests Status Video Meeting Link ProïŹciency Type Person Who Made Request Requested Class Teacher What are all of the data collections?
- 38. Designing the Database New!! Email Users Password ProïŹle Picture Name Classes Image Description Requested Date Requests Status Video Meeting Link ProïŹciency Type Person Who Made Request Requested Class Teacher (R) (R) (R) Find the Relationships
- 39. Developing the MVP Build Feature 1 Test Feature 1 Build Feature 2 Test Feature 2 Build Feature 3 (Just like an actual tech company and dev team would do!)
- 41. Publishing Tasks Setup Legal Business Apply for DUNS number Apple Developer account Android Developer account Website Privacy Policy Text descriptions for app stores Screenshots for app stores
- 42. Launching Coach Teammate Cheerleader 3 Roles for You to Play
- 43. Scope Creep is Real!
- 44. Timeline First Meeting(s) Days 1 - 7 Making the Sale Days 7 - 14* *Could be a lot longer. Sometime it stalls at this point and they take a long time to commit. Designing the App Days 14 - 21 Developing the MVP Days 21 - 36 Testing & Publishing Days 36 - 42 Launching Days 42 - 48
- 45. Top 5 Must-Dos & Wrap-up
- 46. Make sure theyâre on board with the concept of an MVP. 1#
- 47. Make sure you ïŹgure out the list of features before you make the sale. (& you have that in a PSA!) 2#
- 48. Make sure you understand the limits of the no-code tool youâre using. 3#
- 49. Make sure you build it feature by feature (while testing along the way). 4#
- 50. Make sure you work with them on a beta, launch, and future iterations plan. 5#
- 51. Thanks! (If youâre interested in trying out Adalo letâs chat!)