Designing operations for Make.com automation

Design the process before
you automate it.

Henry designs the operational logic. You build the Make scenarios from the specification. Every scenario starts from a specified step — not a guess about what should happen next.

The automation gap

Why do most automations
break or underperform?

Make.com gives you powerful building blocks — modules, connections, filters, routers. But the hardest question isn't how to wire a scenario. It's knowing which process to automate, what each step should accomplish, and where the automation boundary sits.

Most teams automate what's visible rather than what's structural. They build scenarios for the tasks they already do manually, without asking whether those tasks are the right ones. The result is automated busywork — faster execution of the wrong process.

Henry maps your entire operational process before you build a single scenario. It identifies which steps are automation candidates, specifies each one across three planes, and produces a Fit Assessment that tells you which steps should be fully automated, which need human oversight, and which should stay manual.

Without process design

Automate what's visible. Build scenarios from intuition. Hope the edge cases don't break production. Spend more time fixing automations than building new ones.

With Henry

Map the full process. Specify each step. Know which steps should be automated before building. Every Make scenario starts from a structured specification — not a conversation about what might work.

How it maps

How do Henry steps
become Make scenarios?

Henry Specification Make.com Scenario Element
Work Plane — IntentScenario purpose and expected outcome
Work Plane — InputsTrigger data and webhook payloads
Work Plane — OutputsTarget module actions and data mappings
Execution Plane — Trigger typeInstant (webhook) vs. scheduled vs. manual triggers
Execution Plane — ModeFully automated vs. human-approval gates
Execution Plane — Error handlingError routes, retry logic, and fallback paths
Experience Plane — Quality barFilters, validators, and data quality checks
AAAERRR StageScenario organization by business function

These are design-to-execution patterns, not a product integration. Henry produces specifications you translate into Make scenarios.

The diagnostic layer

Which processes should you
automate first?

The AAAERRR framework diagnoses where your operational gaps are. The diagnosis tells you which stage is broken — and which steps within that stage are the highest-leverage automation candidates.

The Funnel
Awareness
Acquisition
Activation
The Flywheel
Engagement← HERE
Retention
Revenue
Referral
Off-Ramp
Emergency Exit Sentinel-triggered · Intervention → Graceful Close → Win-Back
Off-boarding Completion-triggered · Engagement → Retention → Revenue → Referral → Awareness

Funnel — Awareness to Activation

Awareness → Acquisition → Activation. A prospect becomes a committed customer. Linear, sequential, non-reversible. If it breaks here, you have a conversion problem.

Flywheel — Engagement through Referral

Engagement → Retention → Revenue → Referral. A committed customer becomes a sustained relationship. Most businesses have a Flywheel problem they're solving with Funnel dollars.

Off-Ramp — two required pathways

Emergency Exit: Triggered automatically by sentinel conditions. Activates Intervention with a time boundary. If recovery fails, Graceful Close executes. Win-Back routes back to Acquisition.

Off-boarding: Triggered at final delivery. A designed linear exit at peak goodwill. Referral advocacy re-enters the Funnel at Awareness and Acquisition.

Design the process.
Then automate with precision.

Start with a diagnosis. End with scenario-ready step specifications.

Talk to Henry →