Should this work exist?
STOP or SIMPLIFY unnecessary work before software multiplies it.
Coral Shark Lab · First-Workflow Gate
What Should You Automate First in Your Business?
Direct answer
Start with a repeated job that follows a mostly stable path, has visible unusual cases, carries manageable consequences and can fall back to a manual process. The biggest time-sink is not automatically the best first job.
First-Workflow Gate
Burden is an opportunity signal, not a readiness override
A burden-only ranking can point to the wrong first project. A workflow may consume eight owner-hours a week yet remain a poor candidate if inputs are inconsistent, the process changes by customer, exception frequency is unknown and a bad output can commit the business to the wrong price.
A smaller workflow with a stable path, clear exceptions and an easy manual fallback can be a better first automation because it is safer to learn on and easier to control.
Rule: high workload cannot cancel instability, unknown exceptions, high consequence or weak reversibility.
First-Workflow Gate
Run the First-Workflow Gate in sequence
Is the normal process stable?
Can competent people describe trigger, inputs, normal steps, finish state and ownership consistently?
What is the exception rate?
Sample representative cases. If material exception frequency is unknown, mark it UNKNOWN and HOLD.
What must stay human?
Classify steps as DETERMINE, INTERPRET, DECIDE or ACT.
What happens when it is wrong?
Assess consequence, detectability, reversibility and manual fallback separately.
What is the smallest controlled version?
Use the Least-New-System Ladder before buying another platform.
Is the value worth it?
Now compare cash, capacity, risk/error exposure and opportunity value.
First-Workflow Gate
Exception rate is a first-class evidence field
“Mostly standard” is not enough. For a representative sample, record whether each case followed the normal path, why exceptions occurred, whether they could be detected from the available information and what human judgement was required.
CaseStandard?Exception detectable?Human judgement
AYes—Approval only
BNoYesUnusual scope
CNoNo/unknownRelationship context
The point is not the percentage alone. The sample tells you where the machine should stop.
First-Workflow Gate
DETERMINE / INTERPRET / DECIDE / ACT
DETERMINEA rule or calculation can produce the answer from known inputs.
INTERPRETUnstructured information must be read, classified or transformed; AI may help.
DECIDEA choice changes price, scope, rights, risk or relationship; usually human.
ACTSend, update, book or commit through explicit controls.
The goal is not maximum automation. The goal is controlled flow.
First-Workflow Gate
Use the Least-New-System Ladder
0 STOP / SIMPLIFY1 EXISTING FEATURE2 CONFIGURE3 INTEGRATE4 SMALL CUSTOM LOGIC5 CUSTOM SOFTWARE
Start with “what is the smallest controlled change that makes the job behave better?”, not “should we use Zapier, Make, n8n or an AI agent?”
First-Workflow Gate
Capacity Is Not Cash
If a workflow releases five owner-hours but the business does not reduce cost, increase output or use those hours differently, the business may have gained valuable capacity without gaining cash.
Money that actually changes.
Time made available.
Change in failure/rework/missed-action risk.
Potential output or attention enabled.
First-Workflow Gate
STOP, HOLD, NARROW or PROCEED
The framework should not force every workflow toward “yes”. A HOLD is useful only when it states what is missing, why it matters, how to measure it and what result would allow the decision to change.
Evidence-to-Change-HOLD: “Exception frequency is unknown. Sample the last 20 cases, classify exceptions and record whether each was detectable from available data. Reconsider a standard-path automation if standard cases are consistently identifiable and exceptions can stop before commitment.”
First-Workflow Gate
Synthetic quote-preparation example
This example is illustrative, not customer evidence. A service-business owner receives job details by email and repeatedly rebuilds the same quote structure, while price and unusual terms require judgement.
Outcome: HOLD / NARROW. Define the minimum-facts intake, sample recent quotes to measure exception types, automate only routine preparation, and keep price, unusual scope and contractual commitments human.
First-Workflow Gate
A 30-minute first-workflow screen
- List five recurring jobs that create visible drag.
- For each, write the trigger and finish state.
- Cross out work that should simply stop.
- Mark any workflow whose normal path cannot be described as HOLD.
- Sample recent cases and record standard vs exception.
- Mark steps DETERMINE / INTERPRET / DECIDE / ACT.
- Narrow high-consequence, hard-to-reverse autonomous actions.
- Check features already present in the existing systems.
- Only now compare burden, cost and potential value.
Evidence and claim boundary
What this page is — and is not.
First-Workflow Gate is a Coral Shark decision framework, not a claim of scientific or industry consensus. Synthetic examples are illustrative, not customer proof. Where a material external fact is added later, it should be sourced to a current primary source and dated.
Unknown stays unknown. No industry-average saving, automation percentage or customer outcome is invented to make the case more impressive.
Related reading
Need this applied to one real job?
The Owner’s Brief applies the same discipline to one recurring job: what you told us, your estimates, our interpretation and what is still unknown stay separate. The answer can be stop, wait, start smaller or proceed.
Apply this to one job · £249 + VAT