Supernormal field report / 01
Seven manual workflows quietly costing businesses time - and a practical method for deciding which one to delete first.
Start with the work, not the software
It is the visible part of a workflow: someone exports data, fixes the columns, asks a colleague for a missing number, pastes it somewhere else, checks it, and does it again next week. Buying another tool before mapping that sequence usually adds one more place to copy from.
annual labour cost = people × minutes per run ÷ 60 × runs per year × loaded hourly rate
annual exposure = annual labour cost + rework + delay + missed-opportunity cost
Data re-entry
Customer, product, job or finance data leaves one system and is manually re-entered into another. The work feels small because each transaction is small; the volume is what makes it expensive.
Seen in client work: synchronising product and customer information across Webflow, Airtable and Salesforce for Merchgirls.
Recurring reporting
Exports arrive from several tools. Someone cleans them, applies the same logic, formats the same tabs and sends the result to the same people.
Seen in client work: subscription and skip-cycle reporting pulled directly from Recharge for Knobby.
Quoting
Requirements are gathered by email, pricing is found in several places, exceptions live in one person's head, and the finished quote is manually assembled.
Deletion pattern: structured intake, governed pricing logic, approval thresholds and document generation - without automating judgement that belongs with a person.
Follow-up
Leads, approvals, documents or renewals stall because the follow-up is buried in an inbox or owned by nobody after a handoff.
Deletion pattern: define the state change that should trigger the next action, then make exceptions visible instead of automating silence.
Order or job processing
Once an order or job is confirmed, staff copy details into delivery tools, create folders, notify people, request assets and update the customer manually.
Deletion pattern: one confirmed event creates the delivery record, tasks, folders and notifications, with a human checkpoint for exceptions.
Multi-platform synchronisation
Products, memberships, contacts or inventory are maintained in more than one platform. Staff become the integration layer and uncertainty becomes normal.
Seen in client work: a 500-plus product catalogue operating across Webflow, Airtable and Salesforce for Merchgirls.
Reconciliation
Subscription, payment, membership or finance data is compared manually because neither system carries the complete operational truth.
Seen in client work: Recharge subscription reporting for Knobby and member access administration for the Mint Directors Association.
Rank before you build
| Factor | 1 | 5 |
|---|---|---|
| Frequency | Occasional | Daily or continuous |
| Labour | Minutes | Several people or hours |
| Rule stability | Every case differs | Same rules repeat |
| Error consequence | Easy correction | Customer, cash or compliance impact |
| Access readiness | Closed systems | Reliable API/export access |
Start with high frequency, high labour, stable rules and available data. Keep judgement-heavy, rare or badly defined work out of the first automation.
Want the ranked version for your business?
Fifteen minutes in. A one-page ranked Map within 48 hours. Yours to keep.
Map my workflows →