> For the complete documentation index, see [llms.txt](https://appfront.gitbook.io/portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appfront.gitbook.io/portal/digital/become-a-digital-restaurant.md).
# Become a Digital Restaurant
## **Overview - Appfront Tech is the Growth Engine for Restaurant**
This section will take to the process of becoming a Digital Restaurant. There are 3 important stages in becoming a digital restaurant: (ask yourself where are you at so we'll be able to move to the next step
* **Beginner** - your digital sales is up to **10%** of your business
* **Intermediate -** your digital sales is **10%-25%** of your business
* **Fast Grower - +25%** of your sales are digital
Appfront mission will be to help you move up the stages and help you grow your business, FAST!
## Capture your customers data is the MOST important thing!
**Our marketing campaigns have proved to create a high level of engagement with customers and are powerful tools.** Appfront is working with many fast growing chains and we are working these days on putting everything under our manual.
\- Stay tuned!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://appfront.gitbook.io/portal/digital/become-a-digital-restaurant.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.