Digital for restaurants and cafés: menu, reservations, delivery and advertising without middlemen.
Guests choose a venue by photos on Instagram and a listing in 2GIS, book via WhatsApp and pay with Kaspi. Delivery aggregators take 25–35% of every order. We build a system where reservations and orders come directly to you: a website with a menu and booking form, ads targeting your neighbourhood, CRM for banquets and your own delivery without commissions.
Six directions for restaurants and cafés.
Menu with photos and prices, table reservations, banquet enquiries, own delivery, Kaspi Pay, two languages.
from ₸300,000Mobile appFor chains or high delivery volumes: menu, ordering, bonuses, reservations, Kaspi Pay, push notifications. iOS and Android.
from ₸2,500,000CRM & automationBanquet leads from WhatsApp and Instagram, reservation funnel, reminders, bringing guests back for special occasions.
from ₸350,000SEOCuisine, district and occasion queries, 2GIS and Google Maps, banquet pages, delivery, Kazakh version.
from ₸200,000/moTargeted adsInstagram and TikTok by radius, occasion-specific offers, leads to WhatsApp and CRM, cost per guest in reports.
from ₸150,000/moSearch adsGoogle Ads for banquet and delivery queries, occasion landing pages, call tracking, cost per booking.
from ₸150,000/moThe restaurant business in Kazakhstan runs on three streams: dine-in guests, delivery and banquets. Each has its own funnel and acquisition channel. A dine-in guest finds you on 2GIS or Instagram, looks at photos of the dining room and menu, reads reviews and books a table. Delivery is either your own website and app, or Wolt, Glovo or Яндекс Еда at a 25–35% commission per order. A banquet is a long funnel: enquiry, venue viewing, several WhatsApp touchpoints, a quote and a deposit.
A restaurant's digital infrastructure must cover all three streams. The website shows the menu with prices and photos, accepts table and banquet bookings, and handles delivery orders directly. The CRM manages banquet deals and brings guests back for birthdays. Advertising works within a 3–5 km radius, because most guests live or work nearby.
Below is what we do for restaurants, cafés and bars in Kazakhstan — each direction has its own page with features, integrations and prices.
What restaurants come to us with.
- The menu in Instagram Stories goes stale, prices don't match reality, guests message in Direct — and the administrator replies hours later or loses the messages altogether.
- Delivery aggregators bring orders, but a 25–35% commission eats into the margin; there's no own delivery channel, and dependence on Wolt and Glovo keeps growing.
- Banquet enquiries come through WhatsApp and are tracked in a notebook or Excel — there's no funnel, and it's unclear how many leads are lost at the quoting stage.
- Ads are targeted at the whole city, even though 70–80% of guests come from nearby streets; the budget is spent on people who will never make the trip.
- Reviews on 2GIS and Google aren't collected systematically: the rating is dragged down by two old negative comments that every new guest sees.
- There's no tool for repeat visits: a guest came once, enjoyed it, but the restaurant never followed up — not a month later, not before the holidays.
What matters specifically in Kazakhstan.
- 2GIS is the primary tool for finding a nearby venue: a listing with photos of the dining room, menu, prices, opening hours and responses to reviews influences guest flow no less than the website itself.
- Kaspi Pay is a mandatory payment method in the dining room, on the website and for delivery; the option to pay via Kaspi QR without a terminal lowers the barrier for smaller venues.
- WhatsApp is the main channel for reservations and guest communication; WhatsApp Business API allows booking confirmations and reminders to be sent automatically from the CRM.
- Two languages — menu, website and ads in Russian and Kazakh: the Kazakh-speaking audience is growing in Almaty, and in Astana, Shymkent and the regions, Kazakh-language queries make up a significant share.
- POS systems — iiko, r_keeper and Poster are widely used in Kazakhstan; integrating the website and app with the POS enables real-time synchronisation of menus, stop lists and orders.
- Wolt, Glovo, Яндекс Еда — aggregators drive traffic, but a 25–35% commission makes delivery unprofitable on low-ticket orders; a proprietary delivery channel via website or app pays off at volumes of 200–300 orders per month.
The sequence that pays off fastest.
- Website with menu and reservations — the foundation for everything else: without it, ads lead to Instagram, where guests get lost.
- Location-based targeting on 2–3 offers (business lunch, banquet hall, new menu) — first bookings within 1–2 weeks.
- CRM for banquets — a banquet funnel with automated reminders pays off faster than you'd expect: one saved banquet covers the cost of implementation.
- Own delivery on the website — connects to your existing site, reduces dependence on aggregators and restores your margin.
- SEO — a long-term channel for queries like «café nearby», «restaurant for a birthday in Almaty», «sushi delivery»; results in 4–6 months, but the cost per guest is lower than paid advertising.
Own delivery vs aggregators: when to make the switch.
Aggregators are convenient at the start: traffic is there, nothing needs to be set up. But with an average order value of ₸3,000–5,000 and a 30% commission, the restaurant gives away ₸900–1,500 per order — and receives no guest data.
A proprietary delivery channel — a website or app with Kaspi payment — gives you the full margin and a guest database for repeat orders. Based on our experience and market data, the switch pays off at volumes of 200–300 orders per month: commission savings cover website support and the retention ad budget. Aggregators can be kept as a channel for acquiring new guests, while regulars are moved to direct ordering via a promo code or loyalty card.
Questions from restaurants and cafés.
How much does a restaurant website with a menu and delivery cost?
A landing page for one direction (banquets or delivery) — ₸250,000–400,000; a restaurant website with menu, reservations and two languages — ₸600,000–1,200,000; a website with a delivery module and POS integration — from ₸1,200,000. More details on the restaurant website page.
How do I reduce dependence on Wolt and Glovo?
Launch your own delivery module on the website with Kaspi payment and promote direct ordering to regular guests. Aggregators can be kept for acquiring new guests, but move them to the direct channel with a promo code on the next order.
Does a restaurant need a CRM?
If you have a banquet hall or regular corporate events — yes: a banquet funnel with reminders and quotes in the CRM saves leads that would otherwise get lost in WhatsApp. For bringing guests back on birthdays and holidays, CRM is equally indispensable.
Which advertising works better for a restaurant: targeted or context ads?
Instagram targeting within a 3–5 km radius of the venue — for dine-in guests and delivery in nearby streets. Google context ads — for banquet queries («restaurant for a wedding in Almaty», «banquet hall Astana») and cuisine-specific delivery. We usually start with radius targeting and context ads for banquets.
Does a restaurant need a mobile app for delivery?
For a single venue with up to 500 orders per month — usually not: a PWA version of the website or a mobile delivery page handles the job at a lower cost. An app pays off for a chain or at volumes of 1,000+ orders per month, when you need push notifications, a loyalty programme and order history.
Other industries
Do you run a restaurant or café? Describe your task — we'll tell you where to start and what it costs.
Tell us how many dining rooms and locations you have, whether you offer delivery, where guests currently come from and what hurts most: reservations, delivery or banquets. We'll reply with a plan and quote within 1–2 business days.