Part 1 The problemWhy teams need this
01 · THE PROBLEM
Newsletters die the first week nobody has time to write one. This keeps the writing automatic and the final say with you, so the habit survives busy weeks.
Part 2 How it worksWhat it does, step by step
02 · WHAT IT DOES
Every Monday morning it researches the week's news on your topics, writes the issue, and emails you the draft. The workflow waits. Once you approve, it builds the campaign, attaches your list and sends it.
03 · HOW IT RUNS
Step by step, as built.
Research the week
Three Exa searches fan out from the trigger, one per standing topic, and are merged.
Draft
Claude writes the issue from the merged results.
Ask for approval
The draft is emailed through Gmail and a Wait node holds the run open.
Launch
On approval, the campaign is created in ManyReach, the subscriber list is attached, and it goes out.
04 · WHERE A PERSON STAYS IN
The machine drafts. A person decides.
The run pauses until you approve the emailed draft. About 20 minutes of review, not a morning of writing.
05 · TOOLS AND APPS
Built around the systems already in the process.
06 · WHEN SOMETHING BREAKS
Failure is designed in.
- ✓Anything unhandled triggers our central error workflow, so a crash gets reported instead of failing silently.
Standard on every build
- Schema validation before downstream writes
- Retry and error routes for external API failures
- Duplicate-safe processing and idempotent updates
- Human approval where the action carries business risk
- Execution logging for support and audit review
Part 3 The impactWhat it's worth, and how we'd build yours
07 · PROJECTED IMPACT
What it should change in the business.
Projections for a typical deployment. The calculation below shows the math, and you can put in your own numbers.
08 · ROI CALCULATION
How it pays back in your business.
The starting numbers are a hypothetical deployment sized to the projections above. Change any of them to your own volumes and costs, and the math updates underneath.
- Full-time equivalent freed
- 0.1 people
- Gross value
- $5,126
- Running cost
- −$180
- Return per $1 of running cost
- $28.5
The math: 4 newsletter issues × 180 min × 12 months × 89% ÷ 60 = 128 hours a year × $40/hour = $5,126. Net value = gross value − $180 running cost a year.
09 · HOW WE'D BUILD YOURS
How we'd build yours.
- Discover: map the current process, systems, volumes, owners and exceptions.
- Design: define the canonical data model, approvals, retries and system boundaries.
- Build: implement credentials, nodes, validation and observable error routes.
- Prove: run controlled data through success, duplicate and failure scenarios.
- Operate: publish runbooks, ownership and measurable service levels.
