Back to Index / Strategy & Ideation / Ecosystem Stakeholder Journey Map
33 · Dynery × Ecosystem · Stakeholder Journey Map · June 2026

From first encounter to deeply invested

A unified map of the Dynery ecosystem across all three stakeholder types – Dyner, Restaurant, and Creator – from awareness to advocacy. Covers intents, actions, surfaces, pilot readiness tiers, dependency sequencing, and gap analysis with pillar ownership.

Issued  June 2026 Owner  CEO Version  v1.0 Scope  57 surfaces · 4-phase dependency chain · 11 named gaps
Purpose · Scope · How to read this document

Three stakeholders. One ecosystem.

Dynery's value isn't created by any single stakeholder — it emerges from the interaction between all three. This document maps that interaction from the moment each stakeholder first encounters Dynery to the moment they become a driving force within it. It is both a strategic model and an operational tool.

The restaurant activates the loop. The creator drives people into it. The Dyner completes it. Remove any one leg and the others stall. Core dependency thesis — Doc 33
Stakeholder 01
Dyner
Dynery's term for restaurant guest and consumer. The Dyner is the end beneficiary of the ecosystem — they discover restaurants, earn Dyneros, build habits, and eventually recruit others. Their journey is primarily driven by creator content and restaurant activation quality.
Stakeholder 02
Restaurant
Independent restaurants are the physical infrastructure of the ecosystem. Without live restaurant activation — QR codes, menus, staff briefing — no Dyner loop can complete and no creator has anything real to send their audience to.
Stakeholder 03
Creator
Local food creators are Dynery's primary acquisition engine for Dyners. They convert passive social media attention into app installs and first visits. Their confidence in the platform depends on restaurant quality and live attribution infrastructure.
The dependency chain

Sequence matters. These are not parallel tracks.

Restaurant activation unlocks the Dyner loop. The Dyner loop must be coherent before creators are asked to drive traffic into it. Creator activation then becomes the acquisition engine that scales both Dyner acquisition and restaurant ROI simultaneously. Running all three in parallel without respecting this chain wastes effort and erodes trust with each stakeholder group.

Phase 1: Restaurant live → Phase 2: Dyner loop working → Phase 3: Creator activated → Phase 4: Habit and flywheel.

Five stages

01
Awareness
First encounter with Dynery — usually through a creator post, a friend, or a restaurant visit
02
Discovery
Active evaluation — exploring the app, reviewing the pitch, reading the doctrine
03
Activation
First real transaction — first check-in, first go-live, first post. The loop completes for the first time.
04
Habit
Repeated, self-motivated engagement. Dynery is now part of the stakeholder's regular behavior.
05
Advocacy
Active recruitment — referring restaurants, recruiting creators, referring friends. The flywheel turns.
Unified journey map · All three stakeholders · Click any cell to expand

Intents, actions, and surfaces — across the full arc

Each cell shows the headline intent and key surface tags for that stakeholder at that stage. Click to expand the full breakdown of intents, actions, surfaces, and intersection dependencies.

Dyner
Restaurant
Creator
↔
Intersection point
57 surfaces · 9 categories · Pilot readiness tiers · Pillar ownership

Every surface and touchpoint

All surfaces across the ecosystem, organized by category with pilot readiness tier, stakeholder, stage, and pillar ownership. Must-have surfaces are those required for each stakeholder's journey to be coherent end-to-end in the Seattle pilot.

Must-have
22
Required for pilot coherence
Nice-to-have
12
Enhances pilot experience
Post-pilot
7
Scale and flywheel phase
57 surfaces
Dependency chain · 4 phases · Strict sequencing

What has to be true before the next phase begins

The three stakeholder journeys are not independent tracks to be run simultaneously at full speed. They have hard dependencies. This sequencing model defines the correct order of operations for the Seattle pilot and beyond.

Gap analysis · Pillar ownership · 11 named gaps

What's missing — and who owns it

Surfaces or conditions with no current owner, a known dependency blocker, or a structural risk to pilot coherence. Sorted by urgency. Two critical gaps — creator attribution and creator compensation — are currently blocking the entire Creator activation phase. Two additional important gaps added June 2026: Creator Access Tag infrastructure and shared link page two-variant build.