Our work
Systems in daily use.
Restaurants, businesses, NGOs, a school, and a social center in Lebanon run their daily work on systems Tikram built and still supports. Client names stay private.
Case study 1
A multi-branch grill restaurant group.
A Lebanese grill and broasted chicken restaurant group needed one system for online orders across its branches: one menu, each branch running its own kitchen, stock, and drivers, and a head office that sees everything. Tikram built the branded ordering website and the system behind it, and it now runs every branch.
100% of online orders routed automatically
Every online order lands directly on the selected branch’s dashboard, with that branch’s delivery zones and fees applied. Nobody copies orders by hand between WhatsApp, paper, and the kitchen.
100% of orders announced on WhatsApp
Each new order triggers an instant WhatsApp alert with the full order details, item by item, sent through the official WhatsApp Business API.
Drivers and live tracking
An Android driver app reports location during a shift, staff assign orders to drivers, and customers can follow their delivery live on a map.
Per-branch stock and one shared menu
The owner manages one menu and its prices centrally, while each branch marks its own items sold out.
Reports with Excel export
Sales by order, by item, and by category, for any date range and branch, exportable to Excel.
Promotions built in
Promo codes, branch-specific offers, and a printed QR campaign for first orders, with every discount checked by the server.
Case study 2
A multi-branch fast-casual brand.
A Lebanese fast-casual food brand needed the same discipline without building from scratch. Tikram delivered an ordering and operations system for all of its branches, reusing the proven core and adapting the menu, branding, and options to the brand.
100% of orders routed to the right branch
Delivery, pickup, and pre-orders land directly on the correct branch dashboard, where staff update each order’s status.
Automatic WhatsApp order alerts
Every new order sends an approved WhatsApp message template with the order details, so the team is notified even when no one has messaged first.
Branch dashboards, drivers, and stock
Each branch sees only its own orders, drivers, and stock, while head office manages every branch from one dashboard.
A proven core, not a first version
The brand launched on a core already tested in daily use, adapted to its own menu, options, and branding.
Shared by both restaurant systems
What both restaurants run on.
Both systems offer English and Arabic for customers, Lebanese phone number validation, delivery zones and fees per area, pre-orders, and a staff dashboard that works on a phone. Both are hosted and supported by Tikram and keep improving based on what staff and owners ask for.
Case study 3
Sales, invoicing, and WhatsApp marketing in one system.
A Lebanese business needed its customers, quotes, invoices, and WhatsApp conversations in one place. Tikram built a custom ERP that brings sales, finance, and WhatsApp Business into one system, with an Arabic interface for the team.
Leads to payment in one place
Every lead, note, quotation, invoice, and payment sits on one customer record, from the first enquiry to the final receipt.
Quotations and invoices generated automatically
The system calculates every total, produces the quotation or invoice document, and issues receipts and account statements for recorded payments.
Subscriptions and finance reports
Recurring monthly services, outstanding invoices, and finance reports are tracked without a separate accounting spreadsheet.
WhatsApp Business campaigns
The team sends campaigns with WhatsApp-approved message templates through the official WhatsApp Business API.
A shared WhatsApp inbox
Customer replies arrive in one inbox inside the ERP, so the whole team can see and answer conversations instead of relying on one phone.
Ask the ERP in plain language
The ERP is connected to ChatGPT, Claude, and Gemini, so the team creates quotations, records payments with approval, and asks which invoices are unpaid, all from live data, without opening the dashboard.
Case study 4
Aid distribution for a humanitarian mission.
A humanitarian mission in Lebanon registered families and planned aid in shared spreadsheets, with the distribution rules hidden inside formulas. Tikram replaced the spreadsheets with a web app the team uses to register families, plan distribution rounds, and record every delivery.
One record per family
Each family is registered once, with a code and a full history of everything it has received.
Rules instead of formulas
Who is due food parcels, hygiene kits, baby milk, or diapers is calculated from written, versioned rules (by age and time since the last delivery) that staff can read and change.
Distribution rounds, planned and printed
Rounds are planned per centre and region, printed as lists, and each volunteer sees only their own round.
Every delivery recorded
Deliveries are logged one by one or in batches, so the next round always starts from what was actually handed out.
Roles and an audit log
Each user has a role and permissions, and every change is recorded with who made it and when.
In the team’s language
The interface runs in French, with Arabic and English ready.
Case study 5
Project mission control for an NGO.
An NGO’s mission development office followed its projects, donors, deadlines, and staffing in one large spreadsheet. Tikram built a private mission-control view on top of that data, so the whole portfolio can be read at a glance on a laptop or a phone.
Every project on one map
Projects are shown as a navigable mind map instead of rows in a spreadsheet.
Deadlines, donors, and staffing in view
Each project shows who funds it, who is working on it, and what is due next.
The source spreadsheet stays untouched
The app reads a validated copy of the data, and spreadsheet credentials never reach the browser.
Private by design
Donor, financial, and staffing information stays behind a private deployment.
Case study 6
Management system for a social center.
A community social center managed beneficiaries, consultations, activities, and payments across paper files and spreadsheets. Tikram built one management system the staff use every day.
Beneficiary records
Every beneficiary has one record, with their history across all of the center’s services.
Appointments and consultations
Staff book appointments and record consultations in the same system.
Activities and attendance
Activities are scheduled and attendance is taken in the app, not on paper.
Cashier and reports
Payments are recorded at a cashier screen, and reports are produced from the same data.
Staff accounts and permissions
Administrators manage staff accounts, and each person sees what their role needs.
Case study 7
Management system for a school.
A school needed students, attendance, follow-ups, and fees in one place. Tikram started from the proven core of the social center system and turned it into a separate application with its own database, users, and hosting, so nothing is shared between the two organizations.
Students and follow-ups
Student records with follow-up notes, so staff see the full picture of each student.
Attendance
Daily attendance is taken in the system and feeds directly into reports.
Activities and appointments
School activities and parent or staff appointments are scheduled in one calendar.
School fees
Fees and payments are tracked per student, without a separate spreadsheet.
Reports and staff accounts
Reports for the administration, and accounts with permissions for each staff member.
Immersive websites
This website is the demo.
tikram.ai is a scroll-driven film: scrolling plays the video forward and back, frame by frame, with a separate version made for phones. Tikram builds immersive scroll websites like this for brands, launches, and products that need more than a standard page.