How We See Your Business
The machinery behind your business, and how work actually moves through it.
Before recommending a fix, it helps to have plain language for what's actually there: what a business system is, what your team is able to do, and how work moves from one step to the next.
What is a business system?
A business system is the combination of people, tools, information, and rules that repeatedly produces something important - not a single piece of software, and not a department on an org chart.
We're currently testing four of them as the major systems in most growing service businesses. This is a working model we're still pressure-testing, not a finished, locked list.
Demand
creating enough interest and opportunity to work with
Conversion
moving someone from interested to committed, one step at a time
Fulfillment
reliably delivering what you promised
Retention
keeping and growing the relationships you already have
What is a capability?
A capability is something your business is able to do. Capabilities usually live inside one of the systems above - they're the specific abilities that make it work.
Inside Demand, that might be publishing content, running referrals, or capturing inquiries. Inside Fulfillment, it might be scheduling a job, assigning the right person, or checking quality before you call it done.
A capability isn't the software that helps you do it. Being able to send marketing emails is the capability - the email tool just helps you do it. Swap the tool and the capability can stay exactly the same, or disappear entirely if nobody knows how to use it.
What is a workflow?
If systems are the machinery and capabilities are what it can do, a workflow is the actual movement - how a piece of work, a customer, or a dollar gets from one state to the next.
Every workflow has the same handful of moving parts:
A few workflows you'd recognize, one from each stage of a customer's relationship with your business:
Grow
Inquiry → Qualified Opportunity
Someone reaches out. Somebody has to notice, respond, and decide if it's worth pursuing - before it goes cold.
Flow
Completed Work → Invoice
A job wraps up. Somebody has to turn that into a bill, promptly, without waiting on the owner to remember.
Keep
Customer → Repeat Customer
A job is paid and closed. Somebody has to reach back out later - or that relationship quietly ends by default.
We'll come back to Completed Work → Invoice on the Business Health and Business Anatomy pages - same workflow, looked at through those lenses too.
How a struggling workflow actually shows up
You usually don't see "the workflow is broken." You see the symptom: leads falling through the cracks, staff asking you what happens next, finished work that sits for days before anyone invoices it, customers who go quiet after the job is done.
Those are all evidence that a workflow somewhere isn't moving the way it should - not a diagnosis by themselves. The same symptom can have different causes: unclear ownership, a missing handoff, no one visible to escalate to. Finding out which one it actually is comes before fixing anything.
How this relates to Grow, Flow, and Keep
Elsewhere on this site we talk about Grow, Flow, and Keep - the simpler, three-stage way of describing a customer's relationship with your business. That's deliberately the easier version. Systems, capabilities, and workflows are the more detailed layer underneath it, not a different framework competing with it.
Roughly: Grow leans on Demand and Conversion, Flow leans on Fulfillment, and Keep leans on Retention. That mapping is a useful approximation for getting oriented, not an exact one - we're still refining exactly where the lines sit.
Curious where a workflow like this is actually breaking down in your business? The Workflow Finder narrows it down in about a minute - no email required.
Try the Workflow FinderRecognize a workflow that isn't moving right?
We'll talk through where it's actually breaking down before recommending anything.
Book a Call