Search "signs your business processes are broken" and most answers give you a mood: things feel chaotic, the days feel reactive, you feel like the business runs you. A mood cannot be checked, and it cannot be priced. The signs below can. Each one is a fact about where a record lives, who holds a piece of knowledge, or what happens to a piece of paper — something you can go and look at in your own business this week, true or not true. And each one is shown the way it appears in a real worked example: the weekly catering operations workflow in the Taste & Thyme Catering sample plan published on this site, a synthetic example whose figures are all in public, so the signs here are not abstractions. They are what a broken workflow looks like when someone writes it down and adds it up.
Start with the record, not the feeling
A workflow is broken in a way that costs money when the work depends on a record nobody fully trusts, a memory nobody else holds, or a message nobody can find again. Those are not three ways of saying the same thing. They are three different failure shapes, and the checklist below separates them, because the fix for a record problem is not the fix for a memory problem. Work through the five signs in order. For each one, the test is a question you can answer from the room you are standing in, not from how the week felt. If a sign is true of one of your workflows, note which workflow — the last section of this page is a method for capturing that one workflow on paper, in five fields, so the sign stops being a suspicion and becomes a number.
Sign one: the same fact lives in two places
The test: pick the fact your business runs on — the booking, the order, the appointment, the job date — and ask where it lives. If the honest answer names two places, and a person has to keep them in agreement by hand, the sign is present. Owners describe this one in their own words as "my business runs on spreadsheets", usually followed, a year or two later, by "we have outgrown spreadsheets" — the file that was the system at five jobs a week is still the system at twenty, except now a second copy of the truth has grown up next to it.
In the sample workflow, this sign is the first problem the business names, in its own words: double-booked Saturdays, because the booking record lives in a spreadsheet and on a paper calendar, and the two drift apart. Neither record is wrong on purpose. Each one is right about the bookings that reached it. The failure happens in the gap between them, on the day two events claim the same Saturday and both records can prove they were there first. A second copy of the truth is not a backup. It is a second truth, and the business pays for the difference on the worst possible day.
Sign two: everything depends on you
The test: name the workflow, then ask who can run it on a day you are unreachable. If the answer is nobody — if the exceptions live in your head, the supplier's quirks live in your head, and the team messages you to find out what happens next — the sign is present. The search phrase for this one is the bluntest on this page: "everything in my business depends on me". It is rarely about control. It is about capture: the knowledge was never written down anywhere except in the person who does the work, so that person can never stop doing it.
In the sample, the owner's own block of work is 5 hours a week at $60 an hour, which is $300 a week and $15,600 a year — and that is only the owner's scheduled time, priced. It does not price the interruptions: the relay work of passing changes from the person who heard them to the people who need them, which lands on the owner because the owner is the one who holds the whole picture. Price that relay work for your own business with the same arithmetic, and label it honestly — the inputs are examples, and you replace them with your own: say the relaying takes 2 hours a week, at $60 an hour that is $120 a week, which is $6,240 a year, spent not on doing the work but on carrying news about the work between people. If your number is bigger, the sign is not a management problem. It is an unwritten workflow with a person standing in for the paper.
Sign three: ordering runs on memory
The test: ask how the last order was decided. If the answer is a person remembering what ran out last time, glancing at a shelf, and judging — rather than a count written down somewhere — the sign is present. Ordering from memory fails in both directions at once, which is why owners rarely see it as one problem: the ingredient shortages land on the busy day, when the missing item stops a job, and the overbuys land quietly, as stock that spoils or sits. Different days, different pains, same cause — the order was built from a memory instead of a record.
In the sample, the business names this problem in its own words: ordering from memory, which produces ingredient shortages on some days and overbuys on others. Note what the sample does not do with that problem: it does not price a single shortage or a single spoiled case, because the published figures price blocks of time, not individual bad days. This page follows the sample. The sign is checkable without a price — watch one order get built and ask what it was built from — and the price arrives later, when the capture method prices the block of time the ordering sits inside.
Sign four: the schedule lives in a group text
The test: ask where the current version of the schedule is. If it is a thread — if the agreed change is a message somewhere above the jokes and the photos, and the document the team works from on the day was never updated to match — the sign is present. A group text is a fine place to agree a change. It is a poor place to keep one, because a thread keeps everything and files nothing: the swap is in there, but so is every earlier version of the plan, in the order people sent them, not the order they took effect.
In the sample, this is the third problem, in the business's own words: group-text shift swaps that never reach the event sheet, so the sheet the team works from on the day is not the schedule they agreed. The cost shape here is worth naming plainly. Nobody made an error. The swap was agreed, announced, and acknowledged — and the record the day runs on still shows the old plan, because agreeing a change and recording a change are two different steps, and the workflow only has the first one. When a server arrives at the wrong venue, the business usually blames attention. The checklist blames the record: there was never a step whose job was to move the change from the thread to the sheet.
Sign five: the invoice is retyped and the deposit is not tracked
The test: follow one job's money paperwork from the work to the invoice. If a person retypes figures that already exist somewhere else — from a sheet, a notebook, a message — into the invoicing tool by hand, the sign is present. Then ask where the deposit for that job is written down. If the answer is a memory, a message, or nowhere, the second half of the sign is present too.
In the sample, this is the fourth problem, in the business's own words: invoices retyped by hand, and deposits nobody tracks. The two halves belong together because they have the same shape as every other sign on this page: the fact exists, but it lives in a place the next step cannot use. The figures for the invoice exist in the workflow's own records and are typed again anyway, which costs time and invites the one changed digit nobody catches. The deposit exists in the client's hands and in nobody's ledger, so the business cannot answer the simplest money question — what has this job actually paid so far — without asking around. Retyping and untracked deposits are not bookkeeping untidiness. They are the money version of the two-calendars problem: the truth is in two places, or in no place, and a person bridges the gap by hand.
The sample, added up
Signs tell you where to look. They do not tell you what the looking is worth, and a checklist that stops at recognition leaves the owner where the mood-based lists leave them. So here is the sample workflow with its blocks priced, exactly as published, to show what the five signs above add up to inside one workflow. The workflow — booking in, event staffed, food ordered, invoice out — takes 18.62 hours a week and costs $722.31 a week, which is $37,560 a year, built from four blocks:
- The owner's own work — 5 hours a week at $60 an hour. That is $300 a week, and $15,600 a year.
- Event coordination — 12 hours a week at $30 an hour. That is $360 a week, and $18,720 a year.
- Kitchen deep-clean coordination — 2 times a month, 2.5 hours each time, at $30 an hour. Spread across the weeks of a year, that is $34.62 a week, and $1,800 a year.
- Kitchen equipment servicing — 1 time a quarter, 6 hours each time, at $60 an hour. Spread the same way, that is $27.69 a week, and $1,440 a year.
The sample does not break out a separate cost for each problem, and this page does not invent one — the problems sit inside the blocks, and the published figures price the blocks. What can be priced exactly is the other side: what the named fixes cost, at the prices in the plan catalog this studio publishes. For the double-booked Saturdays, one shared booking record: Tripleseat, listed at $4,500 a year, with Google Calendar connected, listed at $0 a year, and Acuity Scheduling, listed at $192 a year, to catch Saturday conflicts. For ordering from memory, MarketMan, listed at $2,988 a year. For the group-text swaps, Slack, listed at $87 a year, together with the same Tripleseat record, so changes land on the event sheet. For the retyped invoices and untracked deposits, QuickBooks Online, listed at $456 a year, together with Stripe, which the catalog lists as pay-as-you-go with no annual price, so this page gives it none. The priced fixes the sample names come to $8,223 a year, next to the workflow's own $37,560 a year — the only comparison this page will make: the fixes have a published price, the workflow has a worked-out cost, and which fix is worth its price depends on how much of a block the problem behind it really causes. That judgement is the owner's, and the blocks are what make it possible.
The capture method: steps, owners, exceptions, time, cost
If one or more signs are true of a workflow in your business, the next move is not a tool. It is a capture: one workflow, written down in five fields, before anything is bought or changed. The five fields are these:
- Steps — the workflow as it actually happens, in order, including the places where the work waits and the places where a fact is copied from one record to another.
- Owners — for each step, the person who does it, named. A step with no owner, or a step whose owner is whoever notices, is a sign recorded in the workflow's own handwriting.
- Exceptions — the swap that never reached the sheet, the Saturday booked twice, the deposit nobody wrote down, the Friday that never matches the normal day. Exceptions are not edge cases; in a manual workflow they are usually where the cost is.
- Time — for each block of work, how long it takes and how often it happens, stated by the person who does it.
- Cost — each block's time at that person's rate, added up, so the workflow has a total the owner has seen built line by line and can argue with line by line.
That is the whole method, and it is deliberately small: one workflow, five fields, your own numbers. The method guide in these Notes, "How to audit one workflow" — https://www.agenticartists.com/blog/how-to-audit-one-workflow — walks through the capture step by step on the same catering workflow used on this page, with the arithmetic shown. Do the capture on the workflow where the most signs landed. A workflow with three signs captured on paper is worth more than five workflows recognised and left as feelings, because the captured one can be priced, compared against a fix's published price, and decided about — which is the point where a broken workflow stops being a suspicion and becomes a decision.
The worked examples behind this page
This checklist is the top of a small set of worked pages in these Notes, and each sign above has a fuller treatment in the set. The teardown, "What a catering workflow costs", pulls the sample workflow apart block by block and problem by problem, with every figure checkable against the published sample plan. The comparison, "DIY, a productized audit, or a consultant: which audit fits?", lays out the three ways to run the capture with help — do it yourself, buy a productized audit for one workflow, or hire a human consultant — at published prices, with what each way cannot do stated plainly. And the cost guide, "What a workflow audit costs in 2026", gives the full price ladder behind that comparison, rung by rung. Read the teardown for the numbers, the comparison for the choice, and the method guide linked in the capture section above for the worksheet itself.
Doing this with Where AI Fits
Where AI Fits runs the capture for one of your workflows: a guided conversation reconstructs the workflow, you confirm the steps, the owners, the exceptions, the hours, and the rates, and the paid AI Integration Plan, at $49, writes up the time and cost block by block, names the problems in your business's own words, and puts a named fix and its catalog price next to each one. The sample plan used throughout this page is published on this site, so you can check every sign and every figure here against the finished document before deciding.
Sources
Every number on this page traces to the studio's own published sample or catalog, checked on 2026-10-30. Taste & Thyme Catering is a synthetic example, labelled as such on the sample plan itself; its figures are the sample's own, not measurements of a real business. No external statistic or price is used on this page.
- Taste & Thyme Catering sample plan — $722.31 a week, $37,560 a year, 18.62 hours a week, the four blocks, and the four named problems — https://www.agenticartists.com/products/where-ai-fits/sample-plan — checked 2026-10-30
- The Wave 4 teardown of the same sample — the four problems in the business's own words and the named fixes with their catalog prices — https://www.agenticartists.com/blog/what-a-catering-workflow-costs — checked 2026-10-30
- The Wave 3 method guide — the capture method (steps, owners, exceptions, time, cost) worked step by step — https://www.agenticartists.com/blog/how-to-audit-one-workflow — checked 2026-10-30
- The Wave 10 comparison — https://www.agenticartists.com/blog/diy-vs-productized-audit-vs-consultant — and the Wave 2 cost guide — https://www.agenticartists.com/blog/what-a-workflow-audit-costs — checked 2026-10-30
- Where AI Fits plan catalog prices, checked against the catalog in this tree on 2026-10-30 — Tripleseat $4,500 a year, Google Calendar $0 a year, Acuity Scheduling $192 a year, MarketMan $2,988 a year, Slack $87 a year, QuickBooks Online $456 a year; Stripe listed as pay-as-you-go with no annual price
- Where AI Fits — $49 for the AI Integration Plan for one workflow, published on this site at /products/where-ai-fits — checked 2026-10-30
Ready to look at one workflow?
Start with the Where AI Fits sample plan, or learn more about the product and its workflow-first approach.