about
A creator should own the audience, not the daily busywork.
Digest Ops exists because the hardest part of a newsletter is not the send button. It is the daily middle: watching sources, judging relevance, writing in a consistent voice, and turning attention into trust without burning out.
Review before autopilot
AI should earn trust in drafts before it gets permission to send. Every publication starts with human review by default.
Sources stay visible
A digest is only useful when readers can trace the signal. Source links and raw item metadata remain part of the workflow.
Audience context beats generic summaries
The same news means different things to founders, developers, creators, and operators. Digest Ops writes for the defined reader.
Delivery is part of the product
Consent, unsubscribe, send queues, and event history are core infrastructure, not afterthoughts.
Where the product is going
- 04
2026-04MVP
Public site, workspace dashboard, source ingestion, AI issue drafts, subscribers, cron endpoints, and Resend delivery queue.
- Q2
2026-Q2Creator beta
Dedicated Digest Ops credentials, sending-domain setup, first creator dogfood publications, and source quality reports.
- Q3
2026-Q3Operator edition
Agency workspaces, connector templates, source marketplace, and conversion analytics for creator offers.
Two ways to start: