How Dynery transforms every meal into a publishable story — automatically — and delivers it to every surface where a guest might want to share, remember, or build their dining identity. The consumer flywheel that makes the platform sticky and the Academy amortization that makes 3% feel like a gift.
Dynery Academy — all seven curriculum modules, the Origin Interview, the Dish Story Workshop, the City Editor time, the Heritage Layer creation — is included in the 3% value-add experience fee, amortized across every transaction the restaurant processes. No upfront fee. No retainer. No consultancy engagement. The Academy pays for itself through volume.
No deposit, no setup fee, no consultancy retainer. The Academy is activated at onboarding and the fee only accrues when transactions flow through Dynery Pay. A restaurant that activates Dynery in March and does $100,000 in Dynery transactions by June has paid $3,000 toward the Academy and platform — and received the Origin Interview, Heritage Layer, and first three Academy modules as part of that.
A bespoke brand storytelling and hospitality experience design engagement from a boutique consultancy — Origin Interview, Heritage Layer, Dish Story Archive, Spatial Narrative, Service Philosophy facilitation, Seven-Act curriculum delivery — would cost $15,000–$50,000 as a standalone project. Dynery includes this in the transaction fee. An operator who processes $500K through Dynery in Year 1 pays $15,000 in experience fees and receives what would cost them $30,000+ elsewhere.
Once the Heritage Layer, Dish Story Archive, and Spatial Narrative are created, they are permanent assets. Every Memory Card generated, every pre-arrival brief sent, every Heritage Card delivered uses these assets. The Origin Interview happens once; the story it produces is delivered thousands of times. The amortization actually improves with volume — the more transactions, the lower the effective per-story cost, while the narrative compound interest accumulates.
At the moment of checkout — and in the 24 hours that follow — Dynery assembles a complete dining story from the behavioral data of the evening and the restaurant's narrative assets. This is the vignette: a rich, visually beautiful, shareable artifact that captures not just what was eaten but the full experience of being in that place, on that occasion, with those people.
Input 1 — POS transaction data: Every dish ordered, every beverage selected, the sequence and timing of courses, the check total, the party size. The behavioral record of the meal, delivered automatically via the POS integration.
Input 2 — The restaurant's Heritage Layer: The four-sentence origin story written during the Academy's Origin Interview. The founding cultural context, the founder's journey, the philosophy that drives every dish. This is the "why" behind the meal.
Input 3 — The Dish Story Archive: For each dish ordered, the three-sentence narrative — provenance, technique, invitation — pulled from the Academy's Narrative Menu Workshop. The dishes become characters in the story, not just items on a receipt.
Input 4 — The occasion context: Was this an anniversary? A first visit? A birthday? A business dinner? A solo dining adventure? Occasion tagging enriches the narrative frame — the same meal on a first date tells a completely different story than the same meal on a fifth anniversary.
Input 5 — Dining companions: Who was at the table? From the guest's Dining Passport, companion history enriches the vignette — "the third time you've brought this person here" or "first time dining with this companion at this restaurant" becomes part of the story without the guest having to say it.
Input 6 — The restaurant's visual assets: Photography provided by the operator during onboarding. Interior shots, dish photography, the space's distinctive elements. These form the visual layer of every Memory Card, every Heritage Card, and every social-share image generated from this dining experience.
Illustrative example — actual vignette generated from POS data, Heritage Layer, Dish Story Archive, and occasion context. AI-authored narrative grounded in the restaurant's own words and the guest's actual meal.
Instant — triggered at checkout. A single beautifully designed card: restaurant name, the evening's defining dish, a one-sentence narrative from the Heritage Layer, the occasion context. Saved automatically to the Dining Passport. The most shared format.
Delivered the next day when memory has settled. A richer narrative — two to three paragraphs — with the Story Prompt response woven in. Includes the Heritage Card and a shareable visual. This is the format that becomes a portfolio entry.
The first of each month: a narrative summary of the previous month's dining experiences. Companion milestones ("you've now dined with Carter at five restaurants this month"), new regulars, occasions celebrated. The dining month as a story.
The flagship annual memoir. Every restaurant, every companion, every occasion, every dish — curated into a personal dining year-in-review. The format guests share widely. The format that makes people say "I need this in my life." The Dynery Wrapped.
How the vignette reaches the guest after every meal. The delivery architecture is layered — some channels are trivially easy and should ship at launch, others require more infrastructure but add significant consumer value. The sequencing below reflects both technical reality and strategic priority.
The single most powerful consumer feature Dynery can build: a personal dining portfolio page, automatically populated from the guest's Dining Passport, publicly shareable, beautifully designed, and requiring zero effort from the guest beyond the act of dining. This is cookcookeateat.com built for you — automatically, from every meal you share through Dynery.
Each year's dining memoir — the Annual Vintage — lives as a dedicated page within the portfolio. Beautifully laid out: the year's most memorable meals, the occasions that defined it, the companions who appeared most, the dishes that became signatures. A growing archive of Annual Vintages becomes a record of a dining life over years — the exact purpose Mark's blog already serves, built automatically from Dynery data.
Every restaurant visited, with the vignette from the first visit, the number of returns, the defining dishes, the companions who joined. Sortable by city, cuisine, occasion, Constellation tier. A guest who has dined at 50 restaurants has a portfolio that reads like a dining passport — not a Yelp profile but a curated collection of relationships with places that matter. The restaurant page links to the restaurant's Dynery Certified profile, creating mutual discovery.
Every dish the guest has ordered across every Dynery restaurant, with the Dish Story narrative attached. The dishes the guest has ordered multiple times are flagged as favorites. The most recent Heritage Card received for a dish is linked. The guest can curate a "signature dish" collection — their own version of the HadBurger series — tracking a single dish across multiple restaurants and iterations. The Dish Collection is the most personal layer of the portfolio and the most compelling for food-passionate sharers.
Dynery Away experiences mapped geographically. Every city visited, every restaurant discovered while traveling, with the vignette tied to the travel context. "Tokyo, November 2024 — the ramen at Fuunji, discovered through the Dynery Away city guide, the day after landing." The map becomes a record of the relationship between dining and travel — the most aspirational layer of the portfolio, and the one that drives Dynery Away adoption most powerfully.
The people who appear most frequently in the guest's dining life. Not a social graph with follower counts — a relational dining archive. "Carter — 41 meals together. 12 restaurants. Most recent: Anchovies & Salt, April 2026." The companion record is the most emotionally resonant part of the portfolio because it makes the social dimension of dining visible — dining is not just about food, it is about who was at the table.
The restaurants where milestones were celebrated. "Mother's Day — Canlis, 4 years running." "Birthday — El Gaucho, the dry-aged ribeye, always." The occasions layer of the portfolio reveals the dining rituals that structure a year — and makes those rituals visible to the restaurant partners who have been part of them, deepening the loyalty relationship with each acknowledgment.
Every section of the portfolio has granular privacy controls: Public (visible to anyone with the URL), Members Only (visible to Dynery members who follow you), or Private (only you). By default, the portfolio is Members Only — the guest opts into public visibility. Companion records default to Private and require companion consent before they are shared publicly. The Annual Vintage is Public by default at The Tasting Menu tier and above — it is designed to be shared.
Available at The Tasting Menu tier ($29/mo) and above: Connect a custom domain to your Dynery portfolio. A CNAME record pointing dining.yourdomain.com or food.yourname.com to Dynery's portfolio infrastructure renders the full portfolio under the guest's own domain. Dynery provides DNS instructions; the guest makes a single DNS change; the portfolio lives at their custom URL. This is the option for the Mark Hadlands of the world who currently maintain their own site manually — Dynery gives them the same address, with automatically updated content.
For the first cohort of Dynery Certified operators who are also passionate home cooks: the custom domain portfolio is a credential. A chef who has the Dynery Certified designation on their restaurant and a personal portfolio at chef.theirname.com has something no competitor platform offers.
A basic portfolio page at dynery.com/@username with the Annual Vintage, restaurant list, and dish collection — all rendered from existing Dining Passport data — is a standard Next.js server-side rendered (SSR) site generated from structured data. The data already exists; the page is a display layer. The design investment is the primary timeline constraint. Infrastructure cost is minimal: static site generation from the dining data API, hosted on Vercel or similar. This is not hard. It is a design and prioritization decision.
The full portfolio vision — Travel Dining Map with interactive geography, Companion Record with consent architecture, custom domain routing, privacy controls at the section level, TikTok video integration, the dining newsletter with subscriber management, and the export/portability feature — is a 12–18 month roadmap item. But the MVP (the Annual Vintage + restaurant list + dish collection) delivers 80% of the consumer value in 3–4 months and creates the foundation everything else builds on. Ship the MVP, iterate toward the full vision.
cookcookeateat.com is an extraordinary personal dining archive: 58 documented recipes, 21 dining experiences at restaurants from Noma to Sushi Kashiba, 12 HadBurger iterations, 13 travel posts, thousands of photographs, and years of hand-written vignettes. The most frequent tag on the site appears 41 times — a single dining companion who has been part of the most meaningful meals in the archive. The goal of the site, stated directly on the homepage, is to leave a lasting record for his sons: their life together through food, friends, and family.
This is exactly what Dynery's Personal Portfolio builds automatically. Every post on cookcookeateat.com took real time: writing, photography, uploading, categorizing, maintaining. The Dynery portfolio equivalent generates the vignette at checkout, attaches the restaurant's photography assets, categorizes by cuisine and occasion automatically, and publishes to the guest's portfolio without the guest writing a word.
The consumer pitch for the Personal Portfolio is this: most people who live to eat wish they had what cookcookeateat.com represents. They lack the discipline, the time, or the writing habit to build it manually. Dynery builds it for them — automatically, from every meal, at every restaurant in the network. The only thing the guest has to do is eat.
| Feature | cookcookeateat.com (manual) | Dynery Portfolio (automatic) |
|---|---|---|
| Post creation | Manual — hours per entry including writing, photography upload, categorization | Automatic — generated at checkout from POS data + Heritage Layer + Dish Archive |
| Photography | Personal photos + curation effort | Restaurant-provided assets + optional guest uploads via app |
| Narrative writing | Mark writes every vignette by hand | AI-authored from the restaurant's own Heritage Layer and Dish Story Archive in the guest's voice |
| Update frequency | When Mark has time — gaps of weeks or months between entries | After every meal — the archive is always current |
| Social sharing | Manual — copy text, export image, open platform, paste caption | One tap — content bundle pre-built for every platform, native share sheet opens pre-populated |
| Companion record | "Carter (41)" — tracked manually through tagging every post | Automatic — companion graph built from dining data, surfaces milestones and history |
| Annual memoir | Would require manually curating and writing a year-in-review | The Annual Vintage — delivered automatically every January, shareable in one click |
| Version history (HadBurger) | Twelve manual posts across four years | Dish repeat detection automatically tracks iterations; version notation in the Dish Archive |
| Custom domain | cookcookeateat.com — maintained manually on WordPress | Available at Tasting Menu tier — CNAME to any domain, Dynery-generated content |
| Effort required from guest | Significant — hours per week to maintain at Mark's quality level | Zero — the portfolio builds itself from every meal |
| The bottom line | Beautiful, authentic, personal — and only possible for people with exceptional discipline and time | The same outcome, for everyone who eats through Dynery — zero extra effort required |
The full distribution architecture is a multi-phase build. The priority is clear: ship the highest-value, lowest-complexity channels immediately; build toward the portfolio and social content generation over time. Every phase delivers genuine consumer value independently — nothing has to wait for the full vision to land.
| Feature | Phase | Complexity | Timeline | Key Dependency | Consumer Value |
|---|---|---|---|---|---|
| In-app push notifications + Memory Card view | Launch | Already Built | Available now | Dynery app (exists) | Core experience for app users |
| SMS delivery (Twilio) — Memory Card link at checkout | Phase 1 | Very Easy | 1–2 weeks | TCPA consent at onboarding | Reaches guests regardless of app install status |
| Email delivery — Memory Card + Tastings™ cadences | Phase 1 | Very Easy | 2–3 weeks | HTML email design investment | Richest format; home for monthly/annual Tastings™ |
| Open Graph / link previews on all Dynery URLs | Phase 1 | Very Easy | 1 week | None — just meta tag implementation | Every shared link becomes a marketing asset |
| Social share bundles (Instagram, X) — one-tap content | Phase 2 | Easy | 3–4 weeks | Platform-perfect image generation pipeline | Turns every Memory Card into shareable social content |
| Pinterest Rich Pins for restaurant/dish discovery | Phase 2 | Easy | 2–3 weeks | Schema markup + Pinterest API approval | Evergreen food discovery SEO traffic for partner restaurants |
| WhatsApp Business API integration | Phase 2 | Moderate | 4–6 weeks | Meta Business verification + template approval | Critical for international expansion and younger users |
| Personal Dynery Portfolio (MVP) — @username page | Phase 3 | Moderate | 3–4 months | SSR site generation from Dining Passport data | The most powerful consumer retention and acquisition feature |
| Custom domain support for Portfolio pages | Phase 3 | Easy (post-MVP) | 2 weeks after MVP | DNS management + CNAME routing | High value for Tasting Menu+ tier members |
| Personal dining newsletter (Substack-for-dining) | Phase 3 | Moderate | 8–12 weeks | Subscriber list management UI + email infra | Turns members into distribution channels for Dynery |
| TikTok dining reel generation (15-second video format) | Phase 4 | Complex | 6+ months | Video generation pipeline + TikTok Content API | Gen Z dining discovery — highest reach potential |
| Full Portfolio (travel map, companion record, dish iterations) | Phase 4 | Moderate (iterative) | 12–18 months | MVP portfolio as foundation | The complete personal dining memoir — cookcookeateat.com built automatically |
| Auto-posting to social media on behalf of users | Never | Do Not Build | — | Violates platform ToS; destroys authenticity signal | Negative — removes the guest agency that makes sharing valuable |
The most common mistake platforms make when building social distribution is treating it as an automation problem: how do we get content to appear on social media automatically? Dynery's architecture takes the opposite approach. Dynery's job is to generate content so beautiful, so accurately reflective of the meal's emotional truth, and so easy to share that the guest chooses to share it themselves. The guest's tap is the distribution mechanism. Dynery's craft is the content that earns the tap.
This approach is not a constraint — it is a competitive advantage. An auto-posted Memory Card has zero trust signal; it is obviously a bot post. A Memory Card shared by the actual guest who experienced the meal, who chose to share it because it captured something true, carries the full trust value of a genuine peer recommendation. Dynery's content engine is not an automation tool. It is a story-making machine that earns the right to be shared.
The personal portfolio takes this further. A guest's dynery.com/@username page is not a Dynery marketing channel. It is the guest's own dining archive, powered by Dynery. When the guest shares it with a friend who says "I want that" — that friend is not responding to a Dynery ad. They are responding to a life lived at the table, documented beautifully. And Dynery is how they get it.
The Academy-in-the-3% / Distribution flywheel: The Heritage Layer and Dish Story Archive created through the Academy are the raw material for every vignette. Better stories from better Academy completion → better Memory Cards → more sharing → more consumer acquisition → more transaction volume → more fee revenue → more City Editor capacity → better Academy delivery → richer Heritage Layers. The flywheel only works if the Academy is completed. This is why Academy completion is a gate for Dynery Certified status, and why the Academy is included in the 3% rather than priced separately. The platform's commercial success depends on operators doing the story work. Making it free to complete removes every barrier to that outcome.
Social Sharing — The Right Way, Not the Risky Way
Auto-posting to social media on behalf of users is the wrong approach — and not just for legal reasons. The power of Dynery's social content is precisely that it is authentic: a real guest, sharing a real experience, in their own voice, amplified by Dynery's narrative intelligence. Auto-posting removes the guest's agency and turns the story into a bot post. The right architecture is different.
The Rule Is Simple: Generate Beautiful Content. The Guest Does the Sharing.
Meta deprecated personal Instagram API access in December 2024. Third-party auto-posting to personal Instagram accounts violates Terms of Service and results in account suspension. The same principle applies across platforms: authentic social sharing requires user action, not automated posting. This is not a technical limitation to be worked around — it is the right design choice for a platform built on the premise that dining stories are authentic.
What Dynery does instead: Generate platform-perfect content bundles — the right image dimensions, the pre-written caption, the suggested hashtags, the restaurant tag — and present them to the guest with a single tap to open their platform's native share interface. The guest's tap is the authentication. The content is irresistibly ready. The share is theirs.
This approach is more powerful than auto-posting because: (1) it complies with every platform's terms; (2) it preserves the authenticity signal that makes the recommendation valuable; (3) it requires the guest to consciously choose to share, which means the people who do share are genuine advocates, not passive participants in an automated system.
The Content Bundle Architecture — Platform-Perfect by Design
Feed: 1080×1080px (square) or 1080×1350px (portrait 4:5). The Memory Card design: restaurant photography as hero, the vignette's defining sentence as overlay text in Playfair Display, restaurant name, Dynery Constellation tier mark, occasion tag. Stories: 1080×1920px full-screen with the Heritage Card narrative and a "swipe up" story arc. Pre-written caption with restaurant tag and Dynery hashtag. One tap opens Instagram native share sheet with all content pre-loaded.
TikTok's Content Posting API allows approved developers to post videos to Creator accounts programmatically. For Dynery, this opens a 15-second dining reel format: restaurant ambiance footage (operator-provided), the dish in motion, the Heritage narrative as text-over-video, and the guest's Memory Card as the ending card. This is the most technically ambitious format — requires a video generation pipeline — but for Gen Z dining discovery, it is potentially the most powerful distribution channel on the platform.
X: Pre-formatted tweet card with the Memory Card image (1200×675px), the vignette's opening line as tweet text, restaurant tag and location. One-tap native share. Pinterest: 2:3 vertical Rich Pin with recipe/restaurant schema markup — highly optimized for food discovery SEO on Pinterest's search algorithm. Both are technically straightforward via native share API. Pinterest is underutilized in dining discovery and represents a meaningful opportunity for Dynery Away city guide content.
Graph
Every Dynery vignette lives at a URL. That URL is engineered with full Open Graph and Twitter Card meta tags — meaning when the guest texts it, emails it, or shares it anywhere that renders link previews (iMessage, WhatsApp, Slack, Discord, Facebook, LinkedIn), the preview shows the restaurant photography, the vignette headline, and the Memory Card design. The link preview is itself a marketing asset. A beautiful preview gets opened; a plain URL gets ignored. This is the most technically trivial feature in the entire content distribution stack and possibly the highest-ROI.
At the table, at checkout, on the receipt: a QR code that opens the guest's Memory Card directly. For guests who prefer not to share digitally, the QR code on a beautifully printed receipt provides a physical share moment — a conversation-starter when the printed receipt is left on the table for the next party to see. For restaurants that want to display Dynery Certified credentials physically, a small tabletop card with QR code links to the restaurant's Dynery profile and origin story. Physical and digital sharing architecture integrated.