Service documentation
Service scope table
What the Restaurant Pack includes and when additional work needs a separate quotation.
An agreed scope before work begins
The project proposal allows the content and presentation to be reviewed before contracting. This table summarises the EUR 350 pack, including VAT and payable in one payment, and distinguishes extensions requiring a separate quotation.
Included work and extensions
| Area | Within the pack | Outside the initial price |
|---|---|---|
| Design | A personalised, responsive website using the restaurant’s identity and materials. | Full redesigns or changes extending the agreed scope. |
| Menu and content | Categories, dishes, descriptions, prices, authorised photos and restaurant information. | Additional languages or content and structural extensions outside the engagement. |
| Contact and reservations | Contact details and reservation requests by email. | External booking systems, ecommerce and online ordering are outside the pack. |
| Publication | Preparation and publication after the client’s approval. | Changes requiring an extension of the agreed features. |
| Infrastructure | Domain, hosting and SSL certificate included during the first year. | From the second year, the restaurant pays for domain and hosting renewals. |
| Maintenance | Maintenance and support for minor updates to existing content are included without a time limit or additional recurring fee. | Full redesigns, additional languages, new functionality, external integrations and changes of scope require a separate quotation. |
How to communicate a minor adjustment
Identify the page, dish or detail to change and provide the correct content. Examples include correcting opening hours, replacing text or updating a dish price within the existing structure.
Full redesigns, additional languages, new functionality, external integrations and changes of scope require a separate quotation.
Points reviewed with the restaurant
- Available content and authorised photographs.
- The menu and practical details that should appear in the published version.
- Contact channels and how reservation requests are handled.
- Use of an existing domain and the configuration needed.
- The person who reviews and approves the final version.