K KitHub
Operator worksheet / 01
The Automation Opportunity Scorecard

Find the manual work worth automating first.

A focused 20-minute scorecard for small agencies. Identify repetitive workflows, estimate the monthly capacity they can return, and choose one practical first build.

Use it like an operator: start with three recurring workflows, score each one, estimate the time returned, then select one contained first version. This is a prioritization tool—not a promise that every workflow should be automated.
01 / CAPTURE

List the work

Name the trigger, manual steps, owner, and monthly volume.

02 / SCORE

Test the fit

Rate frequency, time, friction, repeatability, and system readiness.

03 / PRIORITIZE

Choose one

Combine score, capacity value, and a manageable first version.

01 — Build a short workflow list

WorkflowTriggerManual steps todayWho touches it?Times / month
Example: New-client onboardingIntake form submittedCreate record, tasks, welcome, alertAccount manager + ops12
Workflow 1
Workflow 2
Workflow 3

Start where the signal is strongest

Someone copies the same information between tools.
A handoff depends on memory, chat, or email.
A small delay compounds across the month.
The same fields, steps, and destinations repeat.

Do not start with: a rare exception, an undefined process, or work that depends on subjective judgment without repeatable rules.

K KitHub
Operator worksheet / 02
Score the opportunity

Separate useful ideas from first builds.

Give every factor a 1–5 score. Add the scores and multiply by four for an Opportunity Score out of 100.

02 — Score each workflow

Factor1 = weak signal3 = workable5 = strong signalScore
FrequencyMonthly or lessWeeklyDaily / many times weekly
Manual timeUnder 5 min/run10–20 min/run30+ min/run
FrictionMinor inconvenienceRework or follow-upsMissed handoffs, errors, client delays
RepeatabilityDifferent every timeMostly standardClear rules, fields, sequence
System readinessTools/data unclearSome tools connectedKnown trigger and destinations
Total × 4

Score guide

80–100 / Build candidate
Map the workflow and plan a first version.

60–79 / Prepare
Document edge cases or standardize the inputs first.

Below 60 / Park it
It may matter, but it is not the best first automation.

03 — Estimate capacity value

Current monthly hours = (runs × minutes) ÷ 60 Hours returned = current hours × expected time removed Capacity value = hours returned × loaded hourly cost

Use a realistic automation rate: start with 60–80% time removed, not 100%.

Monthly capacity estimate

InputWorkflow 1Workflow 2Workflow 3
Runs per month
Minutes per run
Current monthly hours
Expected time removed (%)
Hours returned / month
Loaded hourly cost ($)
Monthly capacity value

Reality check: only score work that has a known trigger, defined data, repeatable destination actions, a review owner, and a team member accountable for exceptions.

K KitHub
Operator worksheet / 03
Make the call

Prioritize one workflow. Build a real first version.

Use both the Opportunity Score and the capacity estimate. The strongest first build is repeatable, valuable, ready enough, and limited in scope.

04 — Make the priority decision

WorkflowOpportunity scoreHours returned / mo.Capacity valueComplexityDecision
Workflow 1Low / Med / High
Workflow 2Low / Med / High
Workflow 3Low / Med / High

Operator decision rule

Choose the workflow that meets all four conditions:
1. Scores 80+ (or can get there after simple cleanup).   2. Returns enough time or reduces enough friction to matter monthly.   3. Has a known trigger, data source, and destination actions.   4. Can launch as one narrow workflow—not an operations overhaul.
First-build brief

Turn the winner into a controlled build.

Workflow to build first

Trigger

Inputs required

Automation actions

Human review / exception path

Owner + 30-day success measure

Next move

Do not automate everything. Build the highest-confidence workflow, measure the outcome for 30 days, then decide what earns the next build.

Starting with client onboarding? The Make.com Client Onboarding Bundle gives service teams a practical intake-to-handoff structure for standardizing onboarding in Make.com.