← All Builds DAY 28 OF 30

ConnoisseurPlatform / Unshucked

Social discovery for the oyster category — and the connoisseur platform built to scale to every food-and-beverage enthusiast vertical that doesn't have one yet. Drop into a raw bar, pull up the Almanac to check what's on the chalk menu, log a check-in on a Wellfleet or a Kumamoto with a photo and a flavor note, build a tasting history that's actually yours. Discovery layer + social log + raw-bar map + expert-curated pairings, scoped to oysters first because the oyster audience is the most concentrated, most expert, most underserved enthusiast group in food and beverage. · React 18 + TypeScript PWA via Vite, Tailwind, Workbox — mobile-first, installable, offline-capable Almanac so the variety vocabulary travels with the user into rooms with no signal; the full set of pages (Home, Almanac, OysterDetail, Discover, RestaurantDetail, CheckIn, Profile, Login, Register) lives in apps/web/src/pages/ · AWS Lambda + API Gateway, Node 20.x — five public + authenticated handler groups (oysters, restaurants, users, checkins, photos) running the canonical Untappd-shape workflow: browse → check in → photo upload via S3 presigned URL → tasting history · DynamoDB single-table design with GSIs for region (oysters), location (restaurants), and flavor (cross-cutting browse) — single-table-by-construction, scoped to the access patterns enumerated in CLAUDE.md, ready for category expansion without a re-platform · AWS Cognito user pool for auth (us-east-1_B3Bjnci9t / client 3nn4c2l7veunmd38q9fdmsc0i2), Cognito-protected check-in / profile / photo-upload endpoints, public Almanac and raw-bar discovery surfaces — same Untappd shape (public reading, authenticated logging) translated to the oyster context · AWS CDK (TypeScript) — five-stack architecture (Database, Auth, Storage, Api, Frontend) — separate Vite-built React PWA deploy target on the Frontend stack with an ACM certificate via DNS validation on the launch domain (unshucked.co) · Marketing surface on GoHighLevel at unshucked.us — lead-capture / waitlist / cohort-application funnel that pre-dates the Day 28 launch and runs the partner-side intake for raw bars and oyster farms
LIVE https://unshucked.co

Day 28 of 30 — the IRL Premium arc closes with the most concentrated audience in food and beverage

Unshucked is live today at unshucked.co, built with Kirby Winters as GTM Lead & Strategic Partner — the operator-validated co-founder pattern the run has carried since Day 3 PartFoundry, applied to a category where the operator’s domain expertise is the unfair advantage. The product: a social-discovery platform scoped to oysters first — an Almanac of fourteen varieties (Beausoleil, Wellfleet, Pemaquid, Kumamoto, Apalachicola, Murder Point, and eight more), a check-in flow with photo and tasting note, a raw-bar discovery map keyed to coastal cities, and a partnership surface for raw bars and oyster farms. The parent brand, ConnoisseurPlatform, is the expansion architecture that takes the same model to other enthusiast verticals once the oyster wedge has earned the right.

Day 28 morning closes the IRL Premium arc. The thesis the arc carries — the future of premium experience is real, in person, and with people; software’s job is to trigger it, not replace it Each launch pulled AI deeper into a real in-person moment. Unshucked carries the arc to its concrete consumer end: standing at a raw bar in Portland or Charleston, looking at a chalk menu of varieties you’ve never heard of, with the Almanac on your phone telling you the Murder Point you’re about to order is off-bottom-farmed in Mobile Bay and runs clean buttery with a sweet finish.

The problem

There are roughly 500,000 active oyster consumers in the US. The category has a strong regional identity, a real flavor-profile vocabulary, a passionate enthusiast base, and zero social-discovery platforms built for them.

Beer drinkers have Untappd. Wine has Vivino. Spirits has Distiller. Coffee has Beanhunter. Whisky has dramming apps; cocktails have Difford’s; beer enthusiasts can tell you which IPA they had on a Tuesday night in 2022 and what the brewery did differently. Oysters — a category that rewards specific knowledge more than most — live on static guidebooks (Rowan Jacobsen’s A Geography of Oysters is the bible, and it is a book from 2007), the working memory of raw-bar staff, and word-of-mouth in tight coastal communities.

Ask any oyster eater past their first dozen to tell you which Beausoleil they had in Portland six months ago and which raw bar served the Pemaquid they actually liked, and the answer is the same: I don’t remember. The category is fragmented, the data is scattered, the audience is real, and the discovery layer is missing.

That is the gap Unshucked exists to close. Scoped to oysters first because oysters are the category where the gap is widest, the audience is the most concentrated, and the operator-domain expertise on the GTM side (Kirby’s industry network, his craft-vodka-brand audience, his decade-plus inside food and beverage) is the closest thing to an unfair advantage anywhere in food-and-beverage social.

What ships today — three things, all real

The Day 28 launch pulls Unshucked from a January-built MVP to a live launch surface. The three things that ship today are all real and verifiable.

An oyster Almanac of fourteen varieties. Beausoleil (Miramichi Bay, New Brunswick — briny, clean, crisp), Blue Point (Long Island — the classic East Coast oyster), Wellfleet (Cape Cod — briny, mineral, algae notes), Pemaquid (Damariscotta River, Maine — intense brine, mineral, seaweed), Malpeque (Prince Edward Island — classic Canadian brine), Kumamoto (Pacific Northwest, originally Japan — sweet, fruity, melon, the gateway oyster for newcomers), Kusshi (British Columbia — small, tumbled, smooth, sweet), Olympia (Puget Sound, Washington — the only oyster native to the West Coast, mineral and intense), Island Creek (Duxbury Bay, Massachusetts — award-winning, buttery), Apalachicola (Apalachicola Bay, Florida — large, fat, rich, plump, sweet), Gulf Coast Select (Gulf of Mexico — buttery, briny finish), Murder Point (Mobile Bay, Alabama — off-bottom farmed, clean, buttery, plump), Pensacola Bay (Pensacola Bay, Florida — sweet, buttery), and Point aux Pins (Bayou La Batre, Alabama — balanced briny with mineral notes). Each variety carries a region, a primary flavor descriptor, a brininess level (1–10), a creaminess level (1–10), a sweetness level (1–10), a mineral level (1–10), seasonality with peak window and a sustainability rating, a description, and a list of secondary flavor notes. The full Almanac is served live from the production API; the four featured oysters on the homepage are pulled live from the API on every page load. No fabricated content, no AI hallucinated descriptions — Kirby-curated reference data, with the option to expand to two hundred varieties as the platform earns the right.

A check-in flow with photo and tasting note. Log what you ate, where, with whom, with a photo, and build a tasting history that’s actually yours. Same shape as Untappd’s check-in, scoped to the oyster context: variety from the Almanac, raw bar from the Discover map, brininess perception (does this Wellfleet taste briner tonight than the one you had last month?), pairing notes (mignonette, lemon, horseradish, Kirby’s vodka, a Muscadet, a Sancerre — record what you actually paired with the oyster). The check-in is authenticated via Cognito, the photo is uploaded via an S3 presigned URL, and the resulting record is available through the protected GET /users/me/checkins endpoint.

A raw-bar discovery layer. Geolocation-aware search for raw bars near you, restaurant detail pages that show the current oyster list for partner raw bars, and a partner application surface for raw bars and oyster farms that want to sign up. The partner side runs through Kirby’s network — every raw-bar conversation in the first cohort is a Kirby call.

What it is not, today

Unshucked at 9 AM ET on May 28 is not 25,000 users. It is not 500 restaurant partners. It is not a $485K-revenue business. Those are 2026 targets in the business case, not traction claims at launch.

The honest framing: Unshucked was built as a focused MVP, sat dormant through May while the rest of the run played out, and is being lit up for Day 28 because the IRL Premium arc needed the right closer. The product is real, the API is live (and has been since January), the Almanac data is real, Kirby’s network is real. The traction is what the next 90 days are for.

The discipline here is the same as Day 21 PatentFlow: ship what is true, name what is roadmap as roadmap, let the operator-domain credibility and the live-product reality carry the rest.

Kirby Winters is the GTM lead — yes, the same Kirby

The cross-domain founder reveal is the surprise hook of the Day 28 morning launch. Kirby Winters is the operator named publicly across this run in his CyberSavi-founder role (Day 4 CompliancePulse, Day 5 CyberSavi LMS, Day 6 CyberSavIQ, Day 8 GovernAI — four launches inside the Cyber MSP arc). The same Kirby Winters also owns a craft vodka brand and is the oyster-industry expert behind the Unshucked GTM motion. Cybersecurity MSP by day, food-and-beverage operator in his other life, and the Velocity Process portfolio thesis says that’s not a contradiction — it’s the thesis. When AI compresses build time enough, one experienced operator can co-found ventures across multiple verticals because the build-time bottleneck stops being the constraint and the operator’s domain expertise becomes the unlock.

Kirby’s role at Unshucked:

  • GTM lead — restaurant partnership development, raw-bar outreach, oyster-farm relationship development. The first 25 raw-bar conversations are Kirby’s calls.
  • Industry authority — expert content, oyster-and-pairing recipes, the editorial voice on the Almanac descriptors and the pairing layer.
  • Brand integration — the seed pairings in the Almanac feature his craft vodka because the category expert building the category platform of course features the spirit he knows best, on the surface where he can demonstrate the pairing knowledge.
  • Network access — established relationships with raw bars, oyster farms, distributors, food-and-beverage media. The zero-CAC distribution play, sibling to the Day 27 PIM Karen-Rands-network play and the Day 21 PatentFlow IP-bar play.

The architecture — small enough to be obvious

React 18 + TypeScript PWA. Vite-built, Tailwind-styled, Workbox-instrumented for offline. Mobile-first, PWA-installable (tap the share button in mobile Safari → Add to Home Screen → no app-store gatekeeping). The Almanac is offline-capable; the check-in flow needs network to write but caches reads. The full set of pages — Home, Almanac, OysterDetail, Discover, RestaurantDetail, CheckIn, Profile, Login, Register — is in apps/web/src/pages/ and is the canonical user-facing surface.

AWS Lambda + API Gateway + DynamoDB single-table. Five handler groups (oysters, restaurants, users, checkins, photos) covering the public + authenticated endpoints. The DynamoDB single-table design uses three GSIs (region for oysters, location for restaurants, flavor for cross-cutting browse). Access patterns are enumerated in CLAUDE.md and the schema is the by-construction kind of thing that scales to category expansion without a re-platform.

AWS Cognito for user pool + client; protected endpoints gate check-ins, profile updates, and photo uploads. The public Almanac and raw-bar discovery surfaces are open for the audience that wants to browse before committing to an account.

S3 presigned URLs for photo uploads. No multipart through Lambda, no images in DynamoDB, no costly hot paths. The presigned-URL pattern is the cheap, scalable, durable photo-storage shape.

Five-stack CDK (Database / Auth / Storage / Api / Frontend) — separate Vite-built React PWA deploy target on the Frontend stack with an ACM certificate via DNS validation on the launch domain. The frontend-stack adds the custom-domain config for unshucked.co at launch; the CloudFront distribution serves the static PWA build behind it.

Two domains. unshucked.us is the marketing / lead-capture surface (GoHighLevel-hosted, partner intake) and was live before the Day 28 launch. unshucked.co is the new apex for the React PWA — the surface the Day 28 LinkedIn post points to. The two-domain shape is intentional: the marketing motion has its own surface, the product has its own.

The ConnoisseurPlatform expansion architecture (the long bet)

ConnoisseurPlatform is the company name; Unshucked is the consumer brand for the oyster category. The naming choice reflects the long bet: oysters are the wedge because oysters are the category where the discovery-layer gap is widest, but the underlying architecture is generic.

The DynamoDB single-table design takes a category (currently OYSTER#{id}) as a key prefix that generalizes to WHISKY#{id}, STEAK#{id}, CIGAR#{id}. The check-in schema generalizes — primary tasting object, region, flavor profile, secondary notes. The discovery layer (geolocation + partner business surface) generalizes to any consumption-context category (raw bars become steakhouses become cigar lounges become craft-cocktail bars).

The roadmap, named honestly as roadmap: steaks and BBQ (Kirby’s adjacent expertise area), craft spirits (Kirby’s primary domain), cigars and cheese as the further-out categories that need their own operator-domain co-founders before they ship. None of those are claimed as live today. The Day 28 launch is scoped to oysters, the parent brand is named for the architecture, and the expansion path is the investor pitch, not the day-one feature.

Pricing & business model

  • Almanac is free, social layer is free, OysterPlus is the premium tier. The Almanac and the check-in flow are free forever — the network-effects logic depends on the audience showing up to log their tasting history without a paywall in the way. OysterPlus is the premium tier that adds advanced features (pairing recommendations across all spirits + wines + beers, full check-in export, advanced filtering, partner-exclusive content). Pricing target per the business case is $69/year; published pricing settles after the design-partner cohort feedback.
  • Restaurant-partner revenue is the primary model. Partner raw bars pay for featured placement, current-oyster-list publishing, customer-engagement insights, and (where appropriate) reservation integration. The first 25 partners get the founder-cohort treatment — featured placement, custom variety lists, no platform fee for year one, with Kirby personally calling each one.
  • Brand-partnership revenue, secondary. Kirby’s vodka is the seed-data pairing partner; the same surface scales to complementary brands (mignonette purveyors, oyster knives, half-shell servingware, sustainability certifiers). Brand partnerships sit alongside the restaurant revenue, not in the consumer surface.
  • Honest launch state. Unshucked has no paying restaurant partners at launch and no paying users at launch. The founder cohort opens today; published pricing settles after the first wave of partner conversations. The post and this build page name that explicitly.

The Velocity Process notes

What Claude Code handled. The React 18 PWA scaffold with Vite + Tailwind + Workbox + react-router-dom; the nine pages (Home, Almanac, OysterDetail, Discover, RestaurantDetail, CheckIn, Profile, Login, Register); the auth-gated route layer via ProtectedRoute and useAuth hooks; the API client with typed responses for OysterVariety, Restaurant, OysterCheckIn, UserProfile; the five Lambda handler groups (oysters, restaurants, users, checkins, photos) with TypeScript types in @unshucked/shared; the DynamoDB access layer in @unshucked/dynamodb-utils with PK/SK generation, oyster / restaurant / user / checkin queries, and GSI key calculations; the seed-data set of fourteen oyster varieties with the full flavor-profile schema (primary, secondary, brininess level, creaminess, sweetness, mineral, consistency, seasonality, sustainability); the five-stack CDK (Database, Auth, Storage, Api, Frontend) with the photo-bucket integration, the Cognito user pool + post-confirmation trigger, the CloudFront distribution; the seed script that populates the DynamoDB Almanac at deploy time.

What required human judgement. The decision to brand the consumer surface as Unshucked and the parent company as ConnoisseurPlatform — same operator-validated portfolio pattern, with the brand split reflecting the category-expansion roadmap; the call to scope launch to oysters and name the expansion path as roadmap rather than shipping a multi-category surface that nobody asks for; the discipline on the homepage stats bar (verified “10+ varieties / 5 flavor profiles / 3 coastal regions” rather than the README’s projected “25,000 users / 500 restaurant partners”); the operator-side framing (Kirby as GTM Lead, not figurehead — every raw-bar conversation in the first cohort is his call); the cross-domain reveal architecture for the Day 28 morning post (the surprise is Kirby’s cross-domain expertise, which lands harder than a “new oyster app” lede); the two-domain shape (marketing on unshucked.us / product on unshucked.co) so the GHL lead-capture motion can keep running on its own surface while the PWA gets its own apex.

What the readiness pass caught. Three items the Day 28 readiness audit (gtm/DAY-28-READINESS-AUDIT.md) surfaced and the launch pulled back on. (1) The README’s traction projections (25K users / 500 partners / $485K revenue / $8.2B market) were forward-looking targets, not current-state claims; the launch post explicitly distinguishes the projections from the day-one reality (14 oyster varieties, real API, working PWA, Kirby on the GTM) so the audience does not read the projections as traction. Same-class catch as the Day 14 GEOPress and Day 21 PatentFlow fabricated-traction precedents. (2) The CDK does not yet apply the Silverback VelocityStack tagging convention (Project / Client / Environment / BillingCode / ManagedBy / DeployedBy / CostCenter) that SapphireInvestments and other later-run builds use as their compliance baseline; the launch post does not claim VelocityStack compliance, and the Day 29 punch-list item is to add the tags before any repo-public move. (3) Kirby Winters is already publicly named in the run as the CyberSavi founder; the Day 28 framing repositions him in the oyster-industry / vodka-brand-owner role, which is a different audience-facing role than the prior posts established. The pre-flight gate is explicit Kirby sign-off on the cross-domain framing landing in front of an audience that knows him as the Cyber MSP operator — the cross-domain reveal IS the hook, so the framing call is the operator’s, not the drafter’s.

What I’d do differently. Apply the VelocityStack tagging convention from day one rather than retrofitting it. The Day 28 launch can ship without it (the product is real, the API is live, the PWA serves), but the in-house portfolio hygiene gap is a Day 29 punch-list item that pulls the cleanup work into the same week as the retrospective. Day 0 of the next consumer launch in the portfolio gets the tagging convention baked into the CDK scaffold so the operator never has to backfill it.

What’s next this week

  • Day 28 morning (today): ConnoisseurPlatform / Unshucked is live at unshucked.co; the Almanac of fourteen oyster varieties, the check-in flow, the raw-bar discovery layer, and the partner-cohort intake are all working; Kirby Winters is the GTM Lead.
  • Day 28 afternoon (today, 1:00 PM ET): SapphireInvestments closes the Investing arc Karen Rands (Day 27 PIM) opened. Three-tier signal engine, Phase 0 paper-trading validated, $99 Standard / $299 Premium / accredited-only autonomous Q3 2026, Jim Rozich on the cap table. Same operator-validated pattern, regulated vertical. The double-launch architecture is the demonstration: when build time is no longer the bottleneck, one launch day can carry two ventures in two arcs.
  • Day 29 (Fri May 29): the 30-day retrospective. TFTSL Week 4 wrap drops.
  • Day 30 (Sat May 30): Silverback Ventures public launch.
  • This quarter — design-partner punch list: the first 25 raw-bar partner sign-ups close into Kirby-led calls; the OysterPlus premium tier ships once the design-partner feedback names the right premium-features set; the AI-pairing recommendation engine (Bedrock-routed Claude, same regulated-vertical AI-architecture pattern as Day 10 / Day 21) ships in the Phase 2 roadmap when the partner-side data volume justifies the inference spend.
  • Roadmap, named honestly as roadmap: the VelocityStack tagging convention applied to the CDK; the multi-category expansion (steaks, BBQ, craft spirits) when an operator-domain co-founder is identified for each new category; the partner-side reservation integration when the first cohort needs it; the brand-partnership surface beyond Kirby’s vodka.

Want to talk

If you eat oysters — open Unshucked at unshucked.co, create an account, log your next dozen. The Almanac is free; the social layer gets better the more people are on it.

If you run a raw bar — the first 25 partners get founder-cohort treatment. Featured placement, custom variety lists, no platform fee for year one. Kirby Winters will personally call you. Reach out via unshucked.co or DM Todd on LinkedIn.

If you’re an oyster farm or distributor — partnership conversations open this quarter. The Almanac is built to credit the farms; the check-in data is the demand signal nobody currently has.

If you’re an investor watching the IRL Premium thesis — Unshucked is the sixth proof point this week of the same thesis. The Day 29 retrospective pulls the six together; the Silverback Ventures studio reveal lands Saturday.

silverbackcto.com/builds for the daily.

Live Product →