Picture four restaurants side by side on Ankara's Kızılay strip: behind the first counter, a 60-year-old esnaf uncle with 32 years on the floor; in the second, a 28-year-old MBA founder with margin tables on his laptop; in the third, an investor-owner meeting weekly with his CFO; in the fourth, a chain regional manager signing a compliance checklist. Same city, same block — but pitch all four with the same script and you'll get four "no thanks." Turkish restaurant operators cluster into four distinct archetypes, and each has a completely different trigger.
Type 1: Esnaf Uncle — Relationship and Slow Trust
50+ years old, two decades behind the counter, sits with the neighborhood at the same tea-shop. His decision metric is one phrase: "Do I trust him?" Excel, ROI, A/B tests — irrelevant. Visit one is not a pitch, it's tea. Visit two: still tea. By visit three, "abi, let's take a look at that QR menu" surfaces organically.
Open: "Mahmut abi, I saw this at Hasan amca's place in Eyüp — he mentioned you." Middle: "No monthly contract, leave whenever." Close: "No signature, I install it myself, try it a week, I'll pull it out if you don't like it." No paper — just a reference.
Type 2: Modern Young Operator — Data and ROI
Age 25-38, often an MBA or returned-from-abroad founder. First question is "average basket lift, what percentage?" Instagram following 10K+, asks about POS integration, wants a dashboard screenshot. He'd fall asleep during esnaf uncle's tea chat; instead he expects a 30-minute Zoom and one PDF case study.
Open: "47 restaurants in Istanbul use us, average basket up 22%." Middle: live screen-share of the dashboard. Close: "First month free, churn anytime, full data export in one click." Concrete number, concrete window, concrete exit.
Type 3: Investor Owner — CFO-Driven
Doesn't operate, owns. Usually came from another industry (construction, textile), employs a manager. You won't meet him — you'll meet his CFO. Single question: "Impact on EBITDA?" Commission structure, payment terms, billing cycle are everything.
- Open: "Cuts monthly COGS 3%, payback in 4 months."
- Middle: 12-month projection plus sensitivity table.
- Close: "24-month MSA, 3-month opt-out, net-60 invoicing."
Type 4: Chain Manager — Compliance and Scale
Big Chefs, Tavuk Dünyası, Mado tier. Decision sits with the central F&B director, not the regional manager. A single-location pilot is rejected outright; he wants 40-location plus integration checklist. Open: "ISO 27001 certified, 99.9% SLA, webhooks open." Middle: SOC2 report + integration timeline. Close: "3-location pilot, written success criteria, 90-day scale." Not bureaucracy — signal of seriousness.
FAQ
How do I identify the type in the first 30 seconds? Read the visual: old cash register = esnaf uncle, iPad POS = modern operator, a manager present without the owner = investor, branded uniforms and signage standards = chain.
Is showing a dashboard to the esnaf uncle a mistake? Yes — he'll call it "confusing stuff" and quietly cross you off. Build trust first; offer the chart only later, as optional.
How many locations in a chain pilot? Three to five is ideal. One looks unserious, ten-plus reads as risk. Three locations plus 60-day metrics is the minimum package that reaches the approval committee.
Found this helpful? Share it.
Related articles
Why Digital Menus Increase Restaurant Revenue by Up to 30%
Studies show restaurants using digital QR menus see measurable increases in aver…
When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS
Most SaaS apps run a single line of code when a customer downgrades — but old fe…
JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers
Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…