Plate / The Outcome Engineer Rev. A. 2026.05

The Outcome Engineer

Concept and logic brief for the review-routing system.

1. Why this exists

The most common question we get: "My reservation platform already collects feedback. Why is this better?"

The answer is one word. Traffic.

When a guest searches for a place to eat, they use Google, not a reservation app. A 5-star review inside OpenTable or Resy is invisible to that search. It helps the platform, not you.

The risk. A single 1-star review acts as a heavy drag on your overall rating. The math usually requires twelve 5-star reviews to neutralize the average damage of one 1-star.

The system. The Outcome Engineer filters the stream. Happy guests get pushed to Google, where their review drives revenue. Unhappy guests get diverted to a private channel, where you can fix what went wrong before it goes public.

2. The workflow

Workflow logic diagram

The system runs in the background. On the real-time tier, the only staff action required is the standard step of closing the table in your terminal.

  1. The trigger. The guest departs.
  2. The contact. The system sends a plain-text, personal email from the GM asking, "Did you enjoy your experience with us?"
  3. The filter. A "yes" click redirects the guest to Google Reviews, public. A "no" click redirects to a private feedback form, with a management alert attached.

3. Ingestion tiers and pricing

Real-Time Ingestion (Standard)

$0.10 / reservation

Best for. SevenRooms, Toast, Tock.
Mechanism. Direct API or webhook.
Speed. Instant on table close.

Universal Ingestion (Bridge)

$0.06 / reservation

Best for. Resy, basic OpenTable, legacy POS.
Mechanism. Proprietary email parsing.
Speed. Next morning following the visit.

4. Visibility and billing

  • The sentiment dashboard. A live Google Looker Studio dashboard tracks sentiment trends, feedback volume, and "save rate" (negative reviews caught before going public).
  • Usage based. You are billed only for reservations the system processes.
  • Walk-ins. Walk-in guests are not billed unless your staff captures their email and attaches it to a profile.
  • Non-responsive guests. The fee applies to every reservation processed with a valid email. The cost covers the digital work to ingest, parse, and verify data.

5. Implementation

Fee. $599 one-time. Covers architecture setup, domain authentication, dashboard build, logic configuration.

Timeline. 48 hours. Day 1: system access and domain authentication. Day 2: logic test and go-live.

Drawn 2026 / J. Fischer / Operator
Book Deployment Call