Mad Hudson Watches
Sprint 0 in numbers.
Facilitation page for May 26, 2026
Data sources: fresh local Shopify and Google Search Console pulls, local Mad Hudson strategy docs, and the retreat research packet. Whatnot exports are not yet present.
The work is not one problem called social.
Connor is paying reload cost across Instagram, TikTok / WatchTok, Whatnot, events, Shopify/site, DMs, holiday sales, shipping, product releases, and internal ops. Today should separate those worlds and choose the first operating pattern to build.
Events need support branches, not one page assumption.
POS appears in 48 of 137 recent orders. LA is close, Philadelphia follows, and a monthly Pour Souls Chicago lane is emerging. Some event pages will be organizer-owned. Mad Hudson still needs a repeatable support packet for SEO, proof, opt-in, product links, and follow-up.
The product system can become the memory.
Broken Time, CD Watch, Eddie, Marshall, Miami, and Dogma each tell a different story about inventory, demand, search, and promise-keeping. The release system should turn that learning into a reusable gate for new watches.
Shipping is the major decision gate.
They are running fulfillment from the apartment and still like keeping it close. The question is not "outsource or do not outsource." It is what capacity, rules, tooling, and trusted help let them retain the right work until offloading becomes strategically high leverage.
Retention should feel like relationship memory, not extraction.
Mad Hudson's best customers are likely people who want to be remembered: collectors, collaborators, event contacts, repeat buyers, Whatnot regulars, and people waiting for the next strange watch. Email, SMS, and CRM work should preserve consent, context, and timing.
The highest-leverage move today is to make the next few weeks operable without Connor being the only bridge.
Do not run a brand brainstorm. Use the session to create a small operating rhythm around LA, Philadelphia, the recurring Pour Souls lane, Whatnot, apartment fulfillment, relationship capture, and new-watch releases.
Good numbers here do what the OEFF numbers page does: they become observations, recommendations, capacity asks, and source notes. The raw rows stay underneath. The top layer helps people decide.
The practical aim: leave with one Sprint 0, an event-support branch map, a shipping/fulfillment decision gate, a relationship capture block, and a release gate that future watches can pass through without chaos.
Tier 1: Discovery Script
Use this as the live-room layer. The move is Matt Abrahams-style structure: pause, paraphrase, ask one useful question, then turn the answer into what / so what / now what. Keep Connor and Mad in discovery until a repeatable object is obvious.
Opening script
- "I want to understand the work before we solve it."I will probably pause us to separate events, Whatnot, shipping, releases, site, DMs, and relationship capture so none of it collapses into one giant pile.
- "Today does not need a full operating system."It needs one Sprint 0: a concrete pattern we can try around LA, Philadelphia, Pour Souls, shipping, and the next release.
- "Let me reflect back the tension."You want to retain the parts of the work that carry taste, trust, and learning, while building support around the parts that are becoming repetitive or travel-sensitive.
Matt Abrahams-style cues
- Paraphrase before advice."What I hear is that the risk is not volume alone; it is letting the wrong person touch a high-trust part of the operation."
- Name the emotion without dramatizing it."It sounds like this still feels too intimate or brand-sensitive to hand off blindly."
- Ask one question at a time."What part of this would be easy to delegate if the checklist were perfect?"
- Move from abstract to object."Would this become a checklist, a calendar, a Shopify pull, a support packet, or a role card?"
| Area | Discovery question | Write down in the room |
|---|---|---|
| Events | For LA, Philadelphia, and Pour Souls, who owns the public surface, and what support does the event actually need? | Page owner, event job, support packet, product roles, capture owner, proof owner, follow-up date. |
| Shipping | Walk me through the last shipping day that felt heavy. Where did the time, worry, or apartment friction show up? | Parcels/week, hours/week, backlog days, exceptions, supplies gaps, travel-week risk, safe-to-delegate tasks. |
| Whatnot | Before we talk about the right person, what jobs exist before, during, and after a stream? | Prep tasks, live roles, post-stream labels/packing, exceptions, payout/export needs, trust boundary. |
| New watches | Pick one upcoming design. What has to be true before it can move quickly without creating chaos? | Product truth, story truth, page truth, channel truth, ops truth, shipping promise. |
| Relationships | Who should feel remembered after an event, Whatnot stream, DM, or purchase, and what consent do we actually have? | Customer type, contact method, product interest, consent note, promised follow-up, owner, timing. |
| Sprint 0 | If we could only make one thing easier by the next event, what would make the most visible difference? | One artifact, one owner, one deadline, one measure, one review time. |
Tier 2: Numbers That Matter And Resources
Use numbers as decision aids, not as a courtroom. The current pulls are enough to orient the room; the next pulls should answer capacity, retention, event support, and shipping questions without exposing private customer rows on this public page.
| Dimension | Known now | Need next | Use it for |
|---|---|---|---|
| Sales workload | 137 recent orders, $24.3K order value, 155 units, $177 AOV. | Weekly order trend, parcels/week, shipping hours/week, fulfillment backlog. | Capacity planning for shipping, helper timing, and travel-week buffers. |
| Event channel | 48 POS orders. Public events page shows 1 click on 1,160 impressions. | LA, Philadelphia, and Pour Souls page owners; event capture counts; post-event follow-up outcomes. | Choosing the right support branch for each event instead of assuming Mad Hudson owns the page. |
| Product promise | Broken Time moved 53 units and has 31 stock; CD Watch has 149 stock; Eddie moved 38 units and has 0 stock. | Restock/waitlist decision, event product focus, Whatnot product focus, launch inventory gates. | Avoiding dead promises while using real product demand to guide events and releases. |
| Search signal | 2,364 GSC clicks, 32,762 impressions; "cd watch" has 20,521 impressions and 423 clicks. | Top product pages by click/impression gap, branded vs. non-branded split, event/local query movement. | Prioritizing SEO work that supports actual products, event proof, and new-watch intake. |
| Abandoned pressure | 43 abandoned checkout rows and about $8.7K abandoned value. | Product-level abandonment by stock state, recovery flow status, high-intent return path. | Deciding where follow-up, waitlist, restock, or page clarity would matter. |
| Whatnot capacity | 0 raw Whatnot exports in the current local view. | Last 3-5 stream readbacks: hours, lots, orders, gross, payout, prep time, post-stream shipping, exceptions. | Separating stream growth from the hidden shipping and support load it creates. |
| Retention quality | Email/customer quality data is not yet pulled into this view. | Aggregate new vs. returning, repeat purchase, cohort/RFM, email list growth, flow performance, consent health. | Building ethical CRM and customer memory without publishing raw PII. |
| Fulfillment strain | Not yet measured directly; user context says fulfillment is apartment-run and still valued. | Shipping station map, supplies failures, package presets, carrier/dropoff rhythm, exception count, travel strain. | Choosing upgraded in-house, helper, hybrid, or 3PL from evidence instead of anxiety. |
| Resource | Look to it for | Next pull or action |
|---|---|---|
| Shopify orders / line items | Recent demand, products sold, POS vs. web contour, shipping methods, inventory promise risk. | Refresh aggregate orders and line items before the next review; keep customer-identifying rows out of the public page. |
| Shopify fulfillment / shipping records | Fulfilled vs. unfulfilled, shipping methods, label workflow, backlog, exception patterns. | Pull a fulfillment-focused aggregate if available; pair it with Connor's lived shipping-time estimate. |
| Google Search Console | Product/search demand, page gaps, event/local visibility, query language people already use. | Compare product pages, event pages, and queries before choosing SEO tasks for Sprint 0. |
| Whatnot exports | Stream performance, hidden prep/load, post-stream shipping spikes, payout/friction. | Ask Connor for the last 3-5 stream reports or readbacks; turn them into a capacity worksheet. |
| Event organizer materials | Page owner, allowed copy fields, image requirements, backlink options, CTA constraints. | Create one support packet that works for Mad Hudson-owned and organizer-owned surfaces. |
| Email / SMS platform | List growth, welcome/post-purchase/review/restock flows, opt-in source, opt-out status. | Pull aggregate flow and consent health before designing retention or SMS pushes. |
| Shipping tool docs | Batch labels, presets, tracking sync, manifests, pickup/dropoff workflow. | Compare Shopify Shipping, Pirate Ship, Shippo, and ShipStation only against the real apartment workflow. |
| Fulfillment partner docs | Receiving, storage, pick/pack, custom packaging, returns, insurance, SLA, escalation. | Use 3PL research as a decision matrix, not a default recommendation. |
| Facilitation cues | Keeping the room structured when the conversation gets broad or emotional. | Use paraphrase, one question, and what / so what / now what to convert discovery into Sprint 0 objects. |
Product Signals
Use the products as operating evidence. Each product tells the room a different thing about inventory truth, search capture, channel fit, and customer promise.
| Product | Signal | Current stock | Use in the room |
|---|---|---|---|
| Broken Time | 53 units, $12.7K gross line value, 301 GSC page clicks. | 31 units. | Anchor product, but protect inventory truth before LA, Philadelphia, or Whatnot pushes. |
| CD Watch | 27 units, $5.8K gross line value. The query "cd watch" has 20,521 impressions and 423 clicks. | 149 units. | Best search-learning object. Use it to define product-page, SEO, support, and story standards for new watches. |
| Eddie Watch | 38 units, $7.4K gross line value, high abandoned-checkout pressure. | 0 units. | Needs a restock, waitlist, or quiet-state decision before any promo creates a dead promise. |
| Marshall / Miami | 24 combined units and about $4.8K gross line value; both show abandoned pressure. | 43 / 57 units. | Useful event or support-copy candidates if the team wants breadth without overcomplicating the story. |
| Dogma | Low current search/click movement relative to stock. | 263 units. | Needs a story, event test, or channel-specific plan before it becomes a major push. |
The product question is not just "what should we sell?" It is "what can we promise, where, with what follow-up, and with what operational support?"
Event Support Branches
Do not assume Mad Hudson creates every event page. The repeatable strategy is event infrastructure: a support packet, source-of-truth fields, product links, proof capture, opt-in language, and follow-up rules that work whether Mad Hudson, the organizer, a ticketing platform, or nobody controls the page.
Immediate need
Confirm LA and Philadelphia facts, then confirm who owns the public event surface. The first question is not "what page do we build?" It is "what support does this event need?"
Recurring lane
There is also a monthly Pour Souls Chicago lane forming. Treat it as a repeatable local relationship system: one support kit, one capture ritual, one recap rhythm, and a rolling proof ledger.
| Branch | Who controls the surface | Mad Hudson support | SEO / capture move |
|---|---|---|---|
| Mad Hudson-owned page | Mad Hudson can create or edit the page. | Full landing/recap page: event name, city/date, products, images, schema, proof, and follow-up. | Optimize title/meta, product links, alt text, Event schema, and opt-in form. |
| Organizer-owned page | Organizer, venue, partner, or event producer creates the page. | Send a copy/image/link packet: official name, product links, 2-4 sentence description, images, alt text, and agreed CTA. | Ask for a backlink, named product/artist language, correct brand spelling, and tracked links if possible. |
| Ticketing/platform page | Eventbrite, Partiful, venue calendar, marketplace, or other platform. | Work within fixed fields. Keep title, brand, city, product names, and CTA consistent. | Use UTM links or a simple event shortlink; capture opt-ins at booth/table if platform cannot. |
| No durable page | Social-only, flyer-only, DM-only, or casual meetup. | Create a lightweight internal event card and post-event proof note. | Use recap/proof, product tags, consent capture, and follow-up. Do not invent a public event page if nobody needs it. |
| Pour Souls monthly | Likely shared or organizer-led; details to confirm. | One reusable monthly kit: title convention, product focus, image set, opt-in copy, recap checklist, and relationship notes. | Build cumulative local proof: "Mad Hudson at Pour Souls Chicago" signals, prior recaps, customer questions, and next-date capture. |
- Confirm the facts and owner.Dates, venue, city, travel, table/booth needs, page owner, organizer contact, and what is confirmed versus assumed.
- Name the event job.Sales, collector contacts, product learning, creator/community proof, content capture, or partner relationship.
- Choose product roles.Broken Time as anchor, CD Watch as search/story object, Eddie as explicit no-promise decision.
- Send the support packet.Copy, images, product links, brand spelling, alt text, UTM/shortlink, opt-in language, and any organizer ask.
- Assign role cards.Lead operator, story/sales, POS, contact capture, proof capture, follow-up owner.
- Debrief while warm.Five minutes after the event: what sold, what people asked, what should be remembered before Philadelphia.
Whatnot Capacity
Connor has named Whatnot as a place where support is needed. The facilitation task is to split stream work before discussing people.
Judgment work
Product choice, pricing exceptions, brand voice, customer relationship risk, and what should not be delegated.
Trusted ops work
Stream prep, SKU checks, packing queue, labels, post-stream batching, and exception triage under clear rules.
Mechanical work
Box prep, materials, packing station reset, inventory counts, shipping supplies, and non-sensitive fulfillment steps.
Ask: what can someone else carry without deciding taste, voice, money, or relationship risk?
Shipping And Fulfillment Decision Gate
Shipping is the big operating decision gate. Mad Hudson currently runs fulfillment out of the apartment and still values keeping that work close. The Meadows move is not premature outsourcing; it is changing the information flows, rules, buffers, and support structure so they retain the right work until offloading is actually strategic.
Keep close
Keep high-judgment watches, event follow-up, exceptions, gift notes, and quality-control-sensitive orders near the founders while the process is still learning.
Professionalize first
Before outsourcing, build the shipping station, SKU/bin map, label workflow, batch days, promise calendar, and error log that make delegation safe.
Offload by rule
Delegate only the parts with clear rules: packing prep, label batching, standard SKUs, supplies, inventory counts, and recurring post-stream shipping work.
| Option | Use when | Build before deciding | Gate / watch-out |
|---|---|---|---|
| Apartment fulfillment, upgraded | Volume is still manageable and founders want quality control, branded packing, and fast learning. | Shipping software, scale, label printer, package presets, SKU bins, supplies map, pickup/dropoff rhythm. | If shipping consumes repeated founder blocks or creates travel-week backlog, move to helper or hybrid. |
| Trusted local helper | The work is mechanical enough to delegate but still too brand-sensitive for a warehouse. | Checklist, packing photos, exception rules, privacy boundary, workspace rules, order-access limits. | This is likely the first high-leverage offload if trust is the bottleneck. |
| Shipping software layer | They need less label/admin friction but do not want to move inventory out. | Compare Shopify Shipping, Pirate Ship, Shippo, and ShipStation against batch labels, tracking sync, rates, and custom fields. | Software does not solve packing labor. It only reduces decision and label friction. |
| Hybrid fulfillment | Some SKUs are stable and boring, while drops, events, Whatnot, or special watches still need founder touch. | Define which SKUs can leave the apartment, what stays close, and how inventory syncs back to Shopify. | Best strategic bridge if they want to retain magic while reducing steady load. |
| 3PL / fulfillment partner | Order volume is predictable, packaging rules are stable, and the cost of apartment fulfillment is higher than the loss of control. | Cost model, pick/pack/storage fees, receiving rules, custom packaging support, returns, insurance, SLA, error process. | Do not send fragile trust to a warehouse before the rules and escalation paths are written. |
Recommended decision posture: keep fulfillment close for now, but make it measurable. Track parcels/week, shipping hours, backlog days, exception count, supplies failures, Whatnot shipping spikes, and travel-week strain. Offload when the bottleneck is clearly mechanical, not when the system is still undefined.
Relationship And Retention System
This is an owned-relationship lane, not a growth-hack lane. The goal is to make Mad Hudson better at remembering people who already care: collectors, repeat buyers, event contacts, Whatnot regulars, collaborators, reviewers, and people waiting for a restock or new drop.
Organic CRM
Track the small human signals: product interest, event met, platform handle, repeat-buyer status, watch they asked about, promised follow-up, and who owns the next touch.
Email as the default
Use Shopify Email or the current email platform for welcome, event follow-up, review request, back-in-stock, and drop alerts. Keep cadence quiet and useful.
SMS only when earned
Use SMS for explicit opt-in moments only: event follow-up, restock alert, day-of event note, or high-intent drop alert. No casual business-card texting.
| Layer | What to capture | Ethical guardrail |
|---|---|---|
| Customer quality | Aggregate new/returning, repeat purchase, cohort, and product-affinity signals. | Owner-approved aggregates first. Do not export customer PII without a clear use case. |
| Event contact | Name or handle, contact method, product interest, consent note, follow-up owner/date. | A conversation is not consent. Record email and SMS permission separately. |
| SMS marketing | Program name, phone, opt-in source, disclosure, timestamp, message type, opt-out status. | Prior express written consent, clear opt-out, and no purchase required for consent. |
| Email marketing | Signup source, product interest, event tag, flow membership, unsubscribe status. | Clear sender, truthful subject, postal address, easy unsubscribe, prompt opt-out handling. |
| Community memory | Repeat questions, praise, objections, sizing/fit notes, artist comparisons, requested designs. | Use notes to serve people better, not to pressure them harder. |
Ask in the room: what would make a returning customer feel recognized without making the brand feel automated?
New Watch Release Gate
The point is not to slow down exciting new designs. The point is to keep each release from becoming a new context-switching explosion across Shopify, SEO, social, events, Whatnot, DMs, inventory, and shipping.
| Gate | Minimum before launch | Why it exists |
|---|---|---|
| Product truth | Name, artist/designer, specs, price, inventory, SKU/variant, availability promise. | Prevents Shopify, events, Whatnot, and shipping from telling different stories. |
| Story truth | One paragraph on the watch's relationship with time, plus three proof points. | Keeps Mad Hudson out of generic watch language. |
| Page truth | SEO title/meta, image alt, creator/entity fields, collection links, review/proof slot. | The CD Watch page proves product search can matter. |
| Channel truth | Website role, event role, Whatnot role, email role, DM/support answers. | Stops every channel from inventing its own launch logic. |
| Ops truth | Packaging, handling time, shipping constraints, exception owner, support boundary. | Turns launch excitement into promises the team can keep. |
What The Pull Tells Us And What Today Needs
Eight observations from the data and local operating docs, each with a recommendation for Sprint 0.
Events need branch logic before page production.
POS appears in 48 of 137 orders, while the public events page has only 1 click on 1,160 impressions. The event channel is real, but Mad Hudson will not always own the page. SEO and capture still need support whether the page is Mad Hudson-owned, organizer-owned, platform-owned, or social-only.
For Sprint 0: Build the LA event support branch now: page owner, support packet, product roles, inventory truth, opt-in capture, proof capture, and 48-hour debrief.
Pour Souls should be treated as a monthly operating lane.
The planned Pour Souls Chicago relationship changes the event problem from one-off prep to recurring infrastructure. A monthly lane can compound proof, local search language, customer memory, product feedback, and follow-up if it has a small repeatable kit.
For Sprint 0: Confirm who controls the Pour Souls public surface, then create one reusable monthly kit: title convention, images, product focus, opt-in copy, recap fields, and relationship notes.
Shipping is the highest-risk capacity gate.
Apartment fulfillment is still part of the brand's control loop. Premature 3PL outsourcing could remove learning and trust before the rules are written. But keeping everything close without measurement can also hide strain until it breaks.
For Sprint 0: Add a shipping gate: parcels/week, hours/week, backlog days, exceptions, supplies failures, travel-week strain, and what can be delegated without losing brand control.
Relationship capture is part of event readiness.
The local channel strategy treats email as the owned relationship channel, and the event-page system already calls events a clean consent surface for email/SMS. That means the event sheet should capture people, context, and permission, not just sales.
For Sprint 0: Add a relationship capture block to the LA sheet: contact method, product interest, consent, promised follow-up, owner, and date. SMS only with explicit opt-in.
CD Watch is the product-page learning object.
The query "cd watch" has 20,521 impressions and 423 clicks, and CD Watch has enough stock to keep promises. That makes it the cleanest place to learn what a strong product page, support answer, and release standard should include.
For Sprint 0: Use CD Watch to define the minimum page/story/SEO standard before new watches enter the pipeline.
Eddie demand exists, but the promise is broken.
Eddie shows real movement and abandoned-checkout pressure, but current inventory is zero. That makes it dangerous to treat past demand as a simple promotion cue.
For Sprint 0: Decide restock, waitlist, or quiet state. Do this before any event, Whatnot, social, or email mention creates avoidable friction.
Whatnot cannot be capacity-planned from the current files.
The repo has Whatnot templates, but no raw weekly order exports, livestream reports, or ledger exports. That is not a failure. It is the next data request.
For Sprint 0: Ask for the last 3-5 stream readbacks or exports: hours, lots, orders, gross, payout, prep time, post-stream shipping load, exceptions.
The repo should become the business memory.
The local command center already says the highest-leverage move is product-data and intent capture, not a big content calendar. The current reports answer enough to start a weekly pulse, but not enough to understand customer quality or retention.
For Sprint 0: Set a 15-minute weekly pulse: product movement, search signal, abandoned pressure, relationship capture, event/Whatnot notes, shipping risk, decisions made.
The page should help Garen facilitate the room. The workbook can hold the raw tabs. The room needs observations, questions, and a first operating rhythm.
Recommended Sprint 0
Recommended scope: Event Support Branches + Shipping/Fulfillment Gate + Relationship Capture. It uses the LA deadline, prepares the Philadelphia runway, starts the monthly Pour Souls lane, and gives Connor a way to retain the right work while making capacity visible.
- LA event support branch.Confirm event facts, page owner, organizer support packet, product roles, capture/proof plan, and 48-hour follow-up.
- Philadelphia runway.Known facts, open questions, decision dates, organizer/page owner, and inherited checklist from LA.
- Pour Souls monthly lane.Recurring title/copy/image/product/opt-in/recap kit, plus a clear owner for the public event surface each month.
- Shipping/fulfillment gate.Parcels/week, hours/week, backlog days, exceptions, supplies failures, travel-week strain, and delegated-safe tasks.
- Helper/software screen.Compare upgraded in-house tools, trusted local helper, hybrid fulfillment, and 3PL only after the work has rules.
- Whatnot capacity model.Stream cadence, prep time, live roles, post-show shipping load, exception load, and export list needed.
- Relationship capture block.Contact method, product interest, consent notes, promised follow-up, owner, date, and channel preference.
- New-watch intake checklist.Product truth, story truth, page truth, channel truth, ops truth, and shipping promise before launch.
- Weekly pulse.One 15-minute review covering product movement, event surface status, Whatnot load, shipping strain, relationship capture, and decisions made.
Garen's Facilitation Posture
Be curious, not clever. Listen for where the work is living in someone's head. Stay in discovery until the room gives you a real pattern, then become decisive about the next object to build.
Signals to catch
- "I have to remember..."Information-flow problem.
- "I do not trust someone else with..."Rules, access, or delegation-boundary problem.
- "We do not know if it worked..."Feedback-loop problem.
- "We need to post more..."Ask what decision posting should change.
- "We should outsource shipping..."Ask which rule, buffer, or measurement is missing first.
Room phrases
"Can I pause and separate the worlds for a second?"
Then map the worlds: events, page ownership, Whatnot, shipping, Shopify/site, DMs, social, relationship capture, holiday, new releases, and internal ops.
Follow-up question: did this person ask to hear from Mad Hudson again, and if so, where?
Shipping question: what should stay close because it carries judgment, and what is mechanical enough to delegate once the rules are written?
Sources And Gaps
All numbers above are aggregate and safe for a public noindex page. Raw customer/contact rows are not published here.
| Source | Authoritative for | Current status |
|---|---|---|
| Shopify product snapshot | Product status, stock, price, handles, vendor/product identity. | Pulled May 26, 2026. |
| Shopify line items and order signals | Orders, units, gross line value, POS/web contour, recent product movement. | Pulled May 26, 2026. |
| Shopify abandoned checkouts | Abandoned value and product-level pressure. | Pulled May 26, 2026; aggregate only here. |
| Google Search Console | Query, page, device, date, and country search signal. | Latest local 180-day report dated May 25, 2026. |
| Whatnot | Stream cadence, orders/show, prep load, shipping load, payout/friction. | Templates exist; raw exports still needed. |
| Facilitation structure | Keeping discovery useful when the conversation is broad, emotional, or moving quickly. | Think Fast Talk Smart, What / So What / Now What, and Stanford GSB Matt Abrahams materials used as facilitation cues. |
| Event surface ownership | Whether the public event surface is Mad Hudson-owned, organizer-owned, platform-owned, or social-only. | LA, Philadelphia, and Pour Souls owner details still need confirmation before support packets are final. |
| Shipping software research | Batch labels, tracking sync, package presets, pickup/manifests, and low-friction in-house fulfillment. | Shopify bulk labels, Shippo batch labels, ShipStation batches, and Pirate Ship integration docs used as option screen, not a vendor recommendation. |
| Fulfillment partner research | When inventory can leave the apartment: receiving, storage, pick/pack, tracking sync, returns, custom packaging, SLA, and error handling. | Shopify Fulfillment Network partner docs, Flexport, ShipBob, ShipMonk, and Red Stag reviewed as categories to compare after volume/cost data exists. |
| Email / customer quality | List growth, event signup source, welcome/post-purchase/review/restock flows, repeat relationship quality. | Not yet pulled into this view; aggregate owner-approved pull recommended. |
| SMS consent guardrails | Marketing texts, opt-in source, opt-out handling, message type, consent proof. | Governed by TCPA/FCC rules; treat as legal-review territory before sending campaigns. |
| Email compliance guardrails | Unsubscribe, sender truth, postal address, opt-out handling, transactional vs. marketing distinction. | FTC CAN-SPAM guide used as baseline guardrail. |
What is still missing
Exact LA and Philadelphia event dates, venue/logistics details, booth/table needs, travel constraints, event page/surface owners, organizer asset constraints, and the exact monthly Pour Souls rhythm.
Shipping facts: parcels/week, shipping hours/week, backlog days, exception/error rate, supplies setup, packaging steps, available apartment workspace, current shipping tools, pickup/dropoff rhythm, travel-week constraints, and the work Connor would feel safe delegating.
Current Whatnot exports, specific new-watch release details, email/SMS list status, consent records, repeat-customer aggregates, and current flow performance are still missing from this view.
Ask for these in the room. Do not invent them.