Zhivko Todorov
ALL CASE STUDIES

CASE 116 · QUENCH · 2024

STEP FUNCTIONSEXPRESSWORKFLOWSCOST

Step Functions Express, where Standard was overkill.

A marketing automation company ran 14 Standard Step Functions workflows for short, high-volume orchestration tasks. They were paying for state-transition cost they didn’t need. We migrated the right workflows to Express and dropped Step Functions cost 62%.

INDUSTRY

Marketing automation

DOMAIN

COST

DELIVERED

2024

STACK

STEP FUNCTIONS STANDARD·STEP FUNCTIONS EXPRESS·CLOUDWATCH LOGS·EVENTBRIDGE·LAMBDA

RESULTS

What changed, by the numbers.

STEP FUNCTIONS BILL

−62%

$8.4K → $3.2K / MONTH

WORKFLOWS MIGRATED

11 / 14

EXPRESS-ELIGIBLE

WORKFLOW DURATION

UNCHANGED

WITHIN 5-MIN BUDGET

OBSERVABILITY GAP

CLOSED

CLOUDWATCH LOGS

HOW IT WENT

Standard Step Functions bills per state transition; Express bills per millisecond of execution. For short-running workflows with many transitions, Express is dramatically cheaper. The team had stayed on Standard because that was the default and "it works."

We classified each workflow by duration distribution and state-transition count. Eleven of fourteen fit comfortably inside the Express 5-minute and 25k-transition limits. The remaining three had long-running waits that genuinely needed Standard. CloudWatch Logs replaced the per-execution history view that Express does not provide.

Step Functions bill dropped 62% across the migrated workflows. Workflow duration is unchanged (within the budget). The observability gap closed once teams adapted to querying CloudWatch Logs Insights rather than clicking through the console execution view.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →