Comms Infrastructure — CRM, Newsletters and Operating Procedures

Objective

Run communications on our own infrastructure with written operating procedures. First deliverable: both newsletters (Life Itself and Seeds of Renaissance) set up in the new CRM (Twenty, sending via Resend), embedded on the websites, with existing Substack newsletters migrated without subscriber loss.

Vision, needs and job stories

The what and why for this project lives in 2612-comms-infrastructure/. It was moved there from the comms and crm repos on 2026-10-09; the two docs overlap and are to be consolidated into one once settled. Short summary: CRM vision briefing.

• Communications use cases: current state across projects, cross-project needs, communication stories, the first vertical slice, and open decisions.
• CRM motivation and job stories: the SCQH for a single contact store and the nine CRM job stories (capture, segment and outreach, relationship management).

Elsewhere: the product and channel inventory stays in comms; how it is built, guides and the job-story scorecard stay in crm; tasks are in crm Beads epic crm-dxb.

Relationship to other work

• Brand rollout: the Substack migration (lip-42k.2.4) and Over the Mountains consolidation (lip-42k.2.3) are part of the rollout; here they are tracked as one migration with the Life Itself newsletter. Life Itself is somewhat outside the rebrand, but shares the infrastructure.
• Seeds of Renaissance website: newsletter signup embeds and the pilot post depend on it.
• Content delivery pipeline: lists CRM and automation as candidate supporting systems; this project is where they are actually built.
• Sibling repository ../crm holds the CRM implementation.

Open questions

• Is Media House the right parent, or Ops? Provisional.
• Owner not yet confirmed.

Sources

• Rufus's capture, 2026-10-05 (chat).
• Moved in 2026-10-09: comms ref/comms-use-cases.md, crm motivation.md.