Issue 1 — Why we launched OutcomeOS

Base URL: https://outcomeos.cloud. Public archive page: /newsletter/001. Add it to sitemap.xml when published.

Why we launched OutcomeOS

Hi, I'm [Founder name]. This is the first OutcomeOS letter. It's short.

The bill

Most small teams automate with Zapier. It's the default, and it's good at what it does: their homepage lists 9,000+ apps.

Here's a common setup. A lead fills in a form. A workflow looks the lead up, sends an SMS, and notifies the owner. That's a trigger and 3 actions.

At 1,000 leads a month, that's 3,000 tasks. On Zapier's pricing page (checked November 10, 2026), the plan that fits is Professional at the 5,000-task tier: $89 a month billed annually, or $133.50 a month billed monthly.

Zapier counts a task "whenever Zapier successfully completes a unit of work". Make counts credits. n8n counts executions and promises you "only pay when a workflow runs from start to finish". Activepieces counts one credit per run.

All fair meters. All of them measure the workflow.

What none of those numbers tell you

Whether the lead replied.

A run can be green from top to bottom while the SMS went to a dead number. Or it went out twice because a timeout was retried. Or it went out fine and nobody answered.

That gap, between "the workflow completed" and "the thing we wanted actually happened", is why OutcomeOS exists.

How OutcomeOS works

1. You define the outcome. "Every qualified lead gets a reply within 5 minutes." You set the success criteria.
2. Workflows do the work. A visual builder with a webhook trigger, HTTP requests, if/else, delays, wait-for-event with a timeout, notify, and connector actions. Each run gets its own Durable Object on Cloudflare, so a 24-hour wait is just stored state.
3. Only verified events count. A signed webhook, an authenticated API call, or a provider-signed event can mark the outcome achieved. A finished workflow can't. Unsigned events are recorded and ignored for success.

On the reliability side: per-step retries with exponential backoff, idempotency keys, duplicate trigger prevention, a dead-letter queue, step logs with secrets masked, and replay that starts from the failure and reuses what already succeeded. A non-idempotent call, like a POST with no idempotency key, isn't retried blindly. It waits in "Requires attention" for you.

What it costs

Starter is free. Growth is a monthly subscription and Business is custom. The Growth price isn't set yet. It'll be on the pricing page before anyone pays. I won't claim we're cheaper than anyone until there's a number to compare.

The code is MIT. You can run it in Docker or deploy it to your own Cloudflare account for free.

Where we're worse

Integrations. Signed webhooks and generic HTTP are available. Twilio SMS, HubSpot contacts and Stripe are in beta with your own credentials. CRM Messaging, Zoho CRM, Gmail, Salesforce, GoHighLevel, WhatsApp Cloud API, Google Sheets, Slack and Mailchimp are coming. We have no SOC 2, no AI agents and no code steps yet.

If you need 40 apps connected this week, stay on Zapier. If you need proof that each lead got a reply, try this.

How to start

• Sign up: https://outcomeos.cloud/signup?utmsource=newsletter&utmmedium=email&utm_campaign=issue-001
• Compare, with sources: https://outcomeos.cloud/compare?utmsource=newsletter&utmmedium=email&utm_campaign=issue-001
• Run it yourself: https://outcomeos.cloud/docs/self-host?utmsource=newsletter&utmmedium=email&utm_campaign=issue-001

Reply and tell me which outcome you'd verify first.

— [Founder name]