Date: 2026-08-24 Channel: lore thread, permalink https://ryevalley.slack.com/archives/C09QEFHJW7P/p1787587427148699 Signee: Jodi Frank (jodi@culineerapp.com) Reported by: Michael Houck
Jodi Frank signed for Culineer as a Lore client. Michael announced in lore and immediately asked about scheduling a kickoff this week.
Kickoff status: Emma (Emma/U09FUJUDJPJ) is available Tue, Wed, or Thu before 3pm BST this week. Michael is traveling Wed-Mon; prefers Tue or Thu. Kickoff not yet booked as of this capture.
Background: Culineer was introduced as a prospect on 2026-08-04. Strategy call with Geo and Jodi on 2026-08-21 scoped a 3-pronged engagement (technical SEO, content, link building, ~$2,500 over 3 months). Contract signed 2026-08-24.
Roster action needed: Add Culineer as active Lore client in clients/roster.md.
Update: 2026-08-25 - Slack Onboarding Blocker
Jodi Frank replied to the Slack invite (sent from michael@ryevalley.co) with an error: she gets an error screen instead of a confirmation code when trying to join the ryevalley.slack.com workspace (#lore-culineer channel, 3 members). Kickoff is still not booked (Michael traveling Wed-Mon). Onboarding is blocked on Slack access until the login error is resolved.
Action needed: Someone on the team needs to troubleshoot Jodi’s Slack login (re-invite, try a different email, or contact Slack support). Do before kickoff call is scheduled.
Update: 2026-08-28 - Slack Connect workaround agreed
Jodi confirmed Slack Connect requires a paid plan on her end (ryevalley.slack.com uses a feature that needs paid Slack on both sides). Michael replied: proposed using email or WhatsApp as the communication channel. Jodi counter-proposed that she can invite Michael and Emma to a channel in Culineer’s own Slack workspace, and offered to pay for Slack if needed.
Michael should confirm whether to proceed via Jodi’s Slack, email, or WhatsApp. Kickoff call not yet scheduled - Michael was traveling Wed-Mon.
Update: 2026-08-30 - Jodi sent Slack workspace invite
Jodi (jodi@culineerapp.com) sent Michael a formal Slack invitation to join Culineer’s own workspace (culineerapp.slack.com, 5 members already). Invite expires in 30 days. This resolves the communication channel question from 2026-08-28 - Culineer’s Slack is the agreed channel.
Update: 2026-08-31 - Michael rejects Culineer Slack, channel still unresolved
Michael replied to Jodi’s Culineer Slack invite: “Unfortunately that won’t really work well on our end since our Hermes agent won’t be able to have access there.” He has asked Emma to propose the best alternative approach. Communication channel is still unresolved - the 2026-08-30 update was premature in calling it settled.
Action needed: Emma to respond with a channel recommendation. Options remaining: email, WhatsApp, or a solution that keeps Hermes in the loop. Kickoff call still not scheduled.
Update: 2026-09-01 - Emma proceeds via email, onboarding active
Emma Sivess (emma@lorebuilders.com) emailed Jodi Frank directly on Sep 1: “I’ll be emailing from this account for now - until we get into slack - so we can keep everything in the right place.” Emma has reviewed Culineer’s ICP and tone-of-voice preferences. Key notes from Emma’s email: ICP is survey-backed (not assumed), strong signal for content approach. Tone items incorporated: health/trust/taste/chemical-free on Do list; balancing community vs. self-interest addressed (Culineer’s data says users act for themselves first, guidelines were over-indexing community). Communication channel is now settled: email via lorebuilders.com until a Slack solution is found. Kickoff not yet formally scheduled but onboarding has started in substance.
Update: 2026-09-02 - Positive client signal; content priorities clarified; Hermes blind spot confirmed
Client health: Positive. Jodi Frank replied (Sep 2): “The plan is solid and I have complete confidence in the process.” No churn signal.
Content priority correction from Jodi: Do not over-index on recipes. Culineer’s user-base strategy is a 3-legged stool: (1) what is in season, (2) where to buy locally, (3) recipe inspiration. Recipe data Jodi shared was market-shopping context, not product priority.
Active asks from Jodi: (1) She wants to review the content calendar and flag missing topics - Emma to keep her in the loop on blog decisions. (2) Existing Culineer blog post (food-labels/organic decoding) needs to be SEO-structured per Lore strategy - pending Emma action.
Slack channel settled - Hermes blind spot: Jodi confirmed she will not upgrade her own Slack. Emma accepted and will use Culineer’s Slack (culineerapp.slack.com) for working comms with Jodi going forward. Michael explicitly flagged to Emma (Sep 2 email): “Hermes won’t have any context on conversations with them. Not a blocker of course but just a heads up.” Emma acknowledged. Ongoing Culineer working comms will be invisible to Hermes; periodic email syncs or explicit brain captures are the only way to surface Culineer context going forward.
Action needed: Emma to SEO-structure the food-labels blog post. Emma to loop Jodi into content calendar review.