Hungry App: food ordering service with low takeout fees and high driver pay

[GENERAL] Name and surname of main applicant

Dima Bezzubenkov

[GENERAL] Are you delivering this project as an individual or as an entity (whether formally incorporated or not)

Entity (Incorporated)

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

6

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language

No

[GENERAL] Summarize your solution to the problem (200-character limit including spaces)

We replace traditional apps with open-source apps and decentralized finance. It helps to reduce the price of an average pickup order by 15-30%. Later, we'll add food delivery and better drivers' pay.

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

Yes

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.”

We don't have any technical dependencies, but the project's success also depends on how fast restaurant owners are ready to join the system. Onboarding of the restaurants is not part of this proposal, though, and we've already been working on it, and the response is very positive. But sometimes it takes some time to sign all the papers as some owners can be busy. By the end of this proposal, we will have tech solutions in place - the web app, the mobile apps, the API, and smart contracts. Also, we will have some of the restaurants joined. The onboarding will continue after the proposal is completed and will be a continuous process. 

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] Please provide here more information on the open source status of your project outputs

All our outputs will be fully open source. We are building a protocol, so it has to be open source. We will use MIT license.

We will also open source our client apps that we have already built and are not part of this proposal (Web and Mobile apps), but at a little bit later stage (when we already have fully functional network).

For our idea to work, the code has to be open source and anyone should be able to improve the system and review the source code.

[METADATA] SDG rating

SDG rating:

SDG goals:

• Promote sustained, inclusive and sustainable economic growth, full and productive employment and decent work for all
• Reduce inequality within and among countries

SDG subgoals:

• By 2030, progressively achieve and sustain income growth of the bottom 40 per cent of the population at a rate higher than the national average
• By 2030, reduce to less than 3 per cent the transaction costs of migrant remittances and eliminate remittance corridors with costs higher than 5 per cent
• Promote development-oriented policies that support productive activities, decent job creation, entrepreneurship, creativity and innovation, and encourage the formalization and growth of micro-, small- and medium-sized enterprises, including through access to financial services

Key Performance Indicator (KPI):

• Remittance costs as a proportion of the amount remitted
• Growth rates of household expenditure or income per capita among the bottom 40 per cent of the population and the total population

#proposertoolsdg

[SOLUTION] Please describe your proposed solution

The background:

When Grubhub, UberEats, DoorDash, and other similar food delivery apps were introduced, they brought an effortless and convenient way to order food by choosing from one of the many available restaurants nearby. Nothing like that has ever been possible before. Unsurprisingly they immediately attracted millions of users worldwide. The audience capture was so impactful that if a restaurant wanted to attract customers, they had to be on one of the platforms and had to sign any draconian agreements the app overlords would offer them to sign. Each of those apps is a great tool. But in the hands of corporate middlemen, slowly, step by step, they imposed enormous fees on the restaurants. The restaurants eventually passed the costs to the customers. And instead of decreasing their fees, the apps cut the expenses by lowering earnings for those who are the least in control - the delivery drivers, who often struggle to get even the minimum wage.  

The problem: 

• Revolutionary tools like the Internet and food-ordering apps helped a few individuals to monopolize the market.
• A small group of people in charge of the apps is driven by self-interest, which results in high restaurant fees and low driver pay.
• The audience capture and convenience of the apps don't leave many options for restaurants and delivery drivers.

The reasons behind decentralization and how decentralization can fix the problem:

Any business can decrease the fees even without the blockchain. Even more, at this exact time, ChowNow is already doing exactly that and, slowly but surely, taking over the market share! Before ChowNow, there were other similar startups that gained significant market share by lowering the fees. Each of them was purchased by giants like DoorDash and GrubHub: a so-called "purchase to kill the competitor" and keep prices high. And the apps that control the market are bound by Fiduciary Duty to Shareholders to act in the interests of the shareholders: in other words, maximize their profits. The same fate awaits ChowNow and its management. 

That's why, instead of creating another traditional business, we want to create "a protocol" that can't be controlled by company shareholders, similarly to how the Internet can't be controlled by shareholders (there are none). Blockchain and decentralized governance are the tools to make it possible. By providing decentralized infrastructure based on Cardano, we can eliminate unnecessary middlemen in the process, drastically reduce high fees, reduce the overall cost of each order (especially pickup orders), and significantly increase drivers' pay. Additionally, by leveraging the token economy philosophy, we can find new ways of monetization for the builders and early adopters. 

Which problems can be solved in food ordering?

1. We can significantly decrease fees on pickup orders by removing centralized entities from the equation.
2. We can increase drivers' pay by sending all the fees directly to drivers instead of the app owners.

Both problems are important to solve. But we believe it's better to handle one problem at a time. We will start by reducing fees on pickup orders. This problem is easier to solve, requires less funding, and we can prove that our idea is working. Plus, 75% of all food orders in the US are pickup orders. While the app can be used in any country, we will launch in California - one of the most popular places for food ordering on Earth. When thousands of customers and restaurants already use the system and transact on the Cardano platform, adding drivers and food delivery will be much easier.  

Important: This funding will help us to implement a solution for pickup orders. The driver app and delivery orders are not included in this proposal. While we mention our plans for drivers and delivery orders in this proposal, this problem is harder to tackle and will be included in the second version of the app. Let's handle them one at a time and deliver a strong proof of concept first.

The solution:

The solution will benefit all participants in the food pickup process. Restaurant fees go to zero. Customer fees become significantly lower than in any other available service. Drivers get 100% of the delivery fees. Participants will also receive our utility token for different actions they perform for the network. Smart contracts will transparently redistribute the earnings between restaurants, drivers, customer support members, and builders. We will also use our utility token to measure everyone's involvement in the project. There won't be any sale of the token. The token will be paid for different types of work performed for the network, so there is no expectation of profit derived from the efforts of others. The token will be used for governance purposes, and the participants will be able to vote on the network's decisions, like whether we should pay more to drivers or reduce delivery costs for customers. Additionally, tokens will be used to purchase different privileges in the system, so those participants who prove their understanding of the internal workings of the system will be able to gain a slight advantage over newcomers. 

An interesting side effect of the utility token and the fact that all our apps will be open source is that people will be able to clone the code and span multiple delivery services competing with each other with different governance settings. Some can provide better pay for drivers, and others can vote for higher user discounts. The best approach will win. 

The solution consists of multiple apps and smart contracts:

• Web App. The web application is available in your browser to order food and find restaurants near you.
• Mobile App. Mobile apps for iOS and Android provide a seamless transition from apps like DoorDash to our new app. Our team has a UX designer responsible for user research and ease of use. We put extreme emphasis on simple transition, even for people who have no idea what Cardano and cryptocurrencies are. We will leave an option to pay in fiat. Fiat currencies will be internally converted into ADA so that every fiat transaction will be a transaction on the Cardano platform. However, the users who use ADA will gain immediate benefits and better offers. We hope it will motivate more people to understand the ecosystem and gradually switch from fiat to ADA.
• Restaurant Admin Panel. Every restaurant will be able to access the app that will notify them when new orders come in. The app will also allow editing their menu and other information.
• Customer Support Admin Panel. The web app will help to manage the system's data, track the status of the orders, cancel orders when needed, onboard new restaurants, and so on. 

Parties and how they benefit from the system: 

• Customers. Customers will benefit from eliminating restaurant fees on pickup orders and drastically reducing customer fees, resulting in huge discounts. The discounts are parameters in the system that are governed by the utility token and can be changed by the community to achieve the best experience for all parties. Customer fees will become approximately 10 times smaller than current DoorDash fees and will be used to support builders and customer support members.
• Restaurants. We will entirely get rid of restaurant fees.
• Builders. Builders will be rewarded with the minor fees paid by the customers and the utility token's monetary expansion.
• Drivers (Future Versions, not included in the current scope). Drivers are the second primary beneficiary of the system. We plan on the biggest chunk of the profits going to the drivers. However, the distribution of the earnings in the system will be governed by the utility token and can be changed in the future by the community vote.

The Prototype:

You can find landing and test version of the Web App using this link: https://hungryapp.io.

You can find our designs here: Link to the design (Web and Mobile apps) And here: Link to the Admin Panel design

By the time of the Fund12 launch we will also have the mobile apps for both Android and iOS ready (their implementation is not a part of this proposal).

Web App Map:

Web App Menu:

Mobile App Restaurants:

Mobile App Menu:

Restaurant Admin Panel:

[IMPACT] Please define the positive impact your project will have on the wider Cardano community

In what way will the success of our project bring value to the Cardano Community? 

The proposed solution is a marketplace that can attract hundreds of thousands of active users to the ecosystem. Let's look at DoorDash as a competitor and analyze some of the DoorDash statistics:

• DoorDash generated $6.58 billion in revenue in 2022, a 34% increase year-on-year
• DoorDash had 32 million active users who use the app at least once a month
• Doordash has more than 390,000 grocery markets and partnered restaurants on its platform. 
• Doordash is available in over 4000 cities in North America.
• 75% of all food orders in the US are pickup orders

Even if we can attract only 1% of their audience, it's already 320k orders per month. And nothing sells better than the idea of a 20% discount on everything. We believe even a minor investment in marketing can attract enough people to make it worth the investment. 

Benefits for the Cardano platform:

• Even assuming a minimal success of the app, it will attract thousands of users to the platform.
• The ability to use fiat that’s converted into ADA internally will add even fiat-based users to ADA transaction statistics and will help easily onboard new users.
• We will conduct professional UX research. One of our top priorities is the easy-to-use interface. We believe it will help attract a new audience who didn't know much about crypto before.
• The product will be a perfect example of how the blockchain can change the way people conduct online business using open-source software. And this example will be built on Cardano.
• It's perfect timing for an app built with governance in mind. Cardano is at its Governance stage of development. Governance has become more important than ever. Cardano has all the features we need to make the app succeed. There is also a high chance of a bull run around the moment of our launch. Rewards in the form of utility tokens will be very attractive to the customers, restaurants, and drivers, making the marketing of the system much easier.
• Cardano will have one more real-world applicable use case with a real-world utility that is easy to understand for non-tech people. 
• We will use the Cardano logo on every delivery and pickup food bag just because it is cool!!!

How will we measure this impact?

We need to establish metrics we are going to use to measure a success of the project. If we succeed in each of them, it would mean the automatic success of the project. 

Let's define the target goals first: 

• Our apps should be up and running and bug-free by the time of the launch
• Target areas should be chosen based on available statistics: the most popular areas for the food ordering apps
• Restaurants in the target areas should be integrated with our system
• Customer support should be up and running
• A Cardano-based utility token should be integrated into the system
• Become profitable, so we don't need an investment for the second part of the project (integration of the drivers)
• Open-source every piece of the project (100% open source solution)

Based on the target goals, we need to track progress for the following metrics:

• Number of restaurants we onboard in selected areas monthly
• Number of transactions conducted in the system monthly
• Number of users converted from fiat to ADA and using crypto wallets directly
• Average revenue per customer
• Customer acquisition cost: how well do our marketing campaigns perform?
• Customer conversion rate and A/B Testing 
• Customer churn rate: how often do customers return? 
• Customers Feedback: App Store reviews, Freshdesk requests, Customer support queries
• Restaurant conversion rate: how easy is it to onboard new restaurants?
• Restaurant churn rate: why do we lose some of the restaurants?
• Social Media Engagements
• SEO performance: how many unique visits do we get from search engines? 
• Cardano community feedback: is there anything we can do to add even more value to the Cardano ecosystem? 

How will you share the outputs and opportunities that result from your project?

We also need to gather as much of a community feedback as we can, and also be accountable with our work for the community. Let's define detailed steps for sharing the results and outputs of our project:

1. We want to understand what can be done better to improve our users' experience

We want to engage with our audience in the most transparent and informative way. And we want our audience to be able to discuss our project and share their ideas openly. The online community on Discord, Telegram, and Social Media will help to exchange ideas and get real-time feedback from restaurants, customers, drivers, and the community. We will convert the gathered feedback from the online groups and our Freshdesk tickets into Github proposals. 

2. We want to know how we can help the Cardano community and platform to grow

We will engage with the Cardano community through the same online channels (social media, online chats, and groups). But also through conferences and online and real-life events and Q&A. The ideas and suggestions will be converted into Github proposals. 

3. We want to share our updates and announcements

Social media, online chats, our website, and our blog will help to share updates with the community. Participation in startup-oriented podcasts, YuoTube video blogs, and industry-specific conferences can help share the details outside the community and spread the word.  

4. We want to show to the community that we meet the deadlines and deliver on our promise during every milestone 

Publicly available Scrum boards with task statuses and estimations will help the community understand the project's state and how close we are to promised results. 

5. We want to be able to make accurate predictions and estimations about the future of the project based on growth metrics.

We will share our current metrics and statistics of growth in the publicly available dashboard. Revenue, customers and restaurants acquisition and churn rates, and other metrics (see "How will we measure this impact?" section above for reference). 

6. We want to find new possible collaborations inside the Cardano community to help each other and the platform grow

Collaboration with other Cardano projects is essential and can help leverage the experiences of each other to grow. We will prioritize real-life meetings and constant online collaboration through mediums like Twitter Spaces or one-on-one calls and meetings with leaders of other projects.

7. We want to increase awareness and publicity for the project and the Cardano platform.

We will publish research papers, guest articles, and case studies. Participation in startup-related podcasts and YouTube vlogs can help attract founders and investors outside the Cardano community. The same can be said about participation in conferences, tech, and industry-related events. 

8. We want to gather insights from experts in the industry and outside of the industry.

The priority is networking and meeting new people with an influence outside of the Cardano community and sharing our vision and story and how the Cardano platform helps to build decentralized businesses in an innovative way. Sharing the necessity of strong basics, decentralization, and a strong community behind the web3 project can explain why Cardano is better than other platforms. 

[CAPABILITY & FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

A short answer:

1. We already have approximately 60-70% of the product built (see the links to the prototype and proof of the concept below).
2. We are a team of 25 specialists with expertise in web and mobile app development. We have backend and frontend engineers, DevOps and SecOps specialists, project managers, and professional UI/UX designers in-house.
3. We have Haskell and even Plutus school in-house (and we are learning Aiken now!). 
4. We are a software development agency with 7+ years of experience built from zero without any funding or connections at the time. Managing funds is our second job.
5. We are totally fine with being paid upon delivery of every milestone instead of being paid upfront. We work this way for almost 8 years. We have a one-month trial period for all our clients because we are confident in our ability to deliver.
6. Our location is perfect for the project. Our main office is in California - one of the biggest markets for food ordering in the world.  
7. But many of our engineers are also located worldwide (mainly in Eastern Europe and the US, but also in Latin America and Central Asia). That helps to keep our costs reasonable and significantly lower than what it could be with 100% local team.

A long answer:

1.We already have approximately 60-70% of the product built.

What do we already have?

1. Professional UI/UX Research and Design of every app, especially customer-facing Web and Mobile apps. Link to the design (Web and Mobile apps)
2. Web App with the ability to search for restaurants and their menu items, create orders, and submit them into the system without payment. It's a proof of concept and still work in progress. The payment system implementation is not ready yet and is a part of this proposal. You can find it here https://hungryapp.io.
3. Mobile Apps for Android and iOS are in development and will be ready by the time of Fund11 launch. The users will be able to search for restaurants and their menu items, create orders, and submit them to the restaurants without payment. The payment system implementation is not ready yet and is a part of this proposal.
4. An open API that we use to communicate with our central database.
5. DevOps processes for a convenient and easy way to perform autotests, check the quality of the code, deploy code to different environments, and scale the infrastructure on-demand

What do we still need to implement?

1. Payment system: integrations with wallets (both desktop and mobile)
2. Smart contracts for payments, fee management, and governance
3. The Admin Panel for customer support, quality control, accounting, and data management
4. The Restaurant App for restaurants to manage their data and receive/process orders from customers
5. The utility token, tokenomics, and the ability to convert fiat to token and back in a transparent manner 

2. We are a team of 25 specialists with expertise in web and mobile app development.

You can learn more about our team here: https://www.devteam.inc. We have backend and frontend engineers, DevOps and SecOps specialists, project managers, and professional UI/UX designers in-house. Please check the video of some team members saying "Hi!" in the "Team" section below!!! We can start immediately. We already have all the team members we need, including Plutus developers (who are learning Aiken now and we will probably use Aiken in production instead) and even the UX designer who will help us build an easy-to-use web3-based system.   

3. We have Haskell and even Plutus school in-house. 

As a software development agency, we also offer Web3 software development services. And we have our own internal Plutus school (based on the amazing Plutus pioneer program by Lars Brünjes). We already have engineers who we need to deliver the smart contracts. And we are working on adding Aiken to the program now. 

4. We are a software development agency with 7+ years of experience

We have extensive experience in web and mobile app building and budget management. We don't have external funding, so we have to rely on constant cash flow and be aware that clients come and go, but we don't let our people go even in the most challenging situations. 

5. We are totally fine with being paid upon delivery of every milestone instead of being paid upfront.

We work like that for almost 8 years. One of the main features that you can find on our website is that we provide a one-month trial period. We are confident that we can deliver on what we promise. 

6. Our location is perfect for the project. Our main office is in California 

The US and, specifically California, is one of the world's biggest markets for food pickup and ordering. Los Angeles, Bay Area, San Diego, and Sacramento are all top places by the number of orders on DoorDash. It means it is much easier to make the project profitable and then expand to other regions of the world. 

7. Many of our engineers are also located worldwide

We have a small team in the US, Los Angeles. But most of our members are in Eastern Europe, Poland. This combination of engineers across different time zones helps to keep costs reasonable and makes it possible to deliver projects much cheaper than many other companies. 

[PROJECT MILESTONES] What are the key milestones you need to achieve in order to complete your project successfully?

Milestone 1: A restaurant onboarding process

Duration: 4 weeks (1 month)

Tasks: 

• API functionality:
• admin authentication
• Restaurant management: add new, update the info (description, phone numbers, addresses, working hours, photo, type of the food, and so on)
• Menu management: add/modify/delete products and their available sizes and ingredients
• Payments to restaurants (no code at this stage, just adding Stripe accounts and Crypto wallets to the system) for all 4 cases:
• The customer pays in fiat; the restaurant receives money in fiat.
• The customer pays in crypto; the restaurant receives money in fiat.
• The customer pays in fiat; the restaurant receives money in crypto.
• The customer pays in crypto; the restaurant receives money in crypto.
• Admin Panel:
• Restaurant management functionality: add/modify/delete. 
• Menu management functionality. 
• Photos upload. 
• Working hours. 
• Available ingredients. 
• Categories of the food.  
• Restaurant App: 
• Authentication
• Ability to edit its own information: contact details, working hours, etc
• Menu, ingredients, categories management
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity

Acceptance Criteria:

• At this point, we should be able to add new restaurants into the system via the API and our Admin Panel.
• Restaurants should be able to edit their own information via the mobile app.
• Restaurants can receive the payments in fiat and crypto (the infrastructure is in place - Stripe and crypto wallets, but no functionality in the apps yet)

Outputs and Evidence to validate the acceptance criteria:

• Anyone should be able to add new restaurants through admin-test.hungryapp.io and admin-staging.hungryapp.io or via API at api-test.hungryapp.io and api-staging.hungryapp.io using publicly available test and staging credentials.
• API documentation should be publicly available.
• Anyone should be able to query existing restaurants via api-test.hungryapp.io, api-staging.hungryapp.io, and api.hungryapp.io (the production environment)
• Anyone should be able to download the Android and iOS apps for restaurants and play with publicly available data for test and staging versions. Also, anyone can add their restaurant to the production environment, but they will have to go through the KYC process.  
• Demo video with the presentation of the restaurant onboarding process. 
• Demo video showing auto-generated Stripe accounts and Crypto wallets for the added restaurants. 
• Daily updates and community engagement on Twitter and in online channels. 

Costs: 33,000 ADA or 15.72% of the Grant Amount

Milestone 2: Process incoming orders functionality

Duration: 6 weeks (1.5 months)

Tasks:

• API functionality
• Ability to create/modify/cancel order
• Track the order status
• Admin Panel functionality:
• Ability to track submitted orders
• Ability to manage the order status and cancellations
• Restaurant App functionality:
• New order notifications 
• Detailed order and customer information
• Order status updates and cancellations
• Fiat payments with Stripe (Web2 functionality)
• Restaurants onboarding in the target areas
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity

Acceptance Criteria:

• We should be able to create new orders using the Web App, iOS and Android mobile apps, and the API.
• The payments should be sent via credit/debit card using fiat. 
• Restaurants should be able to receive the orders and process them by updating the order status in the Restaurant App.
• Operators should be able to monitor the status of the orders and notify restaurants and/or customers in case of bottlenecks.

Outputs and Evidence to validate the acceptance criteria:

• Anyone should be able to create / modify / cancel orders and query the order's status via api-test.hungryapp.io and api-staging.hungryapp.io using publicly available test and staging credentials.
• The API documentation should be updated and publicly available.
• Anyone should be able to query existing restaurants and orders via api-test.hungryapp.io, api-staging.hungryapp.io, and api.hungryapp.io (the production environment)
• Anyone should be able to download the Android and iOS apps for restaurants or operators, receive incoming orders, track / update their status, and conduct quality control on test and staging versions. 
• Live presentation showing the entire process of ordering via API and how real restaurants receive and process orders in a production environment. 
• Daily updates and community engagement on Twitter and in online channels. 

Costs: 46,700 ADA or 22.24% of the Grant Amount

Milestone 3: Wallets Integration

Duration: 4 weeks (1 month)

Tasks: 

• Integration with crypto wallets in the Web and Mobile apps.  
• Ability to pass all 4 payment flows (fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto).
• Payments are received by the restaurant to their fiat or crypto wallets. 
• Restaurants onboarding in the target areas
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity

Acceptance criteria:

• Users should be able to use their browser wallet extensions to pay for orders in crypto using the Desktop version of the Web App.
• Users should be able to use their mobile app wallets to pay for orders in crypto using the DApps browser (at least 2 wallets are integrated)
• Users should be able to pay in crypto from the mobile app using an integration with a mobile app wallet (at least 2 wallets are integrated).

Outputs and Evidence to validate the acceptance criteria:

• Users should be able to connect their crypto wallets to their accounts and send crypto payments via hungryapp.io or Android and iOS mobile apps.
• Users should be able to use their credit cards and send fiat payments via hungryapp.io or Android and iOS mobile apps.  
• We should demonstrate all 4 payment scenarios: fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto.
• Daily updates and community engagement on Twitter and in online channels. 

Costs: 33,000 ADA or 15.71% of the Grant Amount

Milestone 4: Fiat payments mirroring on the blockchain

Duration: 2 weeks (0.5 months)

Tasks: 

• Ability to pass all 4 payment flows (fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto)
• Fiat transactions are just a facade and trigger crypto transactions and the code on the blockchain.
• Restaurants onboarding in the target areas
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity

Acceptance criteria:

• Every payment, including fiat payments, should trigger crypto transactions on the blockchain (but no smart contracts at this stage, just simple transactions and hardcoded fees). 

Outputs and Evidence to validate the acceptance criteria:

• Every payment should trigger a transaction on the Cardano blockchain.
• We should demonstrate all 4 payment scenarios: fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto. Every scenario should trigger the transaction on the Cardano platform.
• Daily updates and community engagement on Twitter and in online channels. 

Costs: 21,300 ADA or 10.14% of the Grant Amount

Milestone 5: Smart Contracts, Governance and Decentralization

Duration: 5 weeks (1 month 1 week)

Tasks: 

• Smart contracts implementation and testing. Fees are becoming part of smart contracts and can be voted on. Nobody can change the fees in the system unless there is a network consensus. 
• Restaurants onboarding in the target areas
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity

Acceptance criteria:

• Fees are part of the smart contract and can't be changed in a centralized way, opening the door for governance implementation.
• Every transaction, including the fiat payments, triggers the smart contract.

Outputs and Evidence to validate the acceptance criteria:

• Every order triggers the execution of the smart contract.
• The only way to change the fees in the system is through the governance process by the community vote
• Daily updates and community engagement on Twitter and in online channels. 

Costs: 40,000 ADA or 19.05% of the Grant Amount

Final Acceptance Milestone : Accounting, statistics, and testing

Duration: 4 weeks (1 month)

Tasks:

• Bug fixing
• Performance and scalability tunings
• Minor improvements when required
• The accounting dashboard in the admin panel
• Publicly available statistics dashboard 
• Covering of the main flow and API with automatic tests if the time left
• Restaurants onboarding in the target areas
• Project Management:
• Tasks management
• Feedback gathering
• Reporting to the community
• Community engagement and publicity
• Launch and a marketing campaign

Acceptance Criteria:

• Fully functioning and stable product (MVP is released)
• Publicly available statistics (dashboard with different kinds of charts)
• The marketing campaign in the target areas

Outputs and Evidence to validate the acceptance criteria:

• The described solution should be stable and don't have any performance issues. Anyone can start using it in real life. 
• Anyone should be able to access the dashboard showing current metrics and the performance of the system at metrics.hungryapp.io. 
• Demo of the marketing campaign: YouTube advertising, social media ads, marketing brochures (the brochures work when you target specific areas as we are going to)

Costs: 36,000 ADA or 17.14% of the Grant Amount

[RESOURCES] Who is in the project team and what are their roles?

Please meet our team! 

We recorded a short intro video here: Our Team Video Intro!

You also may have met some of us at the Cardano Summit!

We are Dev Team Inc, a software development agency with expertise in building web and mobile apps and everything that goes hand in hand: cloud infrastructure, database management, big data and data analysis, UI/UX design, and business analysis. One of our priorities at the moment is to move into Web3 and DApps, and many of our engineers are fans of the Cardano platform. We also have our Plutus school and our pool that we plan to use to finance our school, but it's a work in progress at the moment and has yet to be finished.

Our website: https://www.devteam.inc/

Our members who will be participating in the project: 

1. Dima Bezzubenkov

Role: Product Manager

Responsibilities: 

• Requirements gathering and features prioritization
• Restaurants and drivers onboarding
• Customer feedback and research
• Budget management
• Marketing and publicity
• Community reporting
• Teams interaction (development and marketing)
• Software development, if required 

LinkedIn: https://www.linkedin.com/in/dimabezzubenkov

Twitter: https://twitter.com/dimabezzubenkov

2. Dmitry Nikolaev

Role: Team Lead and Senior Full Stack Engineer 

Responsibilities: 

• Core architecture decisions
• API and backend development
• Authentication process development
• Angular-based web app development
• Plutus smart contracts development and deployment
• DevOps, SecOps, CI and CD processes
• Monitoring, Logging, Scalability
• Code review and analysis
• Bugfixing, performance, and scalability tunings
• Helping the rest of the team when needed

LinkedIn: https://www.linkedin.com/in/dmitry-nikolaev-37206871/

3. Vadzim Antonau

Role: Senior Full Stack Engineer

Responsibilities: 

• API and backend development
• Angular-based web app development
• Plutus smart contracts development and deployment
• Pull requests review
• Bugfixing, performance, and scalability tunings

LinkedIn: 

Vadzim: https://www.linkedin.com/in/vadzim-antonau/

4. Slava Draneu

Role: Mid Full Stack Engineer

Responsibilities: 

• API and backend development
• Angular-based web app development
• Plutus smart contracts development and deployment
• Pull requests review
• Bugfixing, performance, and scalability tunings

LinkedIn: 

Slava: https://www.linkedin.com/in/viachaslau-draneu-252246243/

5. Alex Pinchuk

Role: Mid Full Stack Engineer

Responsibilities: 

• API and backend development
• Angular-based web app development
• Plutus smart contracts development and deployment
• Pull requests review
• Bugfixing, performance, and scalability tunings

LinkedIn: 

Alex: https://www.linkedin.com/in/alexanderpinchuk1/

6. Yauheni Kakhnouski

Role: Mid Full Stack Engineer

Responsibilities: 

• API and backend development
• Angular-based web app development
• Plutus smart contracts development and deployment
• Pull requests review
• Bugfixing, performance, and scalability tunings

LinkedIn: 

Yauheni: https://www.linkedin.com/in/yauheni-kakhnouski/

7. Liza Harokh

Role: Manual and Automation QA Person

Responsibilities: 

• Manual testing of the web app and mobile apps
• Creating test cases and test plans 
• Bug reporting
• API autotests with PostMan
• UI autotests with Selenium

LinkedIn: https://www.linkedin.com/in/lizaveta-harokh-3ab028217/

8. Suhrob Abdurakhmanov

Role: Senior UI / UX Designer 

Responsibilities: 

• UX Research and competitive analysis
• User personas and user flows identification.
• Low-level and high-level wireframing
• Prototype creation
• UI design based on the prototype

LinkedIn: https://www.linkedin.com/in/suhrob-abdurahmanov/

9. Yelena Elbaum

Role: Accountant and Legal Advisor

Responsibilities: 

• Set up a legal entity
• Bookkeeping
• Yearly and quarterly filings 
• Crypto accounting and bookkeeping advisory

LinkedIn: https://www.linkedin.com/in/yelena-elbaum-cpa-ctc-150a8a51/

[BUDGET & COSTS] Please provide a cost breakdown of the proposed work and resources

Please look at the spreadsheet file here. And you can find a detailed breakdown for every milestone below:

[VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

The proposal cost is 210,000 ADA, we also believe it is an easy-to-sell idea for the masses (20% permanent discount on every takeout order for anyone). Return on the investment for this proposal will be disproportionally justified even if we can get only 1% of the DoorDash audience. 1% of the DoorDash audience translates to: 

• 320k transactions on Cardano per month, even when users are using fiat.
• Our audience can be people unfamiliar with crypto yet who can be intrigued by additional benefits available only for Cardano users.
• If we can convert at least 30% of that audience to use the Cardano platform directly and pay in ADA or our native token, we will have additional 100k monthly users on the Cardano platform. 
• It's a real-world example of how the elimination of the middlemen with the help of decentralization can benefit all participants of the system. But for that idea to work, we must build on a truly decentralized platform - Cardano. It's a showcase for VCs why true decentralization matters and why they need to pay more attention to Cardano. 

A detailed breakdown of the costs for every milestone can be found in the Budget Breakdown document in the section above. It is based on the average salaries of software engineers in Belarus, Ukraine, and Poland:

• $4,000 a month for a Senior Engineer 
• $2,500 a month for a Mid Engineer 
• $1,700 a month for a Manual + Automation QA Person (we need only 20 hours a week of QA for this project)