Read in English

Product Roadmap

WebOustaou's Roadmap: A Year of Shipping, and What's Designed Next

From the first restaurant site going live to a v0.10 beta milestone a year later — the shipped timeline, and the phases ahead: ordering, kitchen displays, and an AI phone agent.

Jul 22, 2026

A Roadmap With No Dates, On Purpose

WebOustaou's internal roadmap deliberately avoids committing to dates. Each phase is designed to be independently shippable, and the schema is built to only ever grow, never require a rewrite to reach the next phase. What follows is what actually shipped, in order, and what comes next.

What Shipped: A Year of Changelog Entries

The public changelog is dated and specific, which makes it a more honest source than any pitch deck. A condensed timeline:

  • July 2025 — the first WebOustaou restaurant site goes live: menu, photos, hours, a map, mobile-first from day one. The admin panel follows two weeks later.
  • August 2025 — Darius Pizza becomes the first restaurant running on WebOustaou in production. Photo management and closing-date handling ship soon after.
  • September 2025 — multi-location management from a single account, and the first public live demo.
  • October 2025 — a dedicated guest-facing site (header, hero, full menu browsing) becomes the default for every new customer, forked from the same production template. Live open/closed status ships alongside it.
  • November 2025 — QR codes: create, customize, and distribute trackable, re-pointable links.
  • December 2025 — legal pages and a cookie-consent banner, ahead of any push to bring on more customers.
  • January 2026 — team accounts: multiple staff members, one workspace, revocable access instead of a shared password.
  • February 2026 — scan statistics for QR codes, and structured ingredient management.
  • March 2026 — local SEO improvements.
  • May 2026 — a bilingual help center goes live, documenting the product as it's actually used.
  • June 2026 — the public roadmap itself ships, teasing what's covered below.
  • July 2026 — a dense month: built-in blog publishing, the "Happenings" feature for one-click event promotion, menu offers and featured-product highlights, traffic-origin analytics — and the v0.10.0-beta milestone, which the team's own changelog entry describes as the point where "the core product is functionally complete."

That's roughly a year from first site to a feature-complete beta — not fast by hype-cycle standards, and that's intentional. Every item above is still running in production for the customer who was there for the first one.

What v0.10 Beta Actually Means

QR code tracking and scan analytics, one of the later additions to the beta

Reaching beta doesn't mean the roadmap is done — it means the back-office core (menu, hours, closures, messages, blog, happenings, menu offers, QR tracking, analytics, billing, team accounts) is complete enough to stop building foundation and start building on top of it. What remains before onboarding customers beyond the first one is a focused polish pass, not new architecture.

What's Designed Next

The public roadmap tags every upcoming item shipped, in-dev, or considering — no vague "coming soon." Currently in-dev or next in line:

  • Ordering core — orders, order items, and structured modification rules (removing an ingredient changes price and composition, not just a text note), built on ingredient and allergen data that's already first-class in the schema.
  • KDS — unified order management and planning — a Kitchen Display System: per-station screens, real-time order routing to the kitchen, unified across every ordering channel. Listed as in-dev on the public roadmap.

Structured ingredient and allergen data — the foundation the ordering phase builds on

Further out, under considering: web ordering with customer accounts and payments, in-venue tablet ordering, automatic kitchen-station ticket routing, and — the most ambitious item on the list — an AI phone agent that can take a restaurant's phone orders directly, with a human fallback for anything it can't handle.

Why the Roadmap Reads Like This

None of these later phases are surprises bolted onto an existing product. The schema decisions in the architecture piece — RLS from the first migration, ingredients as reference tables instead of embedded text, the recent re-parenting of operational data from website to shop — were made specifically so this roadmap wouldn't require rewriting what already works. A closer look at what's coming, including the KDS design itself, is here.

A roadmap without dates isn't a lack of ambition — it's a bet that shipping the right foundation once beats shipping the wrong one fast and rebuilding it twice.