Date: 2026-09-21, 1:30 PM EDT Granola: 1e88e4e7-4e8c-43af-a1bd-1cbb5fd1e6da
Attendees
- Blake Stewart (Megaphone AM lead)
- Jon Morehouse (Nuon, jon@nuon.co)
Summary
Catch-up call after Jon’s 4 trips in 6 weeks (including work with Lovable on KYC integration). Social output has been quiet. Jon will review the Notion content board after his meetings today and pull items into “edits required.” Priority is to queue 10-15 backlog items by mid-week to restart publishing.
Content topics flagged as promising: MCP (active, performing well), “Graduation” post, “Source of truth” / image management, app branches/BYOC release process (new feature). Conferences coming up as conference season approaches.
Jon explained the app branches content idea live: the problem of keeping all BYOC customers on consistent versions via a GitOps model, while still allowing deployment control. He sees this as a good thread topic - technically deep but explainable.
Blake to send Jon specific content prompts focused on MCP and dogfooding. Jon will update the board and start pushing items to publication.
Decisions
- Shift from reactive backlog to proactive prompt-based workflow. Blake will send Jon specific prompts around MCP and dogfooding to guide his board feedback.
- App branches/BYOC release process to become a dedicated content thread. Jon’s live explanation from this call used as draft basis.
- S3-related content deprioritized as no longer timely.
Action Items
- Jon: Review content board after meetings today, pull items into “edits required,” add notes, start publishing. Goal: 10-15 items queued by mid-week.
- Blake: Draft a thread on app branches / BYOC release process using Jon’s explanation from this call.
- Blake: Send Jon specific content prompts around MCP and dogfooding.
Notable Excerpts
“I think it’s been a little quieter for me on socials lately, which is always a good thing actually, because then when you kind of spike back up, you get a nice boost by the algorithm.” (Jon)
“There’s this problem that you have where you want all your customers to kind of be the same. You want them to have the same version, but each customer is going to have like different permutations of your software… how do you sort of build like a GitOps model where when you merge your code, it gets deployed to them?” (Jon, on app branches content idea)
“I think the topics that we’re talking about need to be refreshed… the S3 stuff went really, really well, but it’s kind of not the thing going on right now.” (Jon)
Full transcript available in Granola. Also filed as client call: ~/.hermes/profiles/ryevalley/clients/nuon/calls/2026-09-21-1e88e4e7-4e8c-43af-a1bd-1cbb5fd1e6da.md