A complete engineering blueprint: feature spec across Customer, Chef, Admin and Platform layers, the technology stack, the seven AI workflows, the team you need to hire, the month-by-month build plan, and a clean Scope-of-Work you can download as PDF and send out for quotation.
A working build of the EatCookJoy chef-booking experience — captured directly from the founder's device. Browse 847+ chefs, custom menu builder, AI weekly meal-plan, checkout. Same flow that ships to the UAE store.
Recorded May 2026 · iOS · Plays muted on open — tap the speaker for audio.
Four pillars: the Customer App, the Chef App, the Admin Dashboard, and the cross-cutting Platform-Wide features. Every item below is in scope.
Stack chosen for speed, maintainability and team availability in the UAE / MENA market. Same stack that powered the original $1M ARR marketplace rebuild — battle-tested.
Web app + marketing site in one. SEO-friendly URLs, RSC for speed. Why: one language for web and mobile teams.
One codebase → iOS + Android. 80% shared code, 40–50% cheaper than native builds.
API for bookings, matching, payments. GraphQL keeps payloads small for slow phones.
Postgres for relational data. Redis for instant availability cache. Supabase optional.
Client charges, auto split-to-chef, refunds, AED + UAE VAT invoicing, dispute handling.
AWS for backend / DB / storage. Vercel for the global edge CDN. 99.9% uptime target.
Web Application Firewall blocks attacks in real time. Pen-test before launch — catch vulnerabilities early.
Airtable for chef CRM and ops. Looker Studio for live revenue / bookings dashboards.
The original EatCookJoy marketplace rebuild — the exact stack, AI workflows and team structure summarised on this page — is documented end-to-end in the Hypernest Labs case study. Read it before the vendor call.
Each row is a production workflow the AI / Automation engineer must build. Operates on top of the Tech Stack above.
Day-to-day responsibilities + the exact items to verify on every candidate's CV before hiring. Roles below assume a fractional CTO leading two full-stack devs, one mobile, one AI engineer, one designer, one QA.
8–12 months end-to-end. Foundation first (no rushed code), MVP middle, mobile + AI last, then 1–2 month hardening before launch.
Print or save this section as PDF using the button at the top of the page. The page is configured so the printed file contains only this Scope of Work — no marketing visuals — ready to email to engineering vendors for quotation.
Tap the button to save this Scope of Work as a PDF in your Downloads folder. The PDF contains only sections 1–10 above — no marketing visuals — clean and ready to attach to a Request for Quotation.