Discuss a project
Planerix REST

Restaurants & hospitality

The whole restaurant. A more useful view.

Restaurant intelligence that brings together performance, guests, bookings, team activity and everyday decisions.

The whole restaurant. A more useful view.

The business

The challenge

Restaurant owners need to understand revenue, demand and guest relationships while keeping up with the operation. That picture is difficult to assemble from disconnected sales, booking and social tools.

The approach

Give owners and managers a focused view of their location and their role. Link available operational sources to comparable trends, guest profiles and an assistant that can explain the underlying data.

Multi-Location CRM & Analytics / Planerix REST

How the solution came together

Built and documented

01The business need

Restaurant teams need to connect location performance with guest conversations and follow-up work across web and mobile.

02What needed to change

Combine restaurant performance, guest context and communications without mixing brands, locations or incomparable source data.

03How it works

Experience
Owner · Manager
Web · native iOS
Rules & processing
REST API · access scope
Analytics · Guest 360
Assistant · event graph
Data & connections
PostgreSQL
POS · ChoiceQR
Meta / Instagram
Simplified architecture · selected implemented components

04What was built

  1. 01

    Brand and location permissions are applied before building the event graph. Aggregate access does not automatically grant guest access.

  2. 02

    Metrics retain period, currency and source coverage. Menu intelligence keeps unknown costs visible; staff indicators stay separate from payroll. HR programs support review, assignment, lessons, server-scored tests and stored progress.

  3. 03

    Instagram Direct, comments and mentions retain source context in the inbox and Guest 360. AI manager assist analyzes intent and prepares reply suggestions; staff review and provider readiness govern sending.

The key decision

Analytics and Guest 360 share restaurant context but have separate access boundaries. The native inbox keeps channel and guest context together; AI proposes a response for staff review.

How we checked it

Brand/location scope is applied before graph construction. Metrics retain period, currency and coverage; contact matches remain candidates until verified. Sending depends on provider permissions and delivery readiness.

  • FastAPI
  • PostgreSQL
  • Next.js
  • SwiftUI
  • iiko / Syrve
  • ChoiceQR
  • Meta

One complete workflow

  1. 01Select a location
  2. 02Review a metric
  3. 03Compare periods
  4. 04Open the source
  5. 05Follow up

05See the work

Native owner analytics, inbox, Instagram thread and Guest 360 screens use synthetic records. Connector, manager-assist and outbox contracts explain the path from intake to a reviewed reply.

Instagram conversations inside REST

Direct, comments, mentions and tagged content connect to conversation history and Guest 360. AI summarizes the request, suggests profile matches and drafts replies for staff review. Available channels depend on account permissions and activation.

REST inboxInstagram conversationGuest 360 profile
Actual REST native app demonstration screens with synthetic guest data. For Ninja Group, these illustrate the platform experience; private customer conversations and internal figures are omitted under NDA.

06Result and responsibilities

Delivered

A restaurant workspace connects guest communications and Guest 360 with bookings, reviews, influencers, electronic menus, menu/staff analytics and HR learning. Available channels follow provider permissions.

Role & scope

Founder & Product Architect · business model, system design, web and iOS

Scope of the result

The delivered platform supports client-branded configurations. Each rollout has its own source coverage, permissions and support scope; no conversion uplift is claimed.

A workflow in practice

From a change in revenue to a better question.

An owner spots a change, compares periods and asks the assistant to explain it. Guest history and operational detail are a step away.

Owner & managerGuest intelligenceAnalytical AI
  1. 01

    Observe

    Start with revenue, bookings and the indicators for the selected period.

  2. 02

    Compare

    Explore trends and rankings to understand where performance changed.

  3. 03

    Explain

    Ask the assistant a question and follow the supporting analytics.

  4. 04

    Investigate

    Open the relevant guest, booking or operating area for more context.

What this makes possibleThe overview, explanation and supporting records sit within one owner and manager experience.

Extend the pattern to multi-location services, hospitality groups and customer-facing businesses.

Build on this pattern

02 / Inside the system

Designed around the work.

01

A daily operating view

Revenue, bookings, performance indicators and comparisons help focus attention on meaningful changes.

02

Guest relationships

Guest profiles bring together linked reservations, conversations and interaction history from available sources.

03

Rankings & trends

Explore guests, menu items and team performance with period comparisons and clear detail views.

04

An analytical assistant

Ask questions in natural language and follow source links to understand the answer.

03 / Product in focus

Explore the interface.

Open a screen to take a closer look.

Actual product interfaces, shown with demonstration data or existing public marketing content.

The connected ecosystem

The tools you know. A more connected business.

Bring familiar software into the way you run your business. Connections are set up around your workflows.

Tailored connections are scoped for your business before setup.

Discuss your software

Product names and logos belong to their respective owners.

Need a similar workflow?

Discuss a project