Как сделать крутое приложение доставки еды для роста выручки?

Как сделать крутое приложение доставки еды для роста выручки?

How to Create a Successful Food Delivery App

Introduction to the Speaker and Background

  • The speaker is one of the founders of Badhead, with 15 years of experience in custom software development for high-budget projects, including work for major companies like Yandex and Samokat.
  • They launched their own food delivery service during the pandemic, collaborating with a renowned chef from St. Petersburg, but had to return the project due to unforeseen circumstances.

Development of Starter Platform

  • After returning from their initial project, they realized they could offer their developed app and IT infrastructure to the market, leading to the creation of "Starter."
  • Currently, around 200 restaurant projects use Starter, resulting in an average revenue growth of 50% for clients in 2023. In March alone, transactions through their platform reached approximately 123 million rubles.

Website vs. App: What Do You Need?

  • The discussion emphasizes that both a website and an app are essential; websites help new customers place their first order while apps cater to repeat customers.
  • Apps significantly enhance customer perception of product quality and serve as effective communication channels through push notifications compared to social media posts with low engagement rates.

Importance of Quality Communication

  • Quality product offerings combined with effective communication are crucial for success in any regular ordering business model. A case study illustrates how poor communication can lead customers away from direct orders towards third-party platforms like Yandex Eats due to convenience factors.

User Experience Design Considerations

  • The speaker shares insights on user experience design by discussing a successful project for Danilovsky Market that initially thrived until integrating with Yandex Eats led to a significant drop in direct orders due to user preference for convenience within apps over websites.

Enhancing Customer Engagement Through Push Notifications

Effective Use of Push Notifications

  • Engaging users through push notifications can yield substantial increases in order volume; even small user bases can generate significant additional orders weekly through consistent messaging strategies.

Overcoming Misconceptions About App Usage

  • Many potential clients express skepticism about whether users will download individual restaurant apps; however, data shows that around 80% of orders come from apps rather than websites when properly incentivized (e.g., loyalty programs).

Creating an Intuitive User Interface

Key Elements of User Experience

  • A good app should minimize user input requirements while ensuring transparency regarding delivery conditions and costs throughout the ordering process—this enhances overall satisfaction and reduces frustration during checkout experiences.

Anticipating User Questions

  • Developers should anticipate common questions users may have during ordering (e.g., delivery times or costs), providing clear answers directly within the interface instead of requiring navigation away from key actions like placing an order.

Addressing Technical Challenges

Streamlining Payment Processes

  • It's critical that payment processes do not disrupt user experience; systems must be designed so that changes made after initiating payment do not result in lost information or require re-entry by users—this prevents frustration during checkout stages.

Balancing Business Needs with Customer Satisfaction

Strategies for Increasing Average Order Value

  • Implementing features such as reminders about free shipping thresholds or rewards can effectively increase average order values by encouraging customers to add more items before completing purchases—these strategies should be integrated into app design seamlessly without overwhelming users with information overload.

Marketing Your Application Effectively

  • It’s important that marketing efforts highlight app availability prominently across various touchpoints rather than relegating it to less visible areas on websites; this ensures potential users are aware and motivated to download your application immediately upon visiting your site or completing an order process.

By structuring notes this way using timestamps linked back into specific sections allows readers easy access back into detailed discussions while also summarizing key points succinctly!

Importance of Service Quality in Business

Impact of Errors on Revenue

  • Discusses how service quality directly affects order delivery times, leading to potential revenue loss for businesses.
  • Shares a case study of a client who lost 1 million rubles in revenue due to system errors during peak hours, highlighting the critical nature of error-free operations.

Approaches to Error Management

  • Introduces two approaches to managing errors: one being formalized response times and the other focusing on preventing order losses altogether.
  • Emphasizes the importance of not losing orders as a primary goal rather than adhering strictly to response time metrics.

Development Options for Delivery Applications

Custom vs. Off-the-Shelf Solutions

  • Outlines the cost range for custom application development (3-7 million rubles), noting that some projects can exceed 30 million rubles.
  • Discusses alternatives like working with aggregators, which charge around 35% fees but may be more viable for businesses with lower revenues.

When to Consider Custom Development

  • Suggests that custom development is only advisable if monthly delivery revenue exceeds 100 million rubles and if there is an IT-savvy team member involved.

Operational Considerations in Delivery Services

Managing External Resources

  • Highlights that using aggregators requires less management effort compared to developing an in-house solution, allowing focus on operational issues like courier management.

Recommendations Based on Revenue Levels

  • Advises businesses with under 100 million rubles in monthly revenue to utilize ready-made solutions instead of investing in custom applications.

Case Study: Client Experience and Lessons Learned

Shifts in Strategy and Results

  • Describes a sushi delivery client who attempted to scale by acquiring new locations but faced significant revenue drops after switching from a commission-based model to fixed fees.

Importance of Interface and User Experience

  • Stresses how user interface impacts sales performance, illustrating this through the client's experience with their new strategy leading to decreased earnings.

Commission Structures and Profitability

Understanding Commission Models

  • Explains different commission structures where clients can either absorb costs or pass them onto customers, similar to practices seen with Yandex Food's service fees.

Financial Implications of Aggregator Partnerships

  • Discusses how aggregator partnerships can lead to reduced margins but also highlights potential profitability when managed correctly through direct customer engagement strategies.

Addressing Questions About Delivery Models

Comparison Between Aggregators and In-House Solutions

  • Clarifies differences between using aggregators versus developing proprietary delivery systems, emphasizing audience access versus profit margins.

Economic Analysis of Delivery Costs

  • Provides detailed breakdown comparing costs associated with aggregator services against those incurred when managing deliveries internally.

This structured approach captures key insights from the transcript while providing timestamps for easy reference.

Integration and Pricing Structure Discussion

Integration Capabilities

  • The speaker discusses the integration of applications on their website, emphasizing that most modifications are included within the existing pricing plan, with only a few paid adjustments made over three years.
  • A mention of a 3% cost allocation from revenue is highlighted, indicating that this is standard practice for budgeting in their pricing model.

CRM Systems and Features

  • The internal CRM system is introduced, which integrates with external systems like marketing tools and loyalty programs such as Premium Bonus.
  • The internal CRM allows for basic analytics like ABC analysis but lacks LTV (Lifetime Value) calculations; however, RFM (Recency, Frequency, Monetary) analysis is available.

Customer Interaction Tools

  • Current limitations in tracking customer orders outside the app are noted. Future updates aim to enhance data collection regarding customer interactions both in-store and through delivery.
  • Introduction of a Telegram chatbot for alternative user authentication methods is discussed. This tool will eventually send push notifications about order statuses and promotions.

Communication Strategies and User Engagement

Push Notifications vs. Chatbot Functionality

  • The effectiveness of using chatbots for communication is emphasized; currently limited to authorization codes but plans to expand functionality soon.
  • There’s an exploration of how users might be compelled to keep the Telegram app installed due to loyalty program requirements.

Application Development Considerations

  • Discussions around whether to develop a full ordering application or just a loyalty-focused one highlight strategic planning considerations based on user needs.

Client Interactions and Follow-ups

Client Communication

  • A conversation about client follow-up procedures indicates ongoing communication efforts with clients regarding project developments.

Example Analysis Preparation

  • Plans are made to analyze several competitor websites and applications during the session, aiming at improving their own offerings based on observed practices.

Review of Competitor Applications

Initial Observations

  • An overview of various competitor applications begins; specific examples include "Три Соуса" (Three Sauces), focusing on user experience issues encountered during navigation.

User Experience Challenges

  • Critiques arise regarding how feedback requests are timed post-delivery; suggestions include adjusting timing based on meal preparation times for better engagement.

Live Analysis Session

Real-time Application Review

  • A live review process starts where different applications will be assessed based on usability and design features observed by the speaker.

Specific Application Insights

  • Initial impressions focus on interface design flaws such as unclear category divisions leading to poor user navigation experiences.

Navigation Issues Identified

  • Problems with product categorization hinder effective browsing; users struggle to find desired items without clear guidance or prompts.

Checkout Process Evaluation

The checkout process reveals significant friction points including unnecessary registration steps before completing orders, which can deter potential customers from finalizing purchases.

Delivery Information Clarity

  • Users discover delivery fees only after adding items to their cart, highlighting a lack of upfront transparency that could lead to frustration during checkout.

Address Input Complications

  • Users face challenges when entering addresses late in the ordering process, risking negative experiences if deliveries cannot be fulfilled due to location restrictions.

This structured approach captures key discussions while providing timestamps for easy reference back into the transcript content.

Discussion on Development Costs and Budgeting in App Development

Overview of Current Spending

  • The speaker discusses the monthly budget for development, estimating costs around 800,000 rubles over 36 months, totaling approximately 30 million rubles.
  • They mention that their current spending on app development is about 3.5 million rubles per month, indicating a need for increased investment as client numbers grow.

Comparison with Competitors

  • A comparison is made with another company (Dostoevsky), which has a team of 30 developers and spends around 100 million rubles monthly.
  • The speaker notes that while they have a smaller team, their expenses are still significant when considering salaries and operational costs.

Budget Allocation Insights

  • It’s highlighted that many restaurants can afford to spend around 500,000 rubles monthly if their revenue is approximately 50 million.
  • The speaker emphasizes the importance of having features similar to competitors like Secret Kitchen but acknowledges some missing functionalities.

User Experience Feedback on App Design

Design Critiques

  • The speaker provides feedback on the design aspects of Secret Kitchen's app, noting issues with spacing and font sizes affecting usability.
  • They express concerns about navigation difficulties due to poor layout choices in competitor apps.

Functional Features Evaluation

  • There’s an analysis of how product selection works within the app; users struggle with adding multiple items to their cart efficiently.
  • The discussion includes how delivery options are presented and whether users can easily navigate through them without confusion.

Challenges in Order Processing

Issues Encountered During Ordering

  • Problems arise when entering promo codes during checkout; the interface does not clearly guide users through this process.
  • The speaker attempts to demonstrate mobile app functionality but faces technical difficulties sharing screens effectively.

Payment Process Concerns

  • A lack of online payment options is criticized; it complicates transactions by requiring manual card entry instead of seamless integration like ride-sharing apps offer.

Conclusion and Future Considerations

Summary of Key Takeaways

  • Overall insights suggest that there are significant areas for improvement in both user experience design and backend processing within food delivery applications.

Open Floor for Questions

  • The session concludes with an invitation for questions from participants regarding discussed topics or further clarifications needed.
Video description

Как сделать приложение доставки еды “удобным” и только на этом получить +30% выручки? Что учесть в приложении со стороны гостя и доставки? Как повысить средний чек, глубину чека и частоту покупок с помощью приложения? Ответили на эти вопросы 30 мая 2024 года на открытом вебинаре и поделились своим опытом работы с 200+ ресторанами и доставками: Ями-Ями, Даниловский рынок, DuoBand, FARШ, Лепим и варим и т.д. Спикеры: - Леонид Хуополайнен, Леонид Хуополайнен, сооснователь Starter; 15 лет опыта в заказной премиум-разработке; был сооснователем сервиса доставки еды Neo kitchen Также обсудили: 1. Нужно ли вообще доставке еды приложение? 2. Методы проектирования через вопросы и минимизацию усилий 3. Не очевидные сценарии использования приложения 4. Интеграции с POS, программами лояльности и CRM 5. Управление зонами доставки, режимом работы категорий, приборами и другие необходимые настройки 6. Работу с текущей аудиторией через пуши, акции и уровни лояльности Подробнее о Стартер: https://clck.ru/3AzCbf Написать в телеграмм: @starterapp Почта: sales@starterapp.ru