Dynery — World Cup Market Readiness Sprint Brief

Strategic thesis

Dynery is the coordination, discovery, and transaction layer for real-world dining behavior

The World Cup is our first city-scale behavioral catalyst — creating concentrated movement, creator amplification, restaurant activation, and transaction density in Seattle. This sprint is the forcing function for Dynery's transition from a discovery product into a measurable dining coordination and transaction ecosystem.

Dynery Pay going live during the World Cup is the anchor milestone — but the broader objective is proving the Dynery coordination ecosystem. Every feature, integration, creator activation, map surface, and restaurant workflow must support that ecosystem outcome. Wale Martins, CEO · Sprint directive

Sprint theme · May 15 to June 15

Ship Dynery Pay. Make it work for the World Cup. Use the World Cup to prove the business.

Stability fixes that do not support this deadline are deprioritized. Investor proof comes from live transactions at a real event — not from a polished dashboard alone. If it doesn't strengthen one of the four growth loops, it waits.

Success criteria

What success looks like on June 15

Every item below must be true before Dynery Pay activates at Pie Bar. This is the go-live checklist.

Dynery Pay processes live transactions at World Cup partner venues
Pie Bar and founding partner venues fully discoverable in Dynery
World Cup watch locations visible through map-based discovery
Creator content tied to World Cup dining behavior is live
Happy Hour and access-tag redemption flows functioning
Attribution and engagement metrics being captured
Users can coordinate real-world dining activity around matches
Dynery demonstrates measurable restaurant engagement and transaction intent

Disposition categories

How every issue is classified

In sprint

Explicitly committed in the current sprint

Partial scope

Only the strategically necessary subset is included

Deferred

Intentionally postponed until after the World Cup sprint

Operational

Handled manually or outside engineering scope

Re-evaluate

Requires future product clarification

Strategic growth loops

The four loops that every backlog item must strengthen

Every item included in this sprint either strengthens one of these four loops, improves World Cup readiness, supports Dynery Pay execution, strengthens restaurant value, or contributes to the long-term data moat. If it doesn't — it waits.

Discovery loop

Search → View → Save → Share → Return

Search geo accuracy
Map Views MVP
Walkable correctness
Restaurant completeness
Menu/dish data
Missing content ingestion

Creator loop

Content → Open → Engage → Attribute

Creator attribution layer
Share card improvements
Creator-linked maps
World Cup creator content
Access-tag experiences

Restaurant value loop

Promo → Discovery → Redeem → Repeat

Promo redemption tracking
Access-tag infrastructure
Restaurant ops layer
ROB Dashboard
Banner feature

Transaction loop

Discover → Order → Pay → Share

Dynery Pay pilot
Pie Bar activation
OpenTable flow fix
Nash/Stream (partial)
Dynery Reserve (deferred)

World Cup readiness track

The first city-scale density event Dynery can leverage

The roadmap prioritizes match-day dining behavior, creator amplification, group movement, restaurant discovery, and transaction adjacency. The World Cup window runs June 15–July 6 across six matches.

Founding activation venues

Soft launch · target Jun 6–8

Quyen's near-stadium restaurant

Soft-launch venue and operational stress-test environment. COO on-site. Any integration failures surface here — not at the stadium on June 15.

Sports bar with beer tap. Highest operational control of any founding partner location.

Go-live: June 6–8

World Cup activation · June 15

Pie Bar — stadium vendor

Approved World Cup stadium vendor and flagship Dynery Pay activation venue across all 6 Seattle matches. Existing POS in place as fallback.

Cannot be the first live test of the payment flow. Dry run required before June 15.

Dry run: Jun 13 · Live: Jun 15

Stripe onboarding — start today

Stripe business verification takes 3–7 business days and cannot be compressed by engineering effort. Initiate onboarding for both venues on May 15. Any delay collapses the Week 3 soft launch window and puts June 15 at risk.

World Cup Map MVP

Nearby match-watch venues
Creator recommendations
Happy Hour overlays
Partner restaurant visibility
Walkable clusters
Trending fan hotspots
Saved restaurants nearby

World Cup intelligence capture

The World Cup is a high-value behavioral data event. Dynery should intentionally capture structured intelligence throughout the activation period.

Venue traffic patterns
Creator influence and conversion
Access-tag usage behavior
Neighborhood movement patterns
Group dining coordination behavior
Match-day transaction timing
Save/share behavior around matches
Restaurant engagement density

Data & Intelligence layer — the long-term moat

Dynery's long-term moat is not UI alone. It is the dining identity graph and behavioral intelligence infrastructure.

Structural data

Tag ontology cleanup
Dish normalization
Restaurant completeness
Geo-intent signals

Behavioral intelligence

Creator-to-restaurant affinity
Match-day dining patterns
Transaction-linked dining intelligence
Behavioral attribution systems

Week-by-week sequencing

Four weeks to June 15

Week 1

May 15–21

Stripe onboarding — both venues
Crash instrumentation complete
Restaurant data — 3 founding partners
Creator framework sign-off
OpenTable fix or disable
Pho Mo Promo completion
Ordering flow scoped

Week 2

May 22–28

Stripe integration build
Ordering flow build
POS integration completion
Search geo accuracy fix
Sharing fixes
Happy Hour access tag scoped
Content brief → Sara

Week 3

May 29–Jun 4

Dynery Pay live — Quyen's restaurant
Real transactions + stress test
Fix soft-launch issues
Pie Bar integration begins
ROB Dashboard first pass
Happy Hour access tag live

Week 4

Jun 5–14

⚑ Go-live gate

Pie Bar full integration
Dry run — match-day volume
Staff operational briefing
Fallback protocol confirmed
Go-live checklist signed off
Jun 15: Dynery Pay at stadium

Failure conditions & contingency planning

Defined downgrade paths if critical dependencies slip

Contingency triggers

Stripe verification incomplete by Jun 1 → reduce activation scope immediately
POS integration unstable → move to redemption-only pilot flows
Crash instrumentation incomplete → pause live payment rollout
Ordering flow instability persists → limit stadium activation scope
Fallback payment handling must always exist through existing venue POS systems

Needle-moving prioritization principle

Every backlog item must strengthen at least one

Acquisition

Does it bring new users into Dynery?

Retention

Does it make users return?

Restaurant value

Does it give restaurants a reason to stay?

Transaction adjacency

Does it move toward revenue?

Defensibility

Does it build a long-term moat?

Investor narrative

Does it make the story materially stronger?

Issue disposition matrix

All 47 items from the tracking issues list

ID	Issue	Disposition	Sprint placement	Reasoning
1.1	Username signup edge case	Deferred	N/A	Low leverage vs WC sprint
1.2	Tag system audit	In sprint	Data & Intelligence	Core recommendation infrastructure
1.3	"Something went wrong" screen	Partial scope	Stability	Only if blocking payments or onboarding
2.1	Phone validation timing	In sprint	Discovery loop	Direct onboarding friction
2.2	Second profile setup trigger	Deferred	N/A	Not critical to WC execution
3.1	Duplicate external sharing	In sprint	Creator loop	Impacts organic growth
3.2	Profile share card image	In sprint	Creator loop	Important for creator amplification
4.1	Comment text-size inconsistency	Deferred	N/A	Low strategic leverage
4.2	Names vs usernames in tags	Deferred	N/A	Minor UX polish
4.3	Comment character limit	Deferred	N/A	Not strategic for current sprint
4.4	Restaurant disambiguation	In sprint	Discovery loop	Direct search/discovery quality issue
4.5	Clear button — data loss	Partial scope	UX Stability	Fix only if low engineering cost
5.1	Push notification cleanup	Deferred	N/A	Not tied to WC goals
6.1	Remove bug icon	Deferred	N/A	Pure cosmetic
6.2	New recs button	Deferred	N/A	Not core to WC readiness
6.3	Walkable category accuracy	In sprint	Discovery loop	Critical to map/discovery trust
7.1	OpenTable redirect broken	In sprint	Transaction loop	Reservation credibility
7.2	Restaurant visual clarity	Partial scope	Discovery loop	Core clutter issues only
7.3	Hours display sequence	Partial scope	Discovery loop	If bundled into restaurant cleanup
7.4	Belltown Pizza photos	Deferred	N/A	Low leverage
7.5	AYCE typo — Do Si Korean BBQ	Operational	Restaurant ops	Simple content correction
7.6	Full address not displaying	In sprint	Discovery loop	Critical venue trust signal
7.7	Phone number completeness	In sprint	Discovery loop	Reduces Google fallback
8.1	Experience share button	In sprint	Creator loop	Supports social discovery
9.1	Search relevance — Pho Ha, geo	In sprint	Discovery loop	Critical for WC discovery
9.2	Missing content flow	In sprint	Data layer	Feeds content moat
9.3	Missing restaurants (OMO Thai Tea)	In sprint	Data layer	Critical venue completeness
10.1	Group Dining overhaul	Partial scope	Transaction loop	Foundational support for WC only
11.1	1-to-1 chat redesign	Deferred	N/A	Wrong timing
12.1	Download attribution	In sprint	ROB Dashboard	Investor proof
12.2	Promo claims tracking	In sprint	Restaurant value loop	Measures conversion
12.3	Bot behavior tracking	Partial scope	Instrumentation	Only if framework exists
12.4	Crash instrumentation	In sprint	Stability — Week 1	Required before live payments
13.1	Dynery Pay	In sprint	Transaction loop	Primary sprint anchor
13.1.a	Nash integration	Partial scope	Payments	Only required subset
13.1.b	Stream integration	Partial scope	Payments	Only required subset
13.1.c	Menus & dishes	In sprint	Discovery/Data	Needed for venue completeness
13.2	Banner feature	Partial scope	Restaurant value loop	Promo-supporting subset only
13.3	Pho Mo Promo access tag	In sprint	Restaurant value loop	Access-tag proof
13.4	Restaurant Console	Partial scope	Restaurant ops layer	Lightweight ops only
13.5	Influencer Console	Partial scope	Creator loop	Attribution visibility only
13.6	In-app instruction videos	Deferred	N/A	Post-onboarding stabilization
13.7	Admin panel	Partial scope	Restaurant ops	Minimal operational tooling only
13.8.a	Happy Hour access tags	In sprint	Restaurant value loop	Core WC activation mechanic
13.8.b	Military discount tags	Partial scope	Restaurant value loop	After Happy Hour is live
13.8.c	Student discount tags	Partial scope	Restaurant value loop	After Happy Hour is live
13.8.d	Creator access tags	In sprint	Creator loop	Creator ecosystem support
13.9	ROB Dashboard	In sprint	Metrics layer	Investor-grade reporting
13.10	Dynery Reserve	Deferred	N/A	After reservation flow validated
13.11	Map Views	Partial scope	World Cup map MVP	WC-focused subset only
13.12	Access tags for creators	In sprint	Creator loop	Core creator infrastructure
13.13.a	Restaurant signup page	Deferred	N/A	Can operate manually
13.13.b	Creator signup page	Deferred	N/A	Can operate manually
13.14	App Clip (iOS) — lightweight entry point for restaurant check-in, Dynery Pay, and creator recommendation links without full app install	Deferred	Consumer Acquisition / Restaurant Activation	Strong strategic fit — tailor-made for physical restaurant touchpoints and creator-driven discovery links. Requires stable restaurant activation, QR codes at partner locations, and a clear acquisition funnel before building. Trigger: post-pilot. Note for Drew: QR/NFC trigger at the table is directly relevant to partner onboarding.

Final strategic direction

The World Cup is the forcing function

The World Cup is the forcing function for Dynery's transition from discovery product into a measurable dining coordination and transaction ecosystem. Every item included in the sprint either:

Strengthens one of the four strategic loops
Improves World Cup readiness
Supports Dynery Pay execution
Strengthens restaurant value
Contributes to Dynery's long-term data moat

Investor narrative · What we say on July 6

"Dynery is becoming the coordination, discovery, and transaction layer for real-world dining behavior in Seattle — powered by creator-driven acquisition, map-based discovery, restaurant engagement systems, access-tag infrastructure, World Cup activations, and transaction-adjacent dining workflows."