Skip to content
FW Delta Research

FW Delta Research

Publicly verifiable analyses of software economics, portability, automation and self-controlled infrastructure.

No paid rankings. No invented benchmarks. Methodology, sources and assumptions are published alongside.

7 flagship reports · open datasets · traceable methodology · versioned corrections

Methodology Corrections and versions
published reports
7
numbered sources
233
open datasets
33
data cutoff
29 July 2026

How this series came about

These issues were worked on over several months. Data collection, modelling, source checking and review take time, which is why they are not released one by one but as a complete series. All issues listed here were released together on 29 July 2026. From here on the series continues on a rolling basis.

The month in an issue name marks its place in the series, not its release date. Both are stated separately on every report page, together with the data cutoff and the version, and the same applies to the machine-readable metadata. There are no backdated values.

A documentation score measures publicly findable documentation. It is not a compliance, security or quality statement. Missing information means "not documented", not "does not exist".

Sorted by edition month, newest issue first. The series reads from the most recent question backwards; the real first publication date is on every card.

FDR-2026-04 Automation Economics Edition April 2026

Automation Unit Economics Benchmark 2026

FW Delta shows why automation should be compared by billable units, failure paths, review work and successful outcomes rather than by number of workflows.

First published
29 July 2026
Data cutoff
29 July 2026
Methodology
normalized billing unit, workflow topology and cost-per-outcome scenario model
Objects examined
4 platform meters; 12 workflow archetypes; 3 volume tiers; 180 cost-per-outcome scenarios

Key findings

  • CALCULATED In the baseline model, 10,000 identical lead events generate 90,000 Zapier Tasks, 100,000 Make Credits, 10,000 n8n Executions or one active Activepieces flow - before retry and failure paths.
  • CALCULATED Across the twelve extended archetypes, the assumed retry multiplier varies from 1.05 to 1.35; billable technical work therefore rises without additional business value.
View methodology and sources

Research standard and methodology

Statement classes, source hierarchy, score standard, handling of missing information, price and currency rules, rounding and conflict of interest.

Read the standard

Corrections and versions

Version policy, correction log, reporting route for factual errors and the current version status of every issue.

View the log
Newsletter

Technical analyses for decision makers

New posts on SaaS economics, AI architecture, compliance and owned infrastructure.

I would like to receive analyses and updates from FW Delta by email in future. I can withdraw my consent at any time. Further information is available in the privacy policy.

No spam. Unsubscribe at any time. Privacy notice