8cfc831bbae94c0c818086586d309abc

Why Does My To-Do List Keep Getting Longer?

Tue, 06 Oct 2026 12:04:29 GMT

Your to-do list keeps getting longer because new commitments are entering your world faster than old commitments are leaving it .

That is the basic maths.

If during an average week you:

Add 45 things.

Complete 25.

Delegate 5.

Delete 2.

Then your list grows by:

13 items every week.

No app will fix that.

No colour-coding system will fix it.

No clever morning routine will fix it.

You do not primarily have a to-do-list problem.

You have a commitment-flow problem .

And for business owners, the inflow can be enormous.

Employees need decisions.

Customers ask for things.

Emails create actions.

Meetings create actions.

Ideas create actions.

Problems create actions.

Sales creates actions.

Finance creates actions.

Your family exists.

You remember something while walking the dog.

Somebody messages:

“Quick one...”

Nothing involving the words “quick one” has ever improved a business owner's to-do list.

The list gets longer because capturing work is easy.

Making conscious decisions about what doesn't deserve your time is much harder.

A to-do list is not the problem

Writing things down is sensible.

Research on cognitive offloading, essentially using external tools to reduce demands on internal memory, broadly supports the usefulness of external reminders. A 2025 meta-analysis of experimental studies found that cognitive offloading can improve performance on memory-based tasks, particularly for prospective memory, remembering to do something later.

Good.

Your brain should not have to remember:

Ring accountant.

Approve quote.

Renew insurance.

Speak to James.

Book dentist.

Send proposal.

That is precisely what a trusted external system is for.

The problem begins when the place designed to remember commitments becomes the place you expect to complete every commitment immediately .

Those are different jobs.

Your master list can contain 120 things.

Your Tuesday cannot.

Your list has unlimited capacity

You don't.

This sounds obvious.

Yet most task-management systems quietly ignore it.

You can add another task in approximately three seconds.

You cannot add another hour to Thursday.

That asymmetry is why lists expand.

HSE's guidance on workload makes a useful point here. Human capacity for processing information, making decisions and performing tasks is limited, and workload can gradually drift upwards as new activities are added over time.

That is exactly what happens to many owners.

Nothing dramatic changes.

Monday:

One additional meeting.

Tuesday:

One customer issue.

Wednesday:

Two approvals.

Thursday:

New marketing idea.

Friday:

Employee asks you to review something.

Next week:

Repeat.

Three months later you have 147 open tasks and feel strangely guilty every time you look at them.

The work entered gradually.

Your capacity did not.

The first mistake is treating capture as commitment

An idea occurs to you:

We should create a referral programme.

You write it down.

Fine.

But something subtle just happened.

An idea became a task.

Then:

Look into AI note-taking software.

Task.

Could rewrite the service brochure.

Task.

Maybe do a podcast.

Task.

Research second location.

Task.

You have converted every thought into an obligation.

Don't.

Capture is important.

But:

Captured does not mean committed.

Something can enter your system because you do not want to forget it and later be:

Deleted.

Deferred.

Rejected.

Delegated.

Placed on a someday list.

Turned into a proper project.

Or deliberately ignored.

If every captured thought joins the active to-do list, curiosity becomes workload.

Your business generates tasks without asking permission

This is particularly dangerous for capable owners.

An employee says:

“Could you quickly review this?”

You say:

Yes.

Customer says:

“Can you have a look at something?”

Yes.

Supplier sends a question.

Yes.

Someone requests a meeting.

Accepted.

Nobody formally says:

Adam, I would like to remove 45 minutes from the finite amount of time you have available this week.

But that is what happened.

Availability Architecture matters here.

The easier it is for other people to transfer work, decisions and uncertainty onto you, the faster your list grows.

The to-do list is sometimes merely the visible evidence of an organisational design problem.

Count where your tasks come from

This exercise can be eye-opening.

Take everything added over the last week and classify the source.

Perhaps:

Customers.

Employees.

Meetings.

Email.

Your own ideas.

Finance.

Sales.

Family.

Recurring administration.

Then ask:

Which source is creating disproportionate workload?

For many owners, the answer is:

Their own team.

Not because the team is lazy.

Because the owner has become the natural destination for:

Decisions.

Checking.

Approval.

Reassurance.

Exceptions.

Problems.

Now productivity advice aimed entirely at the owner misses the point.

You do not need to become 20% faster at processing requests.

You need to reduce how many requests genuinely require you.

Being capable can become a trap

You can do it quickly.

So you do it.

Someone asks:

“Can you just check this quote?”

Two minutes.

Fine.

Then another.

And another.

Now you personally check 40 quotes each month.

Your competence became part of the process.

Work ethic asks:

How can I get through these quicker?

Agency asks:

Why do these still need me?

That is a much more powerful question.

A to-do list full of work somebody else should be capable of owning is not evidence that you need better personal productivity.

It is evidence that dependency remains inside the business.

Your list probably contains things that are not actually tasks

This creates another problem.

You open the list.

It says:

Website

What does that mean?

Redesign it?

Write copy?

Call developer?

Review analytics?

Then:

Marketing

Brilliant.

You should be finished by lunch.

A project is not a task.

Neither is an outcome.

Examples:

Hire Operations Manager.

Improve cash flow.

Launch new service.

Sort pension.

Fix marketing.

These may be legitimate commitments.

But they are not actions you can physically perform.

Your brain looks at:

Hire Operations Manager

and has to decide again:

What exactly do I do?

A better next action might be:

Email recruitment brief to Sarah for review.

Now the work can move.

Vagueness creates friction

The more vague items on your list, the harder it becomes to start.

You are not only doing the work.

You are repeatedly re-deciding what the work means .

That wastes attention.

A useful task should usually begin with a verb.

Call.

Email.

Review.

Draft.

Approve.

Book.

Read.

Decide.

Ask.

If the item requires ten actions, it is probably a project.

Give the project somewhere appropriate to live and identify the next action.

Your list may also contain waiting

Another classic.

Website quote.

You already requested it.

You are waiting for the developer.

That is not currently a task.

Move it to:

Waiting for.

Then perhaps create:

If no response by Thursday, chase developer.

Now the open loop has structure.

This matters because unfinished commitments can continue pulling at attention.

Research by Masicampo and Baumeister found that unfulfilled goals could produce intrusive thoughts and interfere with unrelated cognitive tasks. In several experiments, creating specific plans for unfinished goals reduced those interference effects.

You do not necessarily need to finish everything to gain mental relief.

You often need to know:

What happens next, and when?

This is why a massive undifferentiated list feels horrible

Everything appears simultaneously unresolved.

Submit VAT information.

Plan summer holiday.

Review website.

Call customer.

Write article.

Replace garage door.

Think about succession.

Book dentist.

Recruit employee.

Renew software.

Every item visually competes as though it deserves attention now.

It doesn't.

Some things are:

Now.

Some:

This week.

Some:

Scheduled next month.

Some:

Waiting.

Some:

Ideas.

Some:

Never.

A flat list strips away those distinctions.

Then your brain has to recreate them every time you open it.

Your master list and today's plan should not be the same thing

This single change helps enormously.

You need somewhere trusted to hold the wider universe of commitments.

Call it:

Master task list.

Task system.

Backlog.

Whatever.

Then you need a much smaller answer to:

What am I actually doing today?

If your master list contains 93 items, fine.

Today's plan might contain:

Three meaningful priorities.

Four smaller actions.

Two scheduled calls.

Much more credible.

The mistake is opening 93 tasks at 7am and somehow hoping your nervous system will politely identify the correct seven.

Stop moving 38 tasks from Monday to Tuesday

Digital task managers make this absurdly easy.

Monday:

27 overdue tasks.

Select all.

Move to Tuesday.

Tuesday arrives.

31 tasks.

Move to Wednesday.

This is not planning.

It is administrative lying.

If something genuinely needs doing Tuesday, schedule it.

If it does not, stop pretending.

An overdue date should mean something.

Otherwise the red warning symbol simply becomes wallpaper.

Dates are not priorities

This is another common mistake.

You decide:

Need to write article sometime.

Date:

Tomorrow.

Why?

No reason.

Tomorrow arrives.

You are busy.

Move it.

After five reschedules, it feels overdue despite never having had a genuine deadline.

Use dates for:

Actual deadlines.

Scheduled work.

Intentional review points.

Not as a method of making the task manager shout at you until eventually you submit.

Your list grows because you never properly review it

Things enter.

Few things leave.

Task management needs maintenance.

A weekly review is powerful because it forces decisions.

What changed?

What was completed?

What is stale?

What no longer matters?

What needs delegating?

What became a project?

What are you waiting for?

What should happen next week?

Without review, the list becomes a sedimentary record of every good intention you have had since 2023.

Delete more

This is probably the least glamorous productivity advice available.

Delete.

The task made sense six weeks ago.

Does it still?

No?

Gone.

You are not legally obliged to finish something merely because Past You once typed it into Todoist.

Things change.

Priorities change.

Ideas age badly.

Opportunities disappear.

Some tasks were never important.

The purpose of capturing something was to make sure you could make a proper decision about it later.

Now make the decision.

Deletion is not failure

Owners sometimes experience an odd guilt about abandoning tasks.

I said I was going to...

Did you?

Or did you write it down when it seemed like a reasonable idea?

A business owner who never changes their mind will eventually spend enormous amounts of time honouring obsolete intentions.

Delete deliberately.

That creates space for what matters now.

Delegate differently

You may already delegate.

But look carefully at what remains.

Task:

Review Sarah's proposal.

Why?

Perhaps Sarah needs:

Approval.

Could she have authority instead?

Task:

Answer Operations question.

Could Operations have a decision framework?

Task:

Check monthly report.

Could Finance send only exceptions?

Good delegation is not simply:

You do the task, then send it back to me for checking.

That can reduce execution work while leaving your to-do list full of approvals.

The deeper objective is:

Outcome moves without repeatedly returning to you.

If every delegated task comes back, you haven't really removed the work

This is a recurring Evolve principle.

If every decision in your company comes back to you, and six months later every decision you make comes back to me, we moved the dependency rather than removed it.

The same is true inside your team.

You delegate:

Draft it.

They draft.

Then:

Review.

Approve.

Correct.

Decide.

You still own the final mile of everything.

Some review is obviously appropriate.

But if your list is permanently full of final-stage approvals, ask which ones are genuinely necessary.

Your list keeps growing when you refuse to say no

This one is less technical.

Sometimes the maths is simply:

You accept more commitments than your life can contain.

Someone asks.

You do not want to disappoint them.

So:

Yeah, no problem.

Except there is a problem.

The time has to come from somewhere.

Another task moves.

Evening gets used.

Exercise disappears.

Family time shrinks.

You work Friday night.

The list then appears to be the enemy.

It isn't.

The commitment happened earlier.

At the moment you said:

Yes.

Better task management begins at the point of acceptance.

A useful phrase is “not yet”

You do not need to reject every opportunity.

Yes, but not this week.

I can look at this next Tuesday.

Send it to James first. If he can't resolve it, bring it back.

I can't take that on at the moment.

Clear boundaries stop future tasks forming invisibly.

This is Availability Architecture at the commitment level.

Your list may genuinely be impossible

This matters.

Productivity advice can become insulting when the underlying problem is simply excessive workload.

HSE's Management Standards say organisations should provide demands that are achievable in relation to agreed hours of work and have systems to respond where people cannot cope with workload demands.

Business owners often exempt themselves from this logic.

You have:

70 hours of commitments.

45 hours available.

Then ask:

“How do I become more productive?”

You don't.

At least not enough.

You need to remove:

25 hours.

Perhaps through:

Delegation.

Delay.

Deletion.

Automation.

Changing scope.

Hiring.

Different standards.

Different commitments.

Capacity is capacity.

Measure task inflow for one week

If your list constantly expands, do this.

Record:

Tasks added.

Tasks completed.

Tasks delegated.

Tasks deleted.

Tasks deferred out of the active system.

You may discover:

Added: 63.

Completed: 31.

Delegated: 8.

Deleted: 4.

Net growth:

Now the mystery disappears.

Your system is receiving work faster than you process or remove it.

There are only two broad solutions:

Increase sustainable throughput.

Reduce inflow.

Most people only work on the first.

Sustainable throughput does not mean working faster forever

Could you become more efficient?

Probably.

Templates.

Automation.

Better batching.

Fewer meetings.

Improved systems.

Those matter.

But eventually you hit biological reality.

Your brain cannot continue increasing output forever.

HSE's workload guidance notes that high workload can contribute to slower performance, errors and mistakes.

So the answer to excessive demand cannot permanently be:

Move faster.

At some point you need to control demand.

Context switching quietly expands your workload

Your list might say:

Write proposal.

Review accounts.

Call supplier.

Work on strategy.

Each sounds reasonable.

But if you bounce between them every fifteen minutes, you create additional cognitive cost.

Sophie Leroy's research on attention residue found that when people switch away from unfinished work, some attention can remain stuck on the previous task, impairing performance on the next one.

This is why ten tasks partially touched can feel much more exhausting than three tasks properly progressed.

Your daily plan should reduce unnecessary switching where possible.

Group similar work.

Finish meaningful chunks.

Give important work enough uninterrupted time to actually move.

Do not use your inbox as a to-do list

An inbox contains:

Information.

Requests.

Newsletters.

Receipts.

Questions.

Other people's priorities.

If unread email is your task-management system, you repeatedly scan everything to rediscover what requires action.

Process it.

Does this email require:

Action?

Reference?

Waiting?

Nothing?

Extract the commitment.

Then let the email be an email.

Messaging apps are even worse

Slack.

Teams.

WhatsApp.

Messages are conversations.

Not reliable task systems.

You read:

“Can you send me that thing tomorrow?”

Then six other messages arrive.

Commitment buried.

Either:

Complete it immediately if genuinely tiny and appropriate.

Or capture the task somewhere trusted.

Do not ask your memory to maintain a distributed database across five communication platforms.

Your list should tell you what you have committed to

Not contain every piece of information connected to the commitment.

Task:

Call Dave about lease renewal.

Good.

You do not need the entire lease copied into the task title.

Reference material belongs with reference material.

Tasks should remain actionable.

Otherwise the list becomes too visually heavy to scan.

Recurring tasks can multiply unnoticed

Weekly report.

Monthly review.

Quarterly audit.

Newsletter.

LinkedIn.

Management accounts.

Staff one-to-ones.

All sensible.

Until the business has created 47 recurring commitments.

Recurring tasks are especially dangerous because they automatically reappear after completion.

Review them occasionally.

Does this still need doing?

At this frequency?

By you?

At all?

A recurring task is a permanent claim on future capacity.

Treat it accordingly.

Meetings create hidden task debt

Meeting ends.

Everybody leaves.

Owner's notes contain:

Call X.

Review Y.

Speak to Sarah.

Look into Z.

Send A.

Decide B.

The calendar showed:

One-hour meeting.

Actual workload created:

Four hours.

That is why your calendar can look manageable while your list explodes.

When accepting meetings, consider not only the meeting itself but the work likely to emerge from it.

Projects generate more work as they progress

This is normal.

You begin:

Replace CRM.

Then discover:

Clean data.

Review fields.

Choose provider.

Train employees.

Build integration.

Rewrite process.

The original commitment grows.

Good project management should surface that reality.

Do not leave all newly discovered actions on one giant personal list.

Give projects structure.

Otherwise your to-do list becomes the project-management system for the entire company.

Owners should not be the company's universal project manager

This deserves saying explicitly.

If every project creates:

Adam to...

your list will never shrink.

Other people need to own outcomes.

A project owner should maintain:

Actions.

Decisions.

Dependencies.

Updates.

You should receive the things genuinely requiring your involvement.

Not carry everybody's project administration in your personal task system.

You probably need a decision list as well as a task list

Owners are often blocked by:

Decisions.

Not actions.

Should we hire?

Do we renew?

Do we increase price?

Do we accept the contract?

Do we proceed with software?

These can sit on the task list forever because they require thought rather than mechanical execution.

Group important decisions.

Give them space.

Perhaps a weekly decision block.

Perhaps management meeting.

Perhaps time with your Finance Director.

Do not let strategic thinking compete randomly with:

Buy printer ink.

The daily list should respect your calendar

You have:

Six hours of meetings.

Then schedule:

Write strategy paper.

Review accounts.

Create proposal.

Record three videos.

Why?

Where exactly are these activities happening?

A useful daily plan begins with reality.

What fixed commitments already exist?

How much usable focused time remains?

Then choose tasks that fit.

You are planning work into capacity .

Not writing a wish list.

Use implementation intentions for important work

Instead of:

Write proposal tomorrow

try:

At 9:00 tomorrow, before opening email, I will work on the proposal for 60 minutes at my desk.

That specifies:

When.

Where.

What.

A major meta-analysis of 94 tests found that implementation intentions, explicit if-then or when-and-how plans, improved goal attainment across a range of settings compared with intentions alone.

You do not need to apply this to every tiny task.

For meaningful work, turning intention into an actual execution plan matters.

Planning can also quiet the mental noise

This is one reason DROP begins with capture but does not end there.

Research on unfinished goals found that creating specific plans could reduce intrusive thoughts associated with those uncompleted goals.

That matches everyday experience.

Compare:

“Need to sort insurance.”

with:

“Insurance renewal is 28 November. Sarah is obtaining three quotes by 6 November. Review booked for Friday 9 November.”

Still unfinished.

Far less mentally noisy.

The brain has somewhere to put it.

This is what DROP is actually for

The DROP System is:

Dump. Review. Offload. Plan.

Not:

Write everything down and then work frantically until the list disappears.

It probably never will.

Dump

Get commitments out of your head.

Tasks.

Ideas.

Problems.

Things you are trying to remember.

This creates visibility.

But do not confuse visibility with obligation.

Review

Now make decisions.

Is this:

Actually important?

Still relevant?

A project?

Waiting?

Mine?

Time-sensitive?

Something I have merely been carrying out of guilt?

This is where a task list becomes a management system rather than storage.

Offload

Can it be:

Deleted?

Delegated?

Automated?

Deferred?

Moved into a project owned elsewhere?

Handled by somebody more appropriate?

This stage is the difference between ordinary task management and capacity management.

Most productivity systems spend too much time organising work and not enough time removing work .

Plan

Only now decide what you are actually doing.

Today.

This week.

When?

For how long?

In what sequence?

Your master list contains possibilities and commitments.

Your plan contains capacity-backed choices.

That distinction is enormous.

Try the Owner Task Test

For every significant item on your list, ask:

Does this genuinely require me?

If no:

Why is it here?

What outcome does this task create?

If you cannot answer:

Question its value.

What happens if I don't do it?

Nothing?

Interesting.

Is this actually one task?

If not:

Turn it into a project with a clear next action.

Does it need a date?

Use real dates, not motivational fiction.

Could this disappear entirely?

Often overlooked.

Where will it fit?

If nowhere exists in the calendar or weekly capacity, it is not currently planned.

Those questions will delete more work than another productivity app ever will.

Run a proper list reset

If your current to-do list has become a graveyard, do not spend four hours lovingly reorganising every task.

Start aggressively.

First pass: remove obvious rubbish

Delete:

Outdated ideas.

Tasks already completed.

Duplicates.

Things you no longer intend to do.

Do not overthink.

Second pass: identify projects

Move anything requiring multiple actions into project form.

Identify one next step.

Third pass: identify waiting

Move things currently owned by somebody else.

Add a review or follow-up date where necessary.

Fourth pass: offload

Delegate items that do not require you.

Properly.

With:

Outcome.

Owner.

Timing.

Authority.

Not simply forwarding the task and retaining all responsibility.

Fifth pass: separate someday

Good ideas that are not current commitments.

Get them away from active work.

Sixth pass: choose this week's priorities

What meaningful outcomes matter this week?

Not 35.

A small number.

Seventh pass: build the actual week

Put meaningful focused work into realistic spaces around existing commitments.

Now your task system and calendar agree with each other.

Your daily list should be finishable

This is a useful discipline.

Not necessarily easy.

Finishable.

If every morning begins with a list you already know you cannot complete, you are rehearsing failure daily.

You teach yourself that:

Today's list means nothing.

Then tasks slide.

Deadlines lose credibility.

The entire system becomes less trustworthy.

Better:

A realistic plan plus access to the wider list if capacity unexpectedly opens.

Leave buffer

You own a business.

Something will happen.

Customer calls.

Employee sick.

Opportunity appears.

You need buffer.

If your week is planned to 100% theoretical capacity, the first interruption destroys it.

Then you conclude:

Planning doesn't work for me because my business is unpredictable.

No.

Your plan assumed a level of predictability your life has never once demonstrated.

Plan with reality.

When everything is urgent, use Article #63

Article #63 deals specifically with prioritising when everything feels urgent.

This article sits one step earlier.

If your list is endlessly expanding, priority management alone will not solve it.

You cannot efficiently prioritise your way through infinite commitments.

First reduce and structure the workload.

Then prioritise what remains.

Your to-do list should shrink temporarily

Not permanently.

New work will always arrive.

But after a strong review, the active list should become cleaner.

If every review only adds more:

You are capturing but not deciding.

A proper review should produce subtraction.

Delete.

Delegate.

Complete.

Move.

Clarify.

The list should change state.

Measure how much of the list is genuinely yours

This can expose owner dependency beautifully.

Take your current list.

Mark each item:

Owner-only.

Could be delegated.

Should never have reached me.

If 70% falls into the last two categories, productivity is not the main problem.

Organisation design is.

You are carrying work the business has not learned to carry without you.

Article #78 goes much deeper into that owner-versus-job distinction.

Do not make zero tasks the goal

This matters.

The objective is not:

To-do list empty.

You run a business.

There will be work.

Ideas.

Projects.

Future commitments.

A trusted system may contain plenty.

The goal is:

Nothing important is being accidentally forgotten, nothing irrelevant is being carried indefinitely, and the amount of active work reflects real capacity.

That is much healthier than Inbox Zero applied to your entire life.

A longer list is not automatically evidence of poor productivity

Perhaps the business is growing.

You have more responsibility.

More opportunities.

More people.

The number of captured items may genuinely increase.

That is okay.

The warning signs are:

Tasks repeatedly rescheduled.

Constantly overdue items.

No idea what actually matters.

Important commitments buried.

Owner working excessive hours.

List expanding much faster than completion.

Employees continually adding work to you.

Tasks with no clear next action.

No regular review.

Guilt every time you open the bloody thing.

Those tell you the system needs work.

Sometimes the answer is additional capacity

Not everything can be:

Deleted.

Delegated to existing employees.

Automated.

Perhaps demand genuinely exceeds available resource.

Then you may need:

Another employee.

Freelancer.

Supplier.

Virtual assistant.

Bookkeeper.

Manager.

Specialist.

But hiring should follow diagnosis.

Do not hire someone simply because your to-do list is long.

First determine:

What work exists?

Does it need doing?

At what skill level?

How regularly?

Could the system remove it?

Then decide whether additional capacity is economically sensible.

Sometimes the answer is reducing ambition

This may be the least fashionable productivity advice available.

You might simply be trying to do too much.

Write book.

Grow company.

Launch course.

Start podcast.

Train four times a week.

Redesign website.

Speak at events.

Be present parent.

Serve customers.

Lead team.

Write daily.

Travel.

Excellent ambitions.

Same human.

At some point:

More efficiency stops solving the problem.

You choose.

Whole-Life Profit matters because a system that technically gets more done while consuming everything else you value is not necessarily better.

The list is trying to tell you something

A permanently expanding to-do list is feedback.

Maybe:

You have weak boundaries.

Too many projects.

Poor delegation.

Uncontrolled access.

No review rhythm.

Excessive workload.

Vague tasks.

Too many recurring commitments.

Insufficient capacity.

Owner dependency.

Or simply a habit of saying yes before asking where the time will come from.

Do not merely organise the evidence.

Use it.

The 60-minute DROP reset

If your list currently feels ridiculous, do this.

Set aside one uninterrupted hour.

First 15 minutes: Dump

Capture anything still floating in your head.

Get to one trusted picture.

Next 15 minutes: Review

Mark each item:

Action.

Project.

Waiting.

Someday.

Delete.

Next 15 minutes: Offload

Delete aggressively.

Delegate.

Move waiting items.

Remove fake deadlines.

Separate things you are not genuinely committed to.

Final 15 minutes: Plan

Choose the small number of outcomes that matter this week.

Put meaningful work into actual available time.

Leave the rest in the trusted system.

Then stop looking at the entire universe of possible work every hour.

And repeat weekly

One giant cleanup will help.

But the inflow continues.

The system only stays healthy through review.

What entered?

What changed?

What can leave?

What matters next?

That is the loop.

Your list is not supposed to keep getting shorter forever.

It is supposed to stay under control .

The answer isn't a better to-do list

It is better decisions about commitments.

Capture so your brain does not need to remember everything.

Then review.

Delete.

Delegate.

Clarify.

Separate projects from actions.

Move waiting items out of active work.

Stop using arbitrary due dates.

Plan within actual capacity.

Protect enough buffer for running a real business.

And pay particular attention to the tasks that should never have belonged to you in the first place.

Because when your to-do list grows endlessly, the problem is rarely that you are too lazy to finish it.

More often, you have built a system where work can enter almost effortlessly and leave only through your personal effort.

Fix that equation.

How Much Should a Small Business Spend on Marketing?

Tue, 06 Oct 2026 10:47:52 GMT

There is no sensible universal percentage of turnover that every small business should spend on marketing.

A good marketing budget should come from:

What growth you are trying to create.

What a new customer is economically worth.

What it currently costs to acquire one.

How much sales and delivery capacity you actually have.

Which marketing channels have proved they can work.

How much cash the business can responsibly invest before seeing the return.

That is considerably more useful than:

“Marketing should be 5% of revenue.”

Five per cent of what business?

A £5 million contractor growing through relationships and tenders?

A £1 million e-commerce company?

A SaaS business with recurring revenue?

A specialist consultant?

A restaurant?

A manufacturer with £100,000 average orders?

The economics are completely different.

So if you searched for the correct percentage, I am going to disappoint you slightly.

There isn't one.

But there is a much better way to work out what your business should spend.

Why percentage-of-revenue rules are so seductive

They are easy.

Turnover:

£2 million.

Marketing percentage:

5%.

Budget:

£100,000.

Done.

It feels scientific.

It isn't.

Even large-company benchmarks vary and need enormous context.

Gartner's 2026 CMO Spend Survey reported average marketing budgets of 7.8% of company revenue. That number is regularly the sort of statistic people repeat as though it provides a budgeting rule. But the survey covered 401 senior marketing leaders across North America, the UK and Europe, and the vast majority worked for organisations generating more than $1 billion in annual revenue. It is emphatically not a benchmark for the average owner-managed small business .

That does not make the research useless.

It makes blind comparison useless.

A £3 million engineering company should not decide its marketing budget because Coca-Cola's CMO spends a particular percentage of revenue.

Use percentages as a sense-check, not the calculation

Once you have built your marketing budget properly, calculate:

Marketing investment as a percentage of revenue.

Marketing investment as a percentage of gross profit.

Marketing investment relative to growth.

Those numbers can be useful.

You can compare:

This year with last year.

Your different business units.

Your budget with whatever credible external benchmarks exist.

But the percentage should usually be the output of the thinking .

Not the input.

Start with the outcome

What exactly are you trying to achieve?

Perhaps:

Maintain existing revenue.

Grow revenue by £500,000.

Enter a new market.

Launch a service.

Replace customer churn.

Increase recurring revenue.

Win larger customers.

Generate more qualified pipeline.

Grow a geographic territory.

Marketing exists to support a business objective.

Business.gov.uk's current digital-marketing guidance takes exactly that approach: start with clear business objectives, understand the audience, decide whether the immediate priority is sales or longer-term brand building, then set a budget and targets based on the return you are trying to create.

So instead of asking:

“How much should we spend on marketing?”

start with:

“What does marketing need to help the business achieve?”

That changes the conversation immediately.

Maintenance marketing and growth marketing are not the same thing

Suppose your business currently produces:

£3 million revenue.

You are happy at roughly £3 million.

Customers repeat.

Referrals are strong.

Churn is low.

Marketing's job may largely be:

Maintain visibility.

Protect existing demand.

Keep pipeline healthy.

Support customer retention.

You may need a relatively modest investment.

Now take exactly the same £3 million business.

Leadership wants:

£5 million in two years.

Different job.

Marketing may need to:

Reach new audiences.

Build new channels.

Improve the website.

Create content.

Run campaigns.

Test paid acquisition.

Support Sales.

Build brand awareness.

Maybe recruit marketing capability.

Why would both businesses spend the same percentage merely because current turnover is identical?

The required change is different.

Work backwards from the amount of new business you need

This is where the budget becomes commercially useful.

Imagine you want:

£600,000 of additional annual revenue.

Your average new customer generates:

£20,000 of first-year revenue.

Roughly speaking, you need:

30 additional customers.

Now ask:

What is the gross profit or contribution from each?

Suppose the average customer generates:

£20,000 revenue.

40% gross margin.

That gives you:

£8,000 gross profit per new customer before wider overhead and acquisition cost.

You now have something against which a customer-acquisition budget can be judged.

Customer acquisition cost matters more than a random revenue percentage

Your customer acquisition cost , or CAC, is roughly:

Total cost of acquiring new customers ÷ number of new customers acquired.

The important phrase is:

Total cost.

Not only Google Ads.

If during a period you spend:

£20,000 paid advertising.

£15,000 agency.

£10,000 content and creative.

£5,000 marketing software.

£20,000 attributable internal marketing resource.

Total:

£70,000.

And marketing produces 50 genuinely new customers.

Approximate CAC:

£1,400.

Now we can have an intelligent conversation.

Is paying £1,400 to acquire a customer attractive?

Depends what the customer is worth.

Compare acquisition cost with contribution, not merely revenue

Suppose a customer spends:

£10,000.

Sounds great.

But gross margin is:

20%.

You generated:

£2,000 gross profit.

Paying £1,400 to acquire them leaves very little before the rest of the company's costs.

Now imagine another service where the customer spends:

£10,000.

Gross margin:

70%.

£7,000 gross profit.

The same £1,400 acquisition cost is completely different economically.

Article #77 looked at customer profitability in depth.

Marketing should increasingly understand which customers create good economics , not simply which customers are easiest to generate.

Lifetime value can justify higher acquisition costs

Perhaps customers normally remain for:

Five years.

Your first-year economics may look ordinary.

But over time they generate considerable contribution.

That can justify spending more to acquire them.

For example:

Annual contribution after direct servicing cost:

£4,000.

Typical relationship:

Four years.

Very simplified expected contribution:

£16,000.

Perhaps spending £2,000 to acquire that relationship is attractive.

But be careful.

Do not create imaginary lifetime value.

If customer retention is poor or you have very little historical evidence, do not justify an enormous marketing budget using:

“They'll probably stay for ten years.”

Use credible data.

Payback period matters

Two acquisition strategies both have excellent lifetime economics.

Channel A pays back its acquisition cost in:

Three months.

Channel B:

Twenty-four months.

If you have enormous cash reserves, perhaps both are viable.

If cash is tight, Channel B can become difficult to fund.

This is why marketing budgeting belongs alongside:

Cash flow.

Not outside it.

Article #85 on the 13-week cash forecast becomes relevant here.

An economically attractive marketing plan can still create a cash problem if expenditure happens months before customers pay.

Work out how much you can afford to invest before the return arrives

Suppose you intend to spend:

£12,000 per month.

The average sales cycle is:

Three months.

Customers then pay:

30 days after invoice.

You may be funding several months of activity before meaningful cash arrives.

How much?

What happens if results take twice as long?

British Business Bank recommends linking investment decisions to business objectives, cash forecasts and expected return rather than evaluating large spending decisions in isolation.

Your marketing budget therefore needs two tests:

Does the economics make sense?

And:

Can the business fund the journey?

Do not define “marketing budget” vaguely

This causes terrible comparisons.

One owner says:

“We only spend £20,000 on marketing.”

They mean:

Google Ads.

Another says:

“We spend £150,000.”

They include:

Marketing Manager salary.

Agency.

Website.

Advertising.

Software.

Events.

Content.

Both might actually have similar levels of external campaign spend.

Decide what you are measuring.

I would normally separate two numbers

Marketing operating cost

The relatively fixed capability required to run marketing.

For example:

Marketing employees.

Retainers.

Core software.

Website support.

Recurring creative resources.

Marketing campaign and growth investment

The more variable money actually deployed into activity such as:

Paid media.

Events.

Sponsorship.

Campaigns.

Content projects.

SEO work.

Direct mail.

Research.

Photography.

Video.

New landing pages.

Keeping them separate helps.

If revenue falls and you ask:

“Can we reduce marketing?”

you can see whether you are discussing:

Cutting advertising.

Or:

Removing the capability required to run the function at all.

Those are very different decisions.

Include the hidden internal cost

Perhaps the owner writes all the articles.

Sales Director spends Fridays creating LinkedIn content.

Administrator manually emails campaigns.

Apparently:

Marketing spend = £0.

No.

There is an internal resource cost.

You may decide not to assign an exact hourly rate.

Fine.

But do not pretend employee and owner time is free.

That becomes particularly important when comparing:

Do it internally.

versus:

Pay somebody else.

Website spend counts when the website is part of customer acquisition

Businesses sometimes separate:

Marketing budget.

Website budget.

Why?

If the website exists primarily to:

Generate enquiries.

Build trust.

Convert visitors.

Support customers.

then at least some of that investment is clearly part of your wider marketing infrastructure.

The same applies to:

SEO.

Photography.

Case studies.

Email marketing.

Marketing automation.

Business.gov.uk specifically says a digital-marketing budget should consider content expenditure alongside paid advertising rather than viewing media cost as the whole marketing investment.

Do not confuse advertising with marketing

This distinction is critical.

Marketing might include:

Market research.

Positioning.

Messaging.

Website.

Content.

SEO.

Email.

Events.

Referral systems.

Public relations.

Customer retention.

Case studies.

Social media.

Direct mail.

Paid search.

Paid social.

Advertising is one component.

So a business saying:

“We tried marketing and it didn't work”

because it spent £1,000 on Facebook ads is being slightly ambitious with the conclusion.

Some businesses need very little paid advertising

Imagine a specialist B2B consultancy.

Average contract:

£150,000.

Target market:

300 companies.

You probably do not need to reach four million consumers.

Your marketing budget may be better spent on:

High-quality research.

Authority content.

Sector events.

Target-account outreach.

Case studies.

Website credibility.

Relationships.

The correct channel depends on the buying process.

British Business Bank's current communications guidance recommends concentrating limited resources on a small number of channels where target customers genuinely spend their time rather than scattering activity everywhere.

This is particularly important for SMEs.

You rarely have enough money to be mediocre everywhere.

Some businesses need substantial paid media

Now imagine:

Consumer product.

Large addressable audience.

Low individual transaction value.

Online purchase.

Marketing can operate completely differently.

Paid search.

Social.

Video.

Retail media.

Creators.

Affiliate.

Potentially significant ongoing investment.

UK digital advertising continues to be an enormous and growing market. IAB UK's latest figures show digital ad spend reached £21.2 billion in the first half of 2026, up 13% year on year, with search alone accounting for £9.1 billion.

That does not mean your business should increase advertising because everybody else is.

It means you are operating in markets where substantial amounts of money compete for attention.

Channel economics matter.

Your previous marketing performance is the best starting benchmark

Before setting next year's budget, look at last year's.

How much did you actually spend?

Where?

What happened?

Article #74 covered marketing measurement in much more depth.

At minimum, understand:

Leads generated.

Qualified opportunities.

Customers won.

Revenue.

Gross profit or contribution.

Acquisition cost.

Where possible:

Retention and repeat purchasing.

Then ask:

Which investment would I happily make again?

Which would I increase?

Which would I stop?

Which do we genuinely not understand?

That is a much better budgeting process than:

“Add 5% because we want growth.”

Do not demand perfect attribution

You will not always know exactly what caused a sale.

Customer:

Saw your LinkedIn posts.

Then Googled you.

Read three articles.

Heard your podcast.

Met you at an event.

Received a referral.

Finally completed a website form.

Google Analytics says:

Organic search.

Was SEO responsible?

Partly.

So was everything before it.

Do not use imperfect attribution as an excuse to measure nothing.

But also do not allocate every pound only to the final click because it happens to be easiest to track.

Business.gov.uk explicitly distinguishes marketing intended to build longer-term brand trust from one-off activity aimed at immediate sales, recognising that the two have different time horizons and should not be evaluated identically.

Brand marketing still needs a commercial reason

“It's brand awareness.”

is not immunity from scrutiny.

What audience are you trying to become known by?

Why?

What evidence suggests awareness is increasing?

Branded search?

Direct traffic?

Target-account recognition?

Survey data?

Referrals?

Sales conversations?

Share of relevant audience?

You may not calculate a precise £3.72 return for every pound.

That does not mean:

Spend anything and call it brand.

Performance marketing is not automatically superior

Because you can see:

Clicks.

Leads.

Conversions.

CAC.

does not make the channel strategically better.

Performance activity can harvest existing demand exceptionally well.

But somebody also needs to create:

Awareness.

Preference.

Trust.

Demand.

This is particularly important where customers take time to decide or where your market is crowded with similar suppliers.

Your budget needs to reflect both:

Capturing demand that exists.

And:

Helping create future demand.

The balance depends on your market.

Beware marketing budgets built entirely around lead volume

You generate:

300 leads.

Amazing.

Sales says:

270 are rubbish.

Useful?

Maybe not.

Article #60 covered the difference between marketing activity and genuine lead generation.

Budget against:

Qualified commercial outcomes.

Not simply response.

That might mean:

Cost per qualified opportunity.

Cost per sales meeting.

Cost per customer.

Cost per £1 of gross profit acquired.

Those become increasingly useful as the business matures.

Sales capacity places a ceiling on useful marketing spend

Suppose Marketing can create:

100 qualified leads per month.

Sales can properly handle:

Should you double Marketing's budget?

Probably not yet.

Fix Sales capacity.

Likewise:

Sales can win the customers.

Operations cannot deliver them.

Article #76 applies.

The purpose of marketing is not generating demand the business cannot economically convert or serve.

Growth needs an operating system behind it.

Marketing should reflect your current constraint

If Sales needs more opportunity:

Marketing may deserve more investment.

If plenty of leads exist but conversion is terrible:

Fix Sales.

If conversion is good but customers are unprofitable:

Fix offer, pricing or targeting.

If work is plentiful but delivery is broken:

Do not blindly increase demand.

This is why I resist percentage rules so strongly.

A company with insufficient demand and one drowning in work should not automatically spend the same percentage of turnover on customer acquisition.

Marketing budget should respond to evidence

Imagine you invest:

£5,000 per month.

It reliably produces:

£20,000 of attributable gross profit from new customers.

Capacity exists.

Payback is acceptable.

What should you do?

Potentially:

Spend more.

Test whether the economics hold at:

£7,500.

Then perhaps:

£10,000.

A budget ceiling should not prevent sensible expansion of something demonstrably working.

The inverse is also true.

You spend:

£10,000 monthly.

Cannot connect it to:

Qualified opportunity.

Revenue.

Retention.

Strategic brand value.

Do not keep spending merely because:

“It's in the budget.”

Budgets are boundaries.

Not commandments.

Returns usually deteriorate eventually

This matters when scaling channels.

Perhaps the first:

£2,000 of Google Ads

captures highly valuable, high-intent searches.

The next:

£5,000

requires broader keywords.

The next:

£20,000

reaches weaker intent.

Your acquisition cost rises.

This is normal.

Do not assume:

£5k spend creates £25k profit.

Therefore:

£50k creates £250k.

Marketing rarely scales perfectly linearly.

Increase gradually and watch marginal performance.

Judge the next pound, not only the average

Suppose average CAC is:

£800.

Excellent.

But the additional budget added during the last quarter produced customers at:

£2,200 CAC.

That tells you the channel may be reaching saturation.

Average historic performance can hide declining marginal returns.

Ask:

What happened when we increased spend?

That is the number relevant to the next increase.

New marketing channels need test budgets

You do not know enough yet to assign a giant annual budget.

Suppose you want to test:

LinkedIn ads.

Trade event.

Direct mail.

You need enough money to conduct a fair experiment.

But not so much that being wrong hurts badly.

Business.gov.uk's current guidance on digital strategy encourages focused testing and analytics before wider investment, particularly where a business is entering a new audience or market.

Define before the test:

Audience.

Offer.

Budget.

Duration.

What success looks like.

What would justify continuing.

What would cause you to stop.

Then learn.

A £200 test can be just as useless as a £200,000 gamble

This depends on the channel.

Business spends:

£200.

Gets no leads.

Declares:

“Google Ads doesn't work for us.”

Maybe.

Or perhaps £200 produced 14 clicks in a competitive market and told you almost nothing.

Testing needs enough volume to generate usable information.

On the other hand:

“We need to give it a proper chance”

can become a wonderful excuse to burn £40,000.

Define the test.

Define the stopping rule.

Give marketing enough time for the channel to work

Paid search can produce signal quickly.

SEO may take considerably longer.

Content builds cumulatively.

Events have long lead times.

Brand investment can influence buying over months or years.

Do not assess every activity on the same timetable.

Likewise, do not hide weak activity behind:

“Marketing takes time.”

Know roughly what evidence you should expect first.

Maybe:

Search impressions.

Traffic.

Response.

Qualified leads.

Pipeline.

Revenue.

Different stages appear at different times.

Do not cut marketing automatically when revenue slows

This is one of the easiest mistakes.

Revenue falls.

Owner cuts:

Marketing.

Because:

“We need to save money.”

Perhaps correct.

But what happens to future pipeline?

Article #79 dealt with exactly this lag.

If marketing is clearly ineffective, cut or change it.

But removing productive demand generation because current revenue is weak can deepen the next decline.

Understand:

What is working.

What is not.

Then decide.

Equally, do not treat marketing as sacred

Some marketers will tell you:

“Never cut marketing in a downturn.”

Why not?

What if your marketing is crap?

Commercial decisions need more nuance.

Protect activities creating valuable demand.

Stop waste.

Reallocate.

Test.

Do not preserve expenditure because Marketing has elevated itself above financial scrutiny.

Build a base budget and an opportunity budget

This can work extremely well.

Base marketing investment

The things you intend to keep doing because they support the business consistently.

For example:

Website.

Core SEO.

Email.

Marketing capability.

Reliable advertising.

Content.

Opportunity or test budget

Money available for:

New campaigns.

Emerging channels.

Events.

Experiments.

New markets.

If something works exceptionally well, money can move towards it.

This avoids the ridiculous situation where a highly profitable new opportunity appears in June but cannot be funded because:

“We've already allocated the annual marketing budget.”

Do not lock every pound twelve months ahead

Strategy needs discipline.

Marketing needs some flexibility.

Gartner's 2026 research on large marketing organisations describes exactly this pressure towards sharper prioritisation and reallocation under constrained budgets, rather than assuming the original annual allocation should remain untouched regardless of performance. Again, its sample is predominantly very large organisations, but the budgeting principle is highly transferable.

Set boundaries.

Then allow evidence to move money.

Allocate budget by customer economics, not marketer enthusiasm

Marketing wants to promote:

Service A.

Why?

Great creative opportunity.

Sales says:

Service B converts better.

Finance says:

Service C produces twice the margin.

Operations says:

Service C is already at capacity.

Excellent.

Now you have a management conversation.

Perhaps marketing should push:

Service B.

Or perhaps the company should fix capacity for C first.

Marketing budget allocation belongs inside business strategy.

Not inside Marketing alone.

Consider the customer's path to purchase

Where do customers actually come from?

For some businesses:

Google.

For others:

Tender portals.

Trade associations.

Referrals.

LinkedIn.

Architects.

Dealers.

Distributors.

Physical location.

Repeat business.

Why spend on TikTok because everybody talks about TikTok if your actual buyer selects suppliers through an approved procurement framework?

Know your customer.

Business.gov.uk's guidance on both branding and digital strategy repeatedly starts with understanding who the customer is, where they are and how they engage before choosing channels or committing budget.

Channel follows customer.

Not fashion.

Existing customers deserve budget too

Marketing is not only acquisition.

Suppose:

Acquiring a customer costs £1,500.

Keeping a good customer engaged costs far less.

Perhaps marketing investment belongs in:

Email.

Customer education.

Account content.

Events.

Loyalty.

Cross-selling.

Case studies.

Useful communications.

Do not pour everything into the front door while existing customers quietly leave through the back.

Referrals are not free marketing

They can be extraordinarily cost-effective.

But strong referral systems may require:

Excellent delivery.

Relationships.

Customer communication.

Case studies.

Networking.

Partnership development.

Time.

Perhaps none appears under:

Advertising spend.

That does not make it free.

Understand the wider system generating referrals.

Then invest appropriately.

SEO is not free either

Another favourite.

“Organic traffic is free.”

No.

Good SEO may require:

Research.

Content.

Technical work.

Website development.

Digital PR.

Expertise.

Time.

The click may not have a media charge.

The capability producing the click does.

Count it properly when comparing channels.

Social media is not free because posting costs £0

If someone spends:

Ten hours a week

creating content:

That is:

520 hours a year.

There is a cost.

Perhaps the return is fantastic.

Fine.

Measure it.

Do not compare:

£0 social media

with:

£30,000 paid advertising

when one contains six months of employee time that has conveniently disappeared from the calculation.

A practical budget calculation

Imagine an established service business.

Current revenue:

£2.5 million.

Growth target:

£3 million.

Additional required revenue:

£500,000.

Average new customer first-year revenue:

£25,000.

Required additional customers:

Approximately:

20.

Average first-year contribution after direct delivery cost:

£10,000.

Management decides that, given retention, cash, capacity and risk, it is initially comfortable testing an acquisition cost of up to:

£2,000 per customer.

Twenty customers at £2,000:

£40,000 acquisition budget.

But marketing also requires:

Website and SEO:

£15,000.

Content and creative:

£10,000.

Marketing technology:

£5,000.

Now indicative total investment:

£70,000.

That is:

2.8% of current revenue.

Is 2.8% the magic number?

No.

We arrived there because of the objective and economics.

If the business needed much faster growth, the answer might be completely different.

Then test the funnel

Twenty additional customers.

What does that require upstream?

Suppose:

25% of qualified sales opportunities become customers.

You need:

80 qualified opportunities.

Suppose:

40% of marketing-qualified leads become genuine sales opportunities.

You need:

200 suitable leads.

Now ask:

Can the proposed £40,000 acquisition spend realistically produce those 200 leads?

Historical data should tell you.

If it cannot, either:

Budget increases.

Target decreases.

Conversion improves.

Offer changes.

Channel changes.

Or several at once.

Now the marketing budget connects to reality.

Improvement in conversion can be more valuable than more budget

Suppose your current website converts:

1% of relevant visitors.

You could buy twice as much traffic.

Or improve conversion.

Likewise Sales could convert:

10%.

Maybe improving qualification, follow-up and sales execution changes the economics dramatically.

Marketing budgeting should not assume the only lever is:

More money.

Sometimes the most profitable marketing investment is improving what already happens after attention arrives.

Measure cost per profitable customer, not merely lead

This is where Article #77 becomes especially useful.

Imagine:

Channel A generates customers at:

£700 CAC.

Channel B:

£1,300.

Easy.

Channel A wins.

Except Channel A's customers:

Purchase small projects.

Need extensive support.

Churn quickly.

Channel B's customers:

Buy larger work.

Pay properly.

Stay.

Generate referrals.

Which channel deserves more budget?

Customer economics must eventually flow back into marketing allocation.

Ask whether Marketing can explain where the next £10,000 should go

This is an excellent test.

Not:

“What is your budget?”

Ask:

“If I gave you another £10,000 tomorrow, where would you put it, why, and what do you reasonably expect to happen?”

A strong answer might be:

“£6,000 into the paid search campaign currently generating qualified opportunities at £420 each, because we have additional search impression opportunity. £4,000 into new landing pages because conversion is currently the limiting factor.”

Weak answer:

“Probably more social.”

Marketing should understand its own marginal opportunities.

Ask the reverse question too

“If I had to remove £10,000, where would it come from with the least commercial damage?”

That reveals:

Weak channels.

Legacy activity.

Vanity projects.

Things nobody has challenged because:

“We've always done it.”

Budgeting is allocation.

That means both adding and removing.

A small business should probably not market everywhere

The UK digital advertising market alone now contains enormous investment across search, social, video, retail media and countless other formats.

You cannot outspend everybody.

You do not need to.

Pick the channels matching:

Your customer.

Buying journey.

Offer.

Resources.

Strengths.

Then become good enough at them to learn something meaningful.

Three well-run channels usually beat eleven neglected profiles and six half-funded campaigns.

Your marketing budget should have an owner

Who decides?

Owner?

Marketing Director?

Sales and Marketing Director?

Leadership team?

Fine.

But one person needs accountability for:

Budget.

Allocation.

Measurement.

Recommendation.

That does not mean Finance stays out.

Marketing should understand commercial numbers.

Finance should understand that not every marketing effect appears instantly.

The business needs both perspectives.

Review the budget monthly, not only annually

Ask:

What did we spend?

Where?

What evidence appeared?

What changed?

Which channels are improving?

Which are deteriorating?

How much qualified pipeline was created?

What should we reallocate?

Article #74 provides the deeper measurement framework.

This should become normal management.

Not an annual argument when somebody asks Marketing to justify £120,000 retrospectively.

Use a rolling forecast

Marketing is dynamic.

Perhaps:

£100,000 annual budget.

You do not need to commit the entire £100,000 on 1 January.

Forecast by month or quarter.

Update based on:

Performance.

Seasonality.

Cash.

Capacity.

New opportunities.

Business.gov.uk recommends connecting sales and marketing strategies to wider business planning and financial forecasts, rather than treating promotional expenditure as a disconnected activity.

Marketing should live inside the commercial plan.

When should you increase marketing spend?

I become more comfortable increasing the budget when:

You have profitable capacity available.

The growth objective genuinely requires more demand.

Existing acquisition channels have credible economics.

Sales can handle more opportunities.

Delivery can serve more customers.

Cash can support the acquisition cycle.

Measurement is good enough to know what is happening.

The target customer is clearly defined.

In that situation:

More marketing can be fuel.

When should you be cautious?

I slow down when:

Nobody knows which marketing activity creates useful customers.

Sales already has more leads than it can handle.

Customer profitability is unclear.

Margins are weak.

Cash is extremely tight.

Website conversion is terrible.

Existing campaigns have never been properly measured.

The company wants marketing to compensate for a weak offer.

Operations cannot handle additional demand.

The only justification is:

“We need more awareness.”

Fix the obvious leak before pouring more money through it.

Do not expect Marketing to fix a sales problem

Lots of leads.

Few sales.

Owner says:

“Marketing isn't working.”

Maybe.

But perhaps Sales is not converting.

Article #59 on falling sales and Article #60 on insufficient marketing leads help separate those problems.

Measure where the funnel breaks.

Do not keep increasing marketing spend because the bottom of the funnel is broken.

Do not expect Marketing to fix a proposition nobody wants

The offer is:

Poorly positioned.

Too expensive for the value.

Undifferentiated.

Unclear.

Wrong audience.

Marketing can make more people aware of the problem.

That is not necessarily useful.

Sometimes marketing's most valuable work is:

Customer research.

Positioning.

Offer design.

Messaging.

Not promotion.

Do not confuse a marketing agency's recommendation with a business budget

Agency says:

“We recommend £5,000 monthly ad spend.”

Why?

What happens at:

£3,000?

£5,000?

£10,000?

How does that connect to:

Search volume?

Audience size?

Historic conversion?

Target CAC?

Sales capacity?

A good agency should be able to explain.

If the recommendation is simply the amount they usually manage for companies your size, keep asking.

An agency fee and media budget are different

Suppose:

Agency:

£2,500 monthly.

Media:

£3,000.

Total external monthly cash:

£5,500.

Do not tell yourself you spend:

£3,000 on marketing.

You spend £5,500 on that activity.

Likewise include:

Creative.

Landing pages.

Software.

when they are materially part of producing the outcome.

Full economics prevent self-deception.

Marketing needs a return threshold

This does not need to be identical across everything.

Paid acquisition might require:

Clear commercial payback.

Brand investment might have a longer horizon.

SEO may build a compounding asset.

Experimentation may have a high failure rate.

But leadership should know:

What would make this investment worthwhile?

Do not approve money without knowing what success looks like.

British Business Bank's decision-making guidance recommends calculating expected ROI before major investments and aligning expenditure with defined growth, productivity or risk objectives.

Marketing is an investment.

Treat it accordingly.

A practical 90-day marketing-budget reset

If your current budget basically exists because:

“That's what we spent last year”

I would reset it.

First, define the growth requirement

What revenue, pipeline, customer or retention outcome needs supporting over the next 12 months?

Second, understand customer economics

Average revenue.

Gross profit or contribution.

Retention.

Payment behaviour.

Capacity consumed.

What is a genuinely valuable customer worth?

Third, audit the last twelve months of marketing

For each significant activity:

What did it cost?

What did it produce?

What can reasonably be connected to it?

What did we learn?

Fourth, identify the bottleneck

Do you need:

More demand?

Better conversion?

Better targeting?

More sales capacity?

Better delivery capacity?

Do not automatically choose more traffic.

Fifth, protect proven activity

Where the economics are good and capacity exists, fund it.

Sixth, remove obvious waste

Subscriptions nobody uses.

Channels nobody measures.

Events attended through habit.

Activity producing the wrong customers.

Seventh, establish a test budget

Choose one or two new opportunities worth learning about.

Define success and stopping points.

Eighth, connect the budget to cash flow

When does money leave?

When does commercial return realistically arrive?

Ninth, review monthly

Reallocate based on evidence.

Not emotion.

Now you have a marketing investment system rather than a fixed annual guess.

If you desperately want a percentage, calculate your own

After all of that:

Total marketing investment:

£120,000.

Annual revenue:

£3 million.

Marketing investment:

4% of revenue.

Useful.

Next year you might spend:

£180,000

because:

A proven channel scales.

Or:

£90,000

because:

You reach capacity and shift focus towards margin.

The percentage changes because the business changes.

That is exactly how it should work.

The right marketing budget can be surprisingly small

If:

Customer demand is strong.

Referrals are reliable.

High-value target market is narrow.

Retention excellent.

Growth ambitions modest.

Then perhaps you need less than conventional wisdom suggests.

Do not increase spending because someone tells you:

“Serious businesses invest 10% in marketing.”

Serious businesses invest according to economics.

The right budget can also be considerably larger than you expect

Perhaps:

You have strong margins.

High customer lifetime value.

Huge capacity.

Proven acquisition channels.

Ambitious growth target.

Why artificially restrict marketing to 3% of revenue?

If every additional £1,000 reliably creates substantially more contribution and the system can handle the customers, the rational budget may be much higher.

That is the other reason percentage caps are dangerous.

They can cause underinvestment too.

The answer is not “spend as little as possible”

Marketing is not a necessary evil.

The objective is not:

Cheapest leads.

Lowest budget.

It is:

Best commercial return from finite resources.

Sometimes spending £100,000 badly is wasteful.

Sometimes spending only £10,000 when a proven opportunity exists is equally poor management.

The number means nothing without the economics.

So how much should your small business spend on marketing?

Enough to support the growth or retention objective you have deliberately chosen.

Enough to properly fund the channels capable of reaching the customers you actually want.

Enough to test new opportunities fairly.

But not more than:

Your customer economics justify.

Your cash can fund.

Your Sales team can convert.

Your Operations team can deliver.

And your evidence suggests is worth deploying.

Start with the outcome.

Work backwards through:

Customer value.

Conversion.

Required opportunities.

Acquisition cost.

Channel capacity.

Cash.

Then build the budget.

Afterwards, by all means divide it by revenue and admire the percentage.

Just don't mistake the percentage for the thinking that created it.

Why Have Standards Started Slipping as My Business Has Grown?

Tue, 06 Oct 2026 10:40:12 GMT

Standards often start slipping as a business grows because the informal mechanisms that used to maintain those standards stop scaling .

When the company was small:

You saw everything.

You knew every employee.

New starters worked beside experienced people.

Mistakes reached you quickly.

Customers spoke directly to you.

You knew what “good” looked like.

If something wasn't right, you corrected it.

Then the business grew.

More customers.

More employees.

More managers.

More locations perhaps.

More projects.

More handovers.

More distance between the owner and the actual work.

Suddenly you hear yourself saying:

“We never used to let work go out like this.”

Probably true.

But the important question is not:

“Why don't people care like we used to?”

It is:

“What maintained the standard when we were smaller, and what has replaced it now that I can't personally see everything?”

Very often, the uncomfortable answer is:

Nothing.

Growth does not necessarily lower standards

It exposes standards that were never really institutionalised.

This is an important distinction.

Perhaps your business always had incredibly high standards.

But where did those standards live?

In:

Your head?

Your eye for detail?

Your relationships?

Your direct supervision?

A few long-serving employees?

That can work brilliantly with eight people.

Everyone knows:

“Adam would never let that leave the building.”

So they learn.

Not necessarily from an employee handbook.

From proximity.

They see what gets corrected.

They hear customer conversations.

They watch how experienced people work.

They absorb thousands of tiny judgements.

Then the company hires another 20 people.

Those new employees do not have five years of accumulated exposure to the founder.

They need another mechanism.

If one does not exist, standards drift.

“Everyone used to know” is not a scalable management system

This phrase appears constantly in growing businesses.

“Everyone used to know what was expected.”

Of course they did.

There were twelve of you.

You sat in the same building.

The owner spoke directly to everyone.

The original team helped create the routines.

Information travelled through conversation.

Growth changes that.

Thirty people cannot all participate in every decision.

Sixty people do not all hear the same conversation.

Multiple teams develop.

Managers interpret expectations differently.

New employees learn from whoever happens to be standing nearest.

The organisation acquires distance.

Not merely physical distance.

Interpretive distance.

What the owner means by:

“Customer service must be excellent”

gets interpreted by:

Director.

Then manager.

Then supervisor.

Then employee.

Without clearer standards, every layer adds variation.

Bigger businesses need more structured management

This is one reason more structured management practices tend to appear as organisations grow.

The latest published ONS Management and Expectations Survey found average management-practice scores rising with employment size. Firms with 10–19 employees averaged 0.51 on its 0-to-1 management-practice scale, compared with 0.58 for firms with 20–49 employees, 0.63 for 50–99, 0.65 for 100–249 and 0.68 for firms with more than 250 employees. The ONS measures practices including continuous improvement, KPIs, targets, training, promotion and management of underperformance. These are associations rather than proof that simply adding management processes makes businesses better.

The pattern still makes intuitive sense.

As direct owner visibility disappears, something has to replace it.

More deliberate:

Management.

Measurement.

Feedback.

Training.

Accountability.

Process.

That does not mean turning your company into a bureaucracy.

It means recognising that:

“People know how we do things”

has an expiry date.

The first problem: “good” was never properly defined

Ask five people:

“What does good customer service mean here?”

You might receive five answers.

Reply quickly.

Solve the problem.

Be friendly.

Never say no.

Keep customers updated.

Which is correct?

Perhaps several.

But what happens when those principles conflict?

Customer wants something impossible by Friday.

Does good service mean:

Say yes and somehow make it happen?

Or:

Tell them clearly what is achievable and protect delivery standards?

That requires judgement.

Standards need enough definition that people can make reasonably consistent decisions.

A standard needs to be observable

“High quality”

is not particularly useful.

What would I observe?

Maybe:

Customer scope confirmed before work begins.

Final output independently checked against specification.

No unresolved defects at handover.

Customer updated within four hours if delivery date becomes at risk.

Now we can manage something.

Likewise:

“Professional behaviour.”

What does that mean?

Maybe:

Respond to customers respectfully.

Own mistakes.

Do not blame colleagues in front of customers.

Arrive prepared.

Escalate serious problems early.

Again:

Observable.

A standard does not need seventeen paragraphs.

It does need to mean approximately the same thing to different people.

The second problem: new people learn from increasingly inconsistent examples

Your first five employees learned directly from you.

Employees 6–10 learned from those five.

Employees 25–40 may be learning from someone who learned from somebody who learned from you.

That can become a very long game of operational Chinese whispers.

Small deviations spread.

One manager thinks:

“That's close enough.”

Their team learns that version.

Another manager is meticulous.

Their team learns something different.

Soon customers receive different versions of the company depending on:

Branch.

Team.

Shift.

Manager.

Person.

The business has begun developing micro-standards.

Growth amplifies whatever you teach

Good or bad.

Imagine an experienced employee takes a shortcut.

At eight employees, one person takes the shortcut.

At eighty, that person trains another five.

Those five train another twenty.

The workaround becomes:

“How we do it here.”

This is why growth makes consistency more important.

You are no longer managing individual behaviour.

You are managing replication .

Whatever gets copied spreads.

The third problem: onboarding became shorter because recruitment accelerated

You hired occasionally.

New starter spent:

Two weeks shadowing.

Time with owner.

Time with experienced employee.

Plenty of questions.

Then growth arrives.

You recruit:

Five people.

Then eight.

Experienced employees are already busy.

So induction becomes:

Here is your login.

Here is the handbook.

Sit with Dave for the morning.

Off you go.

Two months later:

“The new starters aren't as good as the old team.”

Really?

How much of the difference did the organisation create?

The new employee cannot absorb standards they have never been shown.

Onboarding should teach judgement, not only administration

Induction often covers:

Holiday requests.

Timesheets.

IT.

Policies.

Health and safety.

Useful.

But where does the new employee learn:

What excellent work looks like?

What unacceptable work looks like?

What customers value?

Which mistakes matter most?

When should they stop and ask?

What can they decide independently?

What would make a manager reject the work?

That is the knowledge that protects standards.

Show examples.

Real ones where possible.

This is excellent.

This technically passed, but we would not accept it.

This is why.

People calibrate faster when they can see the difference.

The fourth problem: your best people became managers without becoming managers

Business grows.

You need supervisors.

So you promote:

Best engineer.

Best salesperson.

Best carpenter.

Best administrator.

Best project manager.

Reasonable.

Then they keep doing most of their old job and somehow acquire eight employees as a side project.

Now you expect them to:

Set standards.

Coach.

Review work.

Give feedback.

Manage underperformance.

Develop employees.

Communicate.

Plan capacity.

Deal with problems.

When?

CIPD's 2025 Good Work Index found that employees with more positive perceptions of their line managers were more likely to feel effective in their roles and less likely to report negative health effects or consider leaving. The same research found more managers reporting they had the time, training and knowledge to manage people well, reinforcing the importance of actually investing in management capability rather than simply handing someone a title.

Manager is a job.

Not a reward for technical competence.

Standards increasingly travel through managers

This is the transition owners often miss.

At ten employees, you may directly influence almost everybody.

At fifty, your standards increasingly reach employees through managers.

So your question changes from:

“Do my employees understand the standards?”

to:

“Can my managers consistently teach, model, inspect and reinforce the standards?”

That is a completely different capability.

If Manager A accepts mediocre work and Manager B rejects it, the company does not have one standard.

It has two.

Managers need calibrating too

Put three managers in a room.

Show them examples of completed work.

Ask:

Would you accept this?

Would you send it to the customer?

What would you correct?

When would you escalate?

You may discover surprising differences.

This is extremely useful.

The objective is not to eliminate all judgement.

Different situations require judgement.

You want managers aligned on the important boundaries.

Good enough.

Not good enough.

Needs escalation.

Absolutely unacceptable.

That calibration becomes increasingly important as the business grows.

The fifth problem: volume started winning against quality

This is brutally common.

You tell employees:

Quality comes first.

Then measure:

Jobs completed.

Calls handled.

Sales volume.

Projects closed.

Utilisation.

Revenue.

Speed.

What did you actually prioritise?

Suppose a project manager knows:

Taking another hour to properly review the job protects quality.

But it hurts utilisation and makes the schedule red.

Which signal wins?

Employees notice what management really rewards.

If every meeting focuses on:

Volume.

Speed.

Output.

and quality appears only when a customer complains, you have taught the company something.

Standards collapse when the economics make them impossible

Imagine the standard requires:

Four hours.

Management allows:

Two and a half.

You can put the standard in the handbook as many times as you like.

The operating model contradicts it.

HSE's Management Standards are aimed specifically at work-related stress rather than commercial quality, but their principle around demands is relevant: organisations should provide demands that are achievable within agreed working arrangements and match people's skills and capabilities to the job.

If employees must choose between:

The quality standard.

And:

The workload expectation.

do not act surprised when something gives.

The sixth problem: customer promises keep creating exceptions

Growth brings bigger sales targets.

Sales gets ambitious.

An important customer asks:

“Can you do this differently for us?”

Yes.

Another wants:

Faster turnaround.

Yes.

Another wants:

Different reporting.

Yes.

Then Operations receives 47 versions of:

“Standard service.”

Consistency collapses because the commercial model keeps creating exceptions.

This is closely connected to Article #84.

If ordinary work continually gets overridden by urgent or bespoke requirements, employees cannot maintain a consistent operating standard.

Sometimes bespoke work is commercially sensible.

Price it.

Plan it.

Resource it.

Do not call something standard while designing an exception every Tuesday.

The seventh problem: people stopped receiving fast feedback

When the business was smaller:

You saw a mistake.

Corrected it.

Feedback loop:

Minutes.

Now:

Employee completes work.

Supervisor is busy.

Nobody checks.

Customer receives it.

Problem appears three weeks later.

Perhaps nobody even feeds the complaint back to the employee.

Feedback loop:

Weeks.

Standards drift when the distance between:

Action.

And:

Consequence.

gets too long.

Acas's current performance-management guidance recommends combining formal reviews with regular informal performance conversations, feedback, coaching and check-ins rather than relying on an annual appraisal to address performance.

That matters because employees need to know:

What was good?

What needs improving?

Soon enough to change the next piece of work.

Annual appraisals cannot carry your quality system

Imagine someone produces slightly below-standard work for ten months.

December:

“A few areas for improvement...”

Bit late.

Standards are built through:

Daily observation.

Quick correction.

Coaching.

Regular check-ins.

Examples.

Peer feedback.

Formal performance processes when necessary.

Do not save everything for the annual ritual.

The eighth problem: small errors became statistically more visible

This deserves nuance.

Sometimes owners believe quality has collapsed when the percentage has barely changed.

Suppose at small scale you completed:

100 jobs.

Two had problems.

2%.

Now:

1,000 jobs.

Twenty have problems.

Still:

2%.

But you now hear about twenty failures rather than two.

It feels dramatically worse.

Maybe standards have not declined.

Volume increased.

Before launching a cultural crusade, measure.

Look at:

Defect rate.

Complaint rate.

Rework percentage.

Credits.

Returns.

Missed deadlines.

Customer retention.

Not just absolute incident count.

Growth creates more opportunities for failure.

You need to distinguish:

More failures.

from:

A higher failure rate.

But unchanged percentages may still be unacceptable

Even if the rate remains:

2%.

At ten times the volume, those twenty failures may create:

Far more reputation risk.

Management time.

Rework.

Cost.

Customer impact.

So scale can still justify improving the system.

Just diagnose accurately.

The ninth problem: the owner still tries to be final quality control

This works for a while.

Business grows.

Owner keeps checking:

Quotes.

Projects.

Products.

Emails.

Customer issues.

Eventually you become the bottleneck.

So one of two things happens.

Either:

Everything waits for you.

Or:

Things bypass you because there is too much.

Now standards become inconsistent.

The objective is not to get better at personally inspecting 1,000 things.

It is to create a system where quality survives without your eyes on every output .

That is a huge leadership transition.

Stop being the standard

Build one.

This is the heart of the problem.

If employees say:

“Adam likes it done this way.”

you still have a founder-dependent standard.

Better:

“This is the accepted company standard, and here's why.”

Now the organisation can teach it.

Inspect it.

Improve it.

Defend it.

The founder's judgement may have created the standard.

It should not need the founder's physical presence forever.

The tenth problem: consequences became inconsistent

Employee produces weak work.

Manager A corrects it.

Manager B ignores it.

Senior employee gets away with it because:

“They're difficult to replace.”

New employee gets hammered for the same thing.

What is the standard now?

People watch what happens.

Article #81 covered this from the wider culture perspective.

Standards require consistency.

Not identical treatment in every circumstance.

But broadly predictable expectations.

Acas performance guidance recommends making expectations clear and assessing employees against agreed objectives and behaviours, with appropriate support and regular feedback where improvement is needed.

If poor standards carry no consequence, they eventually become normal.

The eleventh problem: long-serving employees are not automatically guardians of the old standard

This can be awkward.

Owners sometimes divide the workforce into:

Original people who get it.

And:

New people who don't.

Sometimes true.

Sometimes not.

A long-serving employee may have accumulated:

Shortcuts.

Cynicism.

Outdated methods.

Territory.

They may actively teach new employees:

“Ignore that. Nobody actually does it.”

Do not judge quality by tenure.

Judge quality by quality.

Your strongest cultural carrier might have joined eighteen months ago.

Your biggest source of drift might have been there fifteen years.

The twelfth problem: nobody owns quality anymore

When the business was small:

You did.

Now?

Operations says:

Managers.

Managers say:

Employees.

Employees say:

Quality team.

Quality team says:

Operations.

Customer says:

“Can somebody please just fix it?”

Quality should be everyone's concern.

But that does not mean accountability should be vague.

Who owns:

The standard?

Training?

Measurement?

Recurring failure?

Improvement?

The quality function, if you have one, may support the system.

Managers still need to own the standard inside their teams.

Do not create a Quality Department so everyone else can stop caring

This is a trap.

Quality Inspector catches problems at the end.

Employees begin to think:

“They'll check it.”

Now quality is outsourced internally.

Inspection has value.

Especially in:

Safety-critical.

Regulated.

Technically sensitive.

High-value work.

But the best place to protect quality is as close as possible to where the work is created.

Employees should understand what good looks like and be capable of checking their own work.

Managers should maintain standards.

Inspection becomes verification.

Not rescue.

Current quality-management thinking still centres on leadership and continual improvement

The newly published ISO 9001:2026 places renewed emphasis on leadership, quality culture, strategic alignment, people and continual improvement while retaining the long-standing process and customer-focus principles of the ISO 9000 family. A company does not need ISO certification for those underlying principles to be useful.

The interesting point is that mature quality systems do not rely on:

“Tell everyone to try harder.”

They rely on:

Clear expectations.

Process.

Leadership.

People capability.

Measurement.

Learning.

That is exactly what a growing business needs.

The thirteenth problem: issues get fixed but not learned from

Customer complains.

Manager sorts it.

Refund issued.

Customer happy.

Close.

Same thing happens next month.

This is service recovery.

Not organisational learning.

Standards improve when failure feeds back into:

Training.

Process.

Product.

Equipment.

Management.

Workload.

The latest ONS Management and Expectations Survey includes continuous improvement as a core part of structured management practice, explicitly distinguishing firms that repeatedly review processes to minimise future problems from those that simply react to issues as they arise.

Fix the customer.

Then fix the reason the customer needed fixing.

The fourteenth problem: growth changes the job before the role catches up

Your employee used to:

Manage eight customers.

Now:

Twenty-five.

Same job title.

Same process.

Same quality expectation.

Very different job.

Or:

Supervisor used to manage four people.

Now:

Fourteen.

You are surprised they spend less time coaching.

The role changed.

HSE guidance on role design emphasises that employees should understand their responsibilities and that organisations should avoid incompatible or conflicting demands where possible.

When businesses grow quickly, role design often lags behind reality.

Standards then suffer because nobody consciously redesigned the work.

The fifteenth problem: management capacity did not grow at the same rate as headcount

This is one of the biggest.

Twenty employees.

Three managers.

Then:

Forty-five employees.

Still three managers.

Management workload more than doubled.

But leadership assumes:

“They already know how to manage.”

Now:

One-to-ones disappear.

Training gets rushed.

Quality checks get skipped.

Problems arrive late.

Underperformance lingers.

Managers become firefighters.

CIPD's evidence on line management is particularly relevant here because capability is not enough on its own. Managers also report needing time and organisational support to manage people effectively.

Ask:

How much real management capacity does the next stage require?

Not:

How thinly can we stretch the current managers before somebody breaks?

The sixteenth problem: the organisation outgrew informal communication

Someone changes a standard.

At twelve people:

Mention it Monday morning.

Done.

At sixty:

Did Sales hear?

Night shift?

Remote employees?

New location?

Subcontractors?

Employees on leave?

Communication needs designing.

Not overengineering.

Perhaps:

Manager briefing.

Updated process.

Short training clip.

Team discussion.

Worked example.

The exact method does not matter.

The standard needs to reach everybody who relies on it.

HSE's guidance on organisational change emphasises timely information, employee understanding of likely impact and appropriate training where roles or ways of working change.

A change nobody understood is not an implemented change.

The seventeenth problem: your standards have become contradictory

Leadership says:

Spend time with customers.

Also:

Reduce non-billable time.

Leadership says:

Check everything thoroughly.

Also:

Increase output 25%.

Leadership says:

Take ownership.

Also:

Ask before making decisions.

Leadership says:

Protect quality.

Also:

Never miss a sales promise.

Employees are forced to choose which standard actually wins.

Then managers complain they chose incorrectly.

Review conflicting expectations.

Standards need hierarchy.

When quality, speed and cost conflict, what matters most?

There may be different answers depending on the situation.

Make those trade-offs understood.

Growth requires standards to become more explicit, not more bureaucratic

This distinction matters.

I am not suggesting you respond to growth by writing:

Quality Manual Volume 1–19.

The aim is clarity.

The critical standards might fit on one page.

For each important area:

What outcome is required?

What are the non-negotiables?

What can employees decide?

What requires escalation?

How do we check it?

What happens when it is missed?

Simple.

The process underneath may contain more detail where genuinely required.

Do not mistake document weight for management quality.

Identify the standards that really matter

Not everything deserves equal control.

Choose standards linked to:

Customer outcome.

Safety.

Legal or regulatory obligation.

Margin.

Reputation.

Critical delivery performance.

Perhaps:

Quotation accuracy.

Installation quality.

Response time.

Project handover.

Invoice accuracy.

Technical compliance.

Focus there first.

If management treats:

Wrong font on internal form

and:

Serious customer defect

with equal intensity, employees stop understanding what matters.

Build a Standards Ladder

I would start with four levels.

Non-negotiable

Safety, legal, regulatory, ethical or absolutely critical customer requirements.

No discretion below the defined threshold.

Core company standard

The normal level customers should consistently receive.

Preferred practice

The best normal way of working, with reasonable judgement allowed.

Individual style

Employees can choose.

This avoids trying to standardise every human movement while giving genuine standards the weight they deserve.

Define the acceptance test

For every critical standard ask:

How would a competent manager know whether this passed?

If the answer is:

“They'd just know”

keep going.

Could you define:

Tolerance?

Checklist?

Example?

Customer requirement?

Sign-off?

Measurement?

Photograph?

Test?

Peer review?

A standard becomes scalable when different competent people can reach reasonably similar conclusions.

Use real examples

Especially for subjective work.

Show:

Excellent.

Acceptable.

Not acceptable.

Why?

This is brilliant for:

Design.

Writing.

Customer emails.

Joinery.

Finishes.

Reporting.

Proposals.

Photography.

Technical reports.

People learn far faster from examples than vague exhortations to:

“Maintain quality.”

Train managers to inspect without micromanaging

The answer is not standing over everybody.

Managers need to know:

What needs checking every time?

What can be sampled?

What can employees self-check?

Where is the consequence of failure high enough to require independent verification?

Sampling can be powerful.

Maybe a manager checks:

10% of routine jobs.

100% of high-risk jobs.

New starters more frequently.

Experienced employees less.

Use risk.

Do not make every task pass through another person's hands unnecessarily.

Track the right evidence

Depending on your business:

Rework.

Defects.

Customer complaints.

Credits.

Returns.

First-time pass rate.

Late delivery.

Warranty.

Repeat visits.

Project margin affected by failure.

Again:

Do not build a dashboard with 47 quality measures.

Pick what tells you whether the standard is holding.

Segment the data

Overall defect rate:

3%.

Okay.

What if:

Team A: 1%.

Team B: 7%.

Now we learned something.

Break down where useful by:

Manager.

Branch.

Product.

Service.

New versus established employees.

Customer type.

You may discover company-wide standards are fine.

One part of the organisation is not.

That changes the intervention completely.

Do not automatically blame the manager

If one team performs badly:

Investigate.

Perhaps the manager needs development.

Or:

That team handles the hardest customers.

Has lowest staffing.

Uses old equipment.

Receives worst inputs.

Has impossible targets.

Numbers identify where to look.

They do not always tell you why.

Make customer feedback operational

Do not simply report:

NPS.

Five-star reviews.

Complaints.

Ask:

What specifically are customers telling us about standards?

Are they saying:

Communication deteriorated?

Finish inconsistent?

Deadlines less reliable?

People less knowledgeable?

Response slower?

Then connect customer feedback to the process capable of changing it.

Quality data that never changes behaviour is decoration.

Reset consequences

This is delicate but necessary.

If an employee repeatedly ignores an established reasonable standard despite:

Clear expectations.

Training.

Support.

Feedback.

then eventually you have a performance issue.

Deal with it fairly.

Acas recommends regular performance conversations, clear agreed objectives and support for improvement, with records where appropriate.

Do not allow an endless gap between:

What the company says is required.

And:

What employees learn is actually tolerated.

That gap is the culture.

The owner needs to stop creating exceptions too

If the owner repeatedly says:

“I know that's the standard, but just this once...”

employees notice.

Sometimes exceptions are commercially justified.

Fine.

Call it an exception.

Understand the cost.

Do not pretend the standard remains intact while leadership repeatedly teaches everyone to bypass it.

The owner also needs to stop personally rescuing every standard failure

You see something wrong.

Fix it yourself.

Faster.

Customer protected.

But what did the manager learn?

Perhaps:

Adam will catch it.

Instead:

Correct the immediate risk if necessary.

Then take the issue through the responsible manager.

They need to own:

Correction.

Feedback.

Prevention.

Otherwise the owner remains the invisible Quality Department.

Growth should make quality more organisational, not more founder-dependent

The UK government's August 2026 analysis of high-growth firms found that firms experiencing high growth had persistently higher average management scores than non-high-growth firms, including before entering high-growth periods. The researchers are careful not to claim that a sudden improvement in management automatically causes growth, but the pattern supports the wider point that organisational capability matters in businesses operating at greater scale.

You cannot personally scale your standards indefinitely.

The organisation has to carry them.

I learned this while growing a company myself

When you grow from roughly £1.5 million towards £8.5 million turnover, one thing becomes painfully obvious:

What worked because a handful of experienced people knew how everything should happen stops being enough.

At smaller scale, you can compensate for weakness personally.

You notice something.

Speak to somebody.

Fix it.

At larger scale, you can no longer be present at every point where quality gets created.

That means management, process and accountability have to mature before your personal oversight becomes impossible .

Otherwise growth creates a strange feeling.

The company becomes objectively more successful.

While the owner increasingly thinks:

“We're not as good as we used to be.”

Sometimes they are right.

The answer is not going backwards.

It is building the management infrastructure the larger company now requires.

A 90-Day Standards Reset

If you believe standards are genuinely slipping, I would not start with a company-wide speech about:

“Getting back to basics.”

Do this instead.

Weeks 1–2: Prove where standards are slipping

Look at:

Customer complaints.

Rework.

Returns.

Credits.

Late jobs.

Defects.

Margins.

Manager feedback.

Employee feedback.

Do not rely entirely on owner frustration.

Identify the specific areas.

Week 3: Select the critical standards

Choose perhaps three.

For example:

Job handover quality.

Customer communication.

Finished-work acceptance.

Not twenty-three.

Week 4: Define them properly

For each:

What exactly is required?

What does good look like?

What does failure look like?

Who owns it?

What can employees decide?

What requires escalation?

How is it checked?

Weeks 5–6: Calibrate managers

Put managers through real examples.

Would you accept this?

Why?

What feedback would you give?

When would you intervene?

Make sure the management layer understands the same standard.

Weeks 6–8: Retrain and re-onboard

Existing employees where required.

New-starter induction.

Examples.

Short practical training.

Do not simply email the revised procedure.

Weeks 8–10: Fix structural conflicts

Does workload make the standard impossible?

Do incentives reward speed over quality?

Does Sales create exceptions?

Does equipment cause defects?

Does one manager have eighteen direct reports?

Fix the conditions.

Weeks 10–12: Measure

Has:

Rework fallen?

Complaints reduced?

First-time pass improved?

Manager intervention changed?

Do not settle for:

“Feels better.”

Week 13: Review and tighten

What worked?

What remains inconsistent?

Where did people misunderstand?

What should now become normal management?

Then move to the next important standard.

Do not launch a “quality initiative”

Please.

Banner.

Logo.

Internal campaign.

PROJECT EXCELLENCE 2027.

No.

Just manage the bloody business better.

Quality should become part of:

Onboarding.

One-to-ones.

Team meetings.

Process review.

Manager coaching.

Performance.

Customer feedback.

Normal work.

The objective is not creating excitement about standards for six weeks.

It is creating boring consistency for six years.

Good standards should make work easier

Employees generally do not want to produce rubbish work.

Poor systems frequently make good work unnecessarily difficult.

If maintaining the standard requires:

Extra unpaid hours.

Constant owner approval.

Three duplicate systems.

Workarounds.

Guesswork.

then investigate the environment too.

ISO's current quality-management principles emphasise the interaction between leadership, people, processes, evidence and continual improvement rather than treating quality as an inspection activity sitting at the end of production.

That is the better model.

Create conditions where doing it right is the normal path.

The standard should survive your absence

This is the final test.

You leave for two weeks.

Would:

Customers receive the same experience?

Managers reject the same poor work?

Employees understand what matters?

Problems be corrected?

New starters learn the same expectations?

If standards only hold when the owner is physically present, the business has not scaled its standards.

It has scaled around an inspector.

Growth inevitably creates distance between you and the work.

Your job is not to eliminate that distance.

It is to make sure quality does not depend on closing it personally every day.

Define what good looks like.

Build managers capable of maintaining it.

Give people enough capacity and training to achieve it.

Measure what matters.

Correct deviations early.

Learn from recurring failures.

Apply consequences fairly.

And stop relying on everybody somehow knowing what the founder would have done.

Because as the company grows, standards can no longer live in the owner's head.

They have to live in the business.

How Do I Build a 13-Week Cash Flow Forecast?

Tue, 06 Oct 2026 10:26:40 GMT

A 13-week cash flow forecast is a week-by-week view of the cash you genuinely expect to enter and leave your business over the next three months .

You start with the money actually available today.

Then, for each of the next 13 weeks, you forecast:

Cash coming in
Cash going out
Net movement
Closing cash balance

The basic calculation is:

Opening cash + cash received - cash paid = closing cash.

Then the following week's opening balance is the previous week's closing balance.

That is essentially it.

The value is not in making the spreadsheet complicated.

The value is being able to see:

“In week seven, we're likely to run £80,000 short unless something changes.”

while you still have six weeks to do something about it.

British Business Bank describes cash flow forecasting in very similar terms: predicting cash entering and leaving over a defined period, recording receipts when they actually reach the business rather than when invoices are raised, and maintaining a running balance so future shortages become visible before they arrive.

That is the entire point.

Not accounting elegance.

Warning.

Why 13 weeks?

Thirteen weeks is roughly one quarter.

That is usually far enough ahead to capture several important cash events:

Payroll.

Supplier payments.

Rent.

Tax.

Loan repayments.

Quarterly costs.

Slow-paying customers.

Stock purchases.

Large projects.

But it is still close enough that much of the forecast can be built using:

Actual invoices.

Known commitments.

Existing orders.

Real payment dates.

Reasonable short-term assumptions.

A twelve-month cash forecast is useful for longer-range planning.

A 13-week forecast does a different job.

It gives you short-term liquidity visibility at weekly resolution .

ICAEW specifically recommends a forward-looking 13-week forecast based on known receipts and payments when businesses need tighter liquidity management, including identifying the lowest point of available headroom during the period.

Monthly forecasting can hide a problem.

You might start November with:

£150,000.

End November with:

£140,000.

Looks fairly uneventful.

Except halfway through November:

Payroll leaves.

VAT leaves.

A large supplier payment leaves.

The major customer payment expected that week arrives ten days late.

Your bank balance falls to:

£12,000.

The month-end number never showed the danger.

Weekly forecasting does.

This is not the same as your profit forecast

This distinction matters enormously.

Your profit and loss account might say:

Revenue this month:

£300,000.

Profit:

£40,000.

Lovely.

But perhaps the £300,000 was invoiced on 60-day terms.

Meanwhile this month you need to pay:

Wages.

Materials.

Rent.

VAT.

Vehicles.

Suppliers.

Loan repayments.

You can be profitable and still run out of cash.

British Business Bank explicitly warns that an otherwise profitable company can experience severe cash pressure when it pays the costs of delivering goods or services before customers pay. Growth can intensify the problem because additional sales often require more working capital before the corresponding cash arrives.

That is why the 13-week forecast deals in cash movement .

Not accounting profit.

Do not build it from the P&L

This is a very common mistake.

Take annual budget.

Divide everything by twelve.

Then divide the next three months by weeks.

Congratulations.

You have produced an extremely neat spreadsheet that may bear very little relationship to your bank account.

The 13-week forecast should usually use the direct method .

Actual cash receipts.

Actual cash payments.

ICAEW recommends this approach for short-term cash forecasting because it is easier for non-accountants to understand and makes receipts, payments and resulting cash headroom visible directly. It also recommends documenting the assumptions behind material forecast items.

Think like your bank statement.

When does the money actually move?

Step 1: Start with the real opening cash position

First number:

Cash available today.

Use the actual cleared bank balance.

If you have several company bank accounts, include the relevant balances.

But distinguish between:

Cash actually available.

And:

Other balances you cannot freely use.

For example:

Restricted cash.

Client money.

Funds reserved under specific arrangements.

You may also have:

An overdraft.

Revolving credit facility.

Other available funding.

Useful.

But I would normally show those separately from cash.

Otherwise:

£50,000 cash + £150,000 overdraft facility

becomes:

£200,000 cash

in somebody's head.

It isn't.

You have £50,000.

And potentially £150,000 of borrowing headroom, subject to the terms of the facility.

That distinction becomes important when cash tightens.

Step 2: Create 13 weekly periods

You need:

Week 1.

Week 2.

Through to:

Week 13.

Use actual week-ending dates.

For example:

Week ending 9 October.

Week ending 16 October.

And so on.

This removes ambiguity.

Then your basic structure becomes:

Opening cash.

Cash receipts.

Cash payments.

Net weekly movement.

Closing cash.

Available facility or additional liquidity if relevant.

Remaining headroom.

Keep it simple enough that the owner and management team can understand it.

A cash forecast that requires an accountant to interpret it every Monday has probably become too clever for its primary purpose.

Step 3: Forecast cash receipts

This is where optimism can destroy the forecast.

Do not ask:

“What are we invoicing?”

Ask:

“What money do we realistically expect to hit the bank, and when?”

Start with existing debtors.

Customer by customer where the values are material.

You may already know:

Customer A owes £42,000.

Invoice due Friday.

Historically pays approximately on time.

Week 1 receipt:

£42,000.

Customer B owes £85,000.

Terms say 30 days.

Historically pays on day 55.

Do not put it in the forecast on day 30 simply because that is what the invoice says.

Forecast behaviour.

Not hope.

British Business Bank makes this point explicitly: a cash flow forecast should record sales in the period where you genuinely expect the customer payment to clear, not merely when the invoice was issued.

Separate existing receivables from future sales

This makes the forecast much easier to challenge.

Your first few weeks might rely heavily on:

Invoices already issued.

Later weeks may rely increasingly on:

Orders not yet invoiced.

Expected project milestones.

New sales not yet won.

Separate them.

There is a huge difference between:

£100,000 customer invoices already due

and:

£100,000 of sales we hope to win, deliver, invoice and collect by week 12.

They should not look equally certain.

Use confidence levels where useful

You do not need another enormous modelling system.

But for significant receipts, you might distinguish:

Committed

Invoice exists.

Payment date credible.

Expected

Work or order exists and receipt is reasonably predictable, but payment has not yet become an issued receivable.

Speculative

Depends materially on future sales activity or uncertain events.

I would be cautious about allowing large amounts of speculative future cash to rescue an otherwise ugly forecast.

If week eleven only works because:

“Hopefully we'll win £250k of something by then”

you have learned something.

Do not hide it.

Forecast customer behaviour honestly

If the business has:

£500,000 of receivables

and historically 20% arrive late, do not assume 100% will suddenly pay precisely on the due date because you have opened Excel.

Use:

Actual customer history.

Known conversations.

Disputes.

Payment plans.

Current debtor ageing.

Customer financial problems.

Then keep updating.

The Office of the Small Business Commissioner continues to identify delayed payment as a significant cash-flow problem for smaller businesses, while current UK government guidance also explicitly recommends incorporating realistic payment timing into cash-flow planning.

Include non-sales receipts

Depending on your business:

Loans.

Shareholder funding.

Grants.

Tax refunds.

Asset sales.

Insurance payments.

Other income.

Again:

Only when realistically expected.

Do not include an overdraft extension because:

“The bank should approve it.”

until you understand how credible that assumption actually is.

Step 4: Forecast cash payments

Now list what genuinely leaves the bank.

Start with the obvious.

Payroll

Gross cash leaving for wages or salaries.

Then remember associated payments such as:

PAYE.

National Insurance.

Pension contributions.

Other payroll-related deductions or costs.

For UK employers paying PAYE monthly electronically, HMRC currently requires payment by the 22nd of the following tax month. HMRC also launched a 2026 deadline-checking tool covering PAYE, VAT, CIS and other filing and payment deadlines, which can help ensure the actual dates are reflected in the forecast.

Do not memorise tax dates from an article forever.

Check the actual deadlines applicable to your business.

Suppliers

Use the purchase ledger.

But again:

Do not simply assume every outstanding supplier invoice is paid immediately.

When is it actually due?

What terms have been agreed?

What recurring direct debits exist?

What major purchases are coming?

Be realistic.

And if you want different payment terms, agree them .

Do not quietly turn supplier credit into unauthorised late payment because the spreadsheet looks uncomfortable.

Rent, premises and utilities

Include the actual cash timing.

Monthly?

Quarterly?

Annual?

Business rates?

Service charge?

Insurance?

Large quarterly payments are exactly why a weekly cash forecast is useful.

A month can look perfectly healthy until three significant payments land together.

VAT

Forecast the actual expected VAT payment date and amount.

Do not simply look at the amount of VAT collected from customers and assume that is the final liability.

Your accountant or accounting software should help establish the expected net payment.

Most ordinary VAT returns and payments have deadlines linked to the end of the relevant VAT period, while businesses using annual accounting or payment-on-account arrangements have different schedules. HMRC provides a deadline calculator and online account information for the specific dates applicable to each business.

The wider principle is:

Tax should appear in the cash forecast before the payment date surprises you.

Corporation Tax and other taxes

Same principle.

Get the amount and expected payment date from:

Your accountant.

Finance team.

HMRC information.

Then include it in the appropriate week.

Do not allow tax to become:

“Future Adam's problem.”

Future Adam may already have payroll that week.

Loan and finance payments

Include actual cash payments.

Loan repayments.

Hire purchase.

Leases.

Interest.

Bank fees.

Remember that accounting treatment and cash treatment can differ.

For a short-term cash forecast, you care about:

What leaves the bank?

Capital expenditure

Vehicles.

Equipment.

Machinery.

IT.

Premises fit-out.

Large deposits.

If management is planning it, put it in.

This creates a useful decision.

Perhaps:

Week 8 currently falls to £25,000.

The £90,000 machine purchase is planned in week 7.

Now you can ask:

Does it need buying then?

Could it be financed differently?

Should the purchase move?

The forecast does not make the decision.

It shows you the consequence.

Owner payments

Depending on structure:

Salary.

Drawings.

Dividends.

Director's loan movements.

Other distributions.

Do not leave them outside the forecast because:

“That's personal.”

If company cash leaves the bank, it belongs in the forecast.

Whether a particular payment is appropriate, lawful or tax-efficient is a separate matter for your accountant or adviser.

Refunds, credits and customer repayments

If they are known and material:

Include them.

Cash forecasts become unreliable when they include all expected money coming in while quietly forgetting the awkward things going out.

Annual and irregular costs

This is where a thirteen-week view often reveals useful surprises.

Insurance renewal.

Software annual licences.

Professional subscriptions.

Bonuses.

Maintenance.

Equipment servicing.

Trade shows.

Large marketing commitments.

If week nine contains something unusual, it still counts.

The bank does not care that it is non-recurring.

Step 5: Calculate the weekly closing cash

Now the useful bit.

For each week:

Opening cash + total receipts - total payments = closing cash.

Suppose:

Opening cash:

£180,000.

Receipts:

£95,000.

Payments:

£130,000.

Closing cash:

£145,000.

Next week's opening cash:

£145,000.

Repeat.

By week 13 you have a path.

Not merely an ending.

The lowest point may be far more important than the final point.

Track the lowest cash point

Imagine your 13-week forecast says:

Starting cash:

£300,000.

Week 13 cash:

£280,000.

Looks reassuring.

Except:

Week 6:

£18,000.

That is the number I care about.

Why?

Because payroll may be £120,000.

You may recover afterwards when a customer pays, but the business still needs to survive week six.

ICAEW's guidance on short-term liquidity forecasting specifically emphasises identifying the lowest level of cash headroom within the 13-week period, not merely looking at the ending balance.

That lowest point is your pinch point.

Add a minimum cash threshold

This makes the forecast more useful.

Suppose management agrees it does not want available cash to fall below:

£100,000.

Why?

Perhaps that represents:

Several weeks of essential payroll and overhead.

A reasonable operating cushion.

A board-approved liquidity threshold.

Article #61 explores cash reserves in more depth.

The number should have a reason.

Now your forecast may show:

Week 1: £240k.

Week 2: £210k.

Week 3: £175k.

Week 4: £135k.

Week 5: £92k.

Technically, you still have cash.

But your warning threshold has already been crossed.

That gives you more time.

Forecast available headroom too

If you have a genuine committed overdraft or facility, show it separately.

For example:

Closing cash:

£40,000.

Available committed facility:

£150,000.

Total liquidity headroom:

£190,000.

That is useful.

But remember:

Borrowing is not profit.

And a facility may contain:

Limits.

Covenants.

Conditions.

Expiry dates.

Talk to your finance team, lender or adviser where those become material.

Build a realistic base case first

Do not start with:

Best case.

Worst case.

Astrology case.

Build the most credible version.

What do we genuinely expect?

Then create a downside scenario where useful.

For example:

Large customer pays two weeks later.

New sales are 20% below expectation.

Supplier cost rises.

Major order slips.

What happens?

ICAEW recommends scenario analysis where uncertainty is significant, while its cash-flow guidance stresses that assumptions should be revisited regularly as circumstances change.

Do not create fifteen scenarios.

You need enough sensitivity to understand the risk.

Stress-test the assumptions that matter

Not every line needs analysis.

Concentrate on the big ones.

What if:

Customer X pays late?

Expected £300,000 contract does not start?

Payroll increases because recruitment happens earlier?

VAT is higher than expected?

Large equipment purchase cannot move?

One significant supplier requires faster payment?

Which assumption changes the cash story?

That tells management what to watch.

Weeks 1 to 4 should be much more reliable than weeks 10 to 13

This is normal.

Near-term information is more concrete.

You know:

Current bank balance.

Existing debtors.

Supplier ledger.

Payroll.

Tax.

Committed purchases.

Further out, assumptions increase.

That does not make the later weeks useless.

Their purpose is partly to expose developing risk.

Do not pretend week 13's balance is accurate to the nearest pound.

£147,283.16

looks impressive.

It may be complete fiction.

Perhaps the useful statement is:

“On current assumptions, cash falls towards approximately £150k in weeks 11–13, mainly because of the VAT payment and reduced customer receipts.”

Precision should reflect certainty.

Update it every week

A 13-week forecast should normally roll .

Week 1 happens.

Replace forecast figures with actual cash movements.

Investigate the differences.

Remove the completed week.

Add a new week 13.

You always maintain roughly the next quarter.

British Business Bank explicitly recommends updating cash forecasts regularly as better information becomes available, rather than treating them as fixed predictions.

This is where the model becomes genuinely powerful.

You learn how your business actually behaves.

Compare forecast with actual

Suppose you forecast:

Customer receipts:

£120,000.

Actual:

£75,000.

Why?

Customer paid late?

Wrong assumption?

Invoice never raised?

Sales milestone slipped?

Forecasting error?

Then improve.

Supplier payments forecast:

£80,000.

Actual:

£125,000.

Why?

Emergency purchase?

Missing supplier invoice?

Payment timing wrong?

Unexpected project costs?

A good 13-week forecast becomes more accurate because management keeps comparing expectation with reality.

If the model is consistently wrong and nobody investigates why, you have a spreadsheet.

Not a forecasting process.

Track material variances, not every £17 difference

Do not spend Monday morning investigating:

£13.42 discrepancy in Microsoft subscription.

Look at material items.

Perhaps:

Anything above £5,000.

Or 10% of the weekly line.

Your threshold depends on company size.

The question is:

What difference could materially change our cash decisions?

That deserves investigation.

Give the forecast an owner

Someone must maintain it.

Usually:

Finance Director.

Financial Controller.

Management Accountant.

Finance Manager.

Or an external/fractional finance resource.

But operational managers need to contribute.

Finance cannot magically know:

When Project A will really bill.

Whether Customer B is disputing an invoice.

When recruitment starts.

Whether Operations wants to buy another vehicle.

When Sales thinks the major contract will land.

ICAEW emphasises that effective cash management needs coordination across the business, not simply a finance spreadsheet maintained in isolation.

Finance owns the model.

Management owns the assumptions.

The owner still needs to understand it

You do not need to build the spreadsheet personally.

You should be able to read it.

Ask:

Where is the lowest cash point?

What causes it?

Which receipts are uncertain?

What significant payments are coming?

How much headroom do we have?

What changed since last week?

What action is required?

The Insolvency Service's updated director guidance states explicitly that directors are responsible for understanding and monitoring company finances, including cash flow and early signs of financial difficulty, even where they are not financial specialists themselves.

“Finance deals with that”

is not a great operating philosophy for a director.

Connect the 13-week forecast to your sales pipeline

This is where Articles #79 and #85 connect.

Your first few weeks may be driven by existing invoices.

Later weeks increasingly depend on:

Work currently in the order book.

Sales opportunities.

Expected new customers.

If pipeline weakens today, future receipts should eventually move.

Do not allow Sales to keep saying:

“We'll make it up.”

while the cash model continues assuming the original revenue.

Forecasts should change when evidence changes.

That is management.

Connect it to your hiring decisions

You want to recruit:

Two people.

Annual salaries:

£50,000 each.

The P&L model says:

Affordable.

Good.

Now look at cash.

Recruitment fees.

First payroll.

Employer costs.

Equipment.

Training.

Productivity ramp.

When does the additional revenue or capacity actually create cash?

Article #75 explained why management accounts and forecasts should inform hiring decisions.

The 13-week cash forecast makes the timing much clearer.

Connect it to pricing and payment terms

Cash problems are not always cost problems.

Perhaps your commercial model says:

Customer pays 60 days after delivery.

Suppliers require 30 days.

Payroll every month.

Growth therefore consumes cash.

The solution might involve:

Higher deposits.

Stage payments.

Shorter terms.

Faster invoicing.

Different purchasing terms.

Invoice finance.

Other working-capital funding.

Not automatically:

Cut costs.

British Business Bank identifies customer payment timing, supplier terms and inventory levels as fundamental parts of the working-capital cycle and recommends using cash forecasting to understand how much funding that cycle requires.

The forecast helps reveal the structural cause.

Invoice faster

One astonishingly simple cash improvement:

Finish work Friday.

Invoice customer Friday.

Not:

Three weeks later when somebody gets around to it.

A customer cannot pay an invoice they do not have.

If billing is linked to:

Project completion.

Timesheets.

Sign-off.

Purchase orders.

Milestones.

make sure the process gets cash moving as quickly as the contract allows.

Chase debt before the forecast says you need it

Another mistake:

Forecast shows £200,000 due from customers next week.

Nobody talks to them until it becomes overdue.

If the cash is materially important, confirm.

Is the invoice approved?

Any dispute?

Correct PO?

Payment run date?

You are not being difficult.

You are managing cash.

A forecast should drive behaviour before the money fails to appear.

Do not treat supplier stretching as your primary strategy

Forecast gets tight.

Simple.

Stop paying suppliers.

No.

If you need revised terms:

Communicate.

Negotiate.

Agree.

Suppliers also have businesses to run.

And if financial distress reaches the point where the company may be unable to pay debts as they fall due, the situation becomes legally more serious.

The UK Insolvency Service states that a company can be insolvent when it cannot pay its debts when due. Once insolvency arises, directors' responsibilities shift towards protecting creditors, and directors should consider professional insolvency advice rather than simply deciding which creditors they would prefer to pay.

That is the point where this stops being merely a forecasting exercise.

Common mistake 1: Forecasting invoices instead of receipts

Invoice issued week 2.

Customer pays week 8.

Cash receipt belongs in:

Week 8.

Not week 2.

Simple.

Critical.

Common mistake 2: Forgetting VAT and tax

The forecast looks fantastic.

Then:

VAT.

Forecast less fantastic.

Put known liabilities in early.

Current Business.gov.uk guidance specifically recommends incorporating tax obligations and their payment timing into cash-flow planning rather than treating tax as a separate afterthought.

Common mistake 3: Using due dates instead of actual payment behaviour

Customer contract says:

30 days.

They always pay:

Forecast 55 until there is credible evidence otherwise.

Then fix the commercial relationship separately.

Common mistake 4: Including sales twice

Existing invoice.

Plus sales forecast that generated the same invoice.

Double-counted.

Very easy to do when different systems feed the model.

Separate:

Existing receivables.

Future invoicing.

Clearly.

Common mistake 5: Forgetting opening cash reconciliation

The model says:

Opening cash £200,000.

Bank says:

£164,000.

Stop.

Do not continue forecasting from a fictional starting point.

Reconcile it.

Common mistake 6: Ignoring annual costs

Insurance.

Subscriptions.

Maintenance.

Bonus.

Licence renewal.

They count.

The benefit of 13 weeks is seeing lumpy expenditure.

Do not smooth it away.

Common mistake 7: Being wildly optimistic further out

Weeks 10 to 13 depend on:

Three sales not yet won.

One customer who always pays late.

And a hoped-for overdraft extension.

Yet the spreadsheet presents:

£290,000 closing cash.

Use cautious assumptions.

Separate uncertainty.

Common mistake 8: Treating the forecast as Finance's private document

Operations changes a project.

Sales moves a contract.

Owner hires somebody.

Nobody tells Finance.

Forecast remains beautifully wrong.

Cash forecasting is a management process.

Common mistake 9: Building a monster spreadsheet

Forty tabs.

Macros.

Charts.

Colour codes.

Nobody understands it.

Simple wins.

The model should answer:

Where does cash start?

What comes in?

What goes out?

Where does cash finish?

Where is the low point?

Why?

What action follows?

You can add detail when needed.

Common mistake 10: Producing it once

Forecast created.

Board impressed.

Saved as:

13_week_cashflow_FINAL_v6_REALFINAL.xlsx

Never opened again.

Pointless.

The value comes from rolling it every week.

A simple worked example

Imagine the business starts with:

£250,000 cash.

Week 1:

Receipts £120,000.

Payments £140,000.

Closing cash:

£230,000.

Week 2:

Receipts £90,000.

Payments £125,000.

Closing cash:

£195,000.

Week 3:

Receipts £75,000.

Payments £160,000 because payroll and a major supplier both land.

Closing cash:

£110,000.

Week 4:

Expected customer receipt £180,000.

Payments £95,000.

Closing cash:

£195,000.

Looks okay.

Except the £180,000 customer has historically paid two weeks late.

Move that receipt into week 6.

Week 4 now closes at:

£15,000.

Very different business decision.

The customer still owes the same money.

Annual profit is unchanged.

The timing changed.

That is cash flow.

What do you do when the forecast shows a shortfall?

First:

Do not panic.

You built the forecast precisely so you could see the problem early.

Diagnose the cause.

Is the shortfall collection-driven?

Could you:

Resolve invoice disputes?

Chase overdue debt?

Confirm payment dates?

Invoice earlier?

Request deposits or stage payments on future work?

Is it spending-driven?

Could you:

Move non-essential capital expenditure?

Delay discretionary spend?

Reduce stock purchasing without hurting delivery?

Reschedule expenditure legitimately?

Is it growth-driven?

Perhaps you need:

Additional working capital.

Invoice finance.

Overdraft.

Asset finance.

Equity.

Another appropriate funding option.

Talk to finance providers before you desperately need them.

British Business Bank notes that lenders and investors commonly use cash-flow forecasts when assessing finance requirements, precisely because the forecast reveals where funding is needed and how it may be repaid.

Is the business structurally losing cash?

Different problem.

If:

Cash falls every week

because:

Gross margin is inadequate.

Overheads exceed contribution.

Then shifting a supplier payment by seven days does not solve anything.

You may need to address:

Pricing.

Costs.

Capacity.

Customer profitability.

Business model.

A 13-week forecast can expose the symptom.

Management still needs to fix the cause.

Build three levels of response

When the forecast identifies pressure, I like thinking in layers.

Immediate

What action protects cash during the next two to four weeks?

Collections.

Billing.

Known expenditure.

Operational

What caused the pressure?

Payment terms?

Stock?

WIP?

Margin?

Hiring?

Supplier terms?

Structural

What needs changing so the same cash problem does not reappear next quarter?

Pricing model.

Working capital structure.

Customer mix.

Financing.

Growth strategy.

Systems.

This prevents cash management becoming permanent short-term juggling.

Give every material action an owner

Forecast says:

Collect £120,000 overdue from Customer X.

Who?

By when?

Forecast says:

Capex may need moving.

Who decides?

Forecast says:

Bank facility needed.

Who contacts lender?

A forecast without actions is simply advanced worrying.

Make it part of the weekly management rhythm

Perhaps every Monday:

Finance updates actual bank balances.

Receipts and payments are refreshed.

Material variances reviewed.

Sales updates expected cash from significant opportunities.

Operations updates project timing.

Leadership reviews:

Lowest cash point.

Available headroom.

Changed assumptions.

Required actions.

Twenty minutes might be enough in a healthy business.

Your 13-week forecast should sit alongside the longer forecast

Do not abandon annual budgeting.

You need different lenses.

Annual or longer-range forecast

Where are we trying to go?

What does the year look like?

Growth.

Profit.

Investment.

Monthly management accounts

What financially happened?

Why?

13-week cash forecast

Can we meet our actual obligations week by week over the next quarter?

They complement each other.

Article #75 dealt with management accounts.

This is the short-term liquidity layer sitting alongside them.

When should you build one?

I would particularly want a 13-week forecast when:

Cash feels tight.

Business is growing quickly.

You have large payroll.

Customers pay slowly.

Work is project-based.

Stock consumes significant cash.

You are investing heavily.

You are hiring quickly.

You are opening another location.

The business is seasonal.

A major customer has become uncertain.

You are approaching funding discussions.

Trading conditions are deteriorating.

But you do not need to be in trouble to use one.

ICAEW notes that short-term cash forecasting is valuable both in stressed businesses and as a normal management discipline because it gives decision-makers visibility of future liquidity rather than forcing them to manage from the current bank balance alone.

The bank balance is not a forecast

This is the biggest behavioural shift.

Owner opens banking app.

£380,000.

Feels safe.

But perhaps during the next four weeks:

Payroll £150,000.

VAT £70,000.

Suppliers £180,000.

Other costs £80,000.

Expected customer receipts £60,000.

That £380,000 meant something completely different once you looked forwards.

Current cash tells you:

Where you are.

The forecast tells you:

Where you are heading.

You need both.

Do not obsess over making it perfect

Forecasting is inherently imperfect.

Customers pay late.

Sales move.

Costs change.

That is exactly why you update it.

The objective is not:

Predict every pound correctly thirteen weeks in advance.

It is:

See potential cash pressure early enough to make better decisions.

A slightly imperfect forecast reviewed every week is vastly more useful than a technically perfect model rebuilt every six months.

Start simple.

Improve it.

ICAEW's guidance explicitly makes this point: even a straightforward spreadsheet can provide useful cash visibility, and having an imperfect forecasting process is preferable to ignoring problems that may be developing ahead.

What should your 13-week cash forecast tell you?

At any point, you should be able to answer:

How much cash is available now?

What is expected to come in this week?

What is expected to leave?

What are the biggest uncertain receipts?

What major payments are approaching?

Where is the lowest expected cash position?

When?

What causes it?

How much available funding headroom exists?

Which assumptions could materially worsen the position?

What do we need to do this week because of what the forecast says?

If it cannot answer those questions, improve it.

The real value is time

Cash forecasting does not create money by itself.

It creates something almost as valuable when finances become tight:

Time to act.

A £100,000 shortfall discovered tomorrow morning is a crisis.

The same £100,000 shortfall identified eight weeks earlier is a management problem.

You might:

Collect cash sooner.

Renegotiate terms.

Change expenditure.

Move investment.

Secure finance.

Adjust recruitment.

Resolve the underlying issue.

The numbers are identical.

Your options are completely different.

That is why I like short-term cash forecasting.

It moves the conversation from:

“Can we pay this?”

to:

“What needs changing now so this does not become a problem in six weeks?”

That is what good management should do.

See further than the bank balance.

Why Is Our Business Always Reactive Even Though We Have Processes?

Tue, 06 Oct 2026 10:19:03 GMT

If your business has processes but still spends most of its time firefighting, the problem is probably not that you need more procedures .

It is usually that the process on paper does not match the way work actually enters, moves through and gets managed inside the business.

You may have:

SOPs
Checklists
CRM stages
Job sheets
Approval processes
Project plans
Handover forms
Weekly meetings
Software workflows

and still feel as though every day starts with:

“Right, what the fuck has happened now?”

That happens when the surrounding operating system is weak.

The process says how normal work should happen.

The business keeps creating abnormal work.

Poor information.

Last-minute promises.

Insufficient capacity.

Unclear ownership.

Missing decisions.

Constant interruptions.

Exceptions nobody designed for.

Managers overriding the process.

Customers bypassing it.

People finding workarounds because following the official version makes getting the job done harder.

The answer is not necessarily another procedure.

It is understanding why the business keeps forcing people out of the process you already have .

A documented process is not the same as a functioning system

This distinction matters.

A process might say:

Sales confirms scope.
Operations reviews capacity.
Customer receives start date.
Materials are ordered.
Job is scheduled.
Delivery begins.

Looks excellent.

What actually happens?

Sales promises Friday before Operations sees it.

Operations discovers the job on Wednesday.

Materials are unavailable.

The customer has already booked contractors around you.

Everyone panics.

Purchasing pays extra for urgent delivery.

Operations moves another customer's job.

That customer complains.

The owner gets involved.

Technically, you have a process.

Operationally, nobody protected it.

The problem is not:

“People need to follow the process better.”

Maybe they do.

But first ask why the organisation repeatedly creates circumstances where bypassing the process feels necessary.

Processes fail when the surrounding behaviour contradicts them

Imagine your procedure says:

All quotations above £25,000 require margin review before issue.

Good.

Then the owner says:

“This one's urgent. Just get it out.”

What did everybody learn?

The process applies until urgency appears.

Next time, the Sales Director makes the same judgement.

Then a Sales Manager.

Eventually:

Urgent = ignore process.

The written procedure still exists.

The real process has evolved.

This is one reason I am cautious when companies respond to operational chaos by writing more SOPs.

HSE guidance on management systems makes a surprisingly relevant point beyond health and safety: organisations can become too focused on formal documentation and lose sight of the human implementation of the system itself. Its wider Plan, Do, Check, Act framework emphasises that a management system needs implementation, monitoring and review, not merely documentation.

That principle translates extremely well into ordinary business operations.

A process only exists if the organisation can reliably operate it.

The process on paper and the work people actually do are often different

Researchers sometimes distinguish between work as imagined and work as done .

That difference is useful.

Management imagines:

Customer request enters here.

Employee follows steps.

Output appears there.

Employees experience:

Customer forgot information.

System is down.

Supplier changed delivery.

Manager is unavailable.

Previous job overran.

Customer changed scope.

Another department needs something urgently.

Software requires eleven clicks for something that can be done in Excel in two minutes.

So people adapt.

A 2026 Safety Science study examining procedural work in a petrochemical environment found substantial variation between written procedures and successful work as actually performed, with context explaining much of that variation. That is a specialist high-risk environment and should not be generalised mechanically to every SME, but the underlying point is valuable: divergence from procedure is not always simple disobedience. Sometimes people are adapting to conditions the written process did not accommodate.

If your employees repeatedly work around a process, ask why.

The workaround may be the problem.

Or it may be evidence of the problem.

Reactive businesses usually have recurring emergencies

This is one of the easiest diagnostic clues.

Look at the last month of firefighting.

How much was genuinely unpredictable?

Customer's building flooded.

Key employee had an accident.

Supplier suddenly entered administration.

Fine.

Those are genuine exceptions.

Now compare:

Material wasn't ordered.

Customer requirements unclear.

Nobody knew who was responsible.

Quote promised something Operations couldn't deliver.

Invoice incorrect.

Employee wasn't trained.

Schedule changed at the last minute.

Owner had not made a decision.

Customer chased because nobody updated them.

Manager discovered deadline too late.

Those are not random emergencies.

They are recurring operational patterns.

If the same category of emergency happens repeatedly, stop calling it an emergency.

It is part of your system.

Your business may have procedures but no operating rhythm

This is another distinction.

Processes explain how individual pieces of work happen .

An operating rhythm makes sure the wider business notices what needs attention before it becomes urgent.

For example:

Weekly capacity review.

Sales and Operations planning.

Pipeline review.

Cash review.

Project review.

Management scorecard.

Customer-risk review.

Recruitment planning.

The exact rhythm depends on the business.

Without those recurring management loops, processes operate in isolation.

Sales follows its process.

Operations follows its process.

Finance follows its process.

Then the outputs collide.

A management system needs feedback.

ONS's Management and Expectations Survey measures structured management practices across areas including continuous improvement, KPIs, targets and people management. Its latest published analysis found stronger structured management practices were associated with higher productivity and resilience, while larger businesses generally reported more structured practices than smaller ones. ONS is clear these relationships are associations rather than proof that one practice automatically causes a particular performance improvement.

The useful lesson is simpler:

Good operations require more than procedures.

They require monitoring and adjustment .

The missing part is often “Check” and “Act”

Businesses love:

Plan.

Do.

Create process.

Train employee.

Go.

Then six months later everybody complains that the process does not work.

What happened to:

Check?

Act?

HSE's Plan, Do, Check, Act model is designed for health and safety management, but it provides an excellent general management principle:

Plan what should happen.

Do it.

Check whether it actually works.

Act on what you learn.

Then repeat.

A process should not be treated like scripture.

It is a current best-known method.

Reality gives you data.

Use it.

Problem 1: The process was designed for the perfect job

This is common.

The workflow works beautifully when:

Customer information is complete.

Product is standard.

Everyone is available.

Supplier delivers.

Job starts on time.

Nothing changes.

Wonderful.

How often does that happen?

If 40% of your work contains meaningful exceptions, your process needs an exception path .

Not 400 separate procedures.

A sensible method for handling deviation.

For example:

What qualifies as an exception?

Who can decide?

What information do they need?

What customer communication occurs?

What thresholds trigger escalation?

Without this, every non-standard situation becomes:

“Can somebody ask Adam?”

Now the process exists.

And so does the owner bottleneck.

Problem 2: Nobody owns the process end to end

Departments own their bit.

Nobody owns the outcome.

Sales says:

“We handed it over.”

Operations says:

“The handover was shit.”

Finance says:

“Nobody told us.”

Customer says:

“I don't care which department caused it.”

Correct.

Processes frequently fail at the joins.

Who owns:

Sales to Operations?

Operations to Finance?

Customer complaint to resolution?

Enquiry to quote?

Quote to mobilisation?

Project completion to invoice?

If responsibility disappears at departmental boundaries, the organisation becomes reactive precisely where work changes hands.

Handoffs deserve disproportionate attention

Imagine each department is 95% reliable.

Excellent.

But a customer journey contains five significant handoffs.

Every handoff creates an opportunity for:

Missing information.

Delay.

Different assumptions.

Lost ownership.

You do not need more departmental procedures.

You may need better interfaces.

Ask at every handoff:

What information must be complete?

Who confirms receipt?

Who owns the next step?

What happens if something is missing?

How quickly should it move?

This is boring operational design.

It prevents enormous amounts of firefighting.

Problem 3: Inputs are poor

A process cannot produce reliable output from permanently unreliable input.

Operations receives:

Half-complete scope.

Wrong measurements.

Missing purchase order.

Unconfirmed delivery address.

Unclear deadline.

Then everyone expects Operations to:

“Follow the process.”

What process?

The first step should probably be:

Do not accept incomplete input.

This applies everywhere.

Payroll receives missing hours.

Finance receives incomplete job information.

Sales receives rubbish leads.

Marketing receives vague propositions.

Managers receive problems without facts.

Define minimum input standards.

Sometimes the easiest way to stop downstream chaos is to stop upstream rubbish entering the process.

Problem 4: The process does not match capacity

You can have the best scheduling process in Britain.

If you have:

100 hours of capacity

and:

140 hours of committed work

you are still going to become reactive.

Process cannot repeal mathematics.

Something will:

Move.

Rush.

Overrun.

Receive overtime.

Miss deadline.

Require subcontractors.

Disappoint somebody.

This is why capacity and process have to be designed together.

Article #68 looked at the profit consequences when too much work enters a weak operating system.

Article #76 looked at the same issue from scale readiness.

If your business is permanently overloaded, stop asking employees to process their way out of a capacity problem.

Problem 5: Your priorities change faster than the process can cope

Monday:

Project A is urgent.

Tuesday:

Forget A. Customer B is furious.

Wednesday:

Director says C has to happen.

Thursday:

Sales promises D.

Friday:

Everyone asks why Project A is late.

That is not process failure.

That is leadership-induced volatility.

Employees cannot work systematically if management repeatedly scrambles the sequence.

Sometimes priorities genuinely change.

Fine.

But the cost of change should be visible.

If D moves forward:

What moves backwards?

Who gets told?

What resource shifts?

What commercial consequence exists?

Article #83 dealt with this at strategic level.

The same principle applies operationally.

Everything cannot move to the front of the queue without something else moving backwards.

Problem 6: Sales is allowed to override Operations

This deserves special attention because it creates enormous operational reactivity.

Sales wins work.

Excellent.

Then promises:

Price.

Scope.

Delivery date.

Customisation.

Response time.

Without asking the people who need to deliver it.

Now the organisation has two choices.

Break the promise.

Or break the system.

Usually it chooses the system.

Operations bends.

Employees work late.

Purchasing rushes.

Margin disappears.

Owner intervenes.

Then everybody complains that Operations is always reactive.

The reaction began upstream.

A healthy commercial process needs boundaries around what can be promised without delivery input.

Sales should be able to sell.

Operations should not need clairvoyance.

Problem 7: The official process is too difficult

This is where employee workarounds become fascinating.

Suppose entering a customer job properly requires:

Open system.

Complete 24 fields.

Upload document.

Select category.

Create task.

Notify manager.

Employees discover:

Send Dave a WhatsApp.

Dave sorts it.

Guess which process wins under pressure?

Research into business-process workarounds describes them as adaptations people use to overcome obstacles, exceptions or constraints that prevent the official system from helping them achieve the intended outcome efficiently.

Do not automatically respond:

“We need better compliance.”

Perhaps.

Or perhaps the official process is shit.

Watch somebody actually use it.

Count:

Clicks.

Duplicate data.

Waiting.

Approvals.

Handoffs.

If the unofficial route is dramatically easier, people are telling you something.

Problem 8: You have too many approvals

Approvals feel like control.

Sometimes they are.

Sometimes they are latency.

Purchase £200?

Manager.

Customer credit £100?

Director.

Small scheduling change?

Owner.

Discount 3%?

Commercial Director.

Now ordinary work repeatedly waits for somebody senior.

Then becomes urgent because it waited.

Then the senior person receives:

URGENT APPROVAL REQUIRED.

The business appears reactive.

But the urgency was designed into the authority structure.

Use decision boundaries.

What can employees decide?

What can managers decide?

What thresholds genuinely require escalation?

Article #78 explored this as owner dependency.

Good process gives capable people enough authority to keep ordinary work ordinary.

Problem 9: Managers solve instead of manage

Something goes wrong.

Manager jumps in.

Fixes it.

Next problem.

Fixes that.

Excellent employee.

Terrible long-term system.

The question after the immediate issue should be:

Why did this happen?

If the manager never gets beyond:

Resolve.

then recurring causes survive.

This is the operational form of the Fixer Loop.

Firefighting feels productive because the feedback is immediate.

Problem existed.

You acted.

Problem gone.

Process improvement is slower.

Problem existed.

You investigated.

Changed system.

Maybe you prevented 50 future problems nobody will ever see.

Less dramatic.

Much more valuable.

Problem 10: Heroics are rewarded more visibly than prevention

This creates a fascinating cultural problem.

Employee stays until 10pm fixing a disaster.

Everybody says:

Amazing commitment.

Another employee quietly redesigns the workflow so the disaster never happens again.

Nobody notices.

What behaviour did you reward?

Businesses become addicted to heroics because heroics are visible.

Prevention is invisible.

A well-run system can look less impressive because fewer dramatic rescues happen.

That is the point.

Celebrate:

Problems eliminated.

Errors reduced.

Better handoffs.

Capacity improved.

Dependencies removed.

Not only the people standing in the smoke holding the extinguisher.

Problem 11: Your meetings report problems rather than manage them

Weekly meeting:

Job A is late.

Customer B unhappy.

Project C over budget.

Sales missed target.

Fine.

What changes?

If next week's meeting contains the same items, the meeting is reporting reality rather than managing it.

For recurring problems ask:

What is the root cause?

What action changes the system?

Who owns it?

By when?

How will we know it worked?

Otherwise management meetings become a weekly guided tour of dysfunction.

Problem 12: Your KPIs are lagging too far behind

Revenue down.

Margin down.

Customer complained.

Job late.

Those are useful.

They are also often late.

What earlier measure would have warned you?

Revenue down:

Pipeline perhaps fell months earlier.

Margin down:

Labour overrun perhaps appeared weeks earlier.

Late project:

Milestones may have slipped repeatedly.

Customer complaint:

Response time may have deteriorated.

ONS's structured-management framework includes the use and review of KPIs precisely because responding effectively to problems depends partly on seeing performance early enough to manage it.

Build a small number of leading indicators around your most important processes.

You want warning.

Not an autopsy.

Problem 13: Nobody reviews recurring failures

A customer complaint is resolved.

Ticket closed.

Move on.

Same issue next month.

Resolve.

Close.

Next.

The company has customer service.

It does not have continuous improvement.

Track recurring categories.

Which errors happen repeatedly?

Which customer complaints repeat?

Which projects overrun for the same reason?

Which invoice errors recur?

Which emergency purchases occur again?

Pattern recognition turns reactivity into improvement.

Problem 14: Process changes are not fed back into the process

Someone discovers a better way.

Great.

They now use it personally.

The official SOP remains unchanged.

Another employee follows the old process.

Two realities emerge.

This is how process drift happens.

Create a simple method for updating standard work.

It does not need a governance committee of seventeen people.

Someone owns the process.

Changes are reviewed.

Approved where necessary.

Communicated.

Documentation updated.

Training adjusted.

Now learning becomes organisational.

Problem 15: Nobody owns continuous improvement

Ask:

Who is responsible for improving how this process works?

Common answer:

“Everyone.”

Dangerous.

Everyone should contribute.

Someone should own it.

Perhaps:

Operations Manager owns scheduling.

Sales Director owns opportunity management.

Finance owns invoicing.

The process owner should understand:

Performance.

Recurring failures.

Current version.

Cross-functional dependencies.

They do not perform every task.

They are accountable for the health of the system.

Problem 16: Technology created another layer rather than removing one

Old process:

Spreadsheet.

Email.

New process:

CRM.

Spreadsheet.

Email.

Teams message.

Congratulations.

Digital transformation.

Article #80 covered software evaluation in detail.

Technology should reduce:

Duplication.

Delay.

Manual transfer.

Invisible information.

If every system needs somebody manually copying data into another, the business has automated very little.

The more tools you add, the more important information ownership and integration become.

Problem 17: The owner keeps bypassing the system

This one may hurt.

Owner says:

“Everyone needs to follow the process.”

Then an important customer calls.

Owner promises something outside the process.

Employee objects.

Owner says:

“This one's different.”

Perhaps it genuinely is.

But every owner exception teaches everybody else how seriously the process should be taken.

If you need the ability to override it, define:

When.

Why.

Who gets informed.

What downstream consequences must be considered.

Owner authority is real.

So is owner responsibility for what their intervention creates.

Problem 18: Customers have learned they can bypass the process

Customer knows:

Normal email takes 24 hours.

WhatsApp the owner and it happens immediately.

What will they do?

WhatsApp the owner.

Or:

Normal change request requires planning.

Call Sales Director directly and ask for a favour.

Now your process competes with a faster unofficial route.

Availability Architecture matters here.

If you repeatedly reward escalation with faster service, you train people to escalate.

You need to make the normal route work well enough that escalation remains exceptional.

Problem 19: Employees are solving for their department, not the whole system

Finance introduces controls.

Operations slows.

Operations changes scheduling.

Sales suffers.

Sales creates workaround.

Finance loses visibility.

Nobody intended the overall mess.

Each department improved its local problem.

This is called local optimisation in various operational contexts.

The practical question is:

Did we improve the process, or did we simply move the inconvenience somewhere else?

End-to-end ownership matters precisely because departmental performance can improve while customer experience or overall efficiency gets worse.

Problem 20: The business grew but the process did not

Processes have capacity too.

At:

Five employees

you can shout across the room.

At:

Twenty-five

that becomes unreliable.

At:

Seventy-five

it becomes ridiculous.

Growth adds:

Handoffs.

Managers.

Locations.

Transactions.

Specialists.

Exceptions.

Article #86 will look more specifically at why standards can start slipping during growth.

For now, ask whether your current systems were designed for the business you used to be .

Something can work brilliantly at £2 million turnover and become completely inadequate at £8 million.

That is not necessarily failure.

The company changed.

The operating system needs changing too.

Stop asking, “Do we have a process?”

Ask five better questions.

1. Does the process describe reality?

Watch the work.

Not the PowerPoint.

Where do people actually deviate?

Why?

2. Can the process handle normal variation?

Not every customer and job will be identical.

What happens when reality differs?

3. Do people have the capacity and authority to follow it?

A process requiring three hours when employees have one is fiction.

4. Do we know whether it is working?

Measures.

Feedback.

Exceptions.

Recurring failures.

5. Who improves it?

Someone needs to convert experience into better standard practice.

Those five questions tell you considerably more than whether an SOP exists.

Run a reactivity audit

For the next four weeks, capture every meaningful firefighting event.

Not every tiny interruption.

Things that:

Disrupt plans.

Require management escalation.

Create customer problems.

Cause overtime.

Damage margin.

Delay other work.

Require owner involvement.

For each event, record briefly:

What happened?

What was the immediate cause?

Where should the issue normally have been controlled?

Why wasn't it?

Was this truly unpredictable?

Has something similar happened before?

Then review the patterns.

Classify the fires

You will probably find categories.

Demand problem

Too much work entered.

Capacity problem

Insufficient people, equipment or time.

Handoff problem

Information or responsibility broke between functions.

Decision problem

Work waited for authority.

Information problem

Nobody knew something early enough.

Process-design problem

Official method does not match reality.

Compliance problem

Good process exists but is not being followed.

Management problem

Recurring issue is known but never permanently addressed.

Customer-boundary problem

Promises or exceptions repeatedly bypass normal control.

System problem

Technology or data does not flow properly.

Capability problem

People lack knowledge or training.

Now the word reactive becomes diagnostic rather than emotional.

Then find the Pareto of chaos

You may log 70 incidents.

Do not try to fix 70 things.

Perhaps:

Twenty-three relate to incomplete Sales handovers.

Fourteen relate to scheduling changes.

Eleven relate to missing approvals.

The majority of chaos may come from three underlying causes.

Start there.

Remove repeated causes.

Do not improve your ability to firefight all 70.

Trace each recurring problem upstream

Customer complains about late delivery.

Immediate cause:

Job started late.

Why?

Materials arrived late.

Why?

Ordered late.

Why?

Job was released to Purchasing late.

Why?

Scope remained unclear.

Why?

Sales handover was incomplete.

Now the intervention is not:

Tell Logistics to try harder.

The visible fire occurred in Logistics.

The system failure began in Sales handover.

This is the level of diagnosis you need.

Distinguish root cause from “five whys theatre”

Do not make people perform ritualistic questioning until somebody says:

“Because communication.”

The purpose is not exactly five questions.

It is understanding enough of the causal chain to change something useful.

Sometimes there are multiple causes.

Capacity plus poor handover plus unreliable supplier.

Fine.

Real businesses are messy.

Use judgement.

Decide whether to standardise, resource or redesign

Once you understand the cause, choose the appropriate intervention.

Standardise

The right method exists but is inconsistent.

Train.

Simplify.

Reinforce.

Resource

The process works but does not have enough capacity.

Add people.

Time.

Equipment.

Management.

Redesign

The process itself creates delay or failure.

Change it.

Automate

Repetitive manual work is causing avoidable errors or delay.

Delegate authority

Work repeatedly stalls at approval points.

Improve information

Management discovers problems too late.

Change commercial boundaries

Customers or Sales keep introducing work the operation cannot absorb.

Different problems need different medicine.

Create escalation rules

A reactive organisation often escalates either:

Everything.

Or nothing until disaster.

Define what should genuinely escalate.

Perhaps:

Margin below threshold.

Safety issue.

Contract variation above value.

Customer at risk.

Delivery failure above defined impact.

Cash exposure.

Legal or regulatory issue.

Everything else remains with the appropriate role.

This keeps leadership attention available for situations that genuinely deserve leadership.

Introduce protected planning horizons

Different businesses need different horizons.

Maybe:

Today.

This week.

Next four weeks.

Next quarter.

The point is to stop today's noise consuming all attention.

For example, an Operations review might look ahead four weeks and ask:

Where is capacity tight?

Which materials are at risk?

Which customers need decisions?

Which projects are likely to overrun?

That is proactive management.

You are deliberately finding tomorrow's fires while they are still smoke.

Build an interruption threshold

Not every problem needs to interrupt the current plan.

Ask:

Does this need resolving:

Now?

Today?

This week?

At the next review?

Without thresholds, urgency becomes contagious.

One person's concern becomes everybody's interruption.

This is where Article #63 on prioritising when everything feels urgent becomes useful.

The organisation needs the same discipline the individual owner does.

Protect improvement time

This is difficult precisely because improvement is rarely urgent.

The process review can wait.

The customer screaming cannot.

So improvement repeatedly moves.

And the customer keeps screaming.

Managers need protected time for:

Process review.

Root-cause work.

Training.

Documentation.

System improvements.

Capacity planning.

If 100% of management time is consumed running today's operation, the operation is unlikely to become substantially better.

You need some capacity to work on the system .

Better beats busier

This is where Agency becomes particularly relevant.

Work ethic asks:

How quickly can we solve today's twenty problems?

Agency asks:

Why did these twenty problems exist?

Work ethic matters.

There will always be moments where everybody needs to pull together and get something sorted.

But an organisation running permanently on exceptional effort has failed to turn learning into system improvement.

You do not want the world's best firefighters.

You want fewer fires.

A practical 90-day Reactive-to-Managed reset

You do not need to redesign the entire company.

Choose the area generating the most repeated disruption.

Weeks 1–2: Observe

Capture incidents.

Watch real work.

Talk to the people doing it.

Do not start by rewriting procedures.

Week 3: Diagnose

Group recurring problems.

Identify the few causes responsible for disproportionate disruption.

Weeks 4–5: Redesign

Decide what needs changing:

Input standards.

Handoffs.

Authority.

Capacity.

Technology.

Customer promises.

Process steps.

Weeks 6–7: Test

Run the revised method in real work.

Watch exceptions.

Do not assume the whiteboard version is correct.

Weeks 8–10: Standardise

Once it works:

Document enough.

Train.

Clarify ownership.

Set measures.

Weeks 11–13: Review

Did:

Escalations fall?

Customer issues fall?

Overtime reduce?

Jobs move faster?

Management interruptions drop?

If yes, keep improving.

If not, learn again.

That is continuous improvement.

Your scorecard should measure reactivity too

If reactivity is a real business problem, measure evidence of it.

Possibilities include:

Emergency purchases.

Owner escalations.

Late schedule changes.

Jobs started without complete information.

Overtime caused by avoidable planning failure.

Customer complaints caused by handoff failure.

Projects requiring senior rescue.

Do not collect twenty metrics.

Choose the few matching your recurring problems.

Then see whether improvement work changes them.

Management meetings should ask what stopped recurring

This is a better question than:

“What problems did we solve this week?”

Ask:

What recurring problem did we eliminate?

What process got better?

What dependency reduced?

What previously required escalation but now works normally?

This changes management attention from:

Activity.

towards:

System capability.

Some reactivity is healthy

This needs saying.

You do not want a business so rigid that employees cannot adapt.

Customers change.

Markets move.

Something unexpected happens.

Good businesses respond.

Being responsive and being reactive are not identical.

Responsive means:

We can adapt deliberately when reality changes.

Reactive means:

Reality repeatedly controls our priorities because we failed to anticipate, design or manage normal variation.

The objective is not zero interruptions.

It is making genuine exceptions exceptional again.

Do not process the life out of the company

There is another extreme.

Every previous mistake produces:

Another form.

Another approval.

Another field.

Another rule.

Eventually simple work becomes impossible.

People circumvent the bureaucracy.

Now management introduces another compliance rule.

Please stop.

Process should make good work easier and more reliable .

Not protect the company from every conceivable human judgement.

Where competent people can make sensible decisions within boundaries, let them.

The best process may be:

Three clear rules.

Not thirty-seven steps.

The strongest process is often the one employees want to use

Because it:

Makes sense.

Saves time.

Prevents mistakes.

Gives clarity.

Reduces repeated questions.

Allows them to get the job done.

If the official process constantly fights the people using it, investigate before blaming the people.

That is not softness.

It is operational intelligence.

Your business does not need more laminated folders

It needs fewer repeated surprises.

So if the organisation is permanently reactive despite having processes, stop writing procedures for a moment.

Look at the operating environment around them.

Are inputs reliable?

Are handoffs clear?

Is capacity realistic?

Can people make decisions?

Are priorities stable?

Does Sales respect delivery constraints?

Do systems communicate?

Do managers review recurring failure?

Does leadership override the rules?

Does anybody actually improve the process after learning something?

That is where the real system lives.

The procedure is only one component.

Processes do not make a business proactive.

Management closes the loop.

Plan.

Do.

Check.

Act.

Learn.

Improve.

Then make the next supposedly urgent problem slightly less likely to exist at all.

How Do You Prioritise Business Goals When Everything Feels Important?

Tue, 06 Oct 2026 10:12:37 GMT

When every business goal feels important, prioritise the ones that most strongly determine what becomes possible next .

That usually means choosing goals that:

Remove the biggest current constraint
Protect the business from a material risk
Create meaningful commercial value
Unlock several other improvements
Have a genuine timing requirement
Support the direction you have already decided the business is going

Then deliberately do not pursue everything else yet .

That last part is where most businesses struggle.

They do not really prioritise.

They rank twenty important things from 1 to 20, call all of them strategic priorities and then expect the same people, money and management attention to somehow progress them simultaneously.

That is not prioritisation.

It is a longer list.

Important and priority are not synonyms

This distinction changes everything.

Lots of things can genuinely be important.

Recruitment is important.

Marketing is important.

Cash flow is important.

Customer retention is important.

Systems are important.

Management development is important.

Cyber security is important.

Succession is important.

Pricing is important.

None of that means they should all become active strategic priorities right now .

A priority is something that receives disproportionate attention or resources at the expense of something else .

If nothing loses time, money, attention or urgency when you declare a new priority, you have not really prioritised it.

You have added it.

Michael Porter's classic strategy work makes exactly this point at organisational level: strategy requires trade-offs and deliberate decisions about what not to do.

That principle becomes incredibly practical in a small business.

Every meaningful goal competes for something finite.

Money.

People.

Management.

Time.

Attention.

Capacity.

So the question is not:

“Is this important?”

It is:

“Is this important enough to take resources away from something else now?”

Most businesses do not have too few goals

They have too many active ones.

A leadership meeting produces:

Increase sales.

Improve margin.

Recruit three people.

Implement new CRM.

Build management team.

Reduce debtor days.

Improve culture.

Launch service.

Open second site.

Rewrite website.

Improve customer retention.

Introduce AI.

Develop succession plan.

Everybody agrees.

They are all good ideas.

Three months later:

CRM half configured.

Website delayed.

Recruitment underway.

Management training postponed.

New service vaguely launched.

Sales team distracted.

Owner overwhelmed.

Nothing has moved enough to materially change the business.

The problem was not motivation.

It was resource allocation.

Research on goal conflict is useful here because multiple worthwhile goals can compete for the same finite resources even when the goals themselves are not logically incompatible. Time spent pursuing one necessarily reduces the time available for another.

Businesses have exactly the same problem.

You have a finite organisation.

Strategy is partly deciding what deserves to wait

This is psychologically harder than it sounds.

Owners are usually good at spotting opportunities.

You see:

What could be improved.

What could make money.

What needs fixing.

What competitors are doing.

What software could help.

What employee needs developing.

The problem is that recognising an opportunity creates a feeling that it should now be acted upon.

It does not.

Not now is a strategic decision.

It is not the same as:

Never.

Suppose your company needs to:

Replace its CRM.

Recruit a Sales Director.

Improve gross margin.

Open a second location.

All four may be completely sensible.

But perhaps weak margin is currently the fundamental constraint.

Opening another location before understanding the economics could simply reproduce poor margin at twice the scale.

The second location matters.

It simply belongs later.

Sequencing is part of strategy.

Start with direction before goals

Before choosing goals, ask where the company is actually trying to go.

Not in motivational-poster terms.

Commercially.

Over the next two or three years, are you trying to:

Increase profitability?

Scale?

Become less dependent on the owner?

Prepare for sale?

Build recurring revenue?

Expand geographically?

Strengthen management?

Reduce risk?

Create a smaller but more profitable company?

Your goals should help create that future.

Without direction, every attractive improvement competes equally.

That is how companies end up pursuing projects because:

A competitor launched something.

A salesperson suggested it.

The owner heard a podcast.

A software company gave a great demo.

Someone said AI repeatedly at a conference.

Direction gives you a filter.

Does this move us towards the company we actually intend to build?

If not, why is it consuming strategic attention?

Separate strategic goals from business-as-usual responsibilities

This is one of the biggest sources of unnecessary priority overload.

You might say your priorities are:

Make payroll.

Deliver customer work.

Maintain safety.

Provide good customer service.

Collect debts.

Manage employees.

Yes.

Those are important.

They are also the ongoing requirements of operating the business.

They do not necessarily need to become quarterly strategic goals.

The company still needs to:

Sell.

Deliver.

Invoice.

Pay people.

Maintain standards.

While pursuing a small number of change goals .

A strategic goal should generally make something meaningfully different.

For example:

Not:

Maintain customer service.

But:

Reduce customer response time from 36 hours to below four hours by redesigning enquiry routing.

Not:

Manage employees well.

But:

Build an operational management layer capable of making routine decisions without owner involvement by the end of Q2.

Normal work keeps the business running.

Strategic priorities change its capability or position.

Keep those concepts separate.

Separate goals from projects too

Another common mess.

Goal:

Improve profitability.

Project:

Review pricing across all service lines.

Project:

Implement job-costing software.

Project:

Exit persistently loss-making contracts.

A goal tells you what outcome you want.

Projects are possible ways of producing it.

This distinction matters because businesses often commit to a project before properly testing whether it is the best route to the outcome.

“Implement new ERP”

is not automatically a strategic goal.

Why are you implementing it?

Reduce administration?

Improve stock visibility?

Support additional locations?

Once the outcome is clear, you can still decide the ERP is the wrong solution.

That is much harder if installing it has already become the sacred objective.

Start with a proper Dump

This is one place The DROP System fits naturally.

Do not attempt to prioritise while ideas remain scattered across:

Meeting notes.

Email.

Whiteboards.

Your head.

Management-team heads.

The budget.

The strategy deck.

Put the candidate goals in one place.

Dump.

Capture everything leadership believes needs meaningful attention over the next 6 to 12 months.

For example:

Recruit Operations Director.

Reduce debtor days.

Increase average gross margin.

Implement CRM.

Launch maintenance service.

Improve employee retention.

Develop second management tier.

Acquire competitor.

Open new branch.

Reduce owner involvement.

Introduce customer profitability reporting.

Build recurring revenue.

Whatever genuinely exists.

Do not prioritise yet.

Get the whole picture visible.

Then ask which goals are actually the same problem

This can dramatically reduce the list.

Perhaps you have:

Improve delegation.

Reduce owner workload.

Speed up decisions.

Develop managers.

Stop operational firefighting.

Those may not be five priorities.

They may all point towards one underlying strategic objective:

Build an operational management team capable of running day-to-day delivery without owner intervention.

Excellent.

You have just turned five competing initiatives into one coherent goal.

Likewise:

Improve cash flow.

Reduce overdue debt.

Improve invoicing.

Reduce WIP.

Shorten customer payment cycle.

Could form a wider goal around:

Release £300,000 of working capital by improving billing and collection.

Look for common causes before treating every symptom as a separate priority.

Identify the constraint

This is one of the most commercially useful filters.

Ask:

What currently limits the business most?

Not what annoys you most.

What genuinely restricts the next stage?

Maybe demand.

Then marketing or sales pipeline deserves attention.

Maybe sales are excellent but operations cannot deliver.

Then more marketing may be exactly the wrong priority.

Maybe capacity exists but margin is weak.

Then pricing or operational profitability comes first.

Maybe everything still depends on the owner.

Then scaling demand may simply create more owner dependence.

Article #76 explored this through scale readiness.

The constraint deserves disproportionate attention because improving somewhere else may produce little benefit until the constraint moves.

Ask the “so what?” question

Goal:

Implement a new CRM.

So what?

Better sales visibility.

So what?

More consistent follow-up and forecasting.

So what?

Increase conversion and reduce the number of genuine opportunities disappearing.

Now we are reaching something commercially useful.

Do the same with:

Recruit a Marketing Manager.

So what?

Produce more marketing.

So what?

If nobody can connect the proposed goal to an outcome that matters, perhaps it should not be a priority.

Activities often masquerade as goals because they sound productive.

Use commercial consequence as a filter

What happens if we achieve this?

What happens if we don't?

Suppose Goal A is:

Launch new service.

Expected potential:

£150,000 additional annual revenue.

Goal B:

Fix job-costing problem causing roughly £250,000 annual margin leakage.

Both important.

Which deserves immediate priority?

Probably B, unless some unusual strategic reason changes the answer.

Quantify where possible.

Revenue.

Profit.

Cash.

Capacity.

Risk.

Time saved.

Customer retention.

Not every benefit needs a perfect financial number.

But try to understand magnitude.

Use risk as a separate filter

Some goals deserve attention because the downside of inaction is unacceptable.

Examples:

Serious cyber vulnerability.

Regulatory exposure.

Dangerous customer concentration.

Critical succession gap.

Cash runway becoming too short.

A risk-reduction goal may not generate visible revenue.

That does not make it strategically weak.

Ask:

How likely is the problem?

How serious would the consequence be?

How difficult would recovery become?

Article #82 addressed this specifically with key-person risk.

Risk and return both compete for resources.

Leadership has to balance them.

Look for leverage

Some goals create multiple benefits.

These deserve particular attention.

Suppose developing the Operations Manager would:

Reduce owner involvement.

Improve employee accountability.

Speed customer decisions.

Strengthen succession.

Allow growth.

That is a high-leverage goal.

Compare it with:

Redesign office layout.

Potentially useful.

Far fewer downstream consequences.

Leverage asks:

If we solve this, what else becomes easier?

That is a powerful prioritisation question.

Look for dependency

Some goals cannot sensibly begin until another goal is completed.

You want to automate quoting.

But the pricing model is inconsistent.

Fix pricing first.

You want to expand geographically.

But current management accounts cannot show profitability by site.

Improve reporting first.

You want managers to take greater accountability.

But nobody has defined their authority.

Clarify decision boundaries first.

The goals are not competing.

They are sequential.

This is another reason a flat list of priorities is insufficient.

Some belong:

Now.

Next.

Later.

Timing genuinely matters sometimes

Opportunities can expire.

Lease becoming available.

Competitor exiting.

Regulatory deadline.

Customer tender.

Employee retirement.

Contract renewal.

Funding opportunity.

That can elevate a goal.

But be careful.

Owners are exceptionally good at converting preferences into artificial deadlines.

“We really need this done by March.”

Why?

If there is no actual consequence, March is simply the date you chose.

Internal deadlines are useful.

Do not confuse them with strategic necessity.

Then assess resource conflict

This is the bit leadership teams regularly ignore.

Two goals may both be excellent.

Can the same people realistically deliver them simultaneously?

Recent experimental research on goal prioritisation reinforces the obvious but important point that multiple goals require coordination of limited cognitive resources, and resource constraints affect how people make prioritisation decisions.

At organisational level, the resources include:

Senior management attention.

Finance team.

IT.

Operations.

Cash.

Project capacity.

If three strategic initiatives all require your Operations Director for 40% of their week, you do not have three properly resourced priorities.

You have a fight scheduled for Monday.

The owner is often the hidden shared resource

This is particularly common in owner-managed companies.

Leadership agrees five priorities.

Each has a different responsible manager.

Excellent.

Except every manager ultimately needs:

Owner approval.

Owner thinking.

Owner decision.

Owner relationship.

Owner review.

Now all five projects compete for the same individual.

You.

This should immediately affect the plan.

Article #78 explored whether a business has really become independent of owner labour.

Strategic planning needs to recognise that dependency.

Do not allocate one person's attention six times.

Choose fewer company-level priorities

How many?

There is no universal scientific number.

I generally prefer a very small number of meaningful company priorities for a 90-day period.

Often:

One to three.

That does not mean the company only does three things.

The rest of the operation continues.

Departments can maintain their own responsibilities.

Smaller improvement projects can happen.

But leadership-level focus should remain concentrated enough that people know what matters disproportionately.

If there are twelve company priorities, a manager facing a conflict between two of them has no useful guidance.

Everything remains important.

Three priorities do not mean equal priorities

Perhaps this quarter contains:

Priority 1

Fix margin leakage.

Priority 2

Recruit Operations Director.

Priority 3

Implement new management reporting.

All matter.

But one may still dominate.

If margin becomes critical, resources may move towards it.

Rank even the shortlist.

There should be a clear answer when two priorities collide.

Use a “must, should, could” distinction carefully

You can categorise goals:

Must

Material consequence if not achieved within the period.

Should

Meaningful value, but timing has some flexibility.

Could

Worthwhile if capacity remains.

Useful.

But do not allow:

Eight musts.

Twelve shoulds.

Fourteen coulds.

We are back where we started.

The purpose is making choices.

Create a “not now” list

This is one of the simplest improvements you can make.

When leadership decides something matters but cannot be a current priority, do not leave it floating around.

Put it somewhere visible.

Not now.

Perhaps:

Website rebuild.

Second location.

New service.

AI project.

International expansion.

The idea has not been rejected.

It has been sequenced.

This reduces repeated debate.

Otherwise someone raises the same idea every management meeting because:

“We never decided what we're doing about it.”

You did.

Not now.

Be willing to stop existing initiatives

This is harder than declining new ones.

Companies accumulate projects.

Each has:

An owner.

Some sunk cost.

A presentation.

Emotional attachment.

So when a new priority appears, leadership adds it without removing anything.

Project overload follows.

Harvard Business Review has written about exactly this tendency, noting that organisations often keep layering new initiatives rather than killing work that no longer fits the strategy.

Ask:

If this new priority genuinely matters, what are we stopping?

That question forces realism.

Sunk cost should not determine priority

You have already spent £80,000 developing a product.

It no longer looks attractive.

Someone says:

“We can't stop now. We've spent £80,000.”

The £80,000 has gone.

The relevant question is:

What should the next £1 and the next hour be spent on?

Continue if the future case is strong.

Stop if it isn't.

Strategy is about future resource allocation.

Not protecting yesterday's decisions from embarrassment.

Beware the exciting goal

Some goals are simply more fun.

New market.

New product.

New brand.

AI.

Acquisition.

Expansion.

Others are dull.

Debtor collection.

Management training.

Margin analysis.

Role clarity.

Process redesign.

The exciting initiative naturally attracts more energy.

That does not make it more important.

Sometimes the most valuable strategic priority is extremely boring.

Reduce average debtor days from 68 to 45.

Nobody is making a Netflix documentary about it.

It could transform your cash position.

Beware the owner's pet project

The owner is allowed ideas.

They are also dangerous because employees may treat every idea as an instruction.

You say:

“I've been thinking about launching a podcast.”

Marketing hears:

New strategic priority.

Design work begins.

Equipment researched.

Meetings happen.

You forget about the comment three days later.

Leaders need discipline around ideas.

Not every thought deserves organisational motion.

Capture it.

Review it later.

This is another form of Dump before Plan.

Strategic goals need clear outcomes

Once you choose the goals, make them specific enough to manage.

Goal:

Improve management.

Meaningless.

Better:

By the end of the quarter, Operations, Sales and Finance managers will independently own agreed routine decisions, reducing owner operational escalations by 50%.

Goal:

Improve profitability.

Better:

Increase average gross margin from 29% to 34% by correcting pricing and delivery losses in the three lowest-margin services.

Specific goals tend to outperform vague instructions when people have appropriate ability, commitment and feedback. Goal-setting theory has accumulated decades of evidence around the value of specific, challenging goals over loose intentions, although task complexity and the way goals are implemented matter.

Clarity matters.

Do not make the goal so specific that you optimise the wrong thing

Targets can distort behaviour.

You want:

10% revenue growth.

Sales discounts heavily.

Revenue achieved.

Margin destroyed.

Congratulations?

This is why strategic goals need guardrails.

For example:

Increase revenue by 10% while maintaining gross margin above 35%.

Or:

Reduce inventory by £200,000 without compromising agreed service levels.

A target should point towards business success.

Not merely create a number people can technically hit.

Distinguish outcome measures from activity measures

Goal:

Generate £500,000 of qualified new pipeline.

Outcome.

Supporting activity might include:

50 target-account conversations.

Two sector events.

Referral campaign.

But those are methods.

If another method creates the pipeline more efficiently, use it.

Do not become loyal to activity after the outcome has disappeared.

Give every priority one accountable owner

Not:

Sales and Marketing.

Not:

Leadership Team.

Not:

Everybody.

One person should be accountable for ensuring the goal progresses.

That does not mean they personally do every task.

They coordinate.

Escalate.

Report.

Make sure it does not quietly die.

Shared ownership often becomes no ownership.

Then identify who else is required

Suppose the Sales Director owns:

Increase qualified pipeline by £1 million.

Marketing contributes.

Owner supports key relationships.

Finance helps establish economics.

Fine.

But Sales Director remains accountable.

Clarify resource needs before launch.

Do not announce a strategic priority and then discover the people required are already committed elsewhere.

Convert goals into 90-day priorities

Article #66 covered this in depth.

A 12-month ambition is often too distant for execution.

Take the bigger strategic direction and ask:

What meaningful progress should exist 90 days from now?

Suppose three-year direction:

Make business capable of operating without owner involvement.

This quarter:

Transfer routine Operations authority.

Next quarter:

Move key customer relationships.

Later:

Develop second-tier leadership.

The long-term objective stays stable.

The active priority changes.

This is how large goals become manageable without pretending everything needs doing now.

Then convert intention into actual action

Setting the goal is not enough.

A meta-analysis of 94 studies found that implementation intentions, plans specifying when, where and how action will occur, improved goal attainment compared with intention alone. The research spans many individual behavioural contexts rather than corporate strategic programmes, so it should not be treated as a precise prediction of business execution. The underlying lesson is still extremely useful: goals become more executable when action is attached to specific circumstances.

So:

Improve margin

becomes:

Monday, Finance produces margin by service line.

Wednesday, Operations reviews the bottom three.

Friday, pricing decisions agreed.

Now movement begins.

Put strategic work in actual capacity

Article #72 dealt with weekly planning.

This is where the two levels meet.

Company priority:

Reduce key-person risk.

What appears in this week's calendars?

If the answer is:

Nothing,

the strategy does not yet exist operationally.

Perhaps:

Tuesday 10am: successor-development meeting.

Thursday: deputy runs payroll.

Friday: customer relationship handover.

Strategy has to eventually occupy someone's Tuesday.

Otherwise it remains language.

Create lead measures

The final outcome may take months.

Track earlier evidence.

Suppose goal:

Reduce debtor days from 65 to 45.

Leading actions might include:

Invoices issued within 24 hours.

All overdue accounts contacted weekly.

Disputes resolved within five days.

Suppose:

Build management independence.

Leading measures:

Routine owner escalations per week.

Percentage of decisions handled within management authority.

Management one-to-ones completed.

Lead measures tell you whether the behaviour required for the result is actually happening.

Keep a scorecard

Progress monitoring matters.

A meta-analysis of 138 studies involving nearly 20,000 participants found that interventions designed to increase monitoring of goal progress improved subsequent goal attainment on average. Effects were stronger in some circumstances when progress was recorded or reported.

Again, business teams are not identical to the experimental populations in every study.

But the practical lesson is strong.

Review progress.

Do not set quarterly priorities in January and rediscover them in March.

Use a simple scorecard:

Where were we?

Where are we now?

Are we on track?

What is blocking progress?

What decision is needed?

No twenty-page presentation required.

Review strategic priorities separately from normal management information

Your management meeting might contain:

Cash.

Sales.

Delivery.

People.

Those matter every month.

Then review:

Strategic priorities.

What moved?

What stalled?

What needs a decision?

This stops urgent operating issues consuming the entire meeting.

The business still needs management.

But change work receives protected attention too.

Do not change priorities every week

This kills execution.

One week:

Sales!

Cash!

Then:

AI!

Then:

Culture!

Businesses facing genuine emergencies obviously need to adapt.

But leadership that constantly changes the strategic message creates learned helplessness.

Employees stop believing the latest announcement because another one will replace it shortly.

A priority needs enough stability to produce an outcome.

Do not confuse strategic agility with managerial attention span.

But do change when reality genuinely changes

The opposite extreme is equally ridiculous.

A major customer collapses.

Cash position changes radically.

Regulation shifts.

A serious risk emerges.

Yet leadership refuses to alter the plan because:

“We agreed the priorities in January.”

Plans exist to serve reality.

Not replace it.

Reprioritise deliberately when material evidence changes.

Explain why.

Then remove or pause something else.

Use a decision test for new goals mid-quarter

Someone proposes a new initiative.

Ask:

Is this genuinely more important than one of our current priorities?

If no:

Not now.

If yes:

Which current priority are we reducing or stopping?

That prevents priority inflation.

New information may justify changing direction.

It does not create more organisational capacity by magic.

Ask whether the goals conflict

Sometimes objectives actively work against each other.

Example:

Reduce labour cost by 15%.

Simultaneously improve customer response speed dramatically.

Possible?

Maybe.

Perhaps technology makes both compatible.

Or perhaps achieving one harms the other.

Recent organisational research has continued to examine multiple goal conflicts, including situations where teams simultaneously face goals such as innovation and short-term revenue. The central problem is that goals can compete for scarce time and cognitive resources even when leadership wants both.

Make the conflict explicit.

Then decide the trade-off.

Do not force managers to discover it secretly.

Some goals reinforce each other

The reverse is also true.

Goal A:

Train managers.

Goal B:

Reduce owner dependency.

Strong reinforcement.

Perhaps one coherent programme achieves both.

Goal A:

Improve customer profitability.

Goal B:

Increase gross margin.

Again, closely linked.

Look for goals where the same intervention advances several outcomes.

That is strategic efficiency.

But do not artificially merge unrelated goals just to reduce the number.

Ask what must be true

This is an excellent strategy question.

Goal:

Open second location.

What must be true?

Existing site reliably profitable.

Management capable.

Cash available.

Demand exists.

Systems repeatable.

Those become prerequisite tests.

Goal:

Double revenue.

What must be true?

Pipeline.

Capacity.

People.

Working capital.

Management.

Now you can see which earlier goal deserves priority.

Perhaps doubling revenue is not the current priority.

Building delivery capacity is.

Ask what would make this goal unnecessary

This is pure Agency.

You want to:

Recruit two administrators.

Why?

Current team overloaded.

Why?

Manual order entry.

Could automation remove most of it?

Now:

Recruit two administrators

may disappear entirely as a strategic goal.

Keep asking:

Is there a better way?

Do not prioritise a solution before challenging the assumption underneath it.

Do not confuse emotional urgency with strategic importance

Some goals feel powerful because they bother the owner.

Branding is ugly.

Office is irritating.

Website embarrasses you.

Competitor opened nearby.

Fine.

Emotion is information.

Not necessarily priority.

Ask what commercial consequence exists.

Perhaps the website genuinely damages conversion.

Then fix it.

Perhaps you simply hate the font.

You may survive.

Use the Friday test

Imagine it is the final Friday of the quarter.

You can only point to one meaningful change and say:

“This got done.”

Which outcome would make the biggest difference to the business?

That question forces trade-offs.

Then ask:

What would be second?

Third?

After that, be suspicious.

Use the failure test

For each proposed priority:

What happens if we do not do this for another 90 days?

Nothing meaningful?

Probably not urgent.

Serious cash risk?

Move it up.

Opportunity expires?

Move it up.

Minor inconvenience?

Down.

This test is especially good for businesses where everything has acquired artificial urgency.

Use the leverage test

If completed, which goal makes several other things easier?

That may deserve elevation.

For example:

Recruiting a capable Operations Director might unlock:

Scale.

Owner time.

Improved accountability.

Better customer delivery.

Manager development.

One intervention.

Several consequences.

Use the constraint test

Which unresolved issue prevents the company exploiting opportunities it already has?

Perhaps you do not need:

More leads.

You need:

More capacity.

Not more employees.

Better management.

Not more revenue.

Better margin.

Prioritise the constraint.

Use the strategic-direction test

Does this directly contribute to the company we have chosen to build?

Or is it simply attractive?

Lots of good ideas fail this test.

Good.

That is the point.

The five-question priority filter

For each candidate strategic goal, ask:

1. What material outcome does this create?

Money, capacity, resilience, strategic position, customer value or another meaningful result.

2. What happens if we delay it by 90 days?

This reveals timing.

3. What else becomes easier if we achieve it?

This reveals leverage.

4. What resources does it compete for?

This reveals realism.

5. Does it support our actual strategic direction?

This reveals relevance.

You do not need a complicated scoring model.

You need a serious conversation.

Then force the choice

After the discussion, choose.

Perhaps the next quarter is:

Restore gross margin to 34%.
Recruit and onboard Operations Director.
Release £200,000 from overdue debt and WIP.

Everything else goes into:

Business as usual.

Next.

Not now.

That is a strategy people can understand.

DROP works surprisingly well at company level

Dump

Capture every potential goal and unresolved strategic issue.

Review

Test them against:

Direction.

Constraint.

Commercial consequence.

Risk.

Leverage.

Dependencies.

Timing.

Resources.

Offload

Remove:

Business-as-usual responsibilities pretending to be strategic goals.

Duplicate goals.

Projects that no longer make sense.

Work that belongs lower in the organisation.

Ideas that should wait.

Plan

Choose the tiny number that genuinely deserve disproportionate attention.

Define:

Outcome.

Owner.

Measures.

90-day target.

Next actions.

Resources.

Review rhythm.

Then execute.

The hardest part is still saying no

You can use:

Frameworks.

Scores.

Sticky notes.

Consultants.

Strategy days.

Eventually, leadership still has to choose.

Porter described trade-offs as fundamental to strategy because without limits, every good idea can be pursued and the organisation loses a distinctive direction.

That is the bit nobody can automate for you.

Someone has to say:

This matters more.

That waits.

We stop this.

We are not pursuing that opportunity yet.

We cannot fund everything.

We cannot make every department's favourite project a company priority.

Good leadership creates clarity by making those choices.

A practical two-hour business-priority reset

If your company currently has too many competing goals, do this with the leadership team.

First 20 minutes: Dump

Put every current strategic initiative and proposed goal in one place.

No debate yet.

Next 20 minutes: combine

Which goals are:

Duplicates?

Symptoms of the same problem?

Projects supporting the same outcome?

Combine them.

Next 30 minutes: test

For each remaining candidate ask:

What commercial outcome?

What risk?

What constraint?

What leverage?

What timing?

What dependency?

Next 20 minutes: check resources

Who would actually deliver each?

Do several rely on the same people?

Do you genuinely have the cash and management capacity?

Next 15 minutes: choose

Pick the small number that deserve active organisational focus for the next 90 days.

Rank them.

Final 15 minutes: park everything else

Business as usual.

Next quarter.

Later.

Stop completely.

Then leave the room with fewer priorities than you entered with.

If you leave with more, you probably had a brainstorming session instead.

Your priorities should make decisions easier

This is the ultimate test.

A manager says:

“I can either spend Thursday helping with the new CRM project or fixing margin data for the profitability priority. Which wins?”

If leadership says:

“They're both important”

you have failed to prioritise.

A useful priority system answers the question.

That is what priorities are for.

They allocate attention when resources conflict.

Everything important cannot be urgent at the same time

Businesses will always contain more opportunities than capacity.

That is not a planning failure.

That is reality.

The answer is not to become infinitely efficient so you can pursue every good idea.

The answer is to choose.

What matters now?

What unlocks what comes next?

What would genuinely hurt if ignored?

What gives the business the greatest leverage?

What belongs later?

Then concentrate enough resources that the chosen goal actually moves.

Because ten goals making 10% progress is often far less valuable than two goals reaching completion and changing what the business can do next.

Prioritisation is not deciding which important things matter.

They may all matter.

It is deciding which important things receive the company's finite resources now .

Everything else waits its turn.

Ho Do You Reduce Key Person Risk In A Small Business

Tue, 06 Oct 2026 10:03:33 GMT

You reduce key-person risk by making sure important business outcomes do not depend on one individual being permanently available .

That does not mean everybody needs to be replaceable tomorrow.

It means identifying where the company has dangerous single points of failure, then deliberately spreading:

Knowledge
Capability
Authority
Relationships
Access
Decision-making
Succession options

across more than one person or system.

The key person might be the owner.

It might also be:

Your Operations Director.

Estimator.

Finance Manager.

Engineer.

Salesperson.

Payroll administrator.

Technical specialist.

Project Manager.

IT person.

Someone who has worked there for twenty years and apparently knows where every body is buried.

Their job title is not what makes them key.

The consequence of losing them is.

If one person's unexpected absence would stop sales, delay customers, prevent payments, remove critical knowledge or leave nobody legally or technically capable of doing something important, you have key-person risk.

And the best time to reduce it is while that person is still sitting at their desk.

This is broader than owner dependency

Article #71 asked what would happen if you , the owner, suddenly became unable to work.

This article asks the wider question:

Who else could disappear tomorrow and seriously damage the business?

That matters because businesses often spend years reducing owner dependency and accidentally create another version of exactly the same problem.

The owner delegates everything operational to an excellent General Manager.

Wonderful.

Six months later, the owner can finally step back.

Except now:

Only the General Manager understands the operation.

Everybody takes difficult decisions to them.

All the key customers know them.

All supplier issues route through them.

When they take two weeks' holiday, the company quietly panics.

You moved the dependency.

You did not remove it.

Key-person risk is a single point of failure

Think of it that way.

If removing one individual causes a disproportionate amount of the business to stop functioning, that person represents concentration risk.

Perhaps they are the only person who can:

Price complex projects.

Operate specialist equipment.

Sign off technical work.

Run payroll.

Produce the monthly accounts.

Access a critical platform.

Manage your largest customer.

Understand a particular contract.

Maintain a bespoke software system.

Approve significant expenditure.

Deal with the bank.

Recruit specialist staff.

Solve a recurring production problem.

Some dependencies are unavoidable in the short term.

The question is whether they remain invisible and unmanaged.

Do not start by asking who your “best people” are

That produces the wrong list.

Your highest performer may not actually be a key-person risk.

Perhaps Sarah is an extraordinary salesperson.

But:

Her CRM records are excellent.

The Sales Director understands every account.

Customers know several people.

Other salespeople can cover.

The sales process is clear.

Losing Sarah would hurt.

That is different from business interruption.

Meanwhile Bob works quietly in Finance.

Nobody describes Bob as a superstar.

Bob happens to be the only person who knows:

How payroll works.

Where the banking files come from.

How a particular customer billing process operates.

Which spreadsheet feeds the cash forecast.

How to fix the weird VAT export every quarter.

Bob takes three weeks off unexpectedly.

Now everybody discovers Bob was infrastructure.

That is why you identify key people by dependency , not status.

Run the 30-Day Absence Test across the business

Take every important role and ask:

What happens if this person becomes completely unavailable tomorrow for 30 days?

Not resigns with a three-month handover.

Not answers occasional questions.

Unavailable.

What stops?

What slows?

Who struggles?

What customer notices?

What decision cannot be made?

What information disappears?

What deadline might be missed?

What system becomes inaccessible?

What regulation or licence creates a problem?

What revenue becomes vulnerable?

This is essentially business-continuity thinking applied specifically to people.

Current UK government guidance describes business continuity management as identifying critical activities and the resources supporting them, then planning how important functions can continue when disruption occurs. It specifically recommends understanding changes in staff, suppliers, organisational structure and other resources that could affect continuity.

Do not begin by trying to predict why somebody becomes unavailable.

Illness.

Resignation.

Family emergency.

Competitor recruitment.

Accident.

Retirement.

The cause matters later.

The operational question is:

What disappears when the person does?

Look for seven types of dependency

Most key-person risk I see falls into a handful of categories.

1. Knowledge dependency

One person knows something important that nobody else can easily reconstruct.

That might be:

Technical knowledge.

Customer history.

Pricing logic.

Production setup.

A complicated spreadsheet.

A legacy system.

How a particular contract works.

Which suppliers can solve unusual problems.

Why a process exists.

Knowledge dependency is dangerous because the business may not realise what has disappeared until it needs it.

You only discover the information mattered when nobody can answer the question.

2. Capability dependency

Several people understand what needs doing.

Only one person can actually do it.

Perhaps one employee is:

Qualified.

Licensed.

Technically competent.

Experienced enough.

Trained on specialist equipment.

Able to prepare a particular calculation.

This is different from undocumented knowledge.

The knowledge may be available.

The capability is not.

3. Relationship dependency

One employee holds a commercially important relationship.

Customer.

Supplier.

Referral partner.

Bank.

Professional adviser.

Key subcontractor.

If that person leaves, does the relationship stay with the business?

Or did the company effectively borrow their personal relationship?

This is particularly dangerous where one salesperson or founder controls a large share of customer revenue.

4. Authority dependency

Other people know what to do.

They simply cannot authorise it.

Only one person can:

Approve payments.

Sign contracts.

Authorise purchases.

Agree discounts.

Approve refunds.

Hire.

Commit resources.

You have capability.

But the business still stalls because authority is concentrated.

5. Access dependency

One employee holds the digital or physical keys.

Administrator account.

Bank authentication.

Domain control.

Payroll credentials.

Software ownership.

Building access.

Encryption keys.

Supplier portals.

This is an increasingly important risk because a company can contain plenty of competent people who remain completely unable to act if the required digital access disappears.

6. Capacity dependency

One person can technically be covered.

But not without overwhelming everybody else.

Suppose you have three project managers.

One leaves.

The remaining two understand their work.

They simply have no realistic capacity to absorb it.

That is still resilience risk.

Cross-training without spare capacity is not always enough.

7. Leadership dependency

Someone holds the organisation together.

They coordinate.

Resolve disagreements.

Set direction.

Make judgement calls.

Keep people calm.

The written processes may survive their absence.

The management system may not.

This tends to appear at owner, director or senior-manager level.

But not always.

Start with the roles that could materially interrupt the business

Do not turn this into an audit of all 83 employees.

Start with the handful of roles where absence could cause serious damage.

CIPD's current succession-planning guidance recommends identifying business-critical positions first, rather than assuming succession planning should only focus on the most senior jobs. It also notes that modern succession planning increasingly uses pools of people capable of covering groups of roles rather than simply identifying one replacement for one executive.

For a small business, I would identify perhaps:

Five.

Ten.

Maybe fifteen critical roles.

Depending on size and complexity.

Then go deeper.

Estimate the impact

For each key person, ask what a prolonged absence could affect.

Revenue

Would sales stop?

Could important customers leave?

Would orders be delayed?

Delivery

Would projects stop?

Could deadlines be missed?

Would quality deteriorate?

Cash

Could invoices still go out?

Could payroll run?

Could payments be approved?

Compliance

Does the person hold a qualification, licence or statutory responsibility the company depends upon?

Customers

Would anyone else understand the account?

Systems

Does the company still have administrative access?

People

Who leads their team?

Replacement time

Could you recruit another capable person in:

Two weeks?

Six months?

Two years?

The longer replacement takes, the more seriously I would treat the dependency.

Do not obsess over creating a precise risk score

You can absolutely use:

High.

Medium.

Low.

Or a numerical matrix if that helps.

But avoid spending three weeks debating whether Jim is:

7.4 out of 10 key-person risk

rather than:

7.1.

The useful question is:

Which few dependencies could seriously hurt us, and what are we going to do about them?

You are building resilience.

Not a scoring competition.

Step 1: Get important knowledge out of people's heads

This is the obvious intervention.

Also the one most likely to become absurd.

Please do not respond by asking everyone to write a 90-page procedure for every element of their job.

Focus on information that is:

Critical.

Difficult to reconstruct.

Time-sensitive.

Used infrequently enough that others would not know it.

Ask the key person:

If you disappeared tomorrow, what would we desperately wish you had written down?

Start there.

That might include:

Process notes.

Customer histories.

Technical procedures.

Pricing logic.

System architecture.

Supplier contacts.

Recurring deadlines.

Decision rules.

Exception handling.

Location of critical documents.

It does not need to become War and Peace.

It needs to let another competent person continue.

Documentation should explain judgement, not only clicks

Weak procedure:

Click File.

Click Export.

Select CSV.

Save to desktop.

Great.

Why are we doing this?

What does the output mean?

What happens if the numbers look wrong?

Which exceptions matter?

What decisions follow?

Key-person knowledge often lives in judgement , not merely procedure.

Capture some of the reasoning.

For example:

“If project margin drops below 25%, check labour overrun first because that is historically the most common cause. If labour looks normal, check subcontract variation orders before changing forecast.”

That is much more useful than:

“Open the margin report.”

Record specialist processes where appropriate

Sometimes written instructions are enough.

Sometimes video is better.

Screen recordings can be excellent for:

Software workflows.

Reports.

Technical administration.

Complex spreadsheet processes.

Combine them with concise written notes so somebody can quickly find what they need.

The objective is not beautiful documentation.

It is recoverability.

Step 2: Build a second capable person

Documentation alone does not create capability.

I can give you a manual for flying a helicopter.

Please do not give me the helicopter.

Some roles require:

Experience.

Practice.

Technical skill.

Professional qualifications.

Judgement.

So somebody else needs exposure before the key person disappears.

CIPD's December 2025 succession guidance specifically recommends proactive development through practical experience, job moves, secondments and other opportunities that prepare people for future or emergency roles.

For an SME, that might simply mean:

Shadowing.

Joint customer meetings.

Cross-training.

Covering holidays.

Leading a project.

Attending key financial meetings.

Running the monthly process once.

Learning specialist equipment.

Gradually making decisions with oversight.

Do not wait for the emergency before beginning the training.

Holiday cover is one of the cheapest resilience tests you have

Your key employee takes two weeks off.

Good.

Let them actually take two weeks off.

Do not build a continuity system that consists of:

“Ring Dave on holiday.”

Before they leave:

Who covers?

What do they need?

Which decisions can they make?

What has to wait?

What might break?

Then observe.

Every question sent to the absent person tells you something.

That is dependency data.

Use it.

Step 3: Develop talent pools, not one heir to every throne

Traditional succession planning can become:

Sarah replaces Dave.

What if Sarah leaves first?

Or does not want the job?

Or turns out not to be ready?

Where possible, build broader capability.

CIPD's latest guidance describes a shift towards talent pools and groups of roles where several individuals develop the skills required for multiple critical positions.

That approach often makes sense in smaller businesses too.

Maybe you cannot have:

Three Finance Directors.

But perhaps two people understand enough of the finance function to maintain basic continuity.

Three people can quote standard work.

Two managers can deal with important customers.

Several supervisors can run a shift.

Resilience improves when capability spreads.

Step 4: Spread customer relationships

This is one of the highest-value interventions.

If your largest customer's entire relationship sits with one individual, widen it.

Not awkwardly.

Naturally.

Introduce:

Another salesperson.

Operations contact.

Director.

Account Manager.

Technical person.

Attend important reviews together.

Make sure customer history is recorded properly.

Let the customer experience the capability of the wider company.

This is particularly important if the key person is the owner.

A company becomes far more robust when customers trust the organisation rather than one personal contact.

Do not suddenly swarm the customer

There is a balance.

You do not need six people joining every account meeting to prove resilience.

That wastes everybody's time.

Build sensible relationship coverage.

Maybe:

Primary commercial contact.

Operational contact.

Senior sponsor.

Enough that the customer knows where to go if one person disappears.

Step 5: Spread supplier and adviser relationships too

The same applies outside sales.

Does only one person know:

Your accountant?

Insurance broker?

Solicitor?

Bank manager?

Landlord?

Critical manufacturer?

IT provider?

Key subcontractor?

If the relationship matters, somebody else should at least know:

Who they are.

What they do.

Where the agreement sits.

How to contact them.

What current issues exist.

Again:

Not everybody.

Enough people.

Step 6: Fix access before it becomes an emergency

This should be boring.

That is good.

Identify the accounts capable of seriously disrupting the company if access is lost.

Banking.

Finance.

Payroll.

HR.

Cloud storage.

Domain.

Website.

CRM.

Key supplier portals.

Important social accounts.

NCSC's April 2026 small-organisation guidance specifically highlights banking, HR and payroll, cloud storage, websites and other important online services and recommends regularly reviewing who has access. It also advises against leaving responsibility for cyber security with a single person.

You want:

Appropriate separate user accounts.

More than one suitably authorised administrator where sensible.

Secure recovery arrangements.

Managed access.

Clear offboarding.

Not:

“Dave has the password.”

Do not reduce key-person risk by wrecking cyber security

The answer is not:

Everybody gets administrator access.

Passwords pasted into Teams.

Bank details in a shared spreadsheet.

That merely exchanges one risk for another.

Resilience and security need to coexist.

Use:

Proper permissions.

Password-management tools where appropriate.

Role-based access.

Documented recovery routes.

Separate administrator accounts.

Your IT provider or security adviser can help for critical systems.

Step 7: Spread authority

If an Operations Director is expected to run operations, decide what they can approve.

If Finance is responsible for paying suppliers, make sure banking and approval structures can continue appropriately when one person is absent.

If Sales owns routine commercial negotiations, define the boundaries.

This is not about eliminating control.

It is about avoiding a control system whose entire design is:

Ask Martin.

A good authority structure answers:

Who can decide?

Within what limit?

What requires a second approval?

What escalates?

What happens if the normal approver is unavailable?

Those questions should be answered before somebody disappears.

Step 8: Remove unnecessary specialist dependency

This is where systems and automation can help.

Suppose only one person knows how to produce the weekly report because it requires:

Four exports.

Three spreadsheets.

Two manual reconciliations.

And one ritual sacrifice.

You could cross-train somebody else.

Good.

You could also ask:

Why is the process like this?

Perhaps Article #70 applies.

Could it be:

Simplified?

Integrated?

Automated?

Redesigned?

The best key-person-risk intervention is sometimes eliminating the specialised task entirely.

Do not preserve complexity just so two people can understand it

This is worth emphasising.

Process is complex.

One person understands it.

Leadership decides:

“We need another person to understand it.”

Maybe.

But first ask whether it should remain complex.

Agency asks:

Is there a better way?

If a process can be reduced from eleven manual steps to three standard ones, you reduce:

Training demand.

Error.

Time.

Dependency.

Do not replicate avoidable complexity.

Step 9: Separate role risk from person risk

This distinction is useful.

Suppose your Operations Director leaves.

Risk exists because:

The Operations Director role is critical.

That may be unavoidable.

But person-specific risk exists if:

Nobody else understands it.

No deputy exists.

No systems exist.

No information exists.

Customers only know them.

Reduce the second.

You cannot design a business where senior leadership suddenly disappearing causes zero inconvenience .

You can stop it causing paralysis.

Step 10: Recruit with succession in mind

Not every hire needs to be someone's successor.

But look at capability depth.

Suppose you have one excellent estimator.

Next hire?

Maybe another estimator becomes strategically more valuable than another salesperson, even if Sales is louder about needing help.

Workforce planning should consider:

Current workload.

Growth.

Scarcity of skills.

Retirement.

Turnover.

Critical-role cover.

CIPD treats succession planning as part of broader workforce and talent planning, specifically linking business-critical roles with recruitment, development and retention decisions.

That is much more useful than thinking about succession only when somebody hands in their notice.

Do not assume succession means promotion

Perhaps your Technical Director disappears.

Their responsibilities could be split between:

Two internal employees.

External consultant.

Another director.

Recruitment.

Temporary specialist support.

Succession does not always mean identifying one replacement human in advance.

The objective is continuity of the capability .

Be flexible.

Planned succession is much easier than emergency succession

You know someone intends to retire in eighteen months.

Excellent.

That is a gift.

Use the time.

Identify what they know.

What relationships they hold.

What nobody else can do.

What should transfer.

Who needs experience.

Which customers need introductions.

Do not spend seventeen months saying:

“We'll really miss Brian.”

and the final month asking:

“Brian, could you document 34 years of knowledge before Friday?”

That is not succession planning.

That is archaeology with a deadline.

Retention is part of key-person-risk management

If somebody is difficult to replace, keeping them matters.

Article #73 covered retention in depth.

For a key person, understand:

Are they engaged?

Paid fairly?

Overloaded?

Developing?

Do they have a credible future?

What might cause them to leave?

Would you know before the resignation arrived?

Retention reduces probability.

It does not remove the risk.

Do not try to solve key-person risk with golden handcuffs alone

Pay them more.

Give shares.

Bonus.

Long notice period.

Maybe useful.

None guarantees permanent availability.

They can still:

Become ill.

Have a family crisis.

Retire.

Change career.

Move country.

Die.

Decide they have had enough.

Retention tools can reduce avoidable loss.

You still need continuity.

Long notice periods are not a substitute for resilience either

Perhaps your contract requires three or six months' notice.

Useful.

It may allow time for transition.

But:

The employee could be placed on leave.

Relationships can deteriorate.

They may be mentally checked out.

Illness does not provide notice.

You still need business capability beyond the individual.

Consider external backup for highly specialist roles

A small company cannot duplicate every specialist employee internally.

That would be wildly expensive.

Perhaps you employ one:

IT specialist.

Technical consultant.

Health and safety professional.

Payroll person.

In some situations, external backup may be sensible.

A retained specialist.

Trusted contractor.

Professional firm.

Partner organisation.

Someone capable of stepping in or supporting transition.

The principle appears explicitly in ICAEW's July 2026 alternate guidance for sole practitioners. ICAEW recommends appropriate alternate arrangements so clients and critical work can continue if a sole principal becomes incapacitated or dies, including clarity around skills, capacity, access and authority. That guidance is specific to accountancy practices and certain regulated situations, but it provides a useful real-world example of formal backup capability for a genuinely critical person.

Your industry may have its own version.

Regulated or licensed roles need special attention

Some dependencies cannot simply be delegated because:

The person holds a statutory appointment.

Licence.

Professional registration.

Authorisation.

Specific competency.

In those cases, the business needs to understand:

What the requirement actually says.

Who else could qualify.

Whether temporary arrangements exist.

Which regulator or customer needs notifying.

How long replacement could take.

Use appropriate legal, regulatory or professional advice.

Do not assume:

“Steve showed Dave how he does it”

creates authority where the law, licence or contract says otherwise.

Key-person insurance can protect the finances

Insurance can be appropriate where the loss of a particular individual could create a serious financial impact.

Business.gov.uk describes key-person insurance as cover against losses associated with a key individual becoming critically ill or dying where the business relies heavily on that person.

That can provide valuable money for things such as:

Recruitment.

Interim management.

Debt.

Lost profit.

Business stabilisation.

The exact cover, definitions, exclusions, tax treatment and structure require appropriate insurance and professional advice.

But understand what insurance cannot do.

Insurance cannot download someone's brain

A policy cannot:

Train their successor.

Explain the customer history.

Provide administrator access.

Take over the relationship.

Finish the technical project.

Lead the department.

Approve payroll.

Money buys time and options.

It does not remove operational dependency.

Treat key-person insurance as one layer.

Not the solution.

One of the best risk controls is testing the business without the person

Once you believe cover exists, test it.

Planned absence is ideal.

The key person takes leave.

They do not answer routine questions.

The deputy runs the process.

What happens?

Document:

What stopped?

What took much longer?

What information was missing?

What authority was unclear?

What customer became nervous?

What required emergency access?

Then improve the system.

Business-continuity guidance recommends exercising and reviewing continuity arrangements rather than assuming a written plan will work when required.

A continuity plan that has never been tested is a theory.

Start with a day, then a week

You do not need to simulate the CFO disappearing for six months next Tuesday.

Take stages.

Can somebody else run:

Payroll this month?

The management meeting?

The key customer review?

The pricing process?

The supplier order?

Then perhaps:

Two weeks of genuine holiday cover.

Confidence develops through use.

The business learns.

The successor learns.

The key person learns what they were still holding unnecessarily.

The key person must cooperate with reducing their own importance

This can become psychologically interesting.

Some people love being indispensable.

Not only owners.

Employees too.

They become:

The only person who knows.

The only person customers trust.

The only person allowed to touch the spreadsheet.

That indispensability can create:

Security.

Status.

Power.

Identity.

So documentation requests get delayed.

Cross-training never quite happens.

Knowledge remains guarded.

Managers need to be alert to this.

The conversation should not be:

“We're trying to make you replaceable.”

You are building:

Resilience.

Progression.

Holidays without interruption.

A stronger team.

An opportunity for the key person to move into more valuable work.

Nobody should need to remain operationally trapped in their current job to prove their worth.

Reward people for building capability beneath them

This matters.

A manager should not become less valued when their team needs them less for routine work.

That is backwards.

One sign of excellent management is:

Their people become stronger.

Knowledge spreads.

Decisions improve.

The department keeps running when they leave.

If your reward system celebrates heroic firefighting but ignores capability building, guess what managers will optimise for?

Heroics.

Beware the “hero employee”

Every company loves the person who saves the day.

System breaks?

They fix it.

Customer furious?

They rescue it.

Deadline impossible?

They stay until midnight.

Useful person.

But if the same hero repeatedly saves the same type of problem, investigate.

Why does the organisation keep requiring heroics?

A resilient business should increasingly convert hero knowledge into normal organisational capability.

Heroes are excellent during genuine emergencies.

They should not be the business model.

The owner's behaviour matters here too

You cannot tell managers:

“Make sure your teams don't depend on individuals”

while every manager depends on you.

Model it.

Take proper leave.

Transfer authority.

Share information.

Introduce other people into relationships.

Document important things.

Reduce your own Fixer Loop.

Article #78 asked whether you own a business or have built yourself a job.

Key-person resilience is one of the clearest ways of moving the answer towards:

Business.

Key-person risk affects growth

Imagine doubling the company.

One estimator currently produces every complex quote.

What happens?

They become twice as busy.

Eventually:

Delay.

Errors.

Bottleneck.

Recruit another salesperson if you like.

All that does is create more work for the estimator.

Scale-readiness Article #76 applies here.

Before increasing demand, find critical people whose capacity does not scale easily.

Build capability ahead of growth.

It also affects saleability

Potential buyers care about whether the company can continue after important people leave.

British Business Bank's current sale guidance explicitly warns that heavy reliance on the owner can make an exit less viable. The same commercial logic extends beyond the founder: a purchaser will care if crucial sales, customer, technical or operational capability is dangerously concentrated in individuals.

Ask:

What would a buyer worry about if they interviewed our management team tomorrow?

That is often a useful way to identify hidden dependencies.

A key-person register can be very simple

You do not need enterprise risk software.

For each critical role, capture:

Who is the key person?

What business capability depends on them?

What is the impact of 30 days' absence?

Who can currently cover?

How capable is that cover?

What knowledge needs transferring?

What access or authority needs addressing?

What relationships need widening?

What is the realistic replacement time?

What action are we taking?

Who owns the action?

When will we test it?

That is enough to turn:

“We'd be screwed if Jane left”

into something manageable.

Review it when the business changes

Key-person risk moves.

You recruit.

Promote.

Automate.

Lose employees.

Open locations.

Win major customers.

Introduce software.

Acquire companies.

Someone who was critical last year may no longer be.

Someone else may have quietly become indispensable.

CIPD's succession guidance stresses that planning needs to reflect both current critical roles and the capabilities the organisation will require as strategy evolves.

Review regularly.

Not only when somebody resigns.

A practical key-person risk audit

If I were doing this with an established small business, I would use five stages.

Stage 1: Identify

Ask managers:

Which individual's 30-day absence would create the most disruption?

Do not restrict them to senior people.

Compare the answers.

Stage 2: Diagnose

For each key person, identify the dependency:

Knowledge?

Capability?

Relationship?

Authority?

Access?

Capacity?

Leadership?

Most people will have more than one.

Stage 3: Prioritise

Which dependencies could materially affect:

Customers?

Revenue?

Cash?

Compliance?

Safety?

Business continuity?

Deal with those first.

Stage 4: Reduce

Choose the right intervention:

Document.

Cross-train.

Develop successor.

Spread relationships.

Change authority.

Fix access.

Automate.

Simplify.

Create external backup.

Insure financial exposure.

Stage 5: Test

Remove the person temporarily where practical.

See whether the solution works.

Then improve it.

That is key-person risk management.

Not a document.

A 90-day reduction plan

Do not attempt to remove every single dependency at once.

Pick perhaps your highest three.

For example:

Risk 1: Complex estimating depends on Technical Director

Over the next 90 days:

Second estimator shadows all complex quotes.

Pricing logic documented.

Second estimator independently prepares five quotes for review.

By quarter end, at least 60% of complex quotes can be produced without the Technical Director.

Risk 2: Largest customer relationship held only by owner

Over 90 days:

Operations Director attends account reviews.

Commercial history fully recorded.

Customer receives alternative senior contact.

Owner stops being default operational contact.

Risk 3: Payroll dependent on one Finance Manager

Over 90 days:

Deputy trained.

Process documented.

Required secure system access created.

Deputy runs one complete payroll cycle with Finance Manager observing.

Those are real outcomes.

Much better than:

“Improve business continuity.”

The goal is not to make talented people unimportant

This needs saying.

A brilliant employee should matter.

Their absence should be felt.

The company should miss:

Their judgement.

Experience.

Leadership.

Relationships.

Talent.

You are not trying to create a business where people are interchangeable cogs.

You are trying to create a business where one person's unexpected absence does not unnecessarily threaten everybody else's livelihood.

That is completely different.

The strongest people often become more valuable after dependency reduces

Once a key person is no longer spending half their week being the only person capable of performing routine critical work, they can often move upwards.

They can:

Develop others.

Improve systems.

Solve more difficult problems.

Lead.

Innovate.

Think.

The business gains resilience.

The employee gains room to grow.

That is an excellent outcome.

Key-person risk is often invisible precisely because the key person is so reliable

They never miss.

Never take much leave.

Always answer.

Always fix it.

So the company has no reason to discover how dependent it has become.

Until suddenly it does.

The reliable employee leaves.

The owner becomes ill.

The technical specialist retires.

Someone gets recruited by a competitor.

Then the business starts trying to transfer knowledge that is no longer sitting in the building.

Do not wait.

The best time to build redundancy is before it feels necessary

Find your critical people.

Understand what disappears with them.

Move important knowledge into the organisation.

Build another capable person.

Widen important relationships.

Create sensible authority.

Secure access without weakening security.

Develop future successors.

Insure the financial exposure where appropriate.

Test the arrangements.

Then repeat.

The objective is not a business without important people.

It is a business where important people have made the company stronger than their own availability.

That is what resilience looks like.

What Does Good Company Culture Actually Look Like in a Small Business?

Tue, 06 Oct 2026 09:56:42 GMT

Good company culture is not everyone being happy all the time.

It is not free food, Friday drinks, beanbags, away days or a list of values painted beautifully across reception.

A genuinely good culture is one where people broadly understand what is expected, trust how decisions are made, take responsibility for their work, can raise problems without unnecessary fear, receive competent management and see reasonable standards applied consistently .

In a small business, it should show up in ordinary moments:

What happens when somebody makes a mistake
Whether poor performance is dealt with
Whether good people are trusted
Whether managers keep their promises
Whether employees can challenge a bad idea
Whether the owner follows the standards they expect from everybody else
Whether workloads are demanding but realistic
Whether people know who decides what
Whether disagreement becomes useful discussion or political warfare
Whether behaviour matters as much as results

That is culture.

Not what the company says it believes.

What repeatedly happens when real people have to make real decisions.

Culture is what people experience, not what leadership announces

This is one reason the word culture can become frustratingly vague.

Businesses describe themselves as:

Innovative.

Collaborative.

People-first.

High-performing.

Entrepreneurial.

Customer-focused.

None of those words tells me much.

CIPD's current guidance makes a useful distinction between organisational culture and organisational climate . Culture can be difficult to define and measure, while climate focuses more specifically on the policies, practices and behaviours employees actually experience in everyday work.

I think that is an extremely practical way for a small-business owner to look at it.

Do not only ask:

“What is our culture?”

Ask:

“What does it actually feel like to work here?”

That question is much harder to bullshit.

Your real values are visible in what you tolerate

Imagine your website says:

RESPECT

in enormous letters.

One senior salesperson regularly treats colleagues like shit.

Everybody knows.

Management ignores it because the salesperson brings in £2 million a year.

Your value is not respect.

Your value is:

Revenue excuses behaviour.

Perhaps the website says:

ACCOUNTABILITY

but deadlines repeatedly slip without meaningful conversation.

Your culture teaches:

Deadlines are optional.

Perhaps:

WORK-LIFE BALANCE

but the owner sends emails at midnight and expects immediate replies.

The cultural signal is stronger than the slogan.

Employees learn the company primarily from what happens.

What gets rewarded?

What gets challenged?

What gets ignored?

What gets promoted?

What gets laughed off?

What causes somebody to lose credibility?

That is where culture lives.

Good culture does not mean “nice”

This distinction matters enormously.

A company can feel friendly and still have a terrible culture.

Everybody gets along.

Nobody wants confrontation.

Nobody challenges poor work.

Managers avoid difficult conversations.

Deadlines slip.

One employee consistently underperforms and the rest of the team carries them because:

“We don't want to upset anyone.”

That is not a healthy culture.

It is conflict avoidance wearing a smile.

Good culture should include kindness.

But kindness is not the absence of standards.

Sometimes the respectful thing to do is tell somebody clearly that their performance is not good enough and help them improve.

Sometimes it is challenge.

Sometimes it is saying no.

Sometimes it is dealing with behaviour everybody else has quietly tolerated for months.

You can have warmth and accountability.

In fact, the strongest cultures usually need both.

Good culture is clear about what good looks like

People should broadly understand:

What is expected from me?

What am I responsible for?

What standard does the company expect?

What can I decide?

What needs escalating?

How will my performance be judged?

Who do I go to when something is unclear?

Role clarity sounds boring compared with inspirational culture statements.

It matters considerably more.

The HSE's Management Standards identify role clarity as one of six important areas of work design. Its guidance says employees should understand their roles and responsibilities and that organisations should reduce conflicting requirements and provide mechanisms for people to raise concerns about uncertainty.

A company where everyone is wonderfully friendly but nobody knows who owns anything will eventually become frustrating.

Good culture reduces ambiguity where clarity is possible.

People know who owns the outcome

This is accountability.

Not blame.

Accountability means:

You own this outcome.

You have enough authority to influence it.

You have the information and resources required.

We will review what happened.

If something goes wrong, we will understand why.

That is completely different from:

“It's your fault.”

Blame cultures hide problems.

People protect themselves.

They delay bad news.

They document everything defensively.

They avoid risky decisions.

They explain why somebody else caused the problem.

An accountable culture does something more useful.

It asks:

What happened?

What did we expect?

What can we learn?

Who owns the next action?

Where was the system weak?

Was this genuinely an individual-performance problem?

You still deal properly with negligence or repeated poor performance.

But mistakes should not automatically trigger a search for somebody to sacrifice.

People can say “I fucked up” early

That is one of my favourite tests.

Something has gone wrong.

Can the employee say:

“I made a mistake. Here's what happened.”

while there is still enough time to fix it?

Or do they hide it because experience tells them honesty will get them publicly humiliated?

Problems become dramatically more expensive when management learns about them late.

A healthy culture encourages early visibility.

Not because mistakes do not matter.

Because reality matters more.

The objective is not to make everybody feel comfortable about failure.

It is to make truth safe enough to reach the people capable of doing something with it.

People can disagree with the boss

This is especially important in a small business because the owner has disproportionate influence.

You employ people partly because they know things you do not.

Perhaps your Operations Manager understands delivery better.

Finance sees a cash risk you missed.

An employee spots something dangerous.

A salesperson thinks your new offer is badly positioned.

Can they tell you?

Or has everyone learned that disagreeing with the owner creates an exhausting forty-minute defence of why the owner was right in the first place?

Employee voice is more than conducting an annual survey. CIPD defines it as employees having ways to express views, concerns and suggestions and having some genuine influence over matters affecting them. Its April 2026 guidance stresses that leadership and line managers are crucial because voice only works when people believe speaking up is both safe and potentially useful.

If everybody agrees with you constantly, do not automatically conclude you hired brilliantly aligned people.

You may simply have trained them to stop arguing.

Speaking up has to produce something occasionally

You do not have to implement every employee suggestion.

That would be ridiculous.

Sometimes the idea is impractical.

Too expensive.

Strategically wrong.

But if employees repeatedly raise legitimate issues and absolutely nothing changes, they learn something.

Speaking is pointless.

CIPD's current employee-voice guidance describes employee silence as the situation where people choose not to speak despite having something useful to say, sometimes because they believe the risks outweigh the benefits or that their voice will not make a difference.

That can be expensive.

Employees often see operational stupidity long before senior leadership does.

They are standing inside the process.

Ask them.

Then respond.

Even:

“We're not changing this, and here's why.”

is more useful than silence.

Good culture allows disagreement without everything becoming personal

Conflict is not evidence of cultural failure.

Humans disagree.

People have different priorities.

Sales wants flexibility.

Operations wants consistency.

Finance wants control.

Marketing wants speed.

Management involves resolving competing interests.

The objective is not a conflict-free company.

It is a company that disagrees usefully .

Acas's large 2025 study found that 44% of working-age adults in Great Britain had experienced some form of workplace conflict in the previous year. Among people who experienced conflict, conversations with managers and direct informal discussions were the most commonly used resolution approaches.

In a separate 2026 Acas/YouGov employer survey, 52% of respondents who tried to resolve disputes informally said that a workplace culture supporting open conversations helped.

Good culture does not eliminate disagreement.

It gives disagreement somewhere constructive to go.

Managers deal with problems before they become theatre

In weak cultures, management waits.

Employee annoying everybody?

Wait.

Tension between two colleagues?

Wait.

Performance slipping?

Wait.

Then six months later something explodes and suddenly:

HR.

Formal grievance.

Investigation.

Meetings.

Statements.

Solicitors.

Everyone wonders how things became so serious.

Often, they became serious because nobody dealt with them while they were still small.

Good managers notice.

They ask.

They have conversations.

They clarify expectations.

They do not turn every disagreement into a formal process, but they also do not pretend difficult behaviour disappears if ignored long enough.

Acas's current work strongly emphasises earlier, informal resolution where appropriate, noting that unresolved concerns can grow into more difficult and expensive problems.

That is culture in practice.

Not a poster saying:

WE COMMUNICATE OPENLY.

Actual conversations.

Good culture requires competent managers

You cannot build culture purely from the top.

The owner matters enormously.

But employees experience the company through their immediate manager every day.

Does the manager:

Give clear direction?

Keep promises?

Provide useful feedback?

Deal with weak performance?

Recognise strong performance?

Protect employees from unnecessary chaos?

Communicate changes?

Listen?

Make decisions?

CIPD's Good Work Index has repeatedly found strong relationships between employee experience and line-management quality. Its 2025 UK survey of more than 5,000 workers found that positive perceptions of managers were associated with better reported job performance, health and lower intention to leave.

You cannot compensate for weak line management with more company values.

Culture gets delivered through managers.

Managers need enough time to manage

This is another mistake in small businesses.

Promote your best technician.

Give them eight direct reports.

Leave them with their entire previous workload.

Then complain that:

“They're not managing properly.”

When exactly were they supposed to?

Management is work.

One-to-ones.

Feedback.

Planning.

Problem-solving.

Training.

Performance management.

Decision-making.

Communication.

If managing people is permanently fitted around the edges of somebody's “real job”, culture will become inconsistent.

Strong managers need:

Skills.

Authority.

Information.

And enough capacity to actually manage.

Good culture includes fair accountability

Employees notice inconsistency extremely quickly.

Two people make similar mistakes.

One gets hammered.

The other is the owner's favourite and nothing happens.

One employee arrives late repeatedly.

Another gets challenged for five minutes.

One person receives flexibility because management likes them.

Another gets told:

“Rules are rules.”

That is culture.

Fair does not always mean identical.

Different circumstances genuinely require different decisions.

But the reasoning should be defensible.

Good culture does not require employees to agree with every decision.

It does require the organisation to avoid arbitrary treatment.

High performers are not punished for being competent

This connects directly with Article #73.

In many small businesses, good people receive:

More difficult customers.

More unfinished work.

More rescue jobs.

More responsibility.

More people to train.

Why?

Because:

“We know you'll get it sorted.”

Eventually, competence becomes a tax.

A good culture recognises contribution without turning the best employees into the company's universal emergency service.

Capability should lead towards:

Trust.

Development.

Autonomy.

Appropriate reward.

Better opportunities.

Not simply a larger pile of everybody else's problems.

Poor performers are not protected from reality

The other side matters just as much.

A good culture is not one where nobody ever feels uncomfortable.

If an employee repeatedly fails to meet reasonable expectations despite appropriate support, that needs managing.

Otherwise the wider team sees that:

Effort does not matter.

Standards are optional.

Someone else will pick up the work.

Article #64 looked at this from the perspective of repairing damaged culture.

Here, the principle is simpler:

Standards become cultural only when they survive contact with uncomfortable situations.

If standards disappear the moment enforcing them becomes awkward, they were preferences.

Good culture contains trust and autonomy

You hired a capable adult.

Let them increasingly operate like one.

Autonomy does not mean:

Do whatever you want.

It means clear outcomes and sensible boundaries with enough freedom to use judgement.

The HSE's Management Standards include control , defined broadly as how much say employees have over the way they do their work. The standard encourages organisations, where possible, to let people use their skills and initiative and have appropriate influence over how work is performed.

Micromanagement teaches dependence.

Appropriate autonomy develops judgement.

If every £100 decision requires permission from three levels above, do not then complain that employees lack initiative.

The operating environment trained them.

People have the resources to do what you ask

This sounds ridiculously obvious.

Yet companies regularly demand outcomes without providing:

Enough people.

Enough time.

Correct equipment.

Information.

Training.

Authority.

Then treat failure as an attitude problem.

Good culture combines standards with support.

The HSE framework explicitly includes support from organisations, managers and colleagues, access to necessary resources and regular constructive feedback as important conditions of healthy work.

Accountability without support becomes punishment.

Support without accountability becomes indulgence.

Good management needs both.

Workload is demanding without permanently being stupid

Good companies can work extremely hard.

There are busy periods.

Deadlines.

Unexpected problems.

Important customers.

That is business.

But permanent overload becomes cultural too.

If everybody regularly works beyond sensible capacity, one of two messages eventually emerges:

Overwork is how you prove commitment.

Or:

Management does not know how much work we're carrying.

Neither is particularly healthy.

HSE identifies demands, including workload and working patterns, among the six major areas employers should manage when considering work-related stress.

A strong culture can be ambitious.

It can be commercially demanding.

It does not need to normalise permanent unsustainable workload as evidence of loyalty.

People broadly understand why decisions are being made

Small businesses change.

Fast.

New customers.

New systems.

New managers.

Restructures.

Different premises.

Different roles.

You cannot consult everybody endlessly on everything.

Leadership eventually has to lead.

But explain.

Why are we changing this?

What problem are we trying to solve?

What does it mean for people?

What remains unknown?

When will we review it?

HSE's guidance on organisational change similarly emphasises timely information, consultation where appropriate, clarity about likely effects and access to support.

Bad news does not become good news because it was communicated well.

But unexplained change creates unnecessary uncertainty on top of whatever difficulty already exists.

People know enough about where the company is going

You do not need to share every confidential detail.

But employees should understand the broad direction.

What are we trying to build?

What matters this year?

What are the priorities?

What are we not doing?

What does success look like?

This creates context.

Otherwise people optimise their own corner of the business.

Sales pursues everything.

Operations protects efficiency.

Finance restricts expenditure.

Marketing chases visibility.

Each function can behave rationally and still pull the company in different directions.

Culture is partly the shared understanding that helps people make locally sensible decisions in service of the wider outcome.

Good culture does not require everyone to be best friends

This is another misconception.

Colleagues need:

Respect.

Professionalism.

Trust.

Useful communication.

They do not need matching friendship bracelets.

You can work brilliantly with someone you would never choose to spend Saturday night with.

That is fine.

Do not confuse social closeness with team effectiveness.

Likewise, do not force artificial fun onto adults.

Some employees will love:

Summer parties.

Christmas events.

Team lunches.

Others would rather receive the free afternoon and go home.

Both can belong in an excellent culture.

Recognition is specific, not theatrical

Good work should be noticed.

But recognition does not require:

Awards ceremonies.

Employee of the Month.

A gong.

A LinkedIn photograph.

Sometimes it is:

“That handover was excellent. You picked up the commercial risk before it became a problem.”

Specific recognition tells employees what the organisation values.

It also reinforces standards.

A culture where management only appears when something goes wrong eventually teaches people that good work is invisible.

Notice it.

Information travels instead of becoming political currency

Weak cultures create information hoarding.

People know things because knowledge creates influence.

Departments protect themselves.

Managers avoid sharing bad news.

Employees hear decisions through rumours.

Good culture does not mean every person knows everything.

It means people receive the information they reasonably need to do their jobs and understand relevant decisions.

This becomes increasingly important as businesses grow.

Informal proximity stops working.

You can no longer rely on everyone overhearing the right conversation.

Communication has to become more deliberate.

CIPD's communication guidance emphasises multi-directional dialogue and the central role line managers play in effective workplace communication.

The owner obeys the culture too

This is perhaps the biggest small-business difference.

Large organisations can sometimes absorb hypocrisy from one senior leader for a while.

In a 25-person company, the owner is highly visible.

If you say:

“Speak openly.”

then become defensive every time somebody challenges you, people notice.

If you say:

“Family matters.”

then repeatedly interrupt annual leave, people notice.

If you demand punctuality and stroll into meetings late, people notice.

If managers are expected to follow purchasing rules while you buy things randomly, people notice.

You cannot exempt yourself from the behaviour you are trying to establish.

Employees will usually believe what the owner does before what the handbook says.

Culture is shaped by who gets promoted

Want to know what behaviour the company values?

Look at who progresses.

Do your future managers get promoted because they:

Develop people?

Take responsibility?

Communicate well?

Deliver results without destroying everyone around them?

Or simply because they are technically excellent and have worked there longest?

Promotion is a cultural signal.

Every promotion tells employees:

This is what success looks like here.

Choose carefully.

Hiring is a cultural decision too

Skills matter.

Experience matters.

But when someone joins a small team, behaviour spreads.

One technically brilliant person who:

Blames others.

Withholds information.

Treats colleagues badly.

Creates drama.

can consume enormous management attention.

This does not mean only hiring people who “fit in”.

That phrase can become an excuse for recruiting clones.

Different perspectives, backgrounds and personalities can strengthen a business.

The question is whether somebody can operate constructively inside the organisation's expected behaviours.

Difference is useful.

Destructive behaviour is not the same thing as difference.

Induction teaches the real culture immediately

New employee arrives.

You give them a handbook containing company values.

Then they watch.

What happens when somebody disagrees?

How do managers speak to people?

Do meetings start on time?

Do people take responsibility?

Does everybody quietly ignore a particular director's behaviour?

Within days, they are learning the actual culture.

CIPD's July 2026 induction guidance notes that early experiences influence how effectively new recruits integrate into the team and their wider job satisfaction.

Do not only explain the culture.

Demonstrate it from day one.

Good culture is not one culture everywhere

This needs nuance as businesses grow.

Your Sales team may naturally feel different from Finance.

Workshop culture differs from Head Office.

One branch may have a slightly different rhythm from another.

That is normal.

You do not need to manufacture identical personalities across departments.

What should remain consistent are the important behavioural principles.

For example:

We tell the truth about problems.

We take responsibility.

We treat people respectfully.

We challenge poor performance.

We share relevant information.

We do what we say.

The personality can vary.

The underlying standards should not.

Microcultures tell you about managers

If one department feels dramatically different from the rest of the company, investigate.

Perhaps that manager has built something excellent.

Learn from them.

Or perhaps:

Turnover is higher.

People are quieter.

Information is controlled.

Problems are hidden.

Standards inconsistent.

Then your company culture may not really be company-wide.

You have a managerial microculture.

This is another reason managers matter so much.

Your values do not reach employees directly.

Managers translate them through daily behaviour.

Good culture helps people perform

Culture should not become detached from the commercial purpose of the organisation.

You are running a business.

A good workplace should help people do good work.

CIPD's 2025 Good Work Index defines good work across dimensions including reward, work-life balance, job design, workplace relationships, employee voice, health and wellbeing, while finding positive employee experiences associated with stronger reported motivation and performance and lower intentions to leave.

The objective is not to create the world's nicest place to avoid doing any work.

It is to create conditions where capable people can consistently perform well without unnecessary organisational stupidity getting in their way.

Good management practices and good culture overlap

ONS research provides another useful clue.

Its Management and Expectations Survey measures structured practices around areas such as performance monitoring, targets, training and managing underperformance. Higher management-practice scores are statistically associated with higher productivity, while 64% of firms in the latest published analysis reported consulting employees about areas for improvement. ONS describes these relationships carefully and they should not be interpreted as proof that a particular management practice automatically causes a particular productivity gain.

Still, there is an obvious practical connection.

Good culture is not vague atmosphere.

It is reinforced by how the business actually manages.

Good culture should survive the owner leaving the room

This may be the best test.

You leave.

What happens?

Do people still:

Tell the truth?

Follow standards?

Take responsibility?

Treat customers properly?

Challenge bad work?

Help colleagues?

Or does behaviour change because:

“Adam isn't here today.”

If the culture only exists under direct observation from the owner, that is not culture.

That is supervision.

A mature culture helps people make good decisions when nobody senior is watching.

It should survive pressure too

Culture is easy when:

Revenue is good.

Nobody is overloaded.

Customers are happy.

No difficult decisions exist.

Then comes:

Cash pressure.

A major mistake.

Redundancy.

Lost customer.

Serious complaint.

Performance problem.

That is when your culture becomes visible.

Do leaders:

Tell the truth?

Blame?

Hide information?

Protect favourites?

Abandon stated principles?

Or do standards still broadly hold?

Pressure tests culture.

The result may not always be perfect.

But it will be revealing.

You can measure culture without trying to reduce it to one number

I would not obsess over a single:

Culture Score: 8.7/10

People are more complicated than that.

Use several forms of evidence.

Look at:

Regrettable employee turnover.

Sickness absence.

Grievances.

Conflict.

Customer complaints linked to behaviour.

Employee suggestions.

Internal promotions.

Performance issues.

Exit feedback.

Manager effectiveness.

Then talk to people.

CIPD's employee-voice guidance specifically notes that effective voice normally requires multiple complementary channels rather than a single survey.

Likewise, the HSE advises using more than one source of information when assessing working conditions rather than depending solely on a questionnaire.

A survey can tell you where to look.

Conversation tells you more.

Behaviour tells you even more.

Ask better culture questions

Instead of asking employees:

“Are you happy with our culture?”

ask questions they can actually answer.

What behaviour gets rewarded here?

What happens when somebody makes a mistake?

What behaviour gets tolerated that shouldn't?

Can you disagree with your manager?

Can your manager disagree with the owner?

What happens when somebody performs badly?

Do you know what you are responsible for?

Do you have enough authority to do it?

What happens when workload becomes unrealistic?

Do managers keep promises?

Would you tell us early if something serious went wrong?

What would a new employee learn about this company after two weeks that is not written anywhere?

Those answers will teach you considerably more than asking whether people think the company has:

“A positive culture.”

The good-culture test

If I wanted to understand a small company's culture quickly, I would look for ten things.

I would want people to understand what good performance looks like and who owns what.

I would want managers who can actually manage.

I would want employees to be able to raise problems early.

I would expect respectful disagreement rather than permanent artificial harmony.

I would want poor performance dealt with fairly.

I would want strong performance recognised and trusted.

I would want reasonable autonomy within clear boundaries.

I would want workloads, resources and expectations to make sense together.

I would want leadership decisions to be explainable even when they are unpopular.

And I would want the owner to behave as though the standards apply to them too.

None of those requires a beanbag.

A good culture is predictable in the right ways

Employees should not need to wake up wondering:

Which version of the owner are we getting today?

Will this mistake be treated completely differently from yesterday's?

Does this rule apply this week?

Can I raise this without getting attacked?

Good culture creates behavioural predictability .

Not rigid uniformity.

People broadly know:

How problems are handled.

How decisions get made.

What matters.

Where authority sits.

What behaviour crosses a line.

That predictability creates trust.

But it should remain adaptable

Strong culture should not become:

“This is how we do things here.”

used as a weapon against change.

Businesses need to evolve.

New people should improve things.

Technology changes.

Customers change.

Markets change.

The culture should provide stable principles without fossilising every method.

For example:

We value accountability.

Good.

That does not mean using the same accountability process forever.

We value customer service.

Good.

That does not mean answering every email manually forever.

Values should guide decisions.

Not preserve obsolete processes.

A simple culture review for a small business

You do not need a giant culture-transformation programme.

Start by comparing what the company says with what people actually experience.

Review the stated values, if you have them.

Then observe:

How meetings work.

How managers behave.

How performance is handled.

How mistakes are discussed.

How decisions are communicated.

Who gets promoted.

Who gets listened to.

Who gets tolerated.

What people complain about repeatedly.

What your best employees appreciate.

What departing employees say.

Where conflict repeatedly appears.

Then identify the two or three behavioural gaps creating the biggest difference between the company you intend to be and the company employees currently experience.

Work there.

Culture changes through repeated evidence.

Do not launch new values unless you need them

Another culture workshop is not automatically the answer.

Perhaps your existing values are perfectly good.

The problem is that nobody behaves according to them.

You do not need:

Accountability 2.0.

You need to manage accountability.

Likewise, if the business genuinely has no clear principles, defining them can be useful.

But keep them practical.

Could an employee use this value to decide how to behave?

If not, it may simply be branding.

Culture becomes real through consequences

This is the final connection to Article #64.

You cannot announce a culture.

You create one through repeated consequences.

When somebody speaks honestly about a mistake and is treated fairly, that is evidence.

When a manager deals constructively with poor performance, evidence.

When a high-performing bully is challenged despite their revenue, evidence.

When the owner admits they were wrong, evidence.

When an employee makes a sensible decision without seeking permission and management supports them, evidence.

When leadership explains a difficult decision clearly, evidence.

Enough repeated evidence becomes expectation.

Expectation becomes normal behaviour.

That is culture.

You will never create a perfect culture

Nor should you waste time trying.

People will still disagree.

Managers will make mistakes.

Someone will feel unfairly treated.

Communication will occasionally fail.

A workload will become ridiculous.

You will recruit the wrong person.

Somebody will leave.

Human organisations are messy.

Good culture does not mean nobody experiences a problem.

It means the organisation has enough trust, capability, clarity and honesty to deal with problems without every difficulty becoming political, personal or catastrophic.

So what does good company culture actually look like?

It looks surprisingly ordinary.

People know what is expected.

Managers have useful conversations.

Employees take responsibility.

Problems travel upwards early.

Decisions travel downwards appropriately.

Poor performance gets managed.

Good people get trusted.

Disagreement is allowed.

People can challenge the owner.

Workload matters.

Promises matter.

Behaviour matters.

The stated values resemble what actually happens.

And when the owner leaves the building, people continue behaving like the same company.

That is considerably more valuable than a brilliant set of values on the wall.

Because culture is not what you wrote.

It is what your people have learned they can expect.

How Do You Know If New Business Software Is Actually Worth It?

Tue, 06 Oct 2026 09:49:19 GMT

New business software is worth buying when the measurable improvement it creates is greater than the full cost and complexity of introducing it .

Not when the demo looks impressive.

Not because it has AI in the name.

Not because your competitor uses it.

Not because somebody at a networking event told you their CRM changed their life.

And definitely not because your current software annoys you occasionally.

The question is:

What gets measurably better if we introduce this?

Perhaps:

Employees save meaningful time
Fewer errors occur
Information moves faster
Customers receive a better service
Capacity increases
Management gets better information
Revenue improves
Margin improves
Risk falls
Several existing systems can disappear

Then ask:

What will it genuinely cost us to achieve that improvement?

Licence fees are only the beginning.

You also need to consider:

Implementation.

Migration.

Integrations.

Training.

Internal time.

Temporary productivity loss.

Customisation.

Support.

Maintenance.

Additional licences.

Data clean-up.

Running two systems during transition.

And eventually:

What happens if you want to leave?

A £400-a-month software product can easily become a considerably more expensive business decision.

That does not mean you shouldn't buy it.

It means you should evaluate software like an investment.

Not an app.

Start with the business problem

This is the single biggest rule.

Do not begin with:

“We need a new CRM.”

Why?

What is wrong?

Perhaps:

Salespeople do not record follow-ups.

Customer information sits in five places.

Nobody knows which opportunities are genuine.

Quotes take too long.

Management cannot forecast revenue.

Customer handovers are poor.

Good.

Now we have problems.

A CRM may solve some of them.

Or perhaps:

The existing CRM already does everything required and nobody uses it properly.

That happens too.

Buying different software does not automatically fix weak management.

The UK government's SME Digital Adoption Taskforce identified exactly this wider implementation challenge. Its 2025 final report said smaller firms frequently find technology adoption too difficult or costly, lack sufficient expertise and execution support, and perceive switching between technologies as risky. The government's June 2026 update continues to focus support on capability, cost and awareness rather than assuming software availability alone solves adoption.

Technology adoption is not primarily a shopping problem.

It is an organisational-change problem with software in the middle.

Do not ask what the software can do

Software demonstrations are dangerous.

Someone shares their screen.

Everything works perfectly.

Buttons glide.

Dashboards update.

Automations fire.

Apparently:

“This will completely transform how you work.”

Perhaps.

But a good salesperson can spend an hour showing you capabilities your company will never use.

Ask instead:

What problem are we specifically buying this to solve?

Then make the vendor demonstrate that .

If you want to reduce quotation turnaround from five days to one day, show me exactly how.

If you want managers to see project margin before jobs finish, show me.

If you want enquiries automatically allocated by region, demonstrate the workflow.

Do not spend an hour being impressed by features unrelated to the business case.

Define the current baseline

You cannot prove improvement if you do not know what happens today.

Suppose the problem is:

Sales administration takes too long.

How long?

Five hours a week?

Fifty?

Across how many people?

Or:

Our current system creates errors.

How many?

What do they cost?

Or:

Customers wait too long.

How long do they currently wait?

Before buying software, establish the baseline.

For example:

Salespeople collectively spend 22 hours a week entering and re-entering data.

Average quote turnaround is 3.8 days.

Twelve per cent of jobs start with missing customer information.

Finance spends 14 hours per month manually creating a management report.

Now implementation can be measured against something real.

Without a baseline, six months later everybody says:

“It definitely feels better.”

Maybe.

Maybe not.

Decide what success will look like before you sign

Write down the intended outcome.

For example:

Within three months of implementation, reduce manual sales administration from 22 hours per week to below 10 while maintaining data accuracy.

Or:

Reduce average quote turnaround from 3.8 days to below one working day.

Or:

Create one reliable customer record accessible to Sales, Operations and Finance and eliminate the three existing duplicated spreadsheets.

Now we know what the purchase is for.

This matters because software projects drift.

Originally:

Improve project visibility.

Six months later:

We have implemented the platform.

Those are not the same outcome.

Installing software is not success.

The business result is success.

Software can absolutely improve productivity

The potential is real.

The UK government's SME Digital Adoption Taskforce cites previous Enterprise Research Centre evidence suggesting firm-level productivity improvements of between 7 and 18 per cent for individual technologies, depending on what was adopted. That should not be treated as a promise that buying a CRM increases your productivity by a particular percentage, but it does reinforce the wider potential of well-chosen digital technology.

The OECD's April 2026 review of UK SME technology adoption similarly concluded that the UK performs relatively strongly in mature technologies such as cloud computing and data analytics, while adoption of management-support tools such as CRM and ERP remains more limited among smaller SMEs. It also stresses that skills, management capability and advisory support are important complements to technology adoption.

The important words are:

Well chosen.

And:

Well implemented.

Buying software and gaining value from software are two different events.

Calculate the value of time saved

This is usually the easiest benefit to quantify.

Suppose 12 employees each spend one hour a week on an administrative process the new system should remove.

That is:

12 hours per week.

Across 48 working weeks:

576 hours.

If the fully loaded cost of those employees averages £30 per hour, the theoretical labour value released is:

£17,280 per year.

Useful.

But be careful.

That does not mean £17,280 magically appears in the bank.

The employees are still employed.

You have created capacity .

Now ask:

What happens to those 576 hours?

Can employees:

Serve more customers?

Produce more output?

Avoid overtime?

Delay another hire?

Sell more?

Improve service?

Work more reasonable hours?

If the time simply gets absorbed by slightly more email, the financial return is much weaker.

Time saved only becomes commercially valuable when the business knows what the released capacity is for.

Separate cash savings from capacity savings

This distinction improves software business cases enormously.

Cashable savings

Costs genuinely disappear.

For example:

Software replaces another £8,000 annual subscription.

Temporary administration spend falls.

Overtime reduces.

External processing fees disappear.

A planned hire is no longer required.

Those savings can affect cash directly.

Capacity savings

Employees gain time.

Still valuable.

But the commercial value depends on what the capacity enables.

Perhaps five employees save four hours each week.

That could be transformative.

But only if leadership actually redirects the time.

Do not present every saved hour as immediate profit.

That is how ridiculous ROI calculations get created.

Revenue improvement can be valuable too

Software may create value by increasing revenue rather than reducing cost.

Perhaps a new CRM improves follow-up.

Quoting software reduces response time.

E-commerce enables customers to buy more easily.

Scheduling software increases the number of jobs completed.

Marketing automation improves conversion.

Fine.

Model it conservatively.

Suppose software is expected to generate:

Twenty additional qualified opportunities each month.

Historical conversion:

20 per cent.

Average gross profit per customer:

£2,000.

Theoretical additional monthly gross profit:

Eight thousand pounds.

Useful hypothesis.

Now test it.

Do not simply insert:

“Revenue increase: 20%”

into the software proposal because the vendor's brochure says customers grow faster.

Your business case should use your economics.

Error reduction has a value

Manual systems create mistakes.

Duplicate entry.

Incorrect addresses.

Missed follow-ups.

Incorrect orders.

Wrong prices.

Lost paperwork.

Payroll mistakes.

If software genuinely reduces recurring errors, estimate the value.

What does each error create?

Rework.

Credits.

Wasted labour.

Customer complaints.

Lost customers.

Management time.

Again, use a reasonable estimate.

Not fantasy.

If you currently spend £20,000 annually correcting a known category of error and a proven workflow can eliminate most of it, that belongs in the business case.

Better information has a value, but it is harder to calculate

This is where management software can create enormous value without obvious time savings.

Suppose the new system means managers can see:

Project margin.

Sales pipeline.

Capacity.

Debtors.

Stock.

Customer profitability.

in near real time.

Previously, decisions were made using information three weeks old.

What is better information worth?

Hard to calculate exactly.

But ask what decisions it improves.

Perhaps you identify margin leakage earlier.

Prevent over-recruitment.

Reduce stock.

Spot a cash problem.

Stop accepting unprofitable work.

Article #75 looked at exactly this issue through management accounts.

Information has value when it changes a decision.

A dashboard nobody uses has almost none.

Customer experience can improve too

Software may reduce:

Waiting.

Repeated questions.

Lost information.

Poor handovers.

Missed appointments.

Customers having to explain themselves twice.

That can create:

Retention.

Referrals.

Higher conversion.

Fewer complaints.

Do not assume every digital interaction automatically improves customer experience.

Some companies install software primarily to make life easier internally and accidentally make customers fight a chatbot for twenty minutes to speak to a human.

Measure customer impact from the customer's side too.

Now calculate the full cost

This is where the £499-a-month miracle starts becoming slightly more realistic.

Licence cost

Obvious.

But check the structure.

Per user?

Per location?

Per contact?

Per transaction?

Per feature?

Additional storage?

API access?

Premium support?

Security features?

AI credits?

Automation runs?

The attractive advertised price may cover the version nobody in a serious business actually needs.

The NCSC specifically warns organisations to check which licence tier includes the security features they require, because features such as mandatory multi-factor authentication or single sign-on may sit inside differently priced plans.

Compare the actual required licence.

Not the homepage price.

Implementation cost

Who sets it up?

Your employees?

The supplier?

A consultant?

How many hours?

Some systems are genuinely:

Create account.

Import contacts.

Go.

Others require months of work.

ERP.

Complex CRM.

Project-management systems.

Manufacturing software.

Finance systems.

Implementation can easily outweigh the first year's licence cost.

Include it.

Data migration

Where is the existing information?

Spreadsheets?

Old CRM?

Accounting platform?

Local drives?

Email?

Can it be exported?

Is it clean?

Who removes:

Duplicates?

Outdated records?

Incorrect fields?

Missing data?

One of the hidden costs of new software is discovering just how bloody awful the old data is.

Do not automatically migrate everything.

Moving ten years of rubbish into a beautiful new database merely produces beautifully organised rubbish.

Integration

What else does this system need to communicate with?

Accounting?

CRM?

Website?

Email?

Project management?

Payroll?

E-commerce?

Reporting?

Calendar?

The demo often shows:

“Yes, we integrate with X.”

What does that mean?

Native two-way integration?

One-way data transfer?

Requires middleware?

Premium plan?

Custom API work?

Only certain fields?

Integration is not binary.

Understand what actually moves.

The fourth-system problem

I see this constantly.

The company has:

CRM.

Project software.

Accounting software.

Spreadsheet.

Then buys another platform to:

“Bring everything together.”

It does not.

Now information exists in five places.

Every new system should answer:

What does this replace?

Not every new product needs to replace something.

Sometimes a genuinely new capability is required.

But if your software stack only ever expands, complexity eventually becomes its own operational problem.

One excellent test is:

Which existing tools disappear if we buy this?

If the answer is:

None,

I want to understand why.

Training cost

People need time to learn.

Who trains them?

How long?

Do managers understand the system deeply enough to support others?

What happens to productivity during the transition?

The OECD's 2026 review of technology adoption in UK SMEs emphasises the complementary importance of management and digital skills, while its wider 2026 SME work identifies time constraints, maintenance costs and skills gaps among the continuing barriers to effective technology implementation.

Training is not something you add at the end.

It is part of the investment.

Internal implementation time

This is frequently ignored because nobody sends you an invoice.

Your Operations Director spends:

40 hours designing workflows.

Finance spends:

20 hours validating data.

Sales spends:

15 hours testing.

Employees spend:

100 hours collectively in training.

That time has a cost.

More importantly, it displaces other work.

Include material internal time in the business case.

Otherwise internally implemented software always looks artificially cheap.

Temporary double-running

For a period, you may operate:

Old system.

New system.

Lovely.

Double entry.

Double licences.

Confusion.

Sometimes necessary while verifying migration and reducing operational risk.

Budget for it.

Do not assume the old platform switches off at midnight on Friday and everyone wakes Monday fully competent in the new one.

Customisation

Be careful here.

Software almost fits.

So:

Custom field.

Custom workflow.

Custom integration.

Custom report.

Custom development.

Six months later you have built a unique piece of software on top of somebody else's standard product.

Sometimes necessary.

But customisation creates:

Cost.

Maintenance.

Implementation risk.

Upgrade complications.

Supplier dependency.

Ask whether the business genuinely needs the custom process.

Or whether the process should change to fit a perfectly sensible standard workflow.

Do not spend £40,000 preserving a stupid process because:

“That's how we've always done it.”

Ongoing administration

Someone needs to own the system.

User accounts.

Permissions.

Fields.

Reports.

Automations.

Updates.

New-starter training.

Departing users.

Data quality.

Support tickets.

Software does not manage itself indefinitely.

An hour a week is still:

Roughly 50 hours a year.

Include ongoing administration where material.

Support cost

What happens when something breaks?

Is support included?

Email only?

Two-day response?

Dedicated account manager?

Paid premium support?

Third-party consultant?

A mission-critical platform with dreadful support creates operational risk.

The cheapest software is not cheap if three employees stop working every time an integration fails.

Contract commitment

Monthly?

Annual?

Three-year contract?

Auto-renewal?

How much notice to cancel?

Price increases?

Minimum users?

Read it.

The financial commitment is not necessarily:

£500 per month.

It may be:

£18,000 that cannot be cancelled for three years.

Different decision.

Switching cost

This is now significant enough that the UK government's SME Digital Adoption Taskforce specifically identifies switching risk, lock-in, unclear costs and data portability as barriers preventing smaller companies adopting digital tools. It recommends clearer, more transparent approaches to moving business data between software providers.

Before entering, ask how you get out.

Can you export:

Customers?

Documents?

Transactions?

History?

Custom fields?

Attachments?

Audit logs?

In what format?

What disappears when the subscription ends?

How long do they retain the data?

How hard would migration be?

An exit plan is not pessimism.

It improves your negotiating position and reduces dependency.

Avoid software lock-in you do not understand

Some lock-in is inevitable.

Employees learn the system.

Processes develop around it.

Integrations connect.

That is normal.

The issue is unrecognised lock-in.

You discover five years later that:

Data cannot be exported cleanly.

Customisations only work through one supplier.

No other platform accepts the format.

Your entire operation depends on the vendor.

Now a 20 per cent price increase becomes difficult to challenge.

Understand the dependency you are creating.

Adoption decides whether the ROI exists

This is perhaps more important than the software itself.

The system can be brilliant.

If people avoid it:

Return to spreadsheets.

Keep their own notes.

Do not complete fields.

Ignore workflows.

Use workarounds.

your theoretical ROI never appears.

The government's SME Digital Adoption Taskforce says effective management and leadership that actively support technology uptake and experimentation are important factors in successful SME adoption, and its evidence review notes that clear internal policies and leadership communication are associated with higher engagement with new technologies.

Software adoption is a management responsibility.

Not an IT announcement.

Ask employees before you buy

Especially the people doing the process every day.

Management says:

“This will save you loads of time.”

Employee says:

“Except it doesn't let us do the one thing we spend half the day doing.”

Useful.

Ask them:

Where does the current process fail?

What must the system do?

What would make it worse?

What exceptions occur?

Which feature really matters?

Employees should not necessarily choose the platform.

But ignoring the people who will use it is an impressive way to spend money badly.

Do not let one employee choose the entire company's software because they like it

The opposite problem.

Someone joins.

Says:

“At my last company we used HubThing Pro Enterprise Ultimate. It was amazing.”

Perhaps.

Different company.

Different processes.

Different scale.

Different requirements.

Evaluate against your business.

Software preference is not strategy.

User experience matters more than feature count

Software A has:

127 features.

Software B:

Which is better?

The one your company can use effectively.

A product can be incredibly powerful and operationally useless because normal employees need fourteen clicks to complete a routine task.

Watch real users perform real work during testing.

Do not judge usability from a polished demo conducted by somebody who has used the software every day for six years.

Configure before customising

This saves enormous pain.

Most decent business software has:

Settings.

Workflows.

Templates.

Permissions.

Fields.

Automations.

Try to solve the process through standard configuration before paying for bespoke development.

Standard software is usually:

Easier to maintain.

Easier to upgrade.

Better supported.

Easier to replace.

The more bespoke your implementation becomes, the more you should understand why that complexity is commercially justified.

Buy for the business you are becoming, not a fantasy company

You do need some headroom.

Replacing the system again in twelve months is expensive.

But do not buy enterprise software designed for:

2,000 employees

because:

“We'll grow into it.”

You currently have 27.

By the time you grow into it, the technology will probably have changed anyway.

Buy for the next realistic stage.

Not the imaginary multinational on your vision board.

Equally, do not knowingly buy something already too small

Cheap software becomes expensive when you outgrow it immediately.

Ask:

How many users can it handle?

Transactions?

Customers?

Projects?

Locations?

Data?

Automations?

What features appear at higher scale?

Does cost increase sensibly?

Could this support the next two or three years under realistic growth?

That is enough horizon for many SME decisions.

Evaluate security according to what the system will hold

A booking app holding:

Names.

Email addresses.

Appointment times.

is different from software holding:

Payroll.

Medical information.

Sensitive HR data.

Financial records.

Commercially sensitive technical documents.

The NCSC advises organisations to assess cloud providers according to how the service will be used and the sensitivity of the information involved, using either its full Cloud Security Principles or a lighter assessment where appropriate.

Security should be proportionate.

Not ignored.

Not turned into a six-month procurement exercise for a basic diary app either.

Ask basic security questions

Depending on the system and risk:

Does it support multi-factor authentication?

Can access be limited by role?

Can departing employees be removed easily?

Are administrative actions logged?

What backup and recovery exists?

How does the vendor handle security incidents?

What independent security assurance exists?

Where is the service hosted?

What happens during outages?

The NCSC recommends building confidence in the provider's security claims and looking for evidence rather than relying solely on marketing assertions.

You do not need to become a cyber-security specialist.

You do need appropriate due diligence.

If it processes personal information, you still have responsibilities

Moving customer or employee data into somebody else's software does not transfer all responsibility to them.

The ICO says organisations acting as controllers must only use processors that provide sufficient guarantees that appropriate technical and organisational measures are in place. The controller is responsible for assessing the processor's competence relative to the nature and risk of the processing and putting an appropriate processor contract in place.

The ICO also explicitly includes decisions about software, applications and services within data protection by design and by default.

For ordinary SME purchases, this often means making sure:

The supplier's data-processing terms make sense.

Security is appropriate.

Personal information is not being used in ways you did not expect.

Access and retention are understood.

If the data or processing is particularly sensitive or high risk, obtain suitable data-protection advice.

Look at supplier viability

This is often overlooked with SaaS products.

You build the company around the system.

What happens if the supplier:

Closes?

Gets acquired?

Stops supporting the product?

Changes strategy?

Raises prices dramatically?

Is this a large, established platform?

Early-stage startup?

One-person software company?

None is automatically wrong.

But dependency should influence due diligence.

The more critical the software, the more I care about the supplier's resilience.

Integration can matter more than individual features

Software rarely lives alone.

Imagine Product A is 15 per cent better at project management.

Product B integrates perfectly with:

CRM.

Finance.

Timesheets.

Reporting.

Product A requires three manual transfers every day.

Which creates the better operating system?

Possibly B.

Evaluate technology as part of the workflow.

Not as an isolated product.

The UK's 2026 digital-adoption work is increasingly recognising this systems issue too. The government's June 2026 update notes active work around systems integration alongside wider SME digital-adoption support.

A brilliant isolated tool can make the overall business worse.

One source of truth is valuable

Suppose:

Sales has its customer address.

Operations has another.

Finance has another.

Which one is correct?

That is a data-design problem.

Good software architecture should reduce unnecessary duplication.

Ask:

Where should customer data live?

Project data?

Financial data?

Employee data?

Which system is authoritative?

Which systems merely use it?

Then integrate where appropriate.

Without this, every new platform can create another slightly different version of reality.

Beware duplicate functionality

Review your software stack.

You may discover you currently pay for:

CRM with email campaigns.

Email platform with CRM features.

Project system with CRM features.

Accounting package with quoting.

Separate quoting software.

Microsoft 365.

Another file-storage system.

Three task-management products.

Two meeting-recording tools.

An AI subscription for almost every employee who saw something on TikTok.

Software accumulates.

Rarely does anyone remove it.

New purchase decisions should consider overlap.

Can we use something we already pay for?

Can this new system allow another tool to disappear?

Feature utilisation is a useful warning sign

Suppose your existing CRM can:

Automate follow-up.

Create reports.

Integrate with email.

Score opportunities.

Generate reminders.

Nobody uses any of it.

Management now wants a new CRM because:

“The current system doesn't do enough.”

Doesn't it?

Or hasn't the company implemented what it already bought?

Before replacing software, understand:

Which limitations are genuine?

Which are configuration?

Which are training?

Which are process?

Buying another product may simply restart the same cycle with a prettier interface.

Sometimes the software is not the problem

This is worth repeating.

The process is unclear.

Nobody owns it.

Standards differ.

Managers do not enforce it.

Employees have never been trained.

Data is poor.

Then leadership buys technology.

Six months later:

Same problem.

Different login screen.

This is why Article #70 began with:

Automate the process only once you understand the process.

Software should enable management.

It cannot replace management.

Run a pilot where possible

The 2025 Digital Adoption Taskforce recommended a test and learn approach to technology adoption support, and the government's 2026 update continues to use pilots and evidence-led evaluation in its SME digital programmes.

Businesses can use the same logic.

Do not necessarily roll the product across the entire company immediately.

Try:

One team.

One workflow.

One site.

One customer type.

One project.

Define success first.

Then test.

Does it actually:

Save time?

Reduce errors?

Improve visibility?

Work with real data?

Handle exceptions?

Integrate properly?

Do employees use it?

A two-week trial containing no real implementation tells you very little.

A structured pilot can tell you a lot.

Test the horrible scenarios, not only the happy path

Software demos always show:

Normal customer.

Normal order.

Normal invoice.

What about:

Customer changes address halfway through.

Duplicate account.

Refund.

Cancelled project.

Employee leaves.

Two locations share customer.

Incorrect data imported.

System unavailable.

Integration fails.

Unusual pricing.

Part payment.

Your business contains exceptions.

Test some.

A system that handles the perfect workflow beautifully and the real business badly is not a good system.

Measure actual adoption after launch

Do not stop at:

Go-live complete.

Thirty days later:

How many employees actually use it?

Are required fields completed?

Have spreadsheets returned?

Has data quality improved?

Has the promised time saving appeared?

Three months later:

Has the business outcome moved?

Implementation is not complete when the software turns on.

It is complete when the new operating behaviour becomes normal.

Calculate ROI again after implementation

You built an original business case.

Good.

Now compare it with reality.

Expected:

Save 20 hours a week.

Actual:

Seven.

Expected:

Reduce software stack by £12,000 annually.

Actual:

Old systems still running because nobody migrated properly.

Expected:

Increase capacity 15 per cent.

Actual:

No measurable change.

That does not automatically mean kill the system immediately.

Maybe adoption needs improving.

But update the business case.

Software should not become immune from scrutiny because management already spent money on it.

Do not fall for sunk cost

You spent:

£25,000 implementing.

Six months later it clearly does not work.

Someone says:

“We can't move away now. We've already spent £25,000.”

That money has already gone.

The relevant question is:

From today onwards, which option creates the better outcome?

Continue investing?

Fix implementation?

Replace it?

Return to previous system temporarily?

Past expenditure should inform learning.

Not imprison future decisions.

Do not keep rubbish software because changing feels painful

The Digital Adoption Taskforce specifically identifies high switching costs and perceived switching risk as barriers for SMEs.

That is understandable.

Changing software is disruptive.

Which is why businesses tolerate unsuitable systems for years.

But there is a cost to not changing too.

Every year:

Manual work.

Errors.

Poor information.

Workarounds.

Frustration.

Lost capacity.

Put a value on staying still as well.

The decision is not:

Change = cost. Stay = free.

Both options have costs.

Build a three-year view where the investment is significant

Suppose:

Implementation costs £12,000.

Annual licence £9,000.

Training and internal time £5,000 in year one.

The system replaces £4,000 of existing annual software.

It also creates an estimated £18,000 annual combination of cash savings and realistically usable additional capacity.

Year one:

Costs are heavier.

Years two and three:

Implementation drops away.

The picture changes.

A software investment with mediocre first-year ROI may be extremely sensible over three years.

Equally, a cheap first year can become expensive when promotional pricing ends.

Look beyond month one.

But do not force a financial ROI onto every system

Some software is infrastructure.

Cyber security.

Backup.

Compliance.

Accounting.

You may buy it because the alternative risk is unacceptable rather than because it produces £37,000 measurable annual profit.

That is fine.

Define the purpose accurately.

Perhaps the return is:

Risk reduction.

Control.

Compliance.

Business continuity.

Do not create fictional productivity savings merely because somebody insists every purchase needs a positive spreadsheet ROI.

The software business case

For any meaningful purchase, I would answer these questions.

What problem are we solving?

One sentence.

What happens today?

Current process and measurable baseline.

What specifically should improve?

Time?

Quality?

Capacity?

Revenue?

Information?

Risk?

How will we measure success?

A number wherever practical.

What is the full first-year cost?

Licence plus implementation, migration, integrations, training and internal time.

What is the ongoing annual cost?

Everything that remains after implementation.

What existing cost disappears?

Other software?

Overtime?

Admin?

External support?

What capacity is released?

And what are we going to do with it?

What new risk appears?

Cyber?

Data?

Supplier dependency?

Operational outage?

What needs integrating?

Be specific.

How will data move in?

And back out later?

Who owns implementation?

One person.

Who owns the system afterwards?

Also one person.

What happens if the pilot fails?

Know before you become emotionally attached.

If those questions produce good answers, the purchase is becoming defensible.

Green flags

I become more comfortable when:

The business problem is specific.

The existing process is understood.

A baseline exists.

Success measures are agreed.

Users have been involved.

The system replaces genuine manual work or other tools.

Implementation requirements are understood.

Integration has been tested properly.

Data migration is achievable.

Training is planned.

Security fits the risk.

The supplier is credible.

Exit and data portability are understood.

A pilot has produced useful evidence.

Someone owns the system.

The three-year economics make sense.

Most importantly:

The software makes the business simpler.

Red flags

I slow down when:

The purchase began with a demo rather than a business problem.

Nobody can explain what success means.

The ROI relies entirely on vague “efficiency”.

Employees already hate the proposed system.

The vendor says implementation is easy but has not seen your data.

Nobody knows which existing systems it replaces.

The platform duplicates software you already own.

Integrations are described as “possible” rather than demonstrated.

Massive customisation is required.

The contract is difficult to exit.

Data export is unclear.

Security answers are vague.

Every feature sits in a higher subscription tier.

The internal implementation owner has no time.

The company has a history of buying software and not using it.

Those do not automatically mean:

Do not buy it.

They mean:

Do not sign yet.

Software should remove complexity, not digitise it

This is where I would ultimately land.

Imagine your existing process contains:

Eight unnecessary steps.

Three handovers.

Two duplicated spreadsheets.

One pointless approval.

You buy software.

Now you have:

Eight digital steps.

Three automated handovers.

Two integrated spreadsheets.

One electronic pointless approval.

Congratulations.

You digitised the nonsense.

Technology should give you the opportunity to rethink the work.

What can disappear?

What can become standard?

What information only needs entering once?

What can happen automatically?

What decisions belong elsewhere?

That is where the real value appears.

The most expensive software is often the one nobody uses properly

Not the one with the highest licence fee.

The one where:

You pay.

Employees avoid it.

Management mistrusts the data.

Spreadsheets continue.

Work is duplicated.

Nobody switches it off because implementing it was painful.

That is expensive.

So judge software by business behaviour , not procurement.

What changes after implementation?

If nothing does, the technology has not transformed the company.

It has joined the subscription list.

Technology should create leverage

A good system lets:

The same team handle more work.

Managers make better decisions.

Customers get answers faster.

Employees stop duplicating administration.

Information move once.

Processes become more reliable.

The owner become less involved in routine activity.

That is leverage.

The objective is not:

More software.

It is:

A better operating system.

Sometimes that means buying something new.

Sometimes configuring what you already have.

Sometimes integrating two systems.

Sometimes deleting three.

And occasionally the best software investment you can make is deciding you do not need another bloody platform at all.

My Sales Pipeline is Dry: What Should I Do Before Revenue Drops?

Tue, 06 Oct 2026 09:41:57 GMT

If your sales pipeline is drying up but revenue still looks healthy, do not wait for revenue to confirm the problem .

Revenue is usually looking backwards.

The pipeline is looking forwards.

The invoices landing this month may have come from opportunities created:

Six weeks ago.

Three months ago.

Six months ago.

Perhaps longer.

So one of the most dangerous periods in business is when:

The team is busy.

Revenue still looks good.

Customers are being served.

But not enough new opportunities are entering behind them.

Nothing appears broken yet.

Then the work finishes.

The existing order book burns down.

And everybody suddenly announces:

“Sales have fallen off a cliff.”

They probably didn't.

The warning appeared months earlier.

The pipeline went quiet.

A dry pipeline is an early-warning signal

That is how I would treat it.

Not automatically as a crisis.

Not automatically as Marketing's fault.

Not automatically as evidence the salesperson needs bollocking.

An early-warning signal.

Your job is to work out where the flow changed while you still have enough time to respond intelligently .

That means examining:

How many new opportunities are entering
Whether they are genuinely qualified
Where they come from
Whether opportunities are progressing
How quickly they progress
How often they convert
How often expected close dates slip
Whether average deal value has changed
Whether your market has weakened
Whether salespeople actually have enough selling capacity
Whether the CRM reflects reality

Then act on the specific constraint.

A dry pipeline is a symptom.

Diagnose it before prescribing more activity.

First, make sure the pipeline is actually dry

Owners sometimes tell me:

“The pipeline's terrible.”

What does terrible mean?

Compared with:

Last month?

Last year?

Target?

The amount of revenue you need?

Your normal sales cycle?

You need a commercial definition.

At its simplest, a sales pipeline represents potential opportunities moving through the commercial process from initial prospecting or lead generation towards a completed sale.

Current GOV.UK investment-readiness guidance describes a revenue pipeline in exactly that sort of way: potential opportunities progressing through defined stages, with deal values and probabilities that can help support revenue forecasting and identify where opportunities are progressing or stalling.

That means pipeline health cannot be judged solely by:

“£1.2 million sounds like a lot.”

£1.2 million might be excellent.

Or nowhere near enough.

Work backwards from the revenue you need

Suppose your business needs to win approximately:

£200,000 of new revenue each month.

Your average new deal is:

£25,000.

You therefore need roughly:

Eight wins each month.

Now suppose historically you win:

One in four properly qualified opportunities.

You need approximately:

32 qualified opportunities to generate those eight wins.

At an average £25,000 each, that means roughly:

£800,000 of qualified opportunity value

needs to convert at that historical rate to generate £200,000 of revenue.

That is already more useful than:

“We normally like about a million quid in the pipeline.”

Why?

Because the requirement came from your economics.

Not folklore.

Stop blindly using “3x pipeline” or “4x pipeline”

You will hear rules like:

“You need three times target in the pipeline.”

Why three?

If your qualified win rate is 50 per cent, three times may be plenty.

If it is 10 per cent, three times target is nowhere near enough.

If your CRM is full of optimistic rubbish, ten times might still be meaningless.

Pipeline coverage should reflect:

Your conversion rate.

Your sales stage.

Average deal size.

Sales cycle.

Slippage.

And how honestly opportunities are qualified.

There is nothing magical about 3x.

Calculate what your business requires.

Pipeline value is not all equal

Imagine two sales pipelines.

Pipeline A contains:

£2 million.

Pipeline B contains:

£1.2 million.

A looks stronger.

Then you inspect it.

Pipeline A contains:

Deals that have not moved for 120 days.

Prospects that have gone silent.

Opportunities with no defined next step.

Quotes sent six months ago.

Deals repeatedly moved from one month to another.

A salesperson's mate who once said:

“Yeah, we should definitely do something together.”

Pipeline B contains:

Active buying processes.

Confirmed requirements.

Decision-makers engaged.

Budget understood.

Next meetings booked.

Real expected timelines.

Which pipeline would you rather own?

Pipeline quantity matters.

Pipeline quality matters more.

Your CRM may be lying to you

Not intentionally.

People leave dead opportunities open because closing them feels like admitting defeat.

Expected close dates get moved:

September.

October.

November.

December.

Apparently the customer has been “about to make a decision” since Easter.

Salespeople may also interpret stages differently.

One person's qualified opportunity is another person's vague conversation.

This makes forecasting unreliable.

Current Gartner research published in June 2026 recommends paying particular attention to three pipeline measures for forecasting risk: initial pipeline value, pipeline conversion rate and pipeline slippage rate .

I like those because they force you beyond today's headline total.

How much genuine pipeline entered?

How much converts?

How much keeps moving into a later period?

Those tell you considerably more.

Clean the pipeline before trying to fill it

If the CRM is full of fantasy, clean it.

For every meaningful opportunity, ask:

What does the customer actually need?

Have they acknowledged the problem?

Is there a credible commercial opportunity?

Who is involved in the decision?

What happens next?

When?

When did we last have meaningful engagement?

What evidence supports the expected close date?

If nobody can answer those questions, the deal may not be where the CRM says it is.

Do not keep zombie deals alive simply because the pipeline total looks prettier.

You want useful information.

Not reassurance.

Sales stages should reflect customer progress

A common pipeline looks something like:

Prospect.

Qualified.

Proposal.

Negotiation.

Closed.

Reasonable.

But there is a danger.

Those are often descriptions of what the seller has done .

Proposal sent.

Great.

What has the buyer done?

A 2019 Gartner analysis made this criticism directly, arguing that modern B2B buying is often non-linear and that simply tracking seller-defined sales stages can give misleading information about genuine opportunity progress. It recommends looking for observable buyer progress or “verifiers” rather than assuming a deal advanced merely because the salesperson completed an activity.

That distinction is extremely useful.

“We sent the proposal.”

is not the same as:

“The customer has confirmed the proposal meets their requirements and scheduled a final commercial review with the decision-maker.”

The first tells me what you did.

The second tells me the buyer moved.

If your pipeline is dry, identify where it went dry

Do not send everyone out prospecting before answering this.

The shortage can appear at completely different points.

Problem 1: Fewer leads are entering

This is the obvious one.

Marketing enquiries dropped.

Referrals slowed.

Outbound stopped.

Website leads fell.

Events produced less.

Existing customers stopped referring.

Now the pipeline is receiving less raw material.

That is primarily a pipeline-generation problem .

Article #60 explored why marketing might not generate enough leads.

Article #74 looked at how to measure whether marketing is actually working.

If lead volume is materially down, start there.

But do not confuse enquiries with pipeline.

You can have hundreds of enquiries and still have a dry qualified pipeline if most are useless.

Problem 2: Lead volume is healthy but fewer qualify

This is different.

Marketing says:

“We're generating exactly as many leads.”

Correct.

Sales says:

“They're shit.”

Potentially also correct.

Perhaps:

Audience targeting changed.

A campaign attracts the wrong people.

Pricing moved you out of their budget.

Marketing messaging is too broad.

A new channel generates volume but weak intent.

Market conditions changed.

Qualification standards became stricter.

Measure:

Enquiry-to-qualified-opportunity conversion.

Then segment it by:

Source.

Campaign.

Product.

Salesperson.

Customer type.

You may discover the pipeline isn't dry because marketing stopped.

It is dry because fewer leads deserve entering it.

Problem 3: The business stopped prospecting because it became busy

This is spectacularly common.

Pipeline healthy.

Business wins loads of work.

Everyone gets busy delivering it.

Salesperson gets pulled into account management.

Owner disappears into operations.

Marketing slows.

Outbound stops.

Networking becomes optional.

Follow-up becomes inconsistent.

Everyone thinks:

“We've got plenty on.”

Three months later:

“Why is nothing coming in?”

Because you stopped putting anything in.

This creates a classic feast-and-famine cycle.

Busy.

Stop selling.

Quiet.

Panic.

Sell aggressively.

Busy again.

Stop selling again.

Repeat for fifteen years.

The solution is not a heroic sales campaign every time revenue falls.

It is a minimum sustainable pipeline-generation rhythm that continues when the business is busy .

Sales activity needs protecting from delivery work

This is particularly important in owner-led companies.

You hire a salesperson.

Then because they are capable and know the customers, they also become involved in:

Account management.

Customer service.

Operational problems.

Quotes.

Project coordination.

Internal meetings.

The role gradually stops being predominantly sales.

Then leadership complains:

“They're not generating enough pipeline.”

How much genuine selling capacity do they have?

Look at the calendar.

Not the job description.

If the company needs four days per week of business development but the salesperson gets eight useful hours after everything else, the maths will eventually catch up.

Problem 4: Opportunities enter but do not progress

Now you have enough leads.

Enough qualified opportunities.

But the middle of the pipeline barely moves.

This might mean:

The buyer lacks urgency.

You are not reaching the decision-maker.

The proposition is unclear.

The business case is weak.

You are sending proposals too early.

The buying group cannot reach agreement.

You are not addressing risk.

The customer is exploring but not genuinely buying.

This is where pipeline velocity matters.

How long do opportunities normally spend at each stage?

How long are current deals spending there?

Gartner's June 2026 work on stalled deals specifically recommends monitoring sales velocity to identify where and why opportunity momentum is breaking down.

You do not need complicated revenue-intelligence software to ask the basic question:

Why has this deal not moved?

A stalled deal is not automatically a lost deal

Sometimes buyers genuinely need time.

Budget cycle.

Board approval.

Procurement.

Technical review.

Contract process.

Fine.

But the expected close date should reflect reality.

Do not treat:

“Still interested”

as equivalent to:

“Actively progressing.”

A useful pipeline review asks what specific buyer action will happen next.

If there isn't one, probability probably needs revisiting.

Problem 5: Your sales cycle got longer

This can make a healthy amount of opportunity appear temporarily dry at the closing end.

Suppose deals historically take:

60 days.

Now they take:

Even if lead generation and win rate remain identical, revenue moves later.

Why did the cycle lengthen?

Customers delaying decisions?

Additional procurement?

Economic uncertainty?

More competitors?

Higher price?

Internal response delays?

Different customer mix?

Current UK business conditions make this plausible in some sectors. The Bank of England's September 2026 Agents' summary described demand as uneven, with elevated uncertainty delaying some decisions and particularly weak conditions in areas including construction, property and some discretionary services.

So do not assume every pipeline slowdown was created inside your company.

Markets change.

But you still need to identify what changed.

Current demand is mixed, not universally terrible

This matters because:

“The economy's shit.”

can become another wonderfully convenient explanation.

ONS reported on 24 September 2026 that 28 per cent of trading UK businesses said turnover had decreased in August, while economic uncertainty was the most commonly reported turnover challenge across trading businesses in September. At the same time, substantial numbers reported stable or improving performance, and the data vary considerably by sector. ONS also labels these Business Insights and Conditions Survey results as official statistics in development and advises appropriate caution when interpreting them.

Translation:

Yes, economic conditions may be affecting demand.

No, you cannot blame “the economy” without evidence.

Compare:

Your sector.

Your competitors.

Your enquiry volume.

Your conversion.

Your customer conversations.

Your historic performance.

Find out whether the weakness is market-wide or specifically yours.

Problem 6: Conversion has fallen

The pipeline enters normally.

Deals progress.

Fewer close.

Now investigate sales conversion.

Has pricing changed?

Competitors?

Proposal quality?

Salesperson performance?

Customer fit?

Decision-maker access?

Commercial terms?

Follow-up?

Confidence?

One salesperson?

One product?

One market?

Do not immediately lower prices.

A lower conversion rate can indicate dozens of things.

Find out why buyers are saying no.

Or why they are doing nothing.

Those are not necessarily the same problem.

Lost and “no decision” should be separated

This is useful.

Lost to competitor

means someone else won.

No decision

means the customer did not proceed.

Different problem.

If competitors repeatedly beat you:

Positioning, price, differentiation, trust or sales execution may need attention.

If customers repeatedly do nothing:

Perhaps the pain is insufficient.

Urgency weak.

Business case unclear.

Buying process complex.

You are selling to people who are curious rather than committed.

Separate the outcomes.

Problem 7: Your average deal value has fallen

Number of opportunities looks normal.

Conversion looks normal.

Pipeline value still drops.

Perhaps the work is smaller.

Why?

Different customer type?

Lower pricing?

Different service mix?

Large customers buying less?

Salespeople pursuing easier small deals?

The sales pipeline should be reviewed in both:

Number of opportunities

and:

Value.

Otherwise ten £5,000 deals and ten £50,000 deals look identical.

They are not.

Problem 8: Too much pipeline is concentrated in one or two deals

Your CRM says:

£2 million pipeline.

Excellent.

Then:

£1.4 million sits in one opportunity.

That is not necessarily a strong pipeline.

It is one enormous bet plus £600,000 of pipeline.

If the major deal moves, your forecast changes dramatically.

Understand concentration by:

Customer.

Opportunity.

Sector.

Product.

Salesperson.

Source.

Healthy aggregate numbers can hide fragility.

Problem 9: Expected close dates keep slipping

This deserves explicit measurement.

Suppose at the start of the quarter you expected:

£900,000 to close.

You win:

£400,000.

Lose:

£100,000.

And £400,000 simply moves into next quarter.

That £400,000 of slippage matters.

Repeated slippage suggests:

Forecasting is overoptimistic.

Buying timelines are not understood.

Salespeople are keeping deals alive.

Customers are delaying.

Or some combination.

That is why Gartner's current pipeline framework includes slippage rate alongside starting pipeline value and conversion.

Track it.

A deal that has slipped four consecutive periods is sending you a message.

Problem 10: You are confusing order book with pipeline

These are different.

Order book or backlog is usually work already won but not yet fully delivered or recognised.

Sales pipeline is work you might win.

A business can have an excellent order book and terrible pipeline.

That is exactly when risk becomes easy to miss.

Everyone is busy fulfilling committed work.

Revenue looks secure for the next few months.

But nothing meaningful follows it.

Ask separately:

How much work have we already won?

And:

How much credible future opportunity exists behind it?

Those are different forms of visibility.

Calculate how much runway you have

Suppose your existing order book gives you approximately four months of normal activity.

Your typical sales cycle is three months.

Your pipeline is currently weak.

You still have time.

But not much.

Suppose your order book gives you six weeks of visibility while the average sale takes six months.

That is a very different situation.

The gap between:

How long existing work lasts

and:

How long replacement work takes to win

determines urgency.

Do not wait until the team becomes quiet before restarting sales activity.

By then, depending on your cycle, you may already be months late.

The revenue forecast should connect to the pipeline

This sounds obvious.

Yet forecasts often contain lines such as:

November: £600,000.

December: £650,000.

January: £700,000.

Why?

Because growth target.

What opportunities support those numbers?

GOV.UK's current financial-model guidance highlights precisely this value of the pipeline: connecting revenue forecasts to actual opportunities, values, stages and realistic conversion assumptions rather than forecasts existing as unsupported ambition.

Your forecast should contain:

Committed revenue.

Reasonably expected pipeline.

Assumptions about future pipeline creation.

Then the uncertainty becomes visible.

A dry pipeline should change the forecast before it changes the bank account

This is management.

You spot pipeline creation falling in October.

The normal sales cycle is four months.

Current order book carries the company through January.

Do not wait for February's revenue to collapse.

Reforecast now.

What does the next six months look like under:

Current pipeline?

Historic conversion?

Current slippage?

Expected new opportunities?

Then decide.

Do we need:

More sales activity?

More marketing?

Different channels?

Different offers?

Reduced hiring?

Delayed expenditure?

More cash headroom?

The earlier you see the gap, the more options you have.

Pipeline creation deserves its own metric

Many businesses measure:

Sales closed this month.

Fine.

That tells you what the sales function successfully completed.

Also measure what it created for the future .

For example:

Value of new qualified opportunities created this week or month.

Not every raw lead.

Qualified pipeline.

That is your future inventory.

If pipeline creation falls consistently while revenue remains strong, you have a leading warning.

Current Gartner research similarly treats initial pipeline value as a core measure of forecast health rather than only analysing what is already sitting in the pipeline at period end.

Track conversion between stages

Suppose 100 leads enter.

Historically:

40 qualify.

20 receive proposals.

8 win.

Now:

100 enter.

20 qualify.

12 receive proposals.

6 win.

Overall wins fell from eight to six.

But the most obvious deterioration happened much earlier:

Qualification.

That tells you where to investigate.

Or perhaps qualification remains strong but proposal-to-win collapses.

Different intervention.

Pipeline management becomes much easier when you know where the funnel changed .

But do not build 19 meaningless stages

CRM implementation can become extraordinary.

Lead.

Contacted.

Engaged.

Exploring.

Discovery booked.

Discovery held.

Potentially qualified.

Qualified.

Very qualified.

Proposal pending.

Proposal sent.

Proposal opened.

Proposal considered.

Negotiation.

Final negotiation.

Verbal yes.

Nearly definitely verbal yes.

Stop.

Use enough stages to represent meaningful changes in buying progress.

Every stage should help management answer something.

If two stages never change what you do, perhaps you only need one.

Measure age

How old are opportunities?

Not just overall.

By stage.

Suppose most successful opportunities spend:

Two weeks in proposal.

Current open proposals average:

Nine weeks.

That is useful.

Something has changed.

Either:

Today's deals are structurally different.

Buyers have slowed.

Or the pipeline contains dead opportunities nobody closed.

Age creates context.

Measure “next step”

For every meaningful opportunity, there should be a clear next action.

Not:

Follow up.

When?

About what?

Ideally:

Customer CFO reviewing proposal Friday. Adam to call Monday at 10am if no response.

That is a next step.

Chase next week

is administrative fog.

A pipeline without next actions is mostly a list of hopes.

Activity metrics can help, but do not worship them

Calls.

Emails.

Meetings.

Proposals.

Useful diagnostically.

Suppose pipeline creation collapsed because outbound conversations fell from 80 per week to 15.

We learned something.

But activity is not the commercial outcome.

One salesperson can make 100 terrible calls.

Another can make 20 highly targeted conversations and generate more pipeline.

Use activity metrics to explain the pipeline.

Do not replace the pipeline with activity.

Speed-to-lead can matter for inbound enquiries

If someone actively requests contact, the delay before your business responds deserves measurement.

Older large-scale lead-response research has repeatedly found substantial differences in outcomes associated with response speed. A 2021 InsideSales/XANT analysis examined more than 55 million sales activities across 5.7 million marketing-generated leads and reported substantially higher conversion where first contact attempts happened very quickly. It is vendor-produced rather than independent academic research, so I would not treat its exact conversion multiplier as a universal law.

The sensible principle survives regardless:

If somebody raises their hand today, responding three days later is probably not helping.

Measure your actual:

First response time.

Contact rate.

Qualification rate.

Then see what the data says for your business.

Do not confuse quick response with harassing everybody immediately

Context matters.

Someone requesting a quote expects contact.

Someone downloading a general article might not appreciate a salesperson ringing 43 seconds later.

The right response depends on buying intent.

This is why lead categorisation matters.

Use automation to ensure high-intent enquiries do not disappear.

Use judgement to decide what appropriate follow-up looks like.

Marketing and Sales need one definition of pipeline

Article #74 covered this from the marketing side.

Marketing says:

“We generated 80 opportunities.”

Sales says:

“You generated 14.”

Fix the definition.

A qualified sales opportunity might require evidence of things such as:

Relevant customer profile.

Real problem or requirement.

Commercial potential.

A plausible buying process.

Depending on your model, budget or access to decision-makers may matter too.

Do not mechanically import some acronym-heavy qualification methodology because LinkedIn says all proper sales teams use one.

Define what your business needs before an opportunity deserves pipeline status.

Qualification protects selling capacity

This is especially important if sales resources are constrained.

A salesperson can spend hours preparing a proposal for somebody who was never likely to buy.

Multiply that across the month.

A 2026 research article on B2B service opportunity management argues that firms with limited selling resources need to prioritise opportunities based on meaningful buyer and opportunity characteristics rather than intuition or ad hoc rules.

That is the practical reason to qualify.

Not bureaucracy.

To decide where scarce sales time deserves going.

If the pipeline is dry, start with existing relationships

Businesses often jump straight to cold prospecting.

Fine.

But inspect the customer base first.

Who has:

Bought before?

Bought one service but not another?

Gone quiet?

Requested something twelve months ago?

Expanded?

Changed management?

Reached renewal?

Could benefit from another part of what you do?

Existing relationships may contain faster routes to credible opportunities because trust already exists.

This is not about spamming every historic customer with:

“Just touching base...”

Please don't.

Have a reason to contact them.

Relevant change.

Useful idea.

New problem.

Renewal.

Opportunity.

Reactivate dormant opportunities properly

A closed-lost or dormant opportunity is not necessarily dead forever.

But look at why it did not proceed.

Timing?

Budget?

Competitor?

No decision?

Wrong fit?

If the reason was:

“Not this year.”

and it is now next year, perhaps revisit.

If the reason was:

“Your solution was completely unsuitable and they hated us.”

maybe leave them alone.

CRM history should help salespeople avoid rediscovering the same failed opportunity every six months.

Ask your best customers for introductions where appropriate

If you have customers who genuinely value what you do, referrals can create excellent opportunities.

Not:

“Do you know anyone who needs our services?”

That puts all the thinking on them.

Be more specific.

Perhaps:

“We're looking to work with more manufacturers facing X. If anyone comes to mind, I'd appreciate an introduction.”

Only where the relationship justifies it.

Referrals should feel natural.

Not like you have suddenly discovered your contact database because this month's pipeline report frightened you.

Increase outbound activity intelligently

A dry pipeline may absolutely require more proactive prospecting.

But:

“Everyone make 50 calls a day”

is not automatically strategy.

Who are you targeting?

Why them?

What problem are you opening with?

What evidence suggests they fit?

What trigger makes this relevant now?

Can you concentrate on:

A particular sector?

Geography?

Role?

Problem?

Customer characteristic?

The objective is not maximum interruption.

It is creating conversations with people sufficiently likely to have a relevant problem.

Look at what used to create your best opportunities

Where did last year's ten best customers come from?

Google?

Referrals?

Existing customers?

Events?

Outbound?

Partners?

LinkedIn?

Your website?

Trade associations?

Something else?

Article #74 provides the deeper marketing measurement framework.

For immediate pipeline recovery, I want to know:

Which sources historically generated opportunities that actually turned into worthwhile customers?

Then investigate whether those sources changed.

Did Marketing stop doing something?

Did a salesperson leave?

Did referral relationships cool?

Did search visibility fall?

Did an event disappear?

Did your message change?

Pipeline decline often has a history.

Find it.

Do not solve a dry pipeline by discounting everything

Desperation creates bad commercial behaviour.

Pipeline thin.

Owner nervous.

Sales instructed:

“Get some deals over the line.”

Discount.

Revenue may arrive.

Article #68 then appears three months later:

Why are we winning plenty of work but not making enough money?

A pipeline shortage does not make bad revenue good.

If pricing genuinely blocks appropriate customers, investigate pricing.

But do not sacrifice margin purely because management noticed the pipeline too late.

Do not fill the CRM with weak deals to make the meeting less uncomfortable

Another predictable response.

Owner says:

“Pipeline needs to be £2 million.”

Salesperson suddenly finds:

£2 million.

Amazing.

Nothing changed in the market.

Nothing changed in activity.

The CRM simply acquired optimism.

Targets for pipeline volume can produce bad data if qualification standards are weak.

Reward truthful pipelines.

A salesperson removing £300,000 of dead opportunities has improved the information.

Do not punish them because the dashboard number fell.

Pipeline reviews should improve decisions, not create theatre

A useful pipeline review asks:

What new opportunities entered?

Which progressed?

Which stalled?

Which slipped?

Which should close?

What evidence supports that?

What was lost?

Why?

What support is needed?

Where is pipeline generation weak?

What action follows?

Do not spend an hour having each salesperson read CRM fields aloud.

Management can read.

Discuss uncertainty.

Risk.

Movement.

Decisions.

Forecast categories can help

You might distinguish:

Committed

Strong evidence suggests the deal should close in the period.

Likely

Credible opportunity, but meaningful uncertainty remains.

Pipeline

Real opportunity that is not yet forecastable with confidence.

Exact terminology does not matter.

What matters is shared interpretation.

If one salesperson's “commit” means:

“Customer verbally approved and contract is in legal”

while another's means:

“I've got a really good feeling about these guys”

your forecast remains nonsense.

Probabilities should come from evidence where possible

CRM systems love:

Proposal stage = 60%.

Why 60?

Because somebody configured it in 2019.

Historical conversion can help.

If opportunities reaching a particular stage historically close 35 per cent of the time, that tells you something.

But two deals in the same stage may still have very different prospects.

Use:

Historical data.

Buyer evidence.

Manager judgement.

Do not pretend probability is precision.

67 per cent likely to close

can still be a human guess wearing a tie.

Use cohorts

This becomes especially useful when sales cycles are long.

Ask:

Of the qualified opportunities created in January:

How many won?

Lost?

Remain open?

What value?

How long did they take?

Then compare February.

March.

You start seeing whether pipeline created in newer periods is:

Smaller.

Lower quality.

Slower.

Converting worse.

This is more informative than mixing opportunities from twelve different generations into one enormous number.

Your scorecard should warn you before revenue does

Useful sales leading indicators might include:

New qualified opportunities created
New pipeline value created
Enquiry-to-qualified conversion
Stage conversion
Average opportunity age
Pipeline slippage
Qualified pipeline coverage against future target
Percentage of opportunities with a defined next step
Sales-cycle length
Win rate
Average deal value

You do not need all of them.

Choose the few that explain future revenue in your model.

Revenue itself is a lagging measure.

Pipeline tells you what may arrive next.

Pipeline creation tells you what may arrive after that.

The pipeline needs an owner

Who is responsible for making sure enough future opportunity exists?

Marketing?

Sales Director?

Owner?

Everyone?

Careful with everyone .

Marketing may own:

Demand generation.

Sales may own:

Qualification and progression.

Leadership owns:

Ensuring the entire commercial system produces enough future revenue.

Roles can differ.

Accountability cannot disappear between departments.

The owner should look at pipeline even when sales are excellent

Especially then.

This is the habit I want.

Great month?

Brilliant.

What happened to pipeline?

Record quarter?

Lovely.

What did we create for the next one?

The easiest time to ignore pipeline is when current revenue feels safe.

The best time to fix pipeline weakness is before revenue feels unsafe.

That gap is management's opportunity.

A practical 48-hour pipeline diagnostic

If someone told me today:

“Pipeline has suddenly gone dry,”

I would do this first.

Clean the data

Remove dead opportunities.

Correct stages.

Correct values.

Correct expected close dates.

Make sure the total means something.

Compare with history

Look at:

New opportunities created.

Value created.

Qualification rate.

Win rate.

Sales cycle.

Slippage.

Average deal size.

What changed first?

Break it down

By:

Salesperson.

Lead source.

Product or service.

Customer type.

Sector.

Geography.

Find where the decline is concentrated.

Review the current opportunities

Which have no next action?

Which have stalled?

Which expected close dates are fiction?

Which need management support?

Check selling capacity

Are salespeople actually selling?

Or servicing existing work?

Check demand generation

What activity has changed upstream?

Then decide what problem you really have.

That is 48 hours considerably better spent than randomly doubling the advertising budget.

Then build a 30-day pipeline recovery plan

The exact actions depend on the diagnosis.

But it may include:

Restore pipeline-generation rhythm

Protect prospecting and business-development time.

Re-engage appropriate existing customers

Look for genuine additional problems you can solve.

Reactivate credible dormant opportunities

Where timing or circumstances changed.

Strengthen referral activity

Through relationships where it is appropriate.

Repair weak lead sources

If marketing volume or quality deteriorated.

Improve follow-up

Particularly for high-intent inbound enquiries.

Focus outbound activity

Around the customer profiles and problems historically producing worthwhile business.

Address stalled deals

With specific buyer-focused actions rather than generic chasing.

Improve qualification

Stop filling selling capacity with weak opportunities.

Reforecast revenue

Reflect the likely lag before new pipeline becomes revenue.

The last one matters.

Even if you fix pipeline generation tomorrow, January's revenue may already be partly determined.

Adjust capacity early if the revenue gap is becoming real

This is where pipeline information becomes commercially powerful.

Suppose the diagnostic says:

The pipeline shortage is genuine.

Normal sales cycle is five months.

Recovery activity has started.

But there is likely to be a revenue gap in Q1.

Good.

Not good that revenue may fall.

Good that you know.

Now you can assess:

Recruitment plans.

Overtime.

Subcontractor commitments.

Inventory.

Capital expenditure.

Cash reserves.

Discretionary costs.

You may not need to cut anything.

But you can plan.

Compare that with discovering the same revenue shortfall when the bank balance starts falling.

Early information creates options.

Do not immediately cut sales and marketing when demand weakens

Another classic.

Revenue starts falling.

Costs need controlling.

Marketing budget gets cut.

Sales headcount frozen.

Pipeline becomes weaker.

Revenue falls more later.

I am not arguing that sales and marketing spend should be sacred.

Article #74 is specifically about measuring whether marketing deserves the money.

Cut what does not work.

But do not destroy future demand merely because current revenue is under pressure.

Understand the lag.

If the market has changed structurally, the answer may be strategic

Perhaps the pipeline is dry because:

The customer problem is disappearing.

Technology changed the category.

Competitors commoditised the service.

Your market is shrinking.

Customers consolidated.

Regulation changed.

The old proposition no longer feels valuable.

In that situation, increasing call volume is not enough.

You may need to change:

Offer.

Market.

Positioning.

Pricing.

Customer segment.

Business model.

A pipeline is not just a sales metric.

It can tell you something about strategic relevance.

Sales pipeline problems can originate anywhere in the business

Marketing can cause them.

Sales can.

Pricing can.

Delivery can.

Reputation can.

Capacity can.

Product can.

Leadership can.

If customers have experienced poor delivery, referrals may fall.

If prices became uncompetitive, conversion may drop.

If the website stopped ranking, enquiries may fall.

If the owner stopped networking, introductions may disappear.

If Sales spends half its week fixing Operations, new pipeline falls.

That is why commercial management needs the whole system.

The pipeline is future inventory

I think this is a useful way of seeing it.

A manufacturer would worry if raw-material inventory was disappearing with nothing coming behind it.

A retailer notices empty shelves.

Sales pipeline is future commercial inventory.

You do not own the revenue yet.

Some will never convert.

But you need enough credible opportunity flowing through the system to replenish the work currently being delivered.

Otherwise the business is consuming tomorrow faster than it is replacing it.

Do not wait for silence

The worst time to start selling is when there is nothing left to sell.

When the workshop goes quiet.

When consultants have empty diaries.

When engineers suddenly have spare capacity.

When the owner opens the forecast and discovers next quarter is half empty.

By then emotion enters.

Prices fall.

Qualification disappears.

Anything becomes a good opportunity.

That is why pipeline management matters.

Not because CRM dashboards are exciting.

Because it gives you enough warning to behave rationally.

If the pipeline is dry today, revenue may already be tomorrow's problem

So act now.

Clean the data.

Establish how much qualified pipeline you actually need.

Find where the flow changed.

Check:

Lead generation.

Lead quality.

Sales capacity.

Opportunity progression.

Conversion.

Slippage.

Deal value.

Market conditions.

Then fix the constraint.

And once the pipeline recovers, do not forget the lesson the moment revenue feels comfortable again.

Build pipeline creation into the normal rhythm of the business.

Review it every week.

Reforecast when the evidence changes.

Because sales rarely fall off a cliff without warning.

Most of the time, the business simply ignored the road signs on the way there.

Do I Own a Business or Have I Just Built Myself a Job?

Tue, 06 Oct 2026 09:36:05 GMT

You can legally own a business and still have built yourself a job.

The distinction is not whether your name appears at Companies House.

It is whether the organisation can create meaningful value without requiring your personal labour, judgement and availability at almost every important stage .

If you stop working and:

Sales stop.

Customers wait.

Decisions stop.

Problems queue.

Quotes do not go out.

Employees cannot proceed.

Nobody knows the numbers.

Important relationships go quiet.

Then you may own the shares.

But operationally, a large part of what you own is still your job .

That is not automatically a failure.

Plenty of people intentionally build highly profitable businesses around their own expertise and love working inside them.

The problem is believing you have built an independent commercial asset when what you have really built is a very demanding form of self-employment with employees attached.

The question is not whether you work in your company.

The question is:

Do you have to?

Building yourself a job is not inherently bad

This is worth establishing immediately.

Suppose you are an exceptional consultant.

You earn £250,000 a year.

Work 30 hours a week.

Choose your customers.

Take ten weeks off.

Love the work.

Have no interest in employing 50 people or selling the company.

Fantastic.

You may have built yourself a highly paid job.

Why should I tell you to turn it into something else?

Equally, someone may own a small trade business, studio, professional practice or specialist consultancy precisely because they enjoy doing the technical work.

There is no rule saying every company must become a machine capable of operating while its founder disappears to Tuscany for six months.

The issue is intentionality .

Are you working inside the business because that is the life and role you consciously chose?

Or because you attempted to build a business and accidentally made yourself its most overworked employee?

Those are very different situations.

The danger is when the job becomes disguised as an asset

This usually happens gradually.

You start the business.

Of course everything depends on you.

You sell.

Deliver.

Invoice.

Solve problems.

Make decisions.

Perfectly normal.

Then you hire somebody.

Revenue increases.

You hire another person.

Then five.

Then fifteen.

The company becomes larger.

Your responsibilities change.

But they do not necessarily shrink.

Instead of doing ten jobs yourself, you now manage ten jobs and still personally intervene whenever anything important happens.

Revenue increases.

Headcount increases.

Overhead increases.

Complexity increases.

Your workload remains enormous.

Eventually you have:

Employees.

Premises.

Systems.

Vehicles.

Customers.

A management team perhaps.

And somehow you are still the person required to make the bloody thing move.

That is when the question becomes useful:

Did we actually build a business, or did we build an increasingly complicated job for the owner?

The first test: what happens when you stop working?

Not permanently.

Take a week.

A genuine week.

No secretly answering emails at 6am.

No:

“Just WhatsApp me if anything comes up.”

No daily phone call with Operations.

What happens?

Perhaps the business operates perfectly well.

Brilliant.

Perhaps things continue but decisions accumulate.

Interesting.

Perhaps employees begin calling immediately.

Perhaps customers ask specifically for you.

Perhaps quotes wait.

Payments wait.

Problems wait.

Now you have information.

Article #71 explored this more deeply through the 30-Day Absence Test.

For this article, the point is simpler:

A business should eventually possess some ability to create value independently of the owner's continuous labour.

The greater that independence becomes, the more the company starts behaving like an asset rather than merely employment you happen to own.

Revenue dependence is the easiest place to start

Ask:

If I personally stopped selling tomorrow, what would happen to revenue?

Do other people sell?

Does marketing generate demand?

Do customers reorder through the company?

Does the brand attract enquiries?

Do recurring contracts exist?

Do referrals arrive because of the organisation rather than only your personal network?

Or does every meaningful sale ultimately require:

Your reputation.

Your phone.

Your relationship.

Your expertise.

Your closing ability.

A business can be extremely profitable while remaining heavily dependent on the owner's personal ability to win work.

That matters because your sales capacity is finite.

It also matters if you ever want:

Time away.

A different role.

Expansion.

Investment.

Succession.

Sale.

The customer should increasingly be buying from the business , not merely hiring the owner through a company wrapper.

Ask whose customers they really are

This is uncomfortable.

You may say:

“They are company customers.”

Fine.

If you left tomorrow, would they remain?

Do they know your Account Director?

Operations Manager?

Sales Director?

Another senior leader?

Or does every important relationship still live between:

Customer.

You.

That is relationship dependency.

It often feels like a strength.

“My customers are incredibly loyal to me.”

Good.

Until you want the business to exist separately from you.

British Business Bank's current guidance on selling a company explicitly identifies excessive reliance on the owner or on a single customer as a reason an exit may not currently be viable.

That makes sense.

A buyer wants to acquire relationships the company can retain.

Not borrow your friendships until you leave.

Delivery dependence matters too

Perhaps other people sell.

Great.

Who delivers the difficult work?

You.

Who checks quality?

You.

Who handles technical exceptions?

You.

Who rescues the project when it starts going wrong?

You.

Again:

You may have employees.

But the operating model still depends on one individual.

The question is not whether people help you.

It is whether they can produce the intended outcome without requiring you as the permanent quality-control mechanism .

That usually requires turning some of what you know instinctively into something the organisation can actually use.

Standards.

Training.

Decision rules.

Processes.

Examples.

Management.

Feedback.

You do not need to extract your entire brain into SharePoint.

You do need to stop making access to your brain part of every ordinary transaction.

Decision dependence is one of the strongest signs

Count how many decisions reach you in a normal week.

Can we discount this?

Can we order that?

Can Sarah have Friday off?

Can we refund the customer?

Which supplier should we use?

What should we quote?

Can we recruit?

Should we work overtime?

Can we change the schedule?

Should we accept these terms?

Some genuinely belong with the owner.

Most probably do not.

The 2026 research on entrepreneurial delegation is useful here. A field study involving 186 entrepreneurs and 47 matched co-founders found that founders were more likely to delegate decision authority where employees were perceived as capable and trustworthy, while perceived risk tended to inhibit delegation. The study involved startup entrepreneurs in Pakistan, so it should not be treated as a direct measurement of established UK SMEs, but the basic tension is recognisable: founders often retain decisions when trust, capability or perceived risk is weak.

If you want the business to become less dependent on you, you need to build both sides.

Capability below you.

And:

Willingness within you to let that capability operate.

Being the best decision-maker can become the problem

Perhaps you really are better.

Twenty years' experience.

Excellent commercial instinct.

Deep technical knowledge.

You can solve something in five minutes that takes a manager half an hour.

So you solve it.

Logical.

Tomorrow another problem appears.

You solve that too.

Eventually everybody learns:

Ask the owner.

Your personal competence has now shaped the company.

Not maliciously.

Not through ego necessarily.

Simply through repetition.

This is where the distinction between work ethic and agency becomes useful.

Work ethic says:

I can deal with this quickly.

Agency asks:

Why does this still need me at all?

Those questions create very different companies.

If every problem needs you, you are part of the operating system

This is an uncomfortable way of framing it.

Your company has:

Software.

Processes.

People.

Equipment.

Management.

And you.

If every serious exception routes to you, then you are infrastructure .

That creates a hard ceiling.

You can improve your time management.

Wake earlier.

Work faster.

Delegate small tasks.

Use AI.

Become extraordinarily efficient.

But the organisation still contains a capacity constraint:

Your brain.

Your attention.

Your availability.

Eventually you cannot personally expand at the same rate as the company.

That is why role transition becomes essential during growth.

Research published in the Journal of Business Venturing describes this as founders “giving up the hats”. Early-stage entrepreneurs naturally perform many different roles, but growth increasingly requires choices about which roles to retain, delegate or abandon. The researchers found that those role changes are not purely operational because the roles can become connected to entrepreneurial identity itself.

That last part explains why changing your own role can be harder than rewriting an organisational chart.

Do you employ managers or assistants to the owner?

This is another excellent test.

You have:

Sales Manager.

Operations Manager.

Finance Manager.

Maybe even directors.

Excellent.

What can they actually decide?

Can the Operations Manager run Operations?

Can the Sales Manager agree normal commercial terms?

Can Finance manage routine financial activity within clear controls?

Or do they:

Gather information.

Prepare recommendations.

Bring them to you.

Wait.

Then execute whatever you decide.

There is nothing wrong with an owner retaining major strategic decisions.

That is literally part of ownership.

But if managers carry responsibility without enough authority to produce the result, you have not really created management capacity.

You have created a layer between the problem and yourself.

Structured management starts replacing owner memory

As businesses become more capable independently of their founders, management practices become more important.

ONS's latest Management and Expectations Survey found that businesses with more structured management practices tended to have higher productivity and greater resilience. The survey measures areas including continuous improvement, use of KPIs, target setting and employment practices. ONS is careful about causal interpretation, but the relationship between structured management and firm performance is statistically significant.

This is not an argument for bureaucracy.

It is an argument for replacing:

“The owner knows.”

with:

“The organisation knows.”

There is a huge difference.

Another test: can somebody explain how your business makes money without you?

Ask a senior manager:

Which work creates the best margin?

Which customers are most valuable?

Where capacity is constrained?

Which numbers matter this month?

What risks are increasing?

What would we stop selling?

What would we invest in?

If only the owner understands the commercial model, then strategic knowledge remains centralised too.

Your management team may be competent operationally while still being unable to run the business commercially.

That matters enormously if you want to build something that eventually operates beyond you.

Financial independence is part of business independence

Some owners remain indispensable because every financial decision requires them.

Only they know:

The real cash position.

Which customers are late.

What the company can afford.

Which investments matter.

What margin is acceptable.

Who can be paid.

Article #75 covered what good management accounts should tell an owner.

The next stage is ensuring appropriate managers understand enough of the financial picture to make good decisions within their responsibility.

Not every employee needs access to every number.

But the business should not become financially brain-dead when the owner leaves the room.

Another clue: you cannot define what your own job is

Ask an owner:

“What's your actual role now?”

Common answer:

“Bit of everything.”

That is reasonable when the business employs four people.

Less impressive at forty.

You should increasingly be able to define what the owner is there to do.

Perhaps:

Strategic direction.

Capital allocation.

Leadership.

Senior recruitment.

Major relationships.

Risk.

Culture.

Future opportunities.

Whatever genuinely deserves the owner.

But if your role description remains:

Whatever nobody else can sort out

you are not occupying a designed role.

You are the organisation's overflow department.

The Fixer Loop keeps turning businesses back into jobs

The pattern often looks like this:

A problem appears.

Someone brings it to you.

You solve it.

The problem disappears.

You feel useful.

The employee gets relief.

Next time:

They bring you another one.

You become faster.

They become more dependent.

You become busier.

Eventually you complain:

“Nobody takes ownership.”

So you recruit somebody better.

A difficult problem appears.

They make a decision.

You disagree.

You take it back.

The loop continues.

That is what I call the Fixer Loop .

Article #67 explored the identity side of this in much more detail.

The commercial consequence is simple:

The business remains designed around your intervention.

The owner's role should evolve as the business evolves

The person who starts the company often needs to be:

Doer.

Seller.

Technician.

Problem-solver.

The person leading a more mature company may increasingly need to become:

Manager of managers.

Strategist.

Allocator of capital and attention.

Developer of leaders.

Designer of systems.

Protector of standards.

Creator of direction.

That transition is not automatic.

Founder identity research has examined precisely this problem: founding a business creates a role that can become central to someone's wider sense of self, while later growth requires the founder's role to evolve again.

There is no single correct owner role.

There is only the question:

What role does the business need from me now?

That may be completely different from the role it needed five years ago.

My own lesson was not that hard work is bad

I spent years believing that the answer to pressure was usually greater effort.

Work harder.

Start earlier.

Be available.

Solve it.

Carry more.

That approach can achieve a lot.

It can also quietly build an organisation around the assumption that you will always carry more .

Eventually, the more useful question becomes:

Is there a better way?

Not:

How can I clear these ten problems faster?

But:

Why did ten problems need to reach me?

Not:

How can I fit another meeting into Thursday?

But:

Why am I in that meeting?

Not:

How can I become more productive?

But:

Why does this work exist?

That shift from effort towards agency is one of the biggest differences between owning your job and designing a business.

The hours are not the whole test

You can work 60 hours a week and still own a real business.

Perhaps you are choosing to lead an aggressive growth period.

Fine.

You can work 25 hours and still have built yourself a job.

Perhaps every one of those 25 hours contains activity only you can perform, meaning revenue stops without you.

The question is not:

How many hours do I work?

It is:

What is the relationship between my hours and the company's ability to create value?

That distinction matters enormously.

A business starts becoming more independent when revenue detaches from owner hours

Suppose your annual revenue doubles.

What happens to your hours?

If they must also double, there is very little leverage.

If they remain broadly stable because:

Other people deliver.

Systems handle volume.

Managers decide.

Technology removes administration.

Customers buy without you personally selling everything.

then the company has gained leverage.

That does not mean costs stay flat.

Employees cost money.

Systems cost money.

Management costs money.

The point is that owner labour no longer scales one-for-one with business output .

That is a much healthier position.

Your salary and business profit are different too

Another interesting test:

How much would the company make if it had to employ somebody to perform your current day-to-day job?

Suppose the accounts show:

£250,000 profit.

Lovely.

But you personally work:

70 hours a week.

Sell most major jobs.

Run operations.

Manage senior employees.

Handle customers.

And pay yourself a relatively modest salary.

What would it cost to replace your operational contribution?

Perhaps:

£120,000.

£160,000.

Maybe more.

The economic profit attributable to ownership may be considerably lower than the headline profit initially suggests.

This does not mean your accounts are wrong.

It means part of the return you currently receive from the business may economically resemble payment for your labour , while another part represents a return on ownership.

Understanding the distinction helps enormously when thinking about:

Sale value.

Succession.

Investment.

Freedom.

Could you replace yourself?

Not with one superhuman clone.

That is usually the wrong question.

You may currently perform five different jobs.

Replacing you could require:

Operations responsibility.

Commercial responsibility.

Leadership.

Technical input.

Perhaps some work disappears entirely once processes improve.

This is another reason owner-dependency removal is rarely solved by hiring:

“A general manager who can do everything I do.”

You probably spent twenty years becoming capable of doing everything you do.

Good luck recruiting another one for £55,000 plus a Mondeo.

Deconstruct the role.

What genuinely needs doing?

Who should own each part?

What needs systemising?

What should remain with you?

What should stop?

The business-versus-job test

I would assess the company across eight questions.

1. Revenue

Would meaningful sales continue if you stopped selling personally?

2. Delivery

Could customers receive the promised result without your routine intervention?

3. Decisions

Can managers make normal commercial and operational decisions without you?

4. Relationships

Are important customers, suppliers and advisers connected to the company or primarily to you?

5. Knowledge

Does critical information exist somewhere beyond your memory?

6. Management

Can somebody lead the organisation when you are not present?

7. Financial control

Can competent people understand performance and keep normal financial operations running?

8. Time

Can the business grow without requiring a broadly proportional increase in your personal working hours?

The more often the answer is:

the more job-like the company remains.

Again, that is not moral judgement.

It is diagnosis.

Then ask the asset question

If you stopped working permanently, what would remain?

Brand?

Contracts?

Recurring customers?

Employees?

Management?

Processes?

Technology?

Intellectual property?

Supplier relationships?

Data?

Reputation?

Cash flow?

Physical assets?

Pipeline?

The company should increasingly possess value that does not disappear when your labour does.

This is especially important if you imagine selling one day.

British Business Bank specifically advises owners preparing for sale to strengthen profitability, cash flow, customer breadth and forward visibility, while warning that heavy owner dependency can undermine exit viability.

A buyer is buying what remains.

Exit value exposes the difference ruthlessly

Suppose you believe the company is worth £3 million.

Potential buyer says:

“Great. What happens when you leave?”

You explain:

You win the important customers.

You hold the technical knowledge.

You approve the prices.

You run the management team.

You know the suppliers.

You handle all major problems.

Buyer says:

“So we'd quite like you to stay for five years.”

That tells you something.

They may value the company.

But some of what they are valuing is clearly still attached to you .

A more independent business gives an acquirer something transferable.

That usually creates considerably more strategic flexibility whether you ultimately sell or not.

Investment exposes it too

External investors ask a similar question.

What exactly is scalable here?

Is the competitive advantage embedded in:

Company capability?

Or:

One talented founder?

British Business Bank guidance for businesses preparing for investment emphasises the importance of understanding financial performance, market opportunity, business structure, key skills and where sustainable value actually sits inside the organisation.

An investor may happily back a founder-led company.

But they are unlikely to ignore what happens if all value remains concentrated in one person.

The company should eventually become better than you

This is perhaps the most interesting part.

Owners often believe the goal is to teach employees to do things as well as I do .

What if the company eventually does some things better?

A Sales Director who is better at managing a sales team.

An Operations Director who sees delivery problems you miss.

A Finance Director who understands working capital better than you ever will.

A specialist marketer who knows far more about marketing.

That is not evidence the owner has become less valuable.

It is evidence the organisation has become more capable.

You should not need to remain the best person in the company at every function.

If you do, you hired badly.

This requires allowing people to become better

Which can be surprisingly uncomfortable.

You built it.

You knew everything first.

Now someone else says:

“I think we should do it differently.”

And they are right.

Wonderful.

That is growth.

If the organisation can never develop beyond the founder's methods, the founder eventually becomes the ceiling.

A successful business should acquire expertise its owner does not possess.

Otherwise every improvement remains limited to what one human can personally learn.

Stronger management practices create organisational capability

This is where the ONS management research becomes useful again.

Its current evidence finds that larger firms tend to use structured management practices more extensively than smaller ones, while stronger management scores are associated with higher productivity. The practices measured include continuous improvement, performance monitoring, targets, training and managing underperformance.

That does not mean you need to turn a 20-person company into a corporate bureaucracy.

It means an organisation becomes less reliant on individuals when it develops repeatable ways of managing itself .

Can you take a proper holiday?

It is a crude test.

Also extremely revealing.

Two weeks.

Could you genuinely disconnect?

If not, why?

Do not settle for:

“Because I'm the owner.”

What specifically requires you?

Customer?

Decision?

Approval?

Knowledge?

Relationship?

Habit?

Fear?

Identity?

Article #67 explores the last two.

This article is interested in what you do next.

Each interruption is evidence of a dependency.

Use it.

Do not merely become better at working remotely

Technology can hide the problem beautifully.

Twenty years ago, owner dependency meant:

The owner has to be physically in the office.

Today:

You can run the entire company from a beach.

Amazing.

You are still running the entire company.

Answering Teams from Tenerife is not owner independence.

It is location-independent dependency.

A laptop does not turn your job into an asset.

Permanent availability is another form of labour

You may say:

“I only work about 35 hours now.”

Fine.

But are you mentally on call for another 60?

Phone nearby.

Email checked.

Always reachable.

Every difficult problem potentially yours.

Research on entrepreneurs' recovery from work is relevant here. A 2026 Small Business Economics study using four surveys of French entrepreneurs found lower reported daily recovery experiences than those seen in prior employee samples, with psychological detachment particularly low. Better recovery experiences were associated with better wellbeing and lower burnout. The evidence is observational and population-specific, so it should not be treated as proof that every owner's availability produces the same outcome, but it reinforces the value of actually being able to disengage from work.

Ownership should ideally create options.

Permanent availability removes them.

Revenue is not enough

This is why I think Whole-Life Profit matters.

A business can produce:

£500,000 annual financial profit

while consuming:

Your evenings.

Weekends.

Health.

Attention.

Family time.

Ability to think.

Freedom to do anything else.

Financial profit still matters.

Enormously.

But the business has other costs.

You do not necessarily need to reduce work.

You need to decide whether the return justifies the whole price you are paying.

A business that gives you less control over your own life than employment did deserves examination.

The real difference is optionality

This is where I ultimately draw the line.

You own more than a job when the business gives you choices .

You can:

Stay operational.

Step back.

Take a month away.

Promote a manager.

Hire a Managing Director.

Sell.

Retain ownership.

Start something else.

Spend more time with family.

Work four days.

Work six because you genuinely want to.

Optionality.

Agency.

You do not have to exercise every option.

The value lies in possessing them.

If you have exactly one option:

Keep working because everything depends on me

then the business owns rather more of you than perhaps you intended.

Build the company around roles, not around yourself

One of the practical shifts is to stop asking:

“What do I currently do?”

and start asking:

“What does this business require?”

Those are not automatically the same thing.

List the required functions.

Sales.

Operations.

Finance.

People.

Marketing.

Technical leadership.

Customer management.

Whatever applies.

Then ask:

Who should own each function at the company's current size?

Some answers may still be:

Me.

Fine.

But make that deliberate.

Do not let the organisation chart simply become a historical record of whatever you happened to start doing first.

Use Dependency Removal deliberately

Choose one area where the company depends on you unnecessarily.

Not fifteen.

One.

For example:

Routine pricing.

Then work through it.

Why does it need you?

Perhaps pricing rules are unclear.

Define them.

Perhaps margins are invisible.

Create better information.

Perhaps employees lack skill.

Train them.

Perhaps limits are unclear.

Set authority thresholds.

Then measure:

How many pricing decisions came to me this month?

If it falls from:

to:

you have changed the business.

Repeat elsewhere.

That is Dependency Removal .

Not delegation as a one-off event.

Deliberately reducing the number of ordinary outcomes that require one specific person.

Your 90-day plan can contain one owner-removal priority

Not:

“Become less operational.”

Too vague.

Something like:

By the end of the quarter, the Operations Manager will independently own scheduling, routine customer escalations and supplier purchasing below £5,000, reducing owner operational decisions by at least 60 per cent.

Now you can manage it.

Article #66 goes much deeper into building 90-day plans that actually get executed.

Owner independence should be treated as a real strategic project if it matters to you.

Not a retirement fantasy.

Do not dump everything onto somebody else

Removing yourself does not mean creating another indispensable person.

If every decision currently comes back to you, and six months later every decision you make comes back to your General Manager, you have moved the dependency.

You have not removed it.

The organisation needs:

Clear roles.

Authority.

Information.

Systems.

Multiple capable people.

Not another heroic fixer.

This is particularly important for resilience.

Article #71 expands the same principle through key-person risk.

Your business may always need an owner

Of course.

Ownership itself creates responsibilities.

Direction.

Governance.

Capital.

Risk.

Certain strategic decisions.

I am not advocating some mythical fully autonomous company where the owner floats above it receiving dividends while robots and managers quietly produce infinite profit.

Real businesses need leadership.

The goal is not to become unnecessary.

It is to stop being necessary for everything .

Those are very different ambitions.

Perhaps you want to keep doing the technical work

Fine.

Do it.

But make it a choice.

Imagine you love designing.

Continue designing.

But build the business so somebody else could .

You love selling.

Keep selling.

But let the sales system survive a three-week holiday.

You love visiting customers.

Wonderful.

Do not make every customer relationship disappear if you stop.

This is the distinction I keep returning to:

Choice versus dependency.

A practical 30-day “Business or Job?” audit

For the next month, track every time the business requires you.

Not every time you choose to get involved.

Every time your involvement is genuinely necessary.

Write down:

What happened?

Why did it require you?

Could somebody else have handled it?

What prevented them?

Was it:

Authority?

Skill?

Information?

System?

Relationship?

Habit?

Your own reluctance to let go?

At the end of the month, group the dependencies.

You will probably find patterns.

Then classify your work

Put your recurring activity into four groups.

Owner-only

Genuinely belongs with you.

Keep it.

Owner-for-now

Someone else could eventually own it but capability has not yet been built.

Develop them.

Owner-by-habit

You still do it because you always have.

Transfer it.

Should-not-exist

Nobody should be doing it.

Remove or automate it.

That exercise can completely change the owner's role.

Measure owner dependency

If this matters, track it.

Useful measures might include:

Number of operational decisions reaching the owner.

Hours spent in day-to-day delivery.

Percentage of major customer relationships held only by the owner.

Number of routine approvals.

Number of direct reports.

Owner involvement in sales.

Owner involvement in technical delivery.

Number of days the company can operate without owner contact.

Do not measure all of those because I listed them.

Choose something capable of telling you whether dependency is falling.

What gets measured becomes easier to discuss.

Give yourself somewhere useful to go

This is crucial.

You successfully remove ten hours of operational work.

What happens?

If you have no better use for the time, you may drift straight back into operations.

The owner's next role needs designing too.

Perhaps the released capacity goes towards:

Strategy.

Developing leaders.

Important relationships.

Acquisitions.

Writing.

New markets.

Product development.

Speaking.

Research.

Another venture.

Or simply living more of your life outside the company.

You do not need to justify every released hour by creating another business task.

Freedom can be the return.

Business ownership should eventually create leverage

Money leverage.

People leverage.

Systems leverage.

Knowledge leverage.

Technology leverage.

Brand leverage.

Capital leverage.

Your individual effort may remain enormously important.

But it should not be the only thing generating movement.

That is the transition.

From:

I create value.

To:

I built something that creates value.

Both can be true simultaneously.

The balance should gradually change if independence, scale or eventual sale matter to you.

Do not wait until you want to sell

Owner dependency takes time to remove.

You cannot spend twenty years making every customer and decision dependent on you, then announce:

“I'm retiring in March.”

and expect somebody to buy an independent company in February.

Relationships need widening.

Managers need developing.

Systems need building.

Knowledge needs transferring.

Authority needs moving.

This is why exit planning begins long before exit.

Even if you ultimately never sell.

A sale-ready company is often simply a better designed company.

More resilient.

Better managed.

Less dependent.

More flexible.

The question is not whether you are indispensable today

You probably are.

Many good owners are.

The question is whether the business is becoming less dependent on that indispensability each year .

If revenue doubles but dependency doubles too, little has changed structurally.

If the company grows while:

Managers strengthen.

Systems improve.

Knowledge spreads.

Customers connect to the organisation.

Decision-making moves down.

Your role becomes more strategic.

then you are building something increasingly capable of standing independently.

That starts looking much more like a business.

So, business or job?

If every pound depends directly on your time, every major customer belongs personally to you, every decision comes back to you and the company becomes paralysed when you disappear, you have built something extremely job-like.

It might be an excellent job.

It might pay extraordinarily well.

You may even love it.

There is nothing wrong with that.

But call it what it is.

If what you actually want is:

An asset.

A scalable organisation.

A saleable company.

More freedom.

More resilience.

More strategic choice.

then start designing for independence.

Not by disappearing.

By building capability around you.

Transfer knowledge.

Develop managers.

Create decision boundaries.

Strengthen systems.

Widen relationships.

Remove unnecessary dependencies one at a time.

And keep asking:

Is there a better way for this to work without needing me?

Because ownership should eventually give you more options than employment did.

Not fewer.

How Do You Know Which Customers Are Actually Profitable?

Mon, 05 Oct 2026 15:52:54 GMT

You know which customers are actually profitable when you stop looking only at how much they spend and start looking at how much value remains after serving them .

At a practical level:

Customer revenue

minus:

The direct cost of what they bought

minus:

The additional cost of serving that particular customer

leaves:

Customer contribution.

Then you still need to consider:

Payment behaviour.

Working-capital requirement.

Risk.

Capacity consumed.

Future value.

That is why your biggest customer is not automatically your best customer.

A customer spending £500,000 a year can be less valuable than one spending £200,000 if the larger account requires:

Constant discounting.

Bespoke work.

Extra management.

Repeated site visits.

Rework.

Special reporting.

Long payment terms.

Senior-owner involvement.

And half your operations team every time something goes slightly wrong.

Turnover tells you how much the customer buys.

It does not tell you what they are worth.

Start with gross profit, not revenue

Suppose Customer A spends:

£500,000 a year.

Customer B spends:

£250,000.

Most businesses instinctively describe Customer A as the more important account.

Now imagine Customer A buys work averaging a 20 per cent gross margin.

Gross profit:

£100,000.

Customer B averages a 40 per cent gross margin.

Gross profit:

£100,000.

Already, the customer generating twice the revenue is producing exactly the same gross profit.

And we haven't considered the cost of actually looking after either of them yet.

This is why customer profitability analysis begins below the revenue line.

Gross profit still doesn't tell you the whole story

Two customers can create identical gross profit and consume completely different amounts of company resource.

Customer A:

Places predictable orders.

Uses your standard service.

Deals with one account contact.

Pays electronically on 30 days.

Rarely complains.

Customer B:

Places lots of small orders.

Requires custom paperwork.

Changes specifications.

Needs frequent meetings.

Calls your technical team constantly.

Demands urgent delivery.

Raises invoice queries.

Pays after 70 days.

Both may appear equally profitable if your reporting stops at product or project gross margin.

They aren't.

The second customer has a much higher cost-to-serve .

This is exactly the problem customer profitability analysis is designed to expose. ACCA's guidance on activity-based management notes that traditional contribution analysis can miss customer-specific overheads such as service time, and that allocating those costs using appropriate activity drivers can reveal supposedly valuable customers that are actually loss-making.

What is cost-to-serve?

Cost-to-serve means the resources your company consumes specifically because that customer exists and behaves in the way they do.

Not simply what it costs to manufacture the product or perform the service.

It can include:

Account management
Sales administration
Order processing
Special deliveries
Additional warehouse handling
Bespoke packaging
Technical support
Additional customer-service calls
Site visits
Complaints
Returns
Credits
Rework
Bespoke reporting
Additional quality checks
Meetings
Contract administration
Tender administration
Chasing payment
Managing invoice disputes
Senior-management involvement

The exact list depends entirely on the business.

A 2008 case study and literature review on cost-to-serve found that measuring customer-specific service activity created a substantially richer view of customer profitability than traditional product-margin analysis alone. The empirical part concerned one Brazilian food-industry business, so its detailed results should not be generalised across every SME, but the underlying distinction between product cost and customer-service cost is extremely useful.

Do not make this more complicated than it needs to be

This is where accountants can accidentally terrify normal human beings.

You hear:

Activity-based customer profitability analysis.

And suddenly it sounds as though you need six consultants and seventeen months to find out whether Dave's Builders is worth keeping.

You don't.

Not initially.

Start with the material costs.

You are trying to improve a commercial decision.

Not produce an academic thesis.

Ask:

What significant additional activity does this customer create compared with a normal customer buying the same thing?

That gets you a long way.

A simple example

Imagine two customers each generate:

£200,000 annual revenue.

Each produces:

£70,000 gross profit.

Looks identical.

Customer One requires roughly:

£5,000 account management.

£2,000 special delivery cost.

£1,000 administration.

£1,000 payment chasing and dispute handling.

Approximate contribution after identifiable service cost:

£61,000.

Customer Two requires:

£14,000 account management.

£8,000 special logistics.

£6,000 additional project support.

£5,000 rework and credits.

£4,000 reporting and administration.

£3,000 payment and dispute handling.

Approximate contribution:

£30,000.

Same revenue.

Same initial gross profit.

One relationship produces roughly twice the contribution of the other before wider company overhead.

That is commercially useful information.

Do not randomly dump every overhead onto every customer

This needs nuance.

You could take:

Head-office rent.

CEO salary.

Insurance.

Marketing.

IT systems.

Finance department.

Then allocate every penny across customers using some formula.

Eventually you arrive at a fully loaded profit figure for each one.

That can be useful for certain analysis.

It can also create nonsense.

Suppose Customer A disappears tomorrow.

Does your office rent immediately fall by £4,700?

Probably not.

Does your FD salary reduce by 7 per cent?

Unlikely.

So distinguish between:

Costs genuinely caused or materially influenced by the customer

and:

General business overhead that exists regardless.

For many customer decisions, I am particularly interested in the customer's contribution after direct costs and identifiable cost-to-serve.

Over the long term, of course, the customer base collectively must generate enough contribution to pay the company's overhead and create profit.

But allocating arbitrary slices of every fixed cost can sometimes make a perfectly useful customer appear loss-making even though removing them would not actually remove the corresponding cost.

Use numbers to improve judgement.

Not replace it.

Focus on costs that change because the customer behaves differently

This is where activity-based approaches become useful.

If one customer places:

Two large orders per month

and another places:

Forty tiny ones

their order-processing costs are probably different.

If one customer accepts standard deliveries

and another requires:

Timed delivery.

Dedicated vehicles.

Special packaging.

then logistics costs differ.

If one requires:

One annual account review

and another has:

Weekly calls involving three senior employees

the account-management cost differs.

You do not need to allocate every paperclip.

Concentrate on material differences in service behaviour .

Account-management time is a real cost

This is one businesses routinely underestimate.

Your customer spends £300,000.

They have a Key Account Manager.

Fine.

But they also regularly involve:

Operations Director.

Finance Director.

Technical Manager.

Managing Director.

Individually, nobody records much of it.

Thirty minutes here.

One meeting there.

A phone call.

Email chain.

Quarterly review.

Tender document.

Another meeting.

Across a year, the customer may consume hundreds of hours of relatively expensive people.

That time has an economic cost.

It also has an opportunity cost.

Those senior people cannot spend the same hour somewhere else.

Owner time counts too

This is especially important in owner-managed businesses because the owner often behaves like free labour.

The customer calls you personally.

You solve the problem.

No additional payroll occurred.

So apparently it cost nothing.

Nonsense.

Your time has a value.

If one customer requires five hours of owner attention every month, that is 60 hours a year.

What else could those 60 hours have created?

Sales?

Strategy?

Management development?

A new product?

Time with your family?

Even if you do not assign an exact hourly cost, record the consumption.

An account requiring enormous owner involvement is commercially different from one that works through the team and systems normally.

Rework belongs with the customer where appropriate

Be fair here.

Not all rework is the customer's fault.

If your company cocked it up, that is primarily an internal operational problem.

But when analysing customer economics, the cost still occurred while serving that customer.

You then need to separate why.

Was it:

Your error?

Customer changes?

Poor specification?

Repeated last-minute requests?

Ambiguous scope?

Bad estimating?

This distinction matters because the action changes.

Internal quality problem?

Fix the process.

Customer-driven variation?

Improve scope control or pricing.

Do not simply label customers unprofitable because your own business repeatedly delivers them badly.

Discounting must be included

You quoted:

£100,000.

Eventually sold:

£88,000.

The £12,000 discount is already visible in revenue.

But look at why.

Does this customer always negotiate aggressively?

Do they demand annual rebates?

Retrospective discounts?

Volume discounts?

Marketing contributions?

Tender reductions?

Do your internal reports show their apparent list-price value or the net revenue actually retained ?

Measure the real commercial deal.

Not the headline contract value.

Returns, credits and warranty matter too

A customer can look profitable on invoices and considerably less attractive once you include:

Credits.

Refunds.

Returns.

Warranty work.

Remedial visits.

Replacement stock.

Again, identify cause.

Some industries naturally contain returns.

Fine.

The question is whether this customer's behaviour is materially different from normal.

Customer profitability is useful precisely because averages hide variation.

Payment behaviour belongs in customer profitability

Two customers each owe you £100,000.

One pays on day 28.

The other pays on day 75.

That difference matters.

The slow-paying customer requires you to fund:

Payroll.

Materials.

Subcontractors.

Overheads.

for longer before receiving the cash.

They may also create:

Credit-control time.

Management attention.

Disputes.

Borrowing requirements.

The Office of the Small Business Commissioner says more than 1.5 million UK businesses are affected by late payments each year and that businesses affected spend an average of around 86 staff hours annually chasing overdue money. It estimates that roughly £26 billion is outstanding in late payments at any one time.

Those are economy-wide estimates, not a costing formula for your individual customer.

The point is straightforward.

Payment behaviour consumes real resources.

Agreed long payment terms are slightly different

Suppose a customer has agreed 60-day payment terms.

They pay on day 59 every time.

They are not paying late.

But you are still financing their terms.

That belongs in the commercial calculation.

If you buy materials today, pay staff Friday and receive customer cash in two months, the relationship has a working-capital requirement.

Maybe the margin justifies it.

Fine.

But recognise it.

One customer producing £100,000 annual contribution with fast payment may be financially more attractive than another producing £110,000 while tying up enormous working capital.

Cash has a cost and a constraint.

Invoice disputes tell you something too

One customer queries nearly every invoice.

Why?

Perhaps:

Your invoices are routinely wrong.

Fix your invoicing.

Or:

They use disputes as a mechanism for delaying payment.

Different problem.

Track it.

If the finance team spends 30 hours every month dealing with one customer's invoicing bureaucracy, that activity belongs somewhere in the account economics.

Customer profitability is not only the cost of fulfilling the physical order.

It is the cost of maintaining the entire commercial relationship.

Small orders can be disproportionately expensive

Imagine two customers.

Customer A buys £100,000 through:

Ten £10,000 orders.

Customer B buys the same £100,000 through:

Two hundred £500 orders.

If every order creates:

Processing.

Picking.

Packing.

Delivery.

Invoice.

Payment allocation.

customer B may require dramatically more administration.

This is one reason minimum order values, delivery charges and handling fees exist.

A customer can be perfectly viable at a different service model.

The objective is not automatically to get rid of them.

It is to make the economics work.

Bespoke requirements deserve a price

Some customers want:

Special reports.

Custom portals.

Unique labels.

Different packaging.

Dedicated stock.

Different ordering procedures.

Separate invoicing.

Special compliance paperwork.

None of that is automatically unreasonable.

They may have perfectly legitimate reasons.

But legitimate requirements still consume resources.

If the customer wants a genuinely bespoke service, the commercial arrangement needs to reflect the cost of providing it.

Otherwise standard customers subsidise bespoke customers.

Usually without anybody deliberately deciding that they should.

Calculate customer contribution in layers

You do not need one magical profitability number.

I prefer looking at several levels.

Revenue

How much do they actually spend after discounts and credits?

Gross profit

Revenue less the direct product or delivery costs you already normally allocate.

Customer-specific service costs

Account management.

Logistics.

Admin.

Support.

Rework.

Whatever is material.

Customer contribution

What remains after those identifiable costs.

Then separately consider:

Working capital.

Future value.

Risk.

Capacity.

That gives management a much richer picture than:

Top customers by turnover.

Start with the largest customers first

If you have 18,000 customers, do not calculate the individual profitability of all 18,000 on Tuesday.

Start where the money is.

Perhaps:

Top 20 by revenue.

Top 20 by gross profit.

Customers management suspects are difficult.

Customers receiving major discounts.

Customers with unusual service requirements.

Customers paying slowly.

Then look at patterns.

For high-volume consumer businesses, segment-level profitability may initially be more useful than individual analysis.

For example:

Customer type.

Order type.

Channel.

Region.

Service tier.

Acquisition channel.

The method should fit the business.

Do not assume your largest customers create most of the profit

Customer profitability can be highly concentrated.

Academic work on customer profitability has long examined the way profits are distributed unevenly across customer bases rather than assuming revenue and profit follow the same pattern.

The 2008 cost-to-serve case study mentioned earlier found an especially dramatic concentration: 80 per cent of margin after cost-to-serve came from only 6 per cent of that company's customers. That is one company's result and absolutely should not be turned into some ridiculous universal “6 per cent rule”.

The useful point is simply:

Look.

Your customer base may contain far greater profitability variation than revenue reporting suggests.

Beware the inevitable “80/20” bullshit

Someone will probably tell you:

“Twenty per cent of customers create 80 per cent of profit.”

Maybe.

Maybe not.

Pareto-style concentration appears in many datasets.

That does not mean your business will conveniently produce that exact ratio.

Calculate yours.

Do not build customer strategy around somebody else's catchy number.

Current profitability and future value are different

Imagine a new customer.

Year one includes:

Sales acquisition cost.

Setup.

Onboarding.

Training.

Integration.

The first twelve months may look mediocre.

But the customer is likely to remain for ten years with low ongoing servicing cost.

That could be an outstanding relationship.

This is why customer profitability analysis and customer lifetime value are related but different.

Research distinguishes current or historical customer profitability from the expected value of the customer's future relationship. One published portfolio-analysis study explicitly combined customer profitability with lifetime value, creditworthiness and payment performance rather than treating today's margin as the whole picture.

Do not fire a fantastic long-term customer because onboarding month looked expensive.

Equally, do not use imaginary future value to excuse terrible customers forever

This goes the other way too.

“They've got huge potential.”

For how long?

The customer has produced awful margin for four years.

Pays slowly.

Requires constant support.

But apparently:

“One day this account could be massive.”

Maybe.

What evidence?

Pipeline?

Committed growth?

New contract?

Strategic expansion?

Or hope?

Future value should be based on reasonable assumptions.

Not commercial fan fiction.

Loyalty does not automatically equal profitability

A customer buying from you for ten years feels valuable.

Often they are.

But longevity alone does not guarantee attractive economics.

Historic research into customer lifetime value and profitability has repeatedly shown that customer behaviour, frequency, value, service demand and future cash flows matter more than simply assuming long relationships are always the most profitable.

An old customer on a heavily discounted legacy price may be much less profitable than a newer account.

Loyalty is good.

Profitability still needs measuring.

Referrals and strategic value can be real

Some customers create value beyond their invoices.

Perhaps they:

Refer excellent customers.

Provide credibility in a target sector.

Act as a useful case study.

Help you enter another market.

Purchase several services.

Create predictable baseline workload.

Provide useful product feedback.

Fine.

Include strategic value in the decision.

But keep it separate from financial profitability.

Do not say:

“They're profitable because they give us great exposure.”

Say:

“The account loses £15,000 annually on direct economics, but we currently choose to retain it because it creates this specific strategic value.”

That is an informed decision.

Very different.

Put a value on referrals where you reasonably can

If a customer has referred:

Six customers.

Producing £400,000 gross profit.

that matters.

You may not allocate the entire £400,000 back to the referring customer, but you should recognise the relationship has broader value.

Likewise:

A reference customer who materially helps you win tenders may be commercially useful beyond their direct spend.

Again, specificity matters.

“Good for the brand”

is not the same as documented strategic value.

Capacity changes the profitability question

This is where customer profitability becomes strategic rather than simply accounting.

Imagine Customer A creates:

£40,000 annual contribution.

Customer B creates:

£55,000.

B looks better.

But B consumes three times as many specialist engineering hours.

Those engineers are already at capacity.

The company is currently turning away high-margin work.

Now the scarce resource matters.

How much contribution does each customer generate per unit of constrained capacity ?

This question becomes more important as businesses become busy.

When capacity is abundant, moderately profitable customers may be perfectly sensible.

When capacity is scarce, opportunity cost rises.

Article #65 touched on this from the perspective of deciding whether to exit a customer.

Customer profitability tells you who deserves the capacity before you reach that decision.

Contribution per scarce hour can be incredibly revealing

Suppose:

Customer A produces £50,000 contribution using 500 specialist hours.

That is approximately:

£100 contribution per specialist hour.

Customer B produces £60,000 contribution using 1,500 specialist hours.

Approximately:

£40 per specialist hour.

B produces more absolute contribution.

A uses scarce capacity much more efficiently.

Which one is better?

Depends on your constraint.

If specialist labour is the bottleneck, this analysis matters.

If specialist capacity is sitting idle, perhaps less.

Profitability depends partly on what resource the business is trying to optimise.

Risk belongs in the conversation

A customer producing excellent margin can still create risk.

Perhaps they represent:

40 per cent of revenue.

Or:

Their financial health looks weak.

Or:

The contract contains significant liability.

Or:

Payment disputes are increasing.

Or:

Their industry is deteriorating.

Risk does not necessarily mean the customer is unprofitable.

Keep the terms separate.

But customer portfolio decisions should consider:

Profitability.

Future value.

Risk.

Concentration.

A brilliant customer can still become a dangerous dependency.

Customer concentration can distort your behaviour

This is where large customers gain power.

They represent 30 per cent of revenue.

They ask for:

Another discount.

Longer terms.

Extra service.

You agree because losing them feels terrifying.

Over time, profitability erodes.

The customer did not necessarily do anything wrong.

They negotiated.

You accepted.

The real problem is dependence.

A stronger customer portfolio gives you the agency to negotiate based on economics rather than fear.

Build a simple customer profitability scorecard

Do not begin with 48 measures.

For major customers, I would want to understand:

Annual revenue

What do they actually spend?

Gross profit

What remains after direct product or delivery cost?

Cost-to-serve

What identifiable additional resource does the relationship consume?

Customer contribution

What remains after those costs?

Payment performance

Do they pay as agreed?

How much working capital do they consume?

Capacity

What scarce resources does the customer use?

Future value

What realistic commercial potential exists?

Risk

Concentration, credit, contractual or strategic risk.

Relationship quality

Is the relationship workable and constructive?

You can add sophistication later.

Those categories already produce a much better conversation than:

“They are our third-largest customer.”

Your CRM, finance and operations data need to meet

This is one reason customer profitability often remains invisible.

Finance knows:

Revenue.

Credits.

Payment.

Operations knows:

Labour.

Rework.

Deliveries.

Customer Service knows:

Complaints.

Sales knows:

Discounts.

Account Management knows:

Meetings.

The owner knows:

How many times the customer called them on Sunday.

None of the systems connect.

So the customer looks brilliant in the sales report.

Customer profitability is partly an information-flow problem.

You need enough of those perspectives in one place to understand the relationship properly.

You do not need perfect data to begin

Owners often postpone this because:

“Our systems don't capture it properly.”

Fine.

Estimate.

For your top ten customers, sit with the people actually serving them.

Ask:

Roughly how much account-management time?

How many unusual deliveries?

How much rework?

How many complaints?

How much senior involvement?

Are they unusually complex?

You will not get an audit-grade number.

You will probably discover enough to identify where deeper measurement is justified.

Approximate insight is better than precise ignorance.

But do not let opinion become the number

There is a danger on the other side.

Operations says:

“That customer is a fucking nightmare.”

Okay.

How?

What do they consume?

How often?

How much?

Maybe the customer genuinely is expensive to serve.

Or maybe one employee dislikes their procurement manager.

Use subjective experience to identify where to investigate.

Then use evidence where possible.

Customers can be profitable for one part of the business and destructive for another

Sales loves them.

Finance hates them.

Operations despises them.

This is useful information.

Why does each department see the customer differently?

Sales sees:

Revenue and commission.

Finance sees:

Slow payment.

Operations sees:

Complexity.

Customer Service sees:

Complaints.

Leadership needs the complete picture.

That is why customer profitability should be a management discussion, not a Finance spreadsheet nobody else sees.

Sales incentives can create unprofitable customers

Suppose a salesperson earns commission on revenue.

They win:

£500,000.

Brilliant.

Whether that work generates:

£150,000 contribution

or:

£20,000

may not materially change their reward.

What behaviour should you expect?

Revenue.

This does not mean every company should pay commission purely on profit.

That can create its own complications.

But incentives should not actively encourage people to win work the company does not actually want.

At minimum, salespeople need visibility around:

Margin.

Discount authority.

Customer fit.

Commercial terms.

Winning work is not enough.

Winning good work is the objective.

Do not punish Sales for costs they cannot control

Be fair here too.

If Sales wins a perfectly sensible contract at good margin and Operations then creates:

Rework.

Labour overruns.

Poor scheduling.

that is not evidence Sales won a bad customer.

Customer profitability can deteriorate because your company serves the account inefficiently.

The analysis should help identify where responsibility sits.

Not become ammunition in departmental warfare.

Segment customers by what you should do next

Once you have the information, avoid immediately ranking everyone from saint to bastard.

Different customers need different action.

Highly profitable and strategically valuable

Protect them.

Understand why the relationship works.

Maintain service.

Do not take loyalty for granted.

Profitable but high cost-to-serve

Good account.

Look for ways to reduce unnecessary service cost without damaging value.

Low profitability but fixable

These are often the biggest opportunity.

Reprice.

Change scope.

Reduce bespoke service.

Introduce minimum orders.

Change delivery terms.

Adjust account management.

Improve your own delivery.

Currently weak but strategically valuable

Make the strategic case explicit.

Set a time horizon.

Define what needs to improve.

Do not subsidise indefinitely because somebody once used the word “strategic”.

Persistently loss-making with little strategic justification

Now Article #65 becomes relevant.

Why are you continuing?

Fix the economics before firing the customer

Customer profitability analysis should create options.

Perhaps the customer is expensive because they place 100 small orders.

Could you introduce:

Minimum order values?

Scheduled consolidated deliveries?

Online ordering?

Perhaps management time is enormous.

Could service move to:

A structured account-review process?

Perhaps reporting is bespoke.

Could it become:

A paid premium service?

Perhaps payment is slow.

Could you agree:

Deposit?

Stage billing?

Shorter terms?

Direct debit?

The purpose of analysis is not to create a hit list.

It is to understand how to improve the customer portfolio.

Some of the best profitability gains require no new customers

This is the interesting bit.

Business growth conversations naturally focus on:

More leads.

More sales.

More customers.

But imagine you already have 200 customers.

You discover that:

Thirty produce weak margin because of old pricing.

Ten create huge servicing costs.

Fifteen require commercial terms that no longer make sense.

Improving the economics of the existing base might produce more profit than winning another fifty customers.

And without adding equivalent operational workload.

That is leverage.

Customer profitability should influence pricing

Do not necessarily charge every customer a different random price based on how annoying they are.

That is hardly a sophisticated pricing strategy.

But understand what drives cost.

Perhaps your pricing needs explicit charges for:

Express delivery.

Custom reporting.

Tiny orders.

On-site support.

Complex setup.

Emergency work.

Additional revisions.

Those are service features.

Price them.

Good profitability analysis often reveals which apparently “free” parts of your offer are not remotely free to deliver.

It should influence service design too

Perhaps the highest cost-to-serve comes from:

Phone-based order entry.

Could standard customers use a portal?

Perhaps account reviews are consuming enormous senior time.

Could they become quarterly rather than monthly?

Perhaps every customer receives the same premium support level regardless of value.

Do you need different service tiers?

Cost-to-serve analysis can improve the system instead of merely identifying expensive people inside it.

That was also a conclusion of the published cost-to-serve case study: profitability information can support changes to commercial policy and the way service activities are designed, rather than simply customer removal.

Payment performance should affect commercial terms

If one customer repeatedly pays late, chasing them is only the visible cost.

There is also:

Cash tied up.

Potential borrowing.

Reduced investment flexibility.

Management attention.

Risk.

The Small Business Commissioner specifically encourages businesses to establish clear payment terms, invoice accurately and promptly, and manage overdue payments actively rather than treating collection as an afterthought.

A customer's price and service proposition should make sense alongside the credit you are effectively extending to them.

Review profitability periodically

Customer economics change.

A fantastic customer becomes difficult after acquisition.

A previously demanding customer standardises their process.

Pricing increases.

Volumes change.

A new manager improves the relationship.

Payment performance changes.

Your own systems become more efficient.

This is not a one-off classification exercise.

For major accounts, review periodically.

Maybe quarterly.

Maybe annually.

Frequency depends on the business.

The point is not to label:

GOOD CUSTOMER

in permanent marker.

It is to understand the current economics.

A practical 30-day customer profitability audit

If you have never done this, keep it manageable.

Week 1: Choose the customers

Start with perhaps:

Your largest accounts.

Customers management believes are unusually demanding.

Customers receiving significant discounts.

Customers with poor payment behaviour.

And a few customers everyone believes are excellent.

The comparison is useful.

Week 2: Build the basic economics

For each customer, establish:

Revenue.

Gross profit.

Discounts and credits.

Payment terms.

Payment performance.

Then identify the major additional service activities they create.

Do not chase pennies.

Find material differences.

Week 3: Speak to the people serving them

Ask:

Sales.

Operations.

Finance.

Customer Service.

Account Management.

What does this customer require that a normal customer does not?

Where does time go?

What problems recur?

What would we change if we could redesign the relationship today?

This is where hidden cost appears.

Week 4: Decide what to do

Protect excellent relationships.

Repair weak economics.

Reprice where justified.

Redesign service.

Improve internal delivery.

Change terms.

Create a deliberate strategic exception where appropriate.

Or consider exiting the relationship if the economics cannot reasonably be fixed.

Then measure again later.

One of my favourite questions still works here

Article #65 used this question when deciding whether to fire a customer:

Would we knowingly take this customer on today?

For profitability analysis, expand it:

Knowing their revenue, margin, cost-to-serve, payment behaviour and capacity requirement, would we actively pursue another customer exactly like them?

That is incredibly revealing.

If the answer is:

Absolutely. Give me twenty of them.

Wonderful.

You have learned something about your ideal customer.

If the answer is:

Jesus Christ, no.

You have learned something equally valuable.

Your ideal customer should be commercially ideal, not merely pleasant

Marketing teams often create ideal-customer profiles around:

Sector.

Company size.

Location.

Job title.

Problem.

Fine.

Add economics.

Which customers produce:

Healthy margins?

Predictable delivery?

Good payment?

Reasonable service requirements?

Retention?

Good use of capacity?

The best target market is not merely the group most likely to buy.

It is the group most likely to create mutually valuable business .

That should influence marketing and sales strategy.

Profitability data should change who you try to win

This completes the loop.

Suppose analysis shows:

Manufacturers with 50 to 250 employees produce excellent customer contribution.

Very small firms buy frequently but consume enormous support time.

Large corporates generate strong revenue but margins suffer through procurement discounts and bespoke requirements.

Now Marketing has useful information.

Sales has useful information.

Perhaps the next campaign deliberately targets the segment creating the best overall economics.

That is considerably more intelligent than telling Marketing:

“We just need more leads.”

More of which leads?

Do not optimise solely for profitability today

One final warning.

If you managed customers purely by immediate current-period profit, you could make stupid decisions.

You might stop investing in:

New customers.

Developing markets.

Strategic relationships.

Innovation.

Accounts with genuine growth potential.

Customer profitability is an input.

Not an algorithm replacing management judgement.

Academic customer-lifetime-value literature exists precisely because forward-looking value can differ from current-period profitability, while risk and payment behaviour can materially change how a relationship should be assessed.

The objective is not:

Keep only the customers producing the highest margin today.

It is:

Understand the economics well enough to make deliberate customer decisions.

Revenue is vanity if you never ask what survives

A customer can make your sales report look fantastic.

Keep employees busy.

Give you a recognisable logo for the website.

And still produce very little economic value.

Another customer can quietly buy a moderate amount, pay on time, use the service exactly as designed and generate excellent contribution year after year.

Which one is more important?

You cannot answer from turnover.

Measure:

What they buy.

What it costs to deliver.

What it costs to serve.

How they pay.

What scarce capacity they consume.

What future value realistically exists.

What risk they create.

Then decide what the relationship deserves.

Some customers need protecting.

Some need repricing.

Some need a different service model.

Some need your own operation fixing.

And some, eventually, may need leaving.

But first you need to know the numbers.

Because the customer spending the most money with you is not necessarily the customer making you the most money.

Is My Business Ready To Scale?

Mon, 05 Oct 2026 15:45:24 GMT

Your business is ready to scale when increasing demand will produce significantly more value without simply multiplying the weaknesses, costs, complexity and owner dependency already inside the company .

That is a much higher bar than:

“We're really busy.”

Or:

“Sales are flying.”

Or:

“We could easily win more work.”

Demand is only one part of scale readiness.

You also need enough:

Margin
Cash and working capital
Delivery capacity
Management capability
Systems
People
Information
Leadership
Customer diversification
Operational control

And, crucially:

The business cannot become progressively more dependent on the owner every time revenue increases.

If doubling turnover requires you to double the number of problems you personally solve, you haven't built a scalable business.

You have built a larger job.

Growth and scale are not quite the same thing

Business language gets messy here.

People regularly use “growth” and “scale” interchangeably.

I wouldn't.

A company grows when it becomes bigger.

More customers.

More employees.

More revenue.

More locations.

More output.

Scaling should ideally mean the business can increase output and commercial value without its costs, complexity and owner involvement increasing at exactly the same rate .

That distinction is easier to see at the extremes.

If a consultant earning £150,000 needs to work twice as many hours to earn £300,000, they have grown revenue.

They haven't scaled much.

If a software company can add another 5,000 customers without adding 5,000 employees, the model is inherently more scalable.

Most real businesses sit somewhere between those extremes.

A construction contractor will always need more delivery capacity as it grows.

A restaurant cannot serve unlimited customers from one kitchen.

A consultancy still needs people.

So “scalable” does not mean:

Revenue increases while costs stay exactly the same.

It means the business becomes capable of handling greater volume without every important resource increasing proportionately or the organisation becoming progressively less efficient .

That is what you are testing.

Being able to sell more does not mean you are ready to scale

This is probably the biggest mistake.

Sales are strong.

Pipeline looks excellent.

Marketing is working.

So leadership says:

“Now we need to scale.”

Perhaps.

But what happens when another 30 per cent of work enters the business?

If the answer is:

Everyone works later.

The owner gets dragged back into operations.

Quality slips.

Customer response times get worse.

More mistakes happen.

Managers become overloaded.

Cash gets tighter.

You recruit desperately.

Margin falls.

then demand is not the constraint.

Your operating system is.

Article #68 looked at this from the profitability side.

Winning more work into an operation that leaks margin can amplify the leak.

Never scale a problem merely because the sales team has found enough customers to feed it.

The first test: is demand proven?

You need evidence that people genuinely want more of what you sell.

Not:

“The market is huge.”

Most markets are huge when described vaguely enough.

What evidence exists inside your business?

Look at:

Growing enquiry volume.

Healthy conversion.

Repeat purchasing.

Strong retention.

Waiting lists.

Capacity-related lost sales.

Recurring revenue.

Geographic demand.

Customers buying additional services.

Pipeline quality.

Referral volume.

Orders repeatedly exceeding current capacity.

Ideally, demand has enough consistency that you are not making permanent investment against one unusually good quarter.

The UK government's August 2026 review of high-growth firms is useful here. It found that rapid business growth is often episodic rather than permanent, with the average high-growth firm spending only a minority of its observed life in a high-growth period. High-growth years often cluster together, but fast growth should not simply be assumed to continue indefinitely.

Yesterday's growth is evidence.

It is not a guarantee.

Ask how much demand you could already handle

This matters before adding more capacity.

Suppose your company generates £4 million revenue.

Leadership thinks £6 million requires:

More people.

Larger premises.

New software.

Another management layer.

Maybe.

But perhaps current capacity is being wasted through:

Poor scheduling.

Rework.

Low-value customers.

Slow decision-making.

Unused equipment.

Bad shift design.

Manual administration.

Owner bottlenecks.

Weak delegation.

Before investing to create new capacity, find out how much additional output the existing operation could produce if it worked better.

Scaling should not become an excuse to avoid operational improvement.

The second test: do the unit economics work?

Before scaling anything, establish whether one additional unit of whatever you sell produces acceptable economics.

One more customer.

One more job.

One more order.

One more location.

One more employee.

One more £100,000 of turnover.

What happens financially?

If each extra £1 of revenue produces healthy contribution and the company has enough capacity to serve it, growth can be extremely attractive.

If each extra £1 creates:

Discounting.

Overtime.

Extra management.

Rework.

Expedited materials.

Additional support.

then the economics may deteriorate with volume.

Your management accounts should make this visible.

Article #75 covered the financial information an owner should be receiving.

You need to know:

What margin are we making now?

What margin do we expect at greater scale?

What changes as volume rises?

Which costs remain broadly fixed?

Which increase?

Which appear only once we cross another capacity threshold?

Do not scale something that barely makes money

This deserves stating plainly.

Imagine a service produces:

£1 million revenue.

£60,000 genuine operating profit.

Management decides:

“Let's get this to £3 million.”

Why?

What happens at £3 million?

Perhaps efficiency improves and margin rises substantially.

Excellent.

Prove the logic.

But if the underlying margin remains 6 per cent, you may triple:

People.

Customers.

Problems.

Working capital.

Risk.

for another £120,000 profit.

Perhaps that is commercially worthwhile.

Perhaps it isn't.

The word scale does not magically turn weak economics into good economics.

The third test: what happens to gross margin as you grow?

Some businesses become more efficient with scale.

Purchasing improves.

Fixed costs spread.

Technology produces leverage.

Management becomes more specialised.

Others experience the opposite.

Overtime increases.

Quality falls.

Recruitment becomes expensive.

Temporary labour appears.

More managers are required.

Operational complexity increases.

Small errors become large errors.

Look at your recent history.

When revenue rose previously:

Did gross margin improve?

Remain stable?

Fall?

Why?

This is useful evidence about how your current model behaves under additional load.

Do not build the next growth plan on assumptions contradicted by your own numbers.

The fourth test: can cash survive the growth?

This is one of the strangest realities of business.

Growth can create a cash crisis.

More work means more money, eventually.

It can also mean paying for:

Wages.

Stock.

Materials.

Subcontractors.

Recruitment.

Vehicles.

Premises.

Equipment.

Marketing.

Software.

before customers pay you.

British Business Bank guidance explicitly identifies scaling and growing a business as activities requiring capital and stresses the importance of cash-flow forecasts, working capital and healthy financial fundamentals when funding expansion.

Its 2025/26 Small Business Finance Markets report similarly notes that external finance can support expansion into markets, technology and capacity where businesses cannot fund the required expenditure entirely from existing cash flows.

This matters because:

Profitable growth can still run out of cash.

Model the cash requirement before pressing the accelerator

Suppose you want to add £2 million of revenue.

What needs to happen first?

Perhaps:

Recruit six people.

Buy £200,000 of stock.

Add three vehicles.

Increase marketing.

Move premises.

Customers pay you 60 days after invoice.

You may spend hundreds of thousands of pounds before the first meaningful new cash arrives.

Create a proper forecast.

Not:

“Revenue will cover it.”

When?

How much?

Under what payment assumptions?

What happens if customers pay later?

What happens if sales ramp more slowly?

What happens if recruitment happens faster than revenue?

Growth eats cash before breakfast if you let it.

The fifth test: can delivery absorb more demand?

Imagine sales increase 30 per cent next month.

What physically happens?

Do you have enough:

People?

Equipment?

Space?

Stock?

Suppliers?

Project managers?

Vehicles?

Production capacity?

Customer service?

Warehouse capacity?

Technical capability?

If the answer is:

“We'll work it out.”

you are not testing scale.

You are testing your team's tolerance for chaos.

Map the constraint.

What breaks first?

That should become part of the growth plan.

Find the choke point

Every operating system has one.

Perhaps:

Sales can generate £10 million but Operations can only deliver £7 million.

Production can manufacture enough but installation cannot fit it.

The workshop has capacity but engineering approval does not.

Marketing creates enough enquiries but Sales cannot follow up.

Everyone can deliver but one person still prepares every quote.

The entire company can grow except Finance cannot fund the working capital.

Scaling means increasing the capacity of the constraint , not randomly increasing everything.

If your business is a ten-lane motorway that narrows to one lane at the owner, hiring more salespeople simply sends more traffic towards the queue.

The sixth test: are your systems repeatable?

At low volume, businesses survive through memory.

Sarah knows.

Ask Dave.

We've always done it this way.

Just speak to Adam.

At greater scale, informal knowledge becomes expensive.

More customers.

More employees.

More shifts.

More locations.

More transactions.

More handovers.

You need enough consistency that competent people can repeatedly produce the intended outcome.

That might require clear processes for:

Sales handover.

Quoting.

Customer onboarding.

Purchasing.

Scheduling.

Quality.

Billing.

Complaints.

Recruitment.

Management reporting.

Not a 600-page procedure manual.

Enough structure to make good outcomes repeatable.

Standardise before you multiply

Suppose you have one branch.

It runs through dozens of informal workarounds.

Then you open three more.

Congratulations.

You now have four slightly different collections of workarounds.

Article #69 made this point about second locations.

Before replication, understand:

What must be standard?

What can vary?

What makes the existing model successful?

Which knowledge needs transferring?

How will quality be monitored?

Scaling inconsistency simply creates bigger inconsistency.

The seventh test: can your management team manage the next version of the company?

A £2 million company and a £10 million company are not simply the same business with a larger sales number.

More employees create:

More communication.

More management.

More coordination.

More decisions.

More conflict.

More performance issues.

More specialist roles.

The owner can no longer personally bridge every gap.

The UK government's 2026 analysis of high-growth firms found that businesses experiencing high growth had higher average management-practice scores than non-high-growth firms, even before entering their growth periods. The report is careful not to claim that this observation alone proves management quality causes growth, but the association is significant and consistent with wider evidence connecting structured management practices with business performance.

That should make intuitive sense.

As complexity increases, management quality matters more.

Ask whether you have managers or senior employees

There is a difference.

A senior employee may be excellent technically.

A manager needs to:

Set expectations.

Allocate work.

Make decisions.

Hold people accountable.

Manage performance.

Develop employees.

Resolve problems.

Communicate.

Protect standards.

Understand commercial consequences.

If every difficult situation still requires the owner, management capability has not scaled.

You may have job titles.

You do not yet have the management layer the next stage requires.

The eighth test: can you recruit fast enough without lowering the bar?

Growth plans often contain an innocent line:

Hire 20 additional people.

Right.

From where?

Article #62 looked at why finding good employees is already difficult for many businesses.

The ScaleUp Institute's 2025 Annual Review found that access to markets remained the most frequently reported challenge among scaleup leaders at 58 per cent, followed by talent and leadership at 55 per cent and finance at 42 per cent.

Those are useful numbers because they show that scaling problems are rarely just about sales.

Can you attract the people?

Can you afford them?

Can you onboard them?

Can existing managers absorb them?

Can you train them without experienced staff spending their entire lives teaching new starters?

A growth plan that requires 30 people you cannot realistically recruit is not yet a plan.

Retention becomes even more important during scale

Imagine hiring ten people while losing six experienced employees.

Technically:

Headcount +4.

Operationally:

Potential disaster.

Existing employees hold:

Customer knowledge.

Technical knowledge.

Culture.

Process knowledge.

Judgement.

Scaling while employee turnover increases creates a permanent training burden.

Article #73 explored why good employees leave.

Before significant expansion, look at:

Regrettable turnover.

Management quality.

Workload.

Career progression.

Pay.

Culture.

Your growth plan should not depend on constantly replacing experienced capability.

The ninth test: can the company make decisions without you?

This may be the most important one.

Revenue grows.

Team grows.

The owner remains the decision hub.

Now every additional employee creates more decisions that eventually reach the same person.

Growth therefore increases owner dependency.

This feels like:

More phone calls.

More approvals.

Give authority before volume arrives

Do not wait until 80 employees are asking questions to decide what managers can authorise.

Define:

Spending authority.

Pricing authority.

Customer credits.

Recruitment decisions.

Scheduling.

Purchasing.

Commercial thresholds.

Escalation boundaries.

People should know:

What is mine?

What requires discussion?

What absolutely must escalate?

You do not remove control by creating clear authority.

You replace constant intervention with deliberate control.

The tenth test: is information good enough?

A small company can be run partly by feel.

The owner knows everyone.

Sees the workshop.

Knows the customers.

Hears the problems.

As the business grows, your senses cover a smaller percentage of reality.

You need management information.

Sales.

Pipeline.

Margin.

Cash.

Delivery.

Capacity.

People.

Customer issues.

Whatever indicates the health of the model.

If your reporting currently requires the owner to ask six people:

“How are things looking?”

your information system probably needs strengthening before the company doubles.

The company should tell you what is happening.

Not require archaeology.

Your scorecard becomes more important as direct visibility falls

You cannot attend every job.

Hear every call.

Inspect every invoice.

Know every employee.

So define the handful of measures that warn you early.

For example:

Qualified pipeline.

Conversion.

Order book.

Gross margin.

Labour utilisation.

Delivery performance.

Customer complaints.

Debtor days.

Employee turnover.

Do not track numbers because dashboards look professional.

Track the numbers that tell you whether scale is working .

The eleventh test: is technology helping or merely decorating the business?

Scaling increases transaction volume.

Customers.

Invoices.

Orders.

Tasks.

Emails.

Reports.

Data.

If each extra unit requires proportional administration, overhead grows quickly.

Article #70 explored where small businesses should automate first.

Before scaling, identify repetitive work likely to increase dramatically with volume.

Can systems handle it?

Can information move automatically?

Can customers self-serve some routine actions?

Can reporting update without manual copying?

Can administrative steps disappear?

Technology should create operating leverage.

Not simply add another subscription.

The twelfth test: are suppliers ready?

Scaling does not happen entirely inside your company.

What about:

Materials.

Subcontractors.

Manufacturers.

Distribution.

IT providers.

Professional services.

Your biggest supplier may currently serve you beautifully at £2 million turnover.

Can they support £6 million?

Do lead times change?

Do payment terms change?

Do you become more or less important to them?

What happens if their capacity becomes constrained?

A growth plan depending on another company's capacity needs their involvement.

Do not discover after winning the work that your supplier cannot fulfil it.

The thirteenth test: what happens to quality?

Growth exposes quality systems.

When volume increases:

Does error rate rise?

Does rework increase?

Do customer complaints increase?

Does onboarding become rushed?

Do managers inspect less?

Do experienced people spend less time supervising?

This is one reason I would scale in controlled stages where possible.

Increase volume.

Watch quality.

Learn.

Then increase again.

You do not need to throw the company from £5 million to £15 million in one heroic leap simply because a spreadsheet says the market exists.

The fourteenth test: how concentrated is your growth?

Imagine your growth plan says:

£5 million today.

£8 million next year.

Wonderful.

Then you discover £2.5 million of the additional £3 million comes from one customer.

That is growth.

It is also concentration.

What happens if that customer leaves?

Changes supplier?

Gets acquired?

Delays payment?

Reduces spending?

The same applies to:

One sales channel.

One employee.

One product.

One supplier.

One geographic market.

Scale should ideally improve the company's resilience as well as its size.

Not create a much larger company balanced on one stick.

The fifteenth test: are you scaling demand or discounting?

Revenue growth is easy if you are willing to make increasingly unattractive deals.

Lower price.

Longer payment terms.

More included service.

Wider scope.

Then leadership celebrates growth.

Article #68 covered what happens when sales rise while profit does not.

Ask:

Are customers buying because the proposition has become stronger?

Or because we made the economics worse for ourselves?

Growth purchased through margin destruction needs careful examination.

The sixteenth test: does the strategy actually require scale?

This is worth asking because business culture tends to treat larger as automatically better.

Why do you want the company to become bigger?

More profit?

Sale value?

Market position?

Employee opportunity?

Personal ambition?

Competitive defence?

Economies of scale?

Perhaps those are excellent reasons.

But perhaps you currently have:

£4 million turnover.

£800,000 profit.

Excellent team.

Strong customers.

Reasonable owner workload.

And you are considering building:

£10 million turnover.

£850,000 profit.

Seventy employees.

Three times the stress.

Because:

“The next target is ten million.”

Why?

Growth is a strategic choice.

Not an obligation.

Whole-Life Profit belongs in the scale decision

Scaling should not only increase the company's numbers.

What does it do to:

Your time?

Family?

Health?

Attention?

Freedom?

Risk?

Some periods of growth genuinely require additional effort.

That is fine.

I have never subscribed to the idea that successful businesses can always be built while everybody skips gently through a field working four hours a week.

But know what you are choosing.

If the plan requires the owner to return to 70-hour weeks indefinitely, the operating model may be scaling revenue while shrinking Whole-Life Profit.

That belongs in the decision.

Scale should eventually create leverage

In the early phase, scale may actually reduce profit.

You hire ahead.

Invest in systems.

Add management.

Move premises.

Buy equipment.

That can be rational.

But those investments should create future leverage.

Ask:

What becomes easier once this investment exists?

New manager?

Removes owner bottleneck.

Automation?

Allows more transactions without equivalent admin.

New machine?

Increases productive output.

Larger premises?

Removes capacity constraint.

If the investment adds cost without creating future capacity, resilience or efficiency, question it.

Be careful with premature management layers

The opposite problem exists too.

Owners read about scaling and immediately hire:

COO.

CFO.

CMO.

HR Director.

Head of Strategy.

Head of People.

Head of Something Else.

Suddenly a £2 million business has the leadership structure of BP.

Build the organisation required by the next stage.

Not the one that looks impressive on LinkedIn.

Every layer needs enough value and complexity underneath it to justify existing.

Finance readiness is more than having money in the bank

If growth requires outside finance, prepare properly.

British Business Bank guidance says lenders and investors commonly consider matters including the company's business plan, cash-flow forecast, credit position, profitability and wider financial health when assessing funding.

Ask:

How much funding do we need?

What is it funding?

How long until the investment produces return?

What happens if the growth takes twice as long?

What repayments or investor expectations follow?

Do we still have enough headroom afterwards?

External finance can create opportunity.

It also creates obligations.

The Scale Readiness Test

Before deliberately accelerating growth, I would assess the business across these areas.

Demand

Do we have strong enough evidence that additional demand exists and is likely to persist?

Economics

Does the current proposition produce acceptable margin?

What happens to margin as volume increases?

Cash

Can we fund the working-capital requirement and upfront investment?

What happens in a slower-growth scenario?

Capacity

Where is the first operational constraint?

Can it be increased economically?

Systems

Can core work be repeated reliably by different competent people?

Management

Do we have enough real management capability for the next level of complexity?

People

Can we recruit, train and retain the additional capability the plan requires?

Owner dependency

Does growth increase or reduce the number of things requiring the owner?

Information

Can management see the business clearly enough to detect deterioration early?

Technology

Can routine volume increase without administration increasing proportionately?

Supply chain

Can critical suppliers support the intended growth?

Quality

Can standards survive higher volume?

Concentration risk

Does growth leave us dangerously dependent on any customer, channel, supplier or person?

Strategy

Why are we scaling?

What outcome makes the additional size worthwhile?

You do not need a perfect score in every category.

You need to know where the weak points are.

Red flags that tell me a business probably isn't ready

I would become cautious if:

Profit is already disappointing at current volume.

Cash is regularly tight.

Management accounts arrive late or are poorly understood.

The owner approves nearly everything.

Managers have job titles but little authority.

Good employees are already overloaded.

Recruitment is permanently reactive.

The business has no idea which customers or services are profitable.

Quality falls every time workload rises.

Systems rely heavily on individual memory.

Sales and operations regularly fight about what was sold.

One customer represents a dangerous share of revenue.

The growth plan assumes every forecast goes right.

The business already struggles to deliver existing work.

Leadership believes hiring more people will automatically solve everything.

None of those necessarily means:

Never scale.

It means:

Fix something first.

Green lights

I become considerably more comfortable where:

Demand has been repeatedly demonstrated.

Core economics are healthy.

Margins remain resilient under additional volume.

Cash forecasts include the growth investment and working-capital requirement.

The company understands its capacity constraint.

Operational processes are reasonably repeatable.

Managers genuinely manage.

The owner is becoming less operationally essential.

Recruitment and development plans exist.

Management information arrives quickly enough to act.

Technology supports rather than complicates the operation.

Customer and supplier concentration are understood.

Quality is measured.

The growth plan survives a credible downside scenario.

Most importantly:

The leadership team knows exactly why it wants to scale.

Run the downside scenario

Do not test only the beautiful version.

Imagine:

Revenue grows half as quickly as forecast.

You recruit the people anyway.

A large customer leaves.

Debtors worsen.

The new manager does not work out.

A software implementation runs late.

Gross margin falls three points.

What happens?

Can the business absorb it?

Do you still have enough cash?

What gets delayed?

What can be reversed?

Which commitments are fixed?

This is not pessimism.

It is risk management.

A business ready to scale should have enough resilience to survive growth being less tidy than the spreadsheet.

Do not confuse temporary pain with structural failure

Scaling can be uncomfortable.

New systems initially slow people down.

New managers need time.

Recruitment creates training demand.

Premises moves disrupt things.

Costs appear before benefits.

That does not mean the growth plan is wrong.

Know what temporary investment should look like.

For example:

“For six months, overhead will increase ahead of revenue because we are building the delivery team required for contracted demand.”

Fine.

Then measure whether reality matches the thesis.

The problem is:

“Margins keep getting worse, everybody is overloaded and we're not sure why, but this is probably what scaling feels like.”

No.

Investigate.

Scale in stages where possible

You do not have to commit the whole company to the final destination immediately.

Perhaps the plan is to move from £5 million to £10 million.

First prove £6 million.

What broke?

What didn't?

What did margins do?

What happened to cash?

What management capability was missing?

What did customers experience?

Then build towards seven.

This creates feedback.

The UK government's latest high-growth research reinforces that growth is often episodic rather than a permanent straight line. Less than 5 per cent of businesses in its dataset ever met the tighter OECD-style high-growth definitions, and even firms that do experience rapid growth typically spend only part of their lives in that state.

There is no shame in consolidation between growth phases.

Sometimes the strongest thing a business can do after growing quickly is stop accelerating for a moment and build the infrastructure capable of supporting what it has already become.

Growth creates a new business

This is something owners underestimate.

At £1.5 million turnover, your company may operate through:

Relationships.

Founder judgement.

Informal communication.

Generalists.

At £8 million:

You need more structure.

More specialist management.

Better reporting.

Clearer authority.

More deliberate systems.

You are not simply enlarging the old business.

You are repeatedly rebuilding the organisation required to carry the next amount of complexity .

I experienced this myself.

Growing a company from around £1.5 million to roughly £8.5 million in turnover was not one long process of simply selling more.

Different stages exposed different weaknesses.

What worked at one level became completely inadequate at another.

More work required different management.

Different structure.

Different systems.

Different conversations.

That is one reason I am cautious when someone says:

“We know how to run the business. We just need more sales.”

You know how to run the business you currently have.

The next version may require you to learn again.

Better management tends to exist before the growth

This is particularly interesting in the government's 2026 high-growth analysis.

High-growth businesses in the dataset showed persistently stronger management scores than non-high-growth companies, including before their rapid-growth periods. The researchers specifically caution against interpreting this as simple proof that improving a management score will directly trigger growth, but the pattern matters.

In other words:

Do not wait until growth overwhelms you before becoming better managed.

Build management capability before you desperately need it.

That is generally cheaper.

The biggest scaling barriers are remarkably unsurprising

The latest ScaleUp Institute review found that leaders of scaling UK companies continued to identify four stubborn areas:

Access to markets.

Talent and leadership.

Finance.

Infrastructure.

Markets came first at 58 per cent, talent and leadership at 55 per cent and finance at 42 per cent.

That is useful because scaling conversations can become obsessed with:

AI.

Software.

Funnels.

“Growth hacks.”

The fundamental issues remain remarkably commercial.

Can we sell?

Can we deliver?

Can we find and lead the people?

Can we fund it?

Does the infrastructure support it?

Your readiness assessment should probably concentrate there before worrying about whichever scaling tactic is fashionable this month.

Sometimes the correct answer is “not yet”

This is not failure.

Suppose the scale-readiness review discovers:

Healthy demand.

Strong margins.

But:

Owner dependency is severe.

Management team weak.

Cash tight.

Excellent.

You learned something incredibly valuable before trying to double.

Perhaps the next six months become:

Build management.

Transfer authority.

Improve cash reserves.

Strengthen reporting.

Then accelerate.

A deliberate pause can increase the probability that the next growth phase actually works.

Turn weaknesses into a 90-day readiness plan

Do not produce a 40-page scale-readiness report and admire it.

Pick the few constraints preventing growth.

For example:

Constraint 1: Owner dependency

90-day outcome:

Transfer routine operational and customer decisions to the Operations Director.

Constraint 2: Weak working capital

90-day outcome:

Reduce debtor days and secure appropriate additional facility before recruitment begins.

Constraint 3: Unclear delivery capacity

90-day outcome:

Establish realistic weekly productive capacity and identify the investment required to increase it by 25 per cent.

Now the scaling decision has become practical.

Article #66 provides the deeper structure for turning those into an executable 90-day plan.

Do not scale chaos

This is the sentence I would put above the door.

If your business currently relies on:

Heroics.

Owner intervention.

Permanent overtime.

Tribal knowledge.

Weak margins.

Cash juggling.

Manual workarounds.

Constant firefighting.

then more customers are unlikely to cure it.

They will probably expose it.

Scaling works best when you already understand the machine.

What makes money.

What creates capacity.

Where constraints sit.

How decisions happen.

Who owns what.

What customers genuinely value.

Then additional demand creates leverage.

Without that understanding, growth can simply create a larger organisation with more revenue and less control.

The final question

Do not ask only:

“Can we become twice as big?”

You probably can.

Given enough money, people and determination, most businesses can become larger.

Ask:

“Will twice the size produce a stronger business?”

More profitable?

More resilient?

Less dependent on you?

Better managed?

Better for customers?

Better for employees?

More valuable?

More strategically useful?

If yes, build towards it.

If not, reconsider what the growth is actually for.

Scale is not a prize awarded for successful entrepreneurship.

It is a strategic choice.

Make sure the business you are trying to create is actually better than the one you already own.

What Should Monthly Management Accounts Actually Tell A Business Owner?

Mon, 05 Oct 2026 15:38:01 GMT

Monthly management accounts should tell a business owner five things:

What happened?

Why did it happen?

Is it better or worse than expected?

What is likely to happen next?

What decision do we need to make because of it?

If your management accounts are 27 pages of numbers that arrive every month, get glanced at for four minutes and then disappear into a folder, they are not doing their job.

They may be technically immaculate.

They may reconcile beautifully.

They may make your accountant extremely happy.

But management accounts exist to help management manage .

They should help you understand:

Whether the business is actually making enough money
Where profit is coming from
Where margin is deteriorating
Whether overhead is under control
Whether cash is becoming tight
Whether customers are paying
Whether stock or work in progress is consuming cash
Whether the business is ahead or behind plan
Whether the original forecast still makes sense
What might happen over the next few months
Which decisions need making now

Annual accounts tell you what happened.

Good management accounts should help you decide what happens next.

Management accounts and annual accounts are not the same thing

A limited company's statutory accounts have a formal purpose.

Companies must prepare annual accounts from their financial records and, subject to the relevant rules and exemptions, provide them to shareholders, Companies House and HMRC. Statutory accounts generally include a profit and loss account, balance sheet and supporting information required by the applicable reporting regime.

Management accounts are different.

They are internal financial information designed to help owners and managers run the company.

They can be:

Monthly.

Quarterly.

Weekly in parts.

Tailored by department.

Tailored by customer.

Tailored by project.

Built around the information your management team actually needs.

Government guidance produced for the further-education sector describes management accounts as a tool for financial oversight and control, with two particularly useful purposes: comparing actual performance with budget and forecasting the likely financial outcome for the year. That guidance is designed for colleges rather than ordinary SMEs, but the underlying management principles transfer extremely well.

ICAEW makes a similar point for businesses more generally: annual accounts are not sufficient to control a company, and most businesses need much more regular information about profit, loss and performance, often monthly.

That is the distinction.

Statutory accounts fulfil an accounting and legal requirement.

Management accounts should fulfil a decision-making requirement .

Start with the question, not the report

Before deciding what your management accounts should contain, ask:

What decisions do I regularly need to make?

Perhaps:

Can we afford to hire?

Can we take another unit?

Do we need to increase prices?

Can we buy that machine?

Can we pay a dividend?

Do we need to slow recruitment?

Which service should we grow?

Which customer type makes the best margin?

Are we heading towards a cash problem?

Can we afford the next stage of expansion?

The report should make those decisions easier.

If your management accounts contain information nobody uses while excluding information management desperately needs, changing the font is not going to solve the problem.

Your accountant should not be the only person who understands them

You do not need to become an accountant.

You should still understand your business financially.

I have met owners who can tell you:

Exactly what every salesperson sold.

How many jobs are booked.

How many employees they have.

Which customer is complaining.

What vehicles need replacing.

But ask:

“What's your gross margin?”

and things become slightly misty.

Or:

“How much cash do you expect to have in three months?”

No idea.

Or:

“Why was profit £40,000 below budget last quarter?”

I'd have to ask the accountant.

Your accountant can help you interpret the numbers.

They can advise on accounting treatment.

They can make sure the reporting is sound.

But you are the person making commercial decisions inside the business.

You need enough understanding to ask useful questions.

The first thing I want to see is the headline

Do not make the owner search page 19 for the important bit.

A good monthly pack should begin with a concise management summary.

Something like:

Revenue ahead of budget.

Gross margin below budget.

Operating profit behind.

Cash stable.

Debtors deteriorating.

Payroll higher following recruitment.

Full-year forecast reduced.

Three decisions required.

That tells me where to look.

ICAEW guidance on presenting financial reports recommends putting key messages, significant metrics and required decisions prominently enough that board members can understand what matters without first interrogating every supporting page.

That is sensible for an SME too.

The detail should exist.

It should not hide the message.

1. Revenue

Start with sales.

What did we generate this month?

What did we expect?

What have we generated year to date?

What happened in the comparable period previously where that comparison is useful?

But do not stop at:

Revenue £620,000.

Is that good?

Compared with what?

Suppose:

Budget was £700,000.

Now we know something.

Or perhaps budget was £550,000.

Completely different conversation.

A number without context is just a number.

Understand what caused the revenue movement

Revenue down 12 per cent.

Why?

Fewer customers?

Lower order values?

A delayed contract?

Seasonality?

Loss of one major account?

Capacity problems?

Sales conversion?

Timing differences?

Revenue up 20 per cent.

Why?

More customers?

Higher pricing?

One unusually large project?

Acquisition?

A temporary spike?

Management accounts should trigger that analysis.

The accounts tell you what changed .

Management needs to determine why .

2. Gross profit and gross margin

For many businesses, this is where things become much more interesting.

Turnover can look fantastic while gross margin quietly deteriorates.

Article #68 covered this problem in detail.

You win plenty of work.

People are busy.

Revenue grows.

Profit does not.

Your monthly accounts should make that visible.

Look at:

Gross profit in pounds.

Gross margin percentage.

Budget.

Prior period.

Year to date.

Current forecast.

If gross margin was historically 35 per cent and is now 28 per cent, I want to know why.

Price?

Discounting?

Material cost?

Labour overrun?

Sales mix?

Customer mix?

Subcontractors?

Rework?

Scope creep?

Do not allow management accounts to report margin decline for six consecutive months with the commentary:

“Gross margin slightly below budget.”

At some point somebody has to explain it.

Margin percentage and margin pounds both matter

Imagine revenue falls.

Gross margin percentage improves.

Management celebrates.

Perhaps.

But if total gross profit has fallen significantly, there may still be a problem.

Equally, revenue can rise enough that gross profit pounds increase even while margin percentage deteriorates.

Both figures tell you something.

Ask:

How efficiently are we creating gross profit?

And:

How much gross profit are we actually creating?

Because gross profit has to pay for everything else.

3. Overheads

Now look at the cost of running the company.

Payroll.

Premises.

Vehicles.

Software.

Insurance.

Marketing.

Professional fees.

Finance.

Administration.

Management.

Everything required to keep the operation running.

Again:

Actual.

Budget.

Year to date.

Trend.

Do not obsess over every £37 stationery variance.

Look for the things capable of materially changing the business.

Payroll 14 per cent over budget deserves attention.

Insurance £82 over budget probably doesn't.

Materiality matters.

Ask whether overhead is growing faster than gross profit

This is particularly important in expanding companies.

Revenue up 25 per cent.

Wonderful.

Gross profit up 15 per cent.

Overhead up 28 per cent.

That growth story has changed slightly.

New layers of management.

Recruitment.

Larger premises.

More software.

Additional admin.

Growth requires investment.

That is normal.

But the management accounts should show whether the investment is producing enough additional economic output.

You need to understand whether higher overhead is:

Deliberate investment ahead of growth.

A temporary step-change.

Or cost creeping upwards without sufficient return.

4. Operating profit

Eventually, what remains?

Different businesses and accounting packs may use measures such as:

Operating profit.

EBITDA.

EBIT.

Profit before tax.

Net profit.

You do not need every possible profitability measure because somebody learned an acronym.

Use the measures that help you understand your business and remain consistent about what they mean.

For many owners, operating profit before financing and tax effects is useful because it shows how the underlying operation is performing.

But talk to your accountant about the appropriate presentation for your company.

The important part is knowing what the number includes.

Beware adjusted numbers

“Adjusted EBITDA” can be useful.

It can also become the financial equivalent of:

“Apart from all the bad stuff, we're doing brilliantly.”

One-off costs genuinely exist.

An acquisition fee.

A major restructuring.

Exceptional litigation.

But if you have enormous “one-off” adjustments every year, they might not be particularly one-off.

Understand what has been removed from the number before using it to make decisions.

5. Actual versus budget

This is where management accounts stop becoming bookkeeping and start becoming management.

What did we expect?

What actually happened?

What is the variance?

Why?

The Department for Education's 2026 management-account guidance, although sector-specific, explicitly identifies comparison of actual performance with budget as one of the core purposes of in-year management reporting.

That is exactly right.

If sales are £80,000 behind budget:

Why?

If wages are £35,000 over:

Why?

If gross margin is four points lower:

Why?

Variance is not the explanation.

It is the invitation to investigate.

Not every variance needs explaining

Do not turn the monthly meeting into an accounting hostage situation.

You do not need a narrative around every £300 movement.

Define sensible thresholds.

Perhaps you investigate:

Material pound variances.

Meaningful percentage variances.

Recurring smaller variances.

Items that indicate risk.

Items management can actually influence.

The objective is decision-making.

Not proving that every line of the general ledger has been discussed.

6. The balance sheet

This is where many owners switch off.

Don't.

The profit and loss account tells you what happened over a period.

The balance sheet tells you what the business owns, owes and is owed at a point in time.

GOV.UK describes the statutory balance sheet in similar basic terms: it shows the value of what the company owns, owes and is owed at the end of the financial year.

For management purposes, I care about it every month because a profitable company can still be quietly creating financial risk.

Look at:

Cash.

Trade debtors.

Stock.

Work in progress.

Fixed assets.

Trade creditors.

Loans.

Tax liabilities.

Other material assets and liabilities.

Then ask what changed.

The balance sheet tells you where the profit went

You made £300,000 profit.

Excellent.

Where is it?

Perhaps:

£180,000 went into debtors.

£100,000 went into stock.

£70,000 funded new equipment.

£40,000 reduced borrowing.

£60,000 went out as tax.

That explains why profit and bank balance are not the same thing.

This is one of the most important financial ideas for a growing owner to understand.

Profit is not cash.

The balance sheet often helps explain the journey between them.

7. Cash

Your management pack should make the current cash position obvious.

Not:

“I can open the banking app.”

Cash is not only the number in the bank today.

Ask:

What is available?

What is restricted?

What facilities exist?

What payments are coming?

What tax is coming?

What debt repayments are due?

What does the forecast say?

ICAEW's business-finance guidance is explicit that a lack of sufficient cash to meet wages, rent and bills can threaten an otherwise viable business and that forward cash visibility helps management act before a shortfall arrives.

That is why management accounts need a forward view.

Today's bank balance is history approximately three seconds after you look at it.

8. Cash-flow forecast

I would want the management-account discussion to connect directly to the latest cash forecast.

What is likely to happen over:

Next month?

Next quarter?

Further out where useful?

ICAEW describes a cash-flow forecast as a way of showing management what the company's cash position is likely to be over the coming months so potential problems can be addressed before they occur.

This is especially important in businesses with:

Large payrolls.

Long payment terms.

Stock.

Project work.

Seasonality.

Rapid growth.

Large tax payments.

Debt.

Capital investment.

A profitable P&L does not protect you from a cash shortfall.

9. Debtors

How much do customers owe you?

How old is it?

Who owes it?

What has moved?

Do not only report:

Trade debtors: £640,000.

Tell me:

How much is current?

How much is overdue?

How much is seriously overdue?

Are debtor days getting better or worse?

Which large balances need management attention?

British Business Bank identifies debtor days as a key component of working-capital management because reducing the time customers take to pay releases cash more quickly into the company.

If revenue grows 30 per cent but debtors grow 70 per cent, that deserves attention.

10. Creditors

What do you owe suppliers?

When is it due?

Are supplier terms being stretched?

There is a difference between:

Efficiently using agreed supplier credit terms

and:

Not paying people because cash is tight.

If creditor days suddenly rise, management needs to understand why.

British Business Bank includes supplier payment timing alongside debtors and inventory when assessing the working-capital cycle.

The accounts should help distinguish deliberate working-capital management from emerging distress.

11. Stock and inventory

Businesses can make accounting profit while steadily converting cash into stock.

How much are you holding?

How quickly does it move?

Is obsolete or slow stock building?

Are you buying earlier than necessary?

Is growth genuinely requiring more inventory?

British Business Bank warns that excess inventory unnecessarily ties up working capital, while insufficient inventory can compromise the company's ability to fulfil demand.

The correct number depends entirely on the business.

The management account should show whether the trend makes commercial sense.

12. Work in progress

For project businesses, WIP can become another place money disappears.

Work completed but not invoiced.

Projects running beyond plan.

Costs incurred before milestones are achieved.

Revenue recognition issues.

Unapproved variations.

The exact accounting treatment needs your accountant.

But commercially, I want to understand:

How much work are we funding before billing?

How old is it?

Why hasn't it been invoiced?

Is WIP rising faster than revenue?

Can any of it realistically be converted into cash soon?

A growing WIP balance deserves explanation.

13. Tax liabilities

Owners sometimes look at a bank account containing £400,000 and feel wonderfully affluent.

Except:

VAT is due.

PAYE is due.

Corporation Tax is accruing.

Some of that cash already has another destination.

Your management information should make significant known and expected liabilities visible enough that nobody mentally spends the same pound twice.

Talk to your accountant about the appropriate accruals and tax treatment.

The management principle is simply:

Do not confuse money currently sitting in the bank with money freely available to spend.

14. The full-year forecast

This is where management accounts become genuinely valuable.

Do not only ask:

“How are we doing?”

Ask:

“Where are we now likely to finish?”

Imagine annual budgeted profit was:

£750,000.

Six months in, actual performance suggests the company is heading towards:

£480,000.

A management pack continuing to show:

Budget: £750,000

for another six months is technically possible and managerially useless.

Reforecast.

British Business Bank defines reforecasting as updating a P&L budget or cash forecast when new facts, material events or trends mean the original assumptions no longer provide a useful picture.

Your original budget is still useful.

It shows the original plan.

The forecast shows what management now believes will actually happen.

You need both.

Budget and forecast answer different questions

The budget says:

What did we intend?

The forecast says:

Given what we now know, what do we think will happen?

Do not continuously rewrite the budget until actual performance magically matches it.

That destroys accountability.

Keep the budget.

Explain the variance.

Update the forecast.

Now you have:

Original expectation.

Current reality.

Latest expectation.

That is far more useful.

A forecast without assumptions is just a prettier guess

Suppose the forecast says sales will rise 25 per cent next quarter.

Why?

Current pipeline?

Signed contracts?

Seasonality?

New salesperson?

New branch?

Marketing campaign?

Pure hope?

The forecast should be connected to operational evidence.

British Business Bank warns that forecasts are only as reliable as the assumptions and data supporting them and recommends regular reforecasting where trends show the original assumptions were wrong.

That does not mean forecasting will become perfectly accurate.

It means you should understand what needs to be true for it to happen.

15. Profitability below company level

Company profit can hide enormous variation.

You made:

£400,000.

Great.

But perhaps:

Service A made £500,000.

Service B lost £100,000.

That matters.

Or:

Most customers generate good margin.

Three large accounts destroy it.

Article #65 looked at customer profitability specifically.

Depending on your business, your management accounts may need useful analysis by:

Department.

Branch.

Product.

Service.

Customer.

Project.

Sales channel.

Region.

Not everything.

Whatever helps management understand where economic value is actually being created.

Government investment guidance describes management accounts as internal reports used for decision-making and separately identifies margin and sales breakdowns by product, geography or customer segment as useful tools for understanding high-value areas and cost centres.

That is exactly the point.

Do not stop at company-level profit if the company contains materially different economics underneath it.

16. Non-financial KPIs

Not everything important appears in the accounts yet.

Suppose sales revenue is currently excellent.

But:

Qualified pipeline has halved.

That may become a financial problem three months from now.

Profit is strong.

But:

Employee turnover has increased dramatically.

Possible future problem.

Cash healthy.

But:

Debtor days worsening.

Future problem.

Good management accounts can sit alongside a small number of operational indicators such as:

Sales pipeline.

Conversion rate.

Order book.

Customer retention.

Employee numbers.

Utilisation.

Project delivery.

Debtor days.

Stock days.

Whatever genuinely predicts performance in your company.

ICAEW's guidance on business monitoring specifically includes key ratios and performance comparisons alongside regular financial information, rather than treating management information as a P&L in isolation.

Think of the pack as a management system.

Not merely an accounting report.

17. Commentary

Numbers tell you where to look.

Commentary should tell you what management currently thinks is happening.

For every material issue:

What changed?

Why?

Temporary or structural?

What happens if nothing changes?

What are we doing?

Who owns the action?

That is useful commentary.

Not:

“Administrative expenses increased by £34,762 versus budget.”

I can read.

Tell me why.

Perhaps:

“Administrative costs are £35k over budget year to date, primarily due to two management hires brought forward from Q4. Full-year payroll is now forecast £62k above original budget, but the hires support planned Site Two expansion.”

Now I understand it.

18. Decisions required

This may be my favourite section.

What decisions are needed from the management team?

For example:

Approve price increase.

Freeze recruitment.

Authorise equipment purchase.

Increase credit-control resource.

Stop unprofitable service.

Renegotiate banking facility.

Reduce discretionary spending.

Recruit another project manager.

Challenge department overspend.

No decision?

Fine.

But if the accounts repeatedly identify a problem and no action follows, why are you producing them?

ICAEW's own reporting guidance recommends identifying decisions required and, where appropriate, presenting a recommended course of action rather than leaving important financial information disconnected from board decisions.

That turns reporting into management.

How quickly should monthly management accounts arrive?

Quickly enough to do something with them.

That answer is more useful than pretending there is one universal deadline.

A highly complex group may require more closing work than a simple service company.

But if January's management accounts appear at the end of March, ask yourself:

What decisions could we realistically have changed in January?

Not many.

Accuracy matters.

So does timeliness.

ICAEW specifically emphasises the need for timely information and says most businesses should monitor profit and loss considerably more regularly than annual accounts allow, often monthly.

Work with your accountant or finance team to create a close process that balances sensible accuracy with management usefulness.

Do not chase perfect numbers for so long they become useless

This is another trap.

Finance wants every accrual perfected.

Every invoice allocated.

Every stock movement resolved.

Every uncertainty gone.

By the time everything is pristine, management has moved on six weeks.

Management accounts need to be sufficiently reliable to support decisions.

Where estimates or accruals are material, use appropriate accounting judgement.

Where something is uncertain, say so.

Do not hide behind false precision.

£412,847.23

can look extremely authoritative while the underlying forecast assumption is basically:

“We think sales should be okay.”

Precision and accuracy are not identical.

Reconcile the important stuff

The opposite extreme is also bad.

Reports produced incredibly quickly but containing unreliable:

Bank balances.

Debtors.

Creditors.

Payroll.

Stock.

Revenue.

do not help management either.

You need enough financial discipline that the numbers deserve trust.

That means appropriate reconciliations and closing procedures.

Exactly what those should be depends on your accounting system and business.

This is an area for your accountant or finance team.

The owner does not necessarily need to perform the reconciliation.

They do need to know whether they are looking at reliable information.

Common red flags I would want management accounts to expose

Revenue up, gross margin down

Possible pricing, mix, delivery or cost problem.

Profit up, cash down

Possible working-capital, investment or timing issue.

Debtors growing faster than sales

Cash may be getting trapped in customer credit.

Stock growing faster than demand

Potential working-capital or obsolescence issue.

Work in progress rising repeatedly

Possible billing, project-control or delivery issue.

Payroll rising faster than output

Could be investment.

Could be productivity deterioration.

Investigate.

Overheads rising faster than gross profit

The company may be scaling cost faster than economic value.

Strong current results, weak pipeline

Today's accounts might look excellent while future performance deteriorates.

Forecast repeatedly missed

Either execution is poor or forecasting assumptions are unrealistic.

One customer or division generates most profit

Concentration risk.

One department consistently misses budget

Management issue, bad assumptions or structural problem.

Every one of those should provoke a question.

That is what management accounts are for.

Do not turn the management meeting into a reading exercise

Send the accounts beforehand.

Expect relevant managers to read them.

Then use the meeting for:

Questions.

Explanation.

Decisions.

Actions.

Not:

“Page one. Revenue was...”

Everybody can read page one.

Spend the time discussing:

Why margin fell.

Whether hiring should continue.

What the cash forecast now says.

Why one division is missing plan.

What corrective action exists.

A management meeting should manage.

Hold managers accountable for numbers they can influence

If the Sales Director owns sales:

They should understand sales performance.

If Operations influences labour efficiency:

They should understand it.

If a Branch Manager owns site profitability:

They should see the site's performance.

Financial literacy should not be reserved for Finance.

But be fair.

Do not hold a manager accountable for a number they:

Cannot see.

Do not understand.

Cannot influence.

And have never been taught to interpret.

Management accounts should distribute useful information along with responsibility.

Connect financial numbers to operational behaviour

Suppose gross margin deteriorates.

Finance sees:

Margin -4%.

Operations sees:

Overtime.

Rework.

Poor scheduling.

Sales sees:

Discounting.

The management conversation connects them.

Numbers without operational context create poor conclusions.

Operational stories without numbers create poor conclusions too.

You need both.

Your scorecard and management accounts should speak to each other

Management accounts are generally lagging information.

They tell you what financially happened.

Your scorecard can include earlier indicators.

For example:

Management accounts:

Revenue behind budget.

Scorecard:

Qualified opportunities have been falling for six weeks.

Management accounts:

Margin down.

Scorecard:

Labour overrun and rework increased.

Management accounts:

Cash tightening.

Scorecard:

Debtor days rising.

Now you have an early-warning system.

By the time something appears in the P&L, it has already happened.

The scorecard should help tell you what may happen next.

Hiring decisions should connect to the accounts

“Can we afford another employee?”

should not be answered from the bank balance.

Look at:

Current profit.

Forecast profit.

Cash forecast.

Existing payroll.

Expected output.

Recruitment cost.

Ramp-up time.

Capacity.

Pipeline.

The role's expected contribution.

Management accounts give context.

They do not make the decision automatically.

Article #61 made the same point about cash reserves.

Money in the bank is one piece of information.

Not permission.

Pricing decisions should connect to the accounts

Management accounts should tell you whether pricing is actually producing the margins you expected.

If:

Revenue rises.

Costs rise faster.

Margin falls.

you have something to investigate.

Perhaps prices need changing.

Perhaps delivery needs fixing.

Perhaps customer mix changed.

Do not automatically raise prices because the accounts show lower profit.

Diagnose first.

But without regular financial information, owners can continue pricing from old assumptions for years.

Growth decisions should connect too

Second location?

Acquisition?

New equipment?

New department?

Management accounts should answer:

How strong is the existing company?

What cash is available?

What profit is genuinely recurring?

How much working capital is already tied up?

What headroom exists?

What does the forecast look like after the investment?

Growth should emerge from financial understanding.

Not merely confidence.

Monthly management accounts do not need to be enormous

More information is not automatically more insight.

For some established SMEs, a useful pack might contain:

A concise executive summary.

Profit and loss with budget comparison.

Balance sheet.

Cash position and forecast.

Debtor information.

Working-capital measures.

Key departmental or customer profitability.

Relevant operational KPIs.

Full-year forecast.

Commentary.

Actions and decisions.

Supporting detail can sit behind it.

The exact pack should be designed around the company.

The Department for Education's current management-account guidance makes this principle explicit in its own sector: format and content should be periodically reviewed and tailored to the needs of the people using it.

That should be obvious.

Yet companies regularly inherit the same management pack for ten years because:

“That's what Finance has always produced.”

More pages can make management accounts worse

Imagine one pack is:

68 pages.

Every nominal account.

Every detail.

No commentary.

Another is:

12 pages.

The important financial statements.

Major variances.

Useful analysis.

Forecast.

Commentary.

Decisions.

Which is better?

Whichever helps management run the business.

Detailed information should be available when needed.

Do not confuse volume with insight.

Ask your accountant to help design them around you

If your accountant currently sends only:

Annual accounts.

Tax computations.

VAT information.

ask what regular management information they can provide.

But do not simply say:

“Can I have management accounts?”

Discuss what you need to understand.

Perhaps you need:

Job profitability.

Branch reporting.

Customer profitability.

Cash forecasting.

Departmental performance.

Better budgeting.

The report should follow the commercial model.

Not force the commercial model into whatever accounting software happens to print by default.

But do not outsource your financial brain

An external accountant can be extremely valuable.

So can:

Finance Director.

Financial Controller.

Management Accountant.

Bookkeeper.

Fractional FD.

The level you need depends on the business.

But ultimately leadership remains responsible for making decisions.

Business.gov.uk's current accounting guidance makes a similar point: using an accountant can free management time and bring expertise, but the business still needs to retain oversight and responsibility for its finances.

That is where I would land too.

Get help.

Absolutely.

Do not become financially blind because somebody else prepares the report.

The management-account test

When you receive your next set of accounts, ask:

Can I tell whether we performed well this month?

Not whether revenue was high.

Whether performance was good.

Can I see what happened against budget?

And understand the important variances?

Can I see where our profit actually comes from?

Products?

Services?

Customers?

Locations?

Where relevant.

Can I understand our current financial position?

Cash, debtors, creditors, stock, liabilities.

Can I see where cash is going?

Particularly if profit looks healthier than the bank balance.

Can I see what is likely to happen next?

Forecast, pipeline, cash and material assumptions.

Can I tell what management needs to do?

What decisions or corrective actions follow?

If you cannot answer those questions, the pack probably needs work.

The best management accounts create better questions

This is the real objective.

Not:

“Profit was £72,436.”

But:

“Why did margin improve three points even though revenue fell?”

Not:

“Debtors are £820,000.”

But:

“Why have debtor days increased for three consecutive months?”

Not:

“Payroll is £90,000 over budget.”

But:

“Did the additional hires create the capacity we expected?”

Not:

“Cash is £350,000.”

But:

“What happens to that cash over the next 13 weeks?”

Not:

“We're currently profitable.”

But:

“Are we still forecast to hit the year-end profit target?”

Numbers do not run a business.

People do.

The numbers help those people see what they otherwise might miss.

Stop treating them as a financial autopsy

Annual accounts can tell you what already happened.

Management accounts should be much more alive than that.

Current performance.

Changing margins.

Working capital.

Cash.

Forecast.

Risks.

Opportunities.

Decisions.

If they arrive every month merely to confirm that last month has, indeed, finished, you are wasting an extremely useful management tool.

Your management accounts should help you understand where the business is.

How it got there.

Where it appears to be heading.

And whether you need to change course before you arrive.

That is what makes them management accounts.

How Do I know If My Marketing Is Actually Working?

Mon, 05 Oct 2026 14:52:16 GMT

Your marketing is working if it is creating enough of the right commercial outcomes to justify the money, time and attention you are putting into it .

That does not automatically mean:

More followers.

More impressions.

More website visitors.

More likes.

More enquiries.

Even more leads.

Those can all be useful indicators.

But none, on its own, tells you whether the marketing is actually helping the business.

For most established small businesses, I would work backwards from the commercial outcome:

Revenue and profit

came from:

Customers

who came from:

Qualified sales opportunities

which came from:

Leads or enquiries

which came from:

People responding to marketing

which required:

The right people seeing something in the first place.

That is the marketing chain.

If you only measure one part of it, you can very easily convince yourself something is working when it isn't.

Start by deciding what marketing is supposed to achieve

This sounds obvious.

It isn't.

Ask:

“What is our marketing trying to do?”

and you may get:

Generate leads.

Build awareness.

Grow the brand.

Increase traffic.

Support sales.

Launch the new product.

Improve retention.

Enter another market.

All legitimate.

But they require different measures.

If the objective is generating sales opportunities, I care enormously about:

Qualified leads.

Opportunities.

Pipeline.

Customers.

Revenue.

If the objective is increasing awareness in a new market, expecting immediate sales from every activity may be unrealistic.

If the objective is retaining existing customers, acquisition metrics may tell you almost nothing useful.

You cannot judge whether marketing is working until you define what working means.

Marketing activity is not marketing performance

You posted 18 times.

Sent four newsletters.

Published six articles.

Spent £3,500 on Google Ads.

Ran an event.

Produced three videos.

Wonderful.

What happened?

Activity describes what Marketing did.

Performance describes what changed because of it.

This distinction matters because busy marketing departments can look incredibly productive.

Content calendar full.

Social posts scheduled.

Campaigns live.

Analytics dashboards everywhere.

Yet the sales team still says:

“We need more decent leads.”

That is a problem.

Not necessarily because marketing is failing.

Perhaps sales follow-up is poor.

Perhaps attribution is broken.

Perhaps the marketing is building future demand that has not matured yet.

But you need to investigate the relationship between the activity and the outcome.

Do not simply report the activity.

Your first measurement should sit at the bottom of the funnel

Start with what the business ultimately receives.

Depending on your model, that could be:

Revenue.

Gross profit.

New customers.

Recurring revenue.

Bookings.

Contracts.

Orders.

Customer lifetime value.

Do not necessarily demand immediate revenue attribution from every individual marketing action.

But your marketing system as a whole eventually has to produce commercial value.

Otherwise you have built an expensive publishing department.

Revenue alone is still not enough

Suppose two marketing channels each generate £100,000 of sales.

Channel A costs £10,000.

Channel B costs £30,000.

Easy.

Channel A looks better.

Except perhaps Channel A's customers buy low-margin work producing £20,000 gross profit.

Channel B's customers produce £50,000.

Now the picture changes.

Or perhaps customers from Channel A typically stay five years.

Channel B customers buy once.

Changes again.

This is why mature marketing measurement increasingly connects marketing data with:

Sales.

Customer.

Revenue.

Margin.

Not merely traffic.

The best metric depends on the economics of your particular business.

Work backwards from customers

Ask:

How many new customers did we win?

Then:

Where did they come from?

How much did we spend creating them?

What did they buy?

What margin did they generate?

How long did the sales process take?

What happens after the first purchase?

For some businesses, this is easy.

An e-commerce customer clicks an advert and buys online.

For many established B2B companies, it is much messier.

Someone:

Reads an article.

Sees you again on LinkedIn.

Signs up for a newsletter.

Hears your name from somebody else.

Returns through Google.

Downloads something.

Speaks to a salesperson.

Waits two months.

Then buys.

Which piece of marketing “caused” the sale?

Probably not one of them in isolation.

That is why marketing attribution needs some humility.

Attribution is a model, not a time machine

Marketing platforms can assign credit to different touchpoints.

Google Analytics 4, for example, allows marketers to analyse key-event paths and use attribution models to distribute credit across interactions leading to important actions. Google explicitly describes attribution models as rules or algorithms for deciding how credit should be assigned between touchpoints.

That wording matters.

Assigning credit.

Not discovering absolute truth.

A last-click model might say Google Search generated the customer because that was the final interaction.

But perhaps the customer searched for you because they had already:

Seen your article.

Heard your podcast interview.

Received your email.

Been referred by a customer.

Watched three videos.

The search click may have captured existing demand rather than created it.

Attribution can make measurement better.

It does not make customer behaviour beautifully linear.

This is why marketing and sales need to share data

For a lead-generation business, one of the biggest mistakes is allowing the measurement to stop at:

Form submitted.

That is not necessarily a successful marketing outcome.

Someone asking for a quote might be:

An ideal customer.

A student.

A competitor.

Somebody looking for a £500 service when your minimum engagement is £20,000.

A current customer submitting through the wrong page.

A salesman trying to sell you SEO.

All count beautifully as form submissions.

They are not commercially equal.

Google Analytics now has dedicated lead-generation reporting that can use recommended events to follow lead acquisition, while Google Ads supports feeding qualified and closed offline lead information and values back from CRM systems.

That is the direction I would want an established B2B business moving towards.

Not:

Which channel generated the most forms?

But:

Which channel generated the most commercially valuable opportunities and customers?

Agree what a lead actually is

Marketing says:

“We generated 120 leads.”

Sales says:

“No you didn't.”

Marketing opens dashboard.

Sales opens CRM.

18 worth calling.

Neither side is necessarily lying.

They are using different definitions.

Create clear stages.

For example:

Enquiry

Someone has contacted you.

Marketing-qualified lead

They broadly fit defined criteria and have shown meaningful interest.

Sales-qualified opportunity

Sales has established that there is a credible requirement, fit and commercial possibility.

Proposal or quotation

A genuine commercial opportunity has reached that stage.

Customer

Money changed hands.

Your exact language does not matter.

Consistency does.

Once marketing and sales use the same definitions, you can finally measure the journey.

Measure lead quality, not merely lead quantity

Suppose Campaign A produces:

100 leads.

Campaign B produces:

At first glance, A wins.

But then Sales qualifies:

10 from Campaign A.

20 from Campaign B.

Suddenly the smaller campaign created twice as many meaningful opportunities.

Then suppose:

2 of Campaign A's opportunities buy.

8 of Campaign B's buy.

The original lead-volume comparison has become almost meaningless.

This is why cost per lead can be a dangerous metric when used alone.

A £20 lead that never becomes a customer is infinitely more expensive than it first appeared.

A £200 lead that regularly produces £20,000 of profitable work may be excellent value.

Build the marketing measurement chain

I would measure marketing across several levels.

Not because every company needs an enormous dashboard.

Because each level diagnoses a different problem.

Level 1: Visibility

Are enough of the right people seeing you?

Depending on the channel, this might include:

Impressions.

Reach.

Search visibility.

Advertising exposure.

Email delivery.

Audience growth.

These are leading indicators .

Useful.

Not the finish line.

If nobody sees the marketing, nothing else can happen.

But seeing something is not buying something.

Level 2: Response

Did people do anything?

That might include:

Website clicks.

Email clicks.

Search clicks.

Calls.

Downloads.

Video engagement.

Event registrations.

Direct messages.

Responses.

Search Console is particularly useful for organic search because its performance reporting shows Google Search impressions, clicks, click-through rate and average position and can break the data down by query, page, device, country and other dimensions.

This can tell you whether your visibility in Google is improving and whether that visibility is translating into visits.

It still cannot tell you whether those visits became good customers.

That requires the next stage.

Level 3: Website or landing-page conversion

Once people arrive, do they respond?

For a lead-generation business:

How many visitors become enquiries?

Which pages generate them?

Which traffic sources produce them?

Which campaigns?

Google Analytics' acquisition reporting can show how users and sessions reached the website across sources and channels, while businesses can define key events for actions considered important to business success.

But do not mark every remotely interesting website behaviour as equally valuable.

Someone scrolling down a page is useful behavioural information.

Someone requesting a consultation is considerably closer to a commercial outcome.

Know the difference.

Level 4: Lead quality

Now connect the website to the CRM.

For each meaningful source or campaign:

How many enquiries?

How many were qualified?

How many became genuine opportunities?

How many were rubbish?

How many came from existing customers?

How many were outside your market?

This is where marketing starts receiving useful feedback rather than merely website statistics.

Level 5: Sales pipeline

How much opportunity value did marketing create?

Suppose Marketing Generated Source A creates:

20 qualified opportunities worth £400,000.

Source B creates:

8 opportunities worth £500,000.

Which is better?

We still don't know.

What is the probability of winning?

What margin?

What sales cycle?

What happens historically?

But now we are discussing commercial value rather than web traffic.

Level 6: Customers and revenue

How many opportunities became customers?

What did they spend?

What did it cost to acquire them?

How quickly?

What was the average deal value?

If the marketing objective is customer acquisition, this is where it eventually has to arrive.

Level 7: Profit and customer quality

Then ask the question many marketing dashboards never reach.

Were they actually good customers?

Article #65 explored why revenue and customer value are not the same thing.

Marketing can generate customers that:

Buy low-margin work.

Pay late.

Consume enormous service capacity.

Churn immediately.

Create fantastic revenue and dreadful profit.

If Marketing is rewarded exclusively for acquisition volume, it may rationally produce customers the rest of the business does not particularly want.

Feed profitability and customer quality back into the marketing system.

Cost per acquisition matters more than cost per click

Cost per click is useful for diagnosing advertising performance.

It is not the ultimate commercial measure.

Imagine one campaign:

£1 per click.

Another:

£5.

The first appears dramatically cheaper.

But if the £1 clicks produce almost no qualified opportunities while the £5 clicks produce customers, the expensive traffic may be vastly better.

Move through the funnel.

Ask what you actually paid for:

The lead.

The qualified opportunity.

The customer.

Then compare that with the commercial value created.

Calculate customer acquisition cost properly

At a simple level:

Customer acquisition cost = total relevant sales and marketing acquisition cost divided by new customers acquired.

But decide what you are including.

Advertising?

Agency?

Software?

Content production?

Marketing employee salaries?

Sales development?

Sales commissions?

Event costs?

Your answer depends on what you are trying to understand.

Do not compare:

A fully loaded acquisition cost from one channel

with:

Ad spend only from another.

Keep definitions consistent.

Return on ad spend is useful but narrower

If you spend £5,000 on advertising and attribute £25,000 of revenue to it, your return on ad spend is:

5:1.

Useful.

But it ignores:

Cost of goods or service delivery.

Agency costs.

Internal marketing costs.

Sales costs.

Customer quality.

So ROAS can help compare advertising performance.

It is not identical to marketing profitability.

Google Ads itself supports conversion-value reporting and metrics based on conversion value relative to advertising cost, precisely so advertisers can move beyond counting conversions and towards the value those conversions generate.

The closer your measurement gets to actual economic value, the more useful it becomes.

Use gross profit where revenue is misleading

Suppose Marketing generates £1 million in sales.

Sounds excellent.

But the work averages 15 per cent gross margin.

Another channel generates £600,000 at 45 per cent.

The smaller revenue source creates:

£270,000 gross profit.

The larger one:

£150,000.

That changes the marketing conversation considerably.

For businesses with materially different margins across customers, services or products, connecting marketing to gross profit can be far more informative than revenue alone.

Beware vanity metrics

I do not believe impressions, followers and engagement are automatically useless.

They become vanity metrics when they are reported without a clear relationship to the objective .

If the goal is brand awareness, reach matters.

If the goal is selling £30,000 consulting projects, celebrating 400 Instagram likes while pipeline collapses deserves questions.

The metric is not vain.

The interpretation is.

Ask:

Why are we measuring this?

What decision will it help us make?

If nobody can answer, remove it from the management dashboard.

Website traffic is particularly easy to celebrate

Traffic up 40 per cent.

Brilliant.

From where?

For what searches?

To what pages?

From which countries?

Did those visitors fit the market?

Did they enquire?

Did enquiries qualify?

Traffic can increase because you published something enormously popular with people who will never buy from you.

That might still create awareness or links.

Fine.

But do not automatically equate more traffic with better marketing.

Search Console lets you inspect which search queries and pages are generating Google visibility and clicks, while GA4's traffic-acquisition reports allow traffic to be segmented by source, medium and channel.

Use that information to understand why traffic changed.

SEO should not be judged purely by rankings

This matters particularly for an article-led strategy.

People obsess over:

“We're number three for this keyword.”

Useful.

But rankings fluctuate.

Different searches produce different results.

And a ranking for a query nobody relevant uses has limited commercial value.

For SEO, I would look across:

Impressions.

Relevant query visibility.

Clicks.

Traffic to commercially useful pages.

Enquiries influenced or generated.

Qualified opportunities.

Ultimately customers and revenue where attribution is possible.

Search Console itself makes impressions, clicks, CTR and average position available precisely because search performance contains several dimensions, not one magic ranking number.

The best SEO creates visibility around problems your potential customers genuinely have.

Then gives them something useful enough to remember you.

Some will convert immediately.

Many will not.

Marketing can work before somebody is ready to buy

This is where direct attribution becomes dangerous.

Imagine an owner searches:

How much cash should a small business keep in reserve?

They read your article.

Useful.

They leave.

Three months later, they search:

business coach for established business owners

See you again.

Then they hear your name from someone.

Then visit directly.

Then book.

What generated the customer?

The final Google search?

The original article?

The referral?

All of them?

Probably some combination.

GA4's attribution-path reporting exists specifically because customers can encounter multiple touchpoints before completing a key event, and it can show channels that initiate, assist and close those paths.

This is why I would never judge useful long-form content solely on whether somebody clicked Book a Call immediately after reading one article.

Content can create memory before it creates action.

But do not use “brand building” to avoid accountability

The opposite problem also exists.

Marketing performs badly.

Someone says:

“It's brand awareness.”

For eighteen months.

Fine.

What evidence suggests awareness is changing?

You might look at:

Relevant reach.

Branded search.

Direct demand.

Search volume for your name or company where available.

Survey evidence.

Share of voice.

More people mentioning they already know you.

Inbound opportunities citing content.

Organic/direct traffic trends interpreted cautiously.

Event attendance.

Newsletter growth among the right audience.

Sales conversations becoming easier because prospects have already consumed your work.

Brand marketing is harder to attribute.

That does not mean it is impossible to measure anything.

Ask new customers how they found you

High technology solution:

Ask them.

Seriously.

Add a question.

“How did you first hear about us?”

Not:

“What was your last click before purchasing?”

Their answer may reveal things analytics misses.

Podcast.

Friend.

Saw your vans everywhere.

Read one of your books.

LinkedIn.

Google.

Trade association.

Can't remember, but have known the company for years.

Self-reported attribution has limitations too.

Human memory is imperfect.

Use it alongside digital data.

Not instead of it.

Track source properly inside the CRM

A surprisingly good measurement system might begin with a handful of fields.

Original source.

Current or latest meaningful source where useful.

Campaign.

Lead date.

Qualification status.

Opportunity value.

Sale date.

Revenue.

Perhaps gross profit or customer category.

Then make sure employees actually complete them consistently.

A breathtaking dashboard built on incomplete CRM data is merely a more expensive way to be wrong.

Use campaign tagging consistently

If you send people to the website from:

Email.

LinkedIn.

Partners.

Paid campaigns.

Online events.

Other trackable campaigns.

use consistent campaign tagging where appropriate.

Otherwise GA4 may struggle to distinguish one marketing initiative from another accurately.

Google's traffic-source dimensions are specifically designed to help identify sources, media and campaigns associated with visits and acquisition.

Naming discipline is boring.

It is also the difference between:

October_Newsletter

and:

email / something / maybe

six months later.

Check whether the tracking actually works

This sounds embarrassingly obvious.

Form submitted.

Does Analytics record it?

Phone call.

Is it captured where appropriate?

Purchase.

Does the value pass through correctly?

CRM status changes.

Can you connect it back?

Google Analytics provides Realtime and DebugView specifically so key-event implementations can be checked rather than simply assumed to be recording properly.

I have seen businesses make serious marketing decisions using tracking everybody assumed worked.

Test it.

Your tracking must also be legally appropriate

Measurement is not a licence to collect everything imaginable about everybody visiting your website.

The Information Commissioner's Office published final updated guidance on storage and access technologies in April 2026, covering technologies including cookies, tracking pixels and device fingerprinting and incorporating changes introduced by the Data (Use and Access) Act.

Make sure your measurement setup complies with the current rules applicable to what you are using.

Particularly where:

Personal data.

Tracking technologies.

Advertising.

Profiling.

Third-party platforms

are involved.

The ICO guidance is the sensible place to start, and specialist advice may be appropriate for more complex setups.

Marketing data will never be perfect

This is important because businesses can disappear down a measurement rabbit hole.

Cookie restrictions.

Multiple devices.

Offline conversations.

Word of mouth.

Long sales cycles.

Several decision-makers.

People seeing things without clicking.

Someone forwarding your article to their business partner.

A customer Googling your brand from another device three weeks later.

You are not going to reconstruct every journey perfectly.

Google itself uses modelling in some Analytics reporting where key events cannot be directly observed because of privacy or technical limitations.

So aim for decision-useful evidence .

Not omniscience.

Compare periods sensibly

One month can lie.

Seasonality.

A large contract.

An event.

Budget timing.

A campaign launch.

A bank holiday.

A particularly strong salesperson closing old pipeline.

Marketing should be reviewed over a period appropriate to your sales cycle.

If the average journey from first enquiry to sale is six months, judging last month's marketing solely against last month's revenue makes little sense.

You need cohorts and pipeline.

For example:

What happened to leads created in January?

How many qualified?

How many eventually purchased?

What value did they create?

That gives marketing enough time to mature.

Long sales cycles need leading and lagging measures

If customers take nine months to buy, you cannot wait nine months before deciding whether marketing is heading in the right direction.

Use both.

Leading measures

Relevant visibility.

Traffic.

Responses.

Enquiries.

Qualified leads.

Opportunity creation.

Pipeline value.

Lagging measures

Customers.

Revenue.

Gross profit.

Customer acquisition cost.

Lifetime value where meaningful.

Leading indicators help you steer.

Lagging indicators tell you whether the journey ultimately arrived anywhere useful.

You need both.

Compare channel quality, not only channel volume

Perhaps:

Organic search creates fewer enquiries but excellent buyers.

Google Ads creates strong volume but high acquisition cost.

LinkedIn rarely creates direct leads but appears repeatedly in customer journeys and self-reported attribution.

Email converts existing demand exceptionally well.

Referral partnerships create the highest-value customers.

Now you have a portfolio.

The question becomes:

What role does each channel play?

That is much more sophisticated than:

“Which channel won?”

Different channels can perform different jobs.

Stop comparing channels using different scoreboards

Marketing reporting often does this:

Google Ads reports attributed conversions.

LinkedIn reports engagement.

SEO reports traffic.

Email reports opens.

Events report attendees.

Then management tries to compare them.

You cannot meaningfully compare:

Clicks

with:

Revenue

with:

Attendees

as though they represent equivalent outcomes.

Bring channels onto a shared commercial funnel where possible.

How many:

Responses?

Leads?

Qualified opportunities?

Customers?

How much:

Revenue?

Gross profit?

What did each channel cost?

Now comparison becomes better.

Not perfect.

Better.

Watch conversion rates through the funnel

If marketing feels weaker, find where the change happened.

Imagine:

Visibility unchanged.

Traffic unchanged.

Enquiries down.

That suggests a conversion problem.

Or:

Traffic up.

Enquiries up.

Qualified opportunities down.

That suggests lead quality deteriorated.

Or:

Qualified opportunities healthy.

Sales down.

Maybe the issue is further downstream.

Sales conversion.

Pricing.

Competitors.

Response speed.

Do not blame marketing for every revenue problem merely because marketing sits near the beginning.

Article #59 made the same point about diagnosing falling sales before taking action.

Follow the numbers through the system.

Marketing and sales should disagree less about facts

They can disagree about interpretation.

Healthy.

But they should share the basic numbers.

How many leads?

How many qualified?

How many opportunities?

How many sales?

What values?

What sources?

If Marketing has one version and Sales another, your first priority is data plumbing.

Not campaign optimisation.

A simple worked example

Imagine you spend £6,000 per month on marketing.

It creates:

120 enquiries.

Forty become qualified opportunities.

Twelve become customers.

Those customers generate £72,000 of initial revenue.

Average gross margin is 40 per cent.

That creates £28,800 of gross profit before wider sales and marketing costs.

Your basic marketing spend per customer is:

£500.

Now suppose next month marketing celebrates because enquiries rise to 180.

Fantastic?

Perhaps.

But only 25 qualify.

Six become customers.

Revenue becomes £36,000.

Lead volume increased 50 per cent.

Commercial output halved.

The marketing dashboard looks better.

The business outcome looks considerably worse.

That is why you measure the whole chain.

Build a monthly marketing scorecard

Keep it short enough that management actually reads it.

I would usually want visibility across five areas.

Investment

How much did we spend?

Include the costs relevant to the decision you are making.

Reach and acquisition

Where did attention and website traffic come from?

What materially changed?

Lead generation

How many enquiries?

From where?

At what cost?

Lead quality and pipeline

How many qualified?

How many opportunities?

What pipeline value?

Commercial return

How many customers?

Revenue?

Gross profit where practical?

Acquisition cost?

Then add commentary.

What happened?

Why?

What are we changing?

A scorecard should provoke decisions.

Not merely prove Marketing has statistics.

Review trends, not isolated numbers

Look over:

Three months.

Six months.

Twelve months.

Depending on the metric and sales cycle.

Which channels are strengthening?

Which are deteriorating?

Is acquisition cost moving?

Are lead volumes stable?

Is quality improving?

Is website conversion changing?

Are customer values changing?

One number is a photograph.

A trend is a film.

You need both.

Review marketing with Sales in the room

Marketing should hear:

“The leads from that campaign look great in Analytics but almost none have budget.”

Sales should hear:

“Thirty-eight per cent of the leads we sent received no recorded follow-up within three days.”

Now you have a useful discussion.

Without shared review, each department can blame the other indefinitely.

Marketing:

“Sales can't close.”

Sales:

“Marketing leads are shit.”

Perhaps both are partly right.

Find out.

Response speed belongs in the measurement too

Marketing can generate an excellent lead and still receive the blame for a poor outcome if nobody responds properly.

Measure:

How quickly are enquiries contacted?

How many attempts occur?

What happens after the first conversation?

Are follow-ups consistent?

Do people disappear because your sales process is weak?

Marketing ends where Sales begins only on an organisation chart.

The customer experiences one journey.

Measure accordingly.

Sometimes your best marketing channel is invisible in the dashboard

Referrals are the obvious example.

A customer recommends you privately.

Someone searches the company name.

Google Analytics records organic search.

Did SEO generate the customer?

It helped them find you.

But the referral created the demand.

This is another reason source-of-awareness questions matter.

Likewise, a person may read months of LinkedIn content and later type the web address directly.

The dashboard sees direct traffic.

The person experienced months of marketing.

Do not become so obsessed with measurable clicks that you stop investing in things known to influence buyers but poorly captured by attribution.

But equally, do not let unmeasurable become unquestionable

Someone tells you:

“You can't measure this stuff.”

You probably can measure something .

Not everything.

Something.

What changed after the campaign?

Relevant demand?

Website behaviour?

Brand search?

Enquiry volume?

Sales conversations?

Customer awareness?

Event attendance?

Pipeline?

At minimum, define the hypothesis.

What do we think this marketing will cause?

Over what period?

What evidence would support or challenge that belief?

That is better than:

“It feels like good exposure.”

Ask what would happen if you stopped

This is a powerful question for recurring marketing spend.

If we stopped this channel for three months:

What do we expect to happen?

Would leads fall?

Would branded demand fall?

Would nothing change?

Could we test it safely?

You do not have to switch everything off.

But thinking counterfactually helps.

Marketing expenditure often survives because:

“We've always done it.”

The same reason bad processes survive.

Run controlled tests where practical

Change one meaningful thing.

Offer.

Audience.

Landing page.

Message.

Channel.

Budget.

Then measure.

If you change:

Website.

Pricing.

Campaign.

Offer.

Targeting.

Sales script.

and lead qualification

all in the same fortnight, good luck explaining which one caused the result.

Perfect laboratory testing is rarely possible inside an SME.

But disciplined experimentation is.

Make it easier to learn.

Do not optimise too early

Twenty website visits is not enough information to conclude:

“The new landing page doesn't work.”

Likewise one enormous deal can make a weak channel look extraordinary.

Use enough data to make the decision proportionate.

The lower the volume, the more judgement and patience you may need.

This is especially true for high-value B2B businesses where ten new customers might represent an exceptional year.

Marketing measurement needs to fit the business model.

Marketing effectiveness is ultimately about decisions

This is the purpose of all the numbers.

Do we:

Spend more?

Spend less?

Change the message?

Change the audience?

Improve the landing page?

Stop the campaign?

Create more content around a particular problem?

Improve sales follow-up?

Increase capacity because demand is working?

Reallocate budget?

If the dashboard contains 64 metrics and produces no decisions, it is decoration.

The five questions I would ask every month

1. Did we create enough demand?

Not simply enough attention.

Enough relevant response.

2. Was the demand good enough?

Qualified prospects, not merely contacts.

3. Did Sales convert it?

If not, why?

4. Was the resulting business commercially attractive?

Revenue, margin and customer quality.

5. What are we going to change because of what we learned?

That final question turns reporting into management.

So, is your marketing working?

You should eventually be able to explain something like:

“We spend approximately £12,000 per month across search, content, email and events. That produces around 70 monthly enquiries, of which roughly 30 become qualified opportunities. We win around nine new customers, generating approximately £110,000 of initial revenue at our normal margin. Organic search creates fewer leads than paid search but a higher proportion qualify, while events produce low volume but our highest-value opportunities. Website conversion has fallen over the past two months, so that is the current priority.”

That is useful.

Compare it with:

“Website traffic is up 22 per cent and we got loads of LinkedIn impressions.”

Maybe your marketing is working.

Maybe it isn't.

You haven't told me enough to know.

Marketing measurement becomes useful when you stop asking:

“How much activity did we create?”

and start asking:

“What commercial movement did this activity produce?”

Measure from attention to response.

Response to lead.

Lead to opportunity.

Opportunity to customer.

Customer to revenue and profit.

Accept that attribution will never be perfect.

Then use the evidence you do have to make better decisions.

The objective is not a beautiful marketing dashboard.

It is knowing which marketing deserves more of your money and which deserves less.

Why Do Good Employees Leave Small Businesses?

Mon, 05 Oct 2026 14:42:53 GMT

Good employees usually leave when the overall deal of staying stops making sense .

Sometimes that is money.

Sometimes it is the manager.

Sometimes workload.

Progression.

Flexibility.

Recognition.

Trust.

The job itself.

Sometimes their life simply changes and there is absolutely nothing the employer could reasonably have done.

Which is why:

“People don't leave jobs. They leave managers.”

is catchy, memorable and incomplete.

Managers matter enormously.

So do another dozen things.

If you are losing good employees, do not search for one universal explanation.

Look for the pattern.

The interesting question is not:

“Why did Sarah leave?”

It is:

“What was Sarah experiencing here that eventually made another option more attractive than staying?”

That is where retention becomes useful business information.

Good employees are often the people with the most options

This is an uncomfortable place to start.

Your strongest employees may also be the easiest people for somebody else to employ.

They are experienced.

Reliable.

Competent.

Commercially valuable.

Good with customers.

Trusted by colleagues.

Perhaps technically scarce.

So when their current job becomes disappointing, they may have alternatives.

Current UK employer evidence reflects that tension. The CIPD's September 2026 Resourcing and Talent Planning report found that 52 per cent of organisations said competition for well-qualified talent had increased during the previous year, while 44 per cent said talent had become more difficult to retain . That was despite a broader cooling in recruitment activity.

That matters.

A weaker labour market does not mean your best employee suddenly has nowhere else to go.

Good people still have choices.

Retention is partly about ensuring staying remains one of the attractive ones.

Not all employee turnover is bad

Do not make zero turnover the objective.

People leave.

They retire.

Move.

Change careers.

Return to education.

Relocate with partners.

Have children.

Start businesses.

Decide they want something your company cannot realistically provide.

Some employees probably should leave.

A business permanently retaining every employee it ever hires would not necessarily be healthy.

The useful distinction is regrettable turnover .

Who left that you genuinely wish had stayed?

Which departures created:

Lost capability.

Lost customer relationships.

Recruitment cost.

Management disruption.

Training cost.

Additional pressure on colleagues.

Delayed growth.

Loss of institutional knowledge.

That is the turnover worth understanding.

CIPD guidance similarly recommends looking beyond a headline turnover percentage because the commercial impact of losing employees varies significantly according to their skills, relationships and the difficulty of replacing them.

Losing an average employee in an easily recruited role is not commercially identical to losing the only person who understands your largest account.

Stop saying they “just left for more money”

Sometimes they did.

Pay matters.

It would be ridiculous to pretend otherwise.

People work partly because they need money.

And if somebody can perform essentially the same job somewhere else for £10,000 more, salary becomes a very reasonable reason to move.

But owners sometimes use pay as the explanation because it is emotionally convenient.

“We couldn't compete with the salary.”

Conversation over.

Nothing else needs examining.

But ask:

Why were they speaking to another employer in the first place?

Perhaps a recruiter approached them completely cold.

That happens.

Or perhaps they had already started wondering whether they wanted to stay.

The eventual pay rise may have closed the deal without creating the dissatisfaction.

That distinction matters.

Pay needs to be fair before the clever stuff matters

You cannot compensate for obviously uncompetitive pay with fruit bowls and a Christmas party.

Employees notice.

Particularly good employees who understand their value.

Review salary against:

The external market.

Internal fairness.

Responsibility.

Performance.

Scarcity.

How the role has changed.

One common problem in growing businesses is salary lag.

Someone joins at £32,000.

Three years later they are effectively managing a team, holding major customer relationships and performing a job worth considerably more.

Their salary has risen to £35,000.

Then you advertise a similar external role for £43,000 because apparently:

“That's what you've got to pay these days.”

Your existing employee can see the advert.

Even if they cannot, they can probably see the market.

Do not make loyalty financially irrational.

But retention is bigger than pay

CIPD's retention guidance points towards a broader combination of factors including fair treatment, flexibility, wellbeing and the quality of the employment experience, rather than reducing voluntary turnover to salary alone.

This is important because occasionally an owner responds to every retention problem with money.

Employee miserable?

Pay rise.

Manager causing problems?

Pay rise.

No development?

Pay rise.

Workload ridiculous?

Pay rise.

For a while, money can make an unpleasant job more tolerable.

That does not necessarily make it a good job.

Eventually the problem returns, except now it costs you more.

Problem 1: Their manager is making a good job worse

Managers absolutely matter.

Your employee does not experience “Evolve Engineering Ltd” in some abstract form.

They experience:

Their manager's communication.

Their manager's expectations.

Their manager's temperament.

Whether their manager listens.

Whether promises get kept.

Whether good work gets recognised.

Whether mistakes become learning or humiliation.

Whether performance problems elsewhere get dealt with.

Whether the workload is manageable.

Whether they are trusted.

CIPD's Good Work Index research has repeatedly found strong associations between perceptions of line-management quality and outcomes including job satisfaction, wellbeing, performance and intention to quit. In its 2025 report, workers with more positive views of their line managers were less inclined to consider leaving their employer.

That does not mean every resignation is secretly the manager's fault.

It does mean management quality belongs near the top of your investigation.

Small businesses create accidental managers very easily

Someone is technically excellent.

Reliable.

Knows the company.

Everyone respects them.

So you promote them.

They now manage eight people.

Nobody teaches them how.

Their previous job required:

Technical competence.

Their new one requires:

Feedback.

Delegation.

Communication.

Coaching.

Conflict management.

Prioritisation.

Performance conversations.

Decision-making.

They are completely different skill sets.

CMI's 2023 research with YouGov found that 82 per cent of workers entering management positions in its sample had received no formal management and leadership training. The same research found strong relationships between manager effectiveness, workplace culture and employees' intentions to leave. It is older evidence rather than a 2026 measure of current turnover, but the underlying management problem remains highly relevant.

If good employees repeatedly leave one particular manager, stop replacing the employees and investigate the manager.

Problem 2: Good employees get rewarded with everybody else's work

This one drives me mad.

Someone is capable.

So when something needs doing:

Give it to them.

Someone else is unreliable.

Who can rescue it?

The good employee.

Customer difficult?

Give it to the good employee.

Deadline slipping?

Good employee.

New starter needs training?

Good employee.

Manager needs help?

Good employee.

Eventually competence becomes punishment.

The employee watches weaker colleagues carry less responsibility while they are continuously handed more because:

“I know you'll get it done.”

That phrase can sound like praise.

Repeated long enough, it becomes exploitation.

The strongest person in the team should not become the dumping ground for every problem created by weaker performance elsewhere.

Reward capability with:

Progression.

Autonomy.

Recognition.

Better work.

Development.

Appropriate reward.

Not merely more work.

Problem 3: Poor performers are allowed to stay poor

Nothing demotivates strong employees quite like carrying people management refuses to manage.

One person repeatedly:

Misses deadlines.

Produces poor work.

Avoids responsibility.

Arrives late.

Creates mistakes.

Lets everybody else pick up the slack.

Management knows.

Nothing happens.

The good employee learns an important lesson:

Performance is optional here.

Worse, they may be asked to rescue the consequences.

Retention and performance management are therefore connected.

You do not create a supportive culture by avoiding difficult conversations.

Sometimes retaining your good employees requires properly managing the poor ones.

Acas's 2025 conflict research found that capability and performance were among important causes of workplace conflict, and that unresolved conflict could affect motivation, productivity and retention. Among people reporting workplace conflict, 49 per cent said it caused a drop in motivation or commitment and 10 per cent reported resigning as an impact.

Do not make your best people pay indefinitely for your reluctance to manage somebody else.

Problem 4: There is nowhere for them to go

Good employees often want progress.

That does not automatically mean:

Promotion every twelve months.

Progress might mean:

New skills.

More authority.

Larger projects.

Different responsibilities.

Training.

Greater pay.

Mentoring.

Exposure to strategic work.

Leading people.

Leading projects without becoming a people manager.

If a capable employee looks three years ahead and sees exactly the same job at approximately the same level, another company may offer a more interesting future.

CIPD's latest September 2026 employer research found that 48 per cent of organisations had increased efforts to develop talent internally , while increased learning and development opportunities were among the most common retention initiatives used by employers taking action on retention.

That makes commercial sense.

If you do not develop good people, somebody else may eventually offer to.

Small businesses think they cannot offer progression

This is often too narrow.

You may not have:

Nine management grades.

An international transfer programme.

Three hundred internal vacancies.

Fine.

You may have something large companies struggle to provide.

Breadth.

Access.

Responsibility.

Influence.

A capable employee in a 30-person company may have the opportunity to:

Build a department.

Own a system.

Lead a major customer.

Launch a service.

Improve a process.

Work directly with directors.

Develop commercial skills.

Small businesses can offer meaningful progression without pretending everyone can eventually become Managing Director.

You need to talk to people about what growth means to them .

Problem 5: They have outgrown the job

This is related but slightly different.

Sometimes an employee hasn't outgrown the company.

They have outgrown their current role.

They joined when the business was smaller.

They have learned quickly.

Their capability expanded.

But the job stayed essentially unchanged.

So they become bored.

This is particularly dangerous with high performers.

They often learn faster.

Solve the existing challenges.

Then look for another one.

Do not wait until the resignation letter to discover they wanted more responsibility.

Ask earlier.

Problem 6: They do not feel trusted

You hired somebody intelligent.

Experienced.

Capable.

Then require approval for everything.

£200 purchase?

Ask.

Customer goodwill gesture?

Ask.

Small scheduling change?

Ask.

Supplier selection?

Ask.

Every email copied to the owner.

Every decision double-checked.

Eventually the employee realises you do not really want them to own the role.

You want them to perform the administration around decisions you still own.

Strong employees frequently want autonomy.

Not unlimited freedom.

Appropriate authority.

Clear boundaries.

A chance to use judgement.

CIPD's talent guidance identifies autonomy, clarity of expectations and good management among features associated with stronger employee experience and performance.

If you recruit good people, let them increasingly behave like good people.

Problem 7: They cannot see how decisions are made

Fairness matters.

Two employees make the same mistake.

One gets hammered.

One gets ignored.

One employee receives flexible hours.

Another is told it is impossible.

One person gets promoted.

Nobody understands why.

Pay appears arbitrary.

Opportunities go to favourites.

The owner's mate receives different treatment.

Employees can tolerate decisions they dislike considerably better when the process feels fair and comprehensible.

Unexplained inconsistency creates stories.

Usually bad ones.

“It's who you know.”

“There's no point.”

“Management doesn't care.”

Culture forms around those stories surprisingly quickly.

Problem 8: Flexibility exists everywhere except their job

Flexibility does not mean everybody works from home.

Many jobs cannot.

A mechanic needs the workshop.

A chef needs the kitchen.

A construction manager needs the site.

But flexibility is broader than homeworking.

Start time.

Finish time.

Compressed hours.

Part-time.

Shift patterns.

Occasional remote administration.

School commitments.

Medical appointments.

How leave is handled.

How much notice people receive.

The CIPD's September 2026 research found that 71 per cent of organisations advertised at least some vacancies as open to flexible working. Among organisations using hybrid or remote arrangements, 34 per cent reported improved retention. That is employer-reported evidence rather than proof that flexibility alone caused the improvement, but it reinforces flexibility's continuing role in attraction and retention.

The useful question is not:

“Can this person work from home?”

It is:

“What flexibility can this job genuinely support?”

Problem 9: Work permanently intrudes into life

This is different from somebody occasionally working late.

Most good employees understand that business sometimes requires extra effort.

A major deadline.

Customer emergency.

Unusual period.

Fine.

The problem is when the exceptional becomes the operating model.

Messages every evening.

Weekend emails requiring answers.

Constant overtime.

Last-minute schedule changes.

Holidays interrupted.

Understaffing treated as commitment.

The employee is effectively told:

Your life gets whatever capacity the business leaves behind.

Some people will accept that temporarily.

Fewer will accept it forever.

Retention is not only about whether somebody likes the job while they are physically doing it.

It is also about what the job does to everything around it.

Problem 10: The company keeps changing the deal

This creates distrust.

Employee joins for one role.

Six months later, responsibilities change.

Then targets.

Then hours.

Then reporting line.

Then flexibility.

None of those changes is automatically wrong.

Businesses evolve.

But repeated change without explanation makes people feel the original agreement was meaningless.

Communicate.

Explain why.

Listen.

Give people a chance to raise concerns.

Acas's current work on workplace conflict strongly emphasises early, open and fair handling of concerns. Its 2026 employer research found that among businesses trying to resolve conflict informally, 52 per cent identified a culture supporting open conversations as something that helped.

People do not need to agree with every decision.

They do need to believe raising a concern is worthwhile.

Problem 11: Nobody notices until they resign

This is perhaps the stupidest part of retention.

Employee works for you for six years.

Nobody asks seriously:

Are you happy?

What frustrates you?

What do you want next?

What would make your job better?

What might eventually cause you to leave?

Then they resign.

Suddenly:

Meeting.

Director involvement.

New job title.

£8,000 pay rise.

Flexible working.

Training budget.

More responsibility.

Apparently the company had all of these options.

It simply waited for a resignation letter before discussing them.

Why?

Have stay conversations before exit interviews

Exit interviews can be useful.

But the employee has already decided.

Try asking useful questions while they still work for you.

Not in a weird:

“You're not thinking of leaving us, are you?”

way.

Have normal career and management conversations.

Ask:

What part of your role do you enjoy most?

What frustrates you?

What would you like to learn?

Where would you like more responsibility?

What gets in the way of doing good work?

What could we improve?

What might make this role difficult to sustain long term?

Then listen.

You do not need to grant every request.

You need information.

Do not promise what you cannot deliver

Retention panic causes bad promises.

“You'll be a director next year.”

Really?

“We'll sort the workload.”

How?

“We'll definitely review your salary in six months.”

Based on what?

Do not manufacture hope because somebody looks unhappy.

Trust will be worse when the promise disappears.

If you cannot provide the thing they want, say so.

A good employee may still choose to leave.

That is better than keeping them for another year on a promise you never intended or were never able to honour.

Counteroffers need caution

Sometimes a counteroffer makes complete sense.

You discover an excellent employee is materially underpaid.

You have the capacity to correct it.

They genuinely want to stay.

Fine.

But a counteroffer should not become your retention strategy.

If somebody resigns because:

Their manager is unbearable.

The workload is permanently unreasonable.

There is nowhere to progress.

They no longer trust leadership.

then an extra £5,000 may merely rent the problem for another six months.

Ask what actually needs fixing.

Problem 12: They no longer believe things will improve

Employees can tolerate imperfect businesses.

All businesses are imperfect.

What becomes dangerous is repeated recognition without change.

Management says:

“We know communication is an issue.”

Again.

“We know you're understaffed.”

Again.

“We're looking at the system.”

Again.

“We need to deal with that manager.”

Again.

Eventually the employee stops believing the words.

That is when disengagement can become resignation.

If you ask employees for feedback, do something visible with it.

You do not need to implement every suggestion.

But repeatedly gathering feedback and producing no discernible response teaches people to stop giving it.

Problem 13: They are doing excellent work and hearing nothing

Recognition does not need to mean:

Employee of the Month.

A trophy.

A LinkedIn post.

Sometimes:

“That customer problem was difficult. You handled it really well.”

is enough.

Specific recognition tells somebody what is valued.

Silence can create an odd situation where poor performance receives constant management attention while good performance becomes invisible because:

“I don't need to worry about them.”

Exactly.

Which means the employee who creates the least management hassle may receive the least management attention.

Do not make reliability invisible.

Problem 14: They no longer trust leadership

Trust goes slowly and leaves quickly.

Promised bonus disappears.

Confidential conversation gets repeated.

Owner says redundancies are not being considered when they clearly are.

Manager takes credit.

Rules change depending on who asks.

Business performance is obviously deteriorating while leadership insists everything is wonderful.

Once employees stop believing what leaders say, retention becomes much harder.

You cannot fix trust with another internal newsletter.

Behaviour rebuilds it.

Consistent decisions.

Honest communication.

Admitting mistakes.

Doing what you said.

Problem 15: Workplace conflict never gets resolved

Conflict is normal.

Unresolved conflict is different.

The employee has raised an issue.

Management avoids it.

Two people stop working properly together.

Everyone knows.

Nothing happens.

Acas's nationally representative 2025 research found that 44 per cent of working-age adults in Great Britain had experienced workplace conflict during the previous year. Of those experiencing conflict, around a third said it remained mainly or completely unresolved. The research also found that 10 per cent reported resigning as an impact of their conflict.

That does not mean 10 per cent of all employees resign because of conflict.

It means unresolved workplace problems can have real retention consequences.

Train managers to deal with things early.

Problem 16: The culture changed as the company grew

Small businesses change character as they scale.

At 10 people:

Everyone knows everything.

The owner speaks to everyone.

Decisions are fast.

At 50:

Departments form.

Managers appear.

Processes appear.

Information travels differently.

At 100:

People can work in the same company and barely know one another.

None of that is automatically bad.

But an employee who loved the original company may stop enjoying the newer one.

Sometimes the business needs to evolve.

Sometimes the employee needs something different.

Do not automatically treat that as betrayal.

But do notice what valuable parts of the original culture are being accidentally lost.

Good people sometimes leave because the business succeeded

Their role changes.

The company professionalises.

Perhaps they loved building.

Now the job is maintaining.

Perhaps they enjoyed knowing everybody.

Now there are 150 people.

Perhaps they wanted entrepreneurial chaos.

You finally created systems.

Sometimes the employee and business simply reach the end of a natural chapter.

Retention should not become captivity.

Thank them properly.

Protect the relationship.

Learn what you can.

Move on.

How do you know why people are really leaving?

Stop relying on anecdotes.

Measure.

Look at regrettable departures over perhaps the last two or three years.

For each, understand:

Which department?

Which manager?

Which role?

How long had they worked there?

What performance level?

What reason did they give?

Where did they go?

Was pay involved?

Progression?

Management?

Workload?

Flexibility?

Culture?

Was there a pattern before resignation?

Had they raised anything previously?

Did the company counteroffer?

Did the replacement require significantly higher pay?

Do not turn this into a giant spreadsheet if the business has twelve employees.

Use proportionality.

But look for patterns.

Segment turnover by manager

This can be incredibly revealing.

Company turnover might be acceptable.

But one department loses good employees constantly.

Why?

Perhaps the work is inherently difficult.

Perhaps pay is poor in that function.

Perhaps competitors aggressively recruit those skills.

Or perhaps the manager is the common denominator.

Do not hide local problems inside company averages.

Segment by tenure

When do people leave?

First three months?

That might indicate:

Recruitment mismatch.

Misleading job expectations.

Poor induction.

Bad early management experience.

The CIPD's July 2026 induction guidance emphasises the influence early organisational experience can have on integration and job satisfaction, and notes that effective induction may support retention.

If good people leave after two to three years, perhaps the problem is different.

Progression.

Pay drift.

Role stagnation.

External opportunity.

Different tenure patterns often point towards different causes.

Look at internal movement too

Retention does not always mean keeping somebody in the same job.

Could they:

Move departments?

Take a project?

Develop another skill?

Lead something?

Progress sideways before progressing upwards?

Businesses sometimes lose a good employee because they treat:

“I don't want to do this exact job forever”

as:

“I don't want to work here.”

Those are not the same statement.

Measure the cost of losing good people

Do not stop at the recruitment agency invoice.

Turnover can involve:

Advertising.

Recruiter fees.

Management interview time.

Vacancy cover.

Overtime.

Temporary labour.

Reduced capacity.

Lost sales.

Customer disruption.

Onboarding.

Training.

Lower productivity while someone learns.

Knowledge leaving.

Management time supporting the replacement.

CIPD guidance specifically recommends understanding turnover costs because replacement expenditure extends beyond recruitment into cover, induction, training and lost organisational knowledge.

The exact number is business-specific.

Calculate yours.

That often makes investment in retention considerably easier to justify.

Do not calculate the cost so you can justify retaining everybody

Again:

Some turnover is healthy.

If a poor performer leaves voluntarily and is replaced by somebody stronger, the company may improve considerably.

The goal is not retention at any cost.

It is retaining people whose contribution, capability and future value justify retaining.

That is talent management.

Not hoarding employees.

Small businesses have genuine retention advantages

This conversation can become depressing.

It shouldn't.

A smaller employer cannot always match:

Corporate pension schemes.

Global career programmes.

Huge salaries.

Hundreds of internal roles.

But you can often provide:

Direct access to decision-makers.

Broader responsibility.

Greater autonomy.

Quicker decisions.

Visible impact.

Closer relationships.

More adaptable roles.

Real influence over how the business develops.

Less bureaucracy.

Faster progression when genuine opportunity exists.

CIPD's current talent guidance emphasises that employee experience is shaped by factors including autonomy, role clarity, management, development, recognition and reward.

Small companies can be exceptionally good at those things.

If they choose to be.

Your best retention strategy is not a perk

You do not need a slide.

Employee Retention Strategy 2027.

Start with good work.

Fair pay.

Competent management.

Reasonable workload.

Clear expectations.

Useful feedback.

Autonomy.

Progression.

Respect.

Flexibility where possible.

Open conversation.

Actually dealing with problems.

Perks can sit on top.

Do not build a games room over a rotten management structure.

Build managers before you build benefits

If I had limited money to improve retention, I would be extremely interested in management capability.

Can your managers:

Set expectations?

Give feedback?

Recognise good performance?

Challenge poor performance?

Have difficult conversations?

Delegate?

Manage workload?

Develop people?

Resolve conflict?

Explain decisions?

The latest CIPD evidence continues to make management central to job quality, and its 2026 retention guidance treats fair treatment and employee experience as key parts of reducing avoidable turnover.

A fantastic benefits package managed badly is still a badly managed job.

Have a conversation when good people become too quiet

This is less scientific and more observational.

Good employees do not always become loudly unhappy before leaving.

Sometimes they become:

Quiet.

Compliant.

Less interested.

Stop suggesting improvements.

Stop challenging bad ideas.

Do their job.

Go home.

That can look wonderfully easy to manage.

It may also mean they have mentally moved on.

Do not diagnose resignation from somebody being quiet for three days.

People have lives.

But know your team well enough to notice meaningful changes.

Management requires paying attention.

Do not take resignations personally

This is difficult in a small business.

You recruited them.

Trusted them.

Developed them.

Perhaps worked beside them for years.

Then they leave.

It can feel personal.

Try not to make it personal.

They do not owe you permanent employment because you trained them.

You did not do them a favour by employing them.

They exchanged labour and capability for reward and opportunity.

Hopefully both sides benefited enormously.

Now circumstances changed.

A professional response protects:

Reputation.

Customer continuity.

Remaining employees.

Potential future relationships.

And your ability to learn something useful.

Exit well

A good employee leaving can still become:

A future customer.

Supplier.

Referral source.

Industry contact.

Boomerang employee.

Friend of the company.

Do not turn a resignation into a loyalty trial.

Handle the handover properly.

Thank them.

Ask for candid feedback.

Pay what is owed.

Communicate professionally.

Keep the door open where appropriate.

The way someone leaves becomes part of your employer reputation too.

A practical good-employee retention audit

If you are worried about losing key people, do not begin by giving everyone a random pay rise.

Identify the people whose loss would genuinely hurt.

Then review each relationship.

Ask:

Is their pay broadly fair for the role and market?

Has their responsibility increased faster than their reward?

Do they have a capable manager?

Is their workload sustainable?

Are they carrying weaker colleagues?

Do they have appropriate autonomy?

Do they know what good performance looks like?

Do they receive useful recognition and feedback?

What can they learn next?

Is there somewhere for their role to develop?

What flexibility could reasonably improve the job?

Have they raised concerns that remain unresolved?

Would they describe leadership as trustworthy?

Do they understand where the business is going?

When did somebody last ask what they want from their career?

You will not know every answer.

Which suggests your first action is probably a conversation.

Then look across the system

Individual conversations matter.

Patterns matter more.

Are good people leaving:

One manager?

One department?

One particular role?

After the same length of service?

After promotions?

After periods of high workload?

Because pay falls behind?

Because the organisation recruits externally instead of promoting internally?

Because flexible working is inconsistent?

Because complaints go unresolved?

Solve the system generating the departure.

Do not simply improve the leaving present.

Recruitment and retention are the same system viewed from opposite ends

Article #62 asked why businesses struggle to find good employees.

Here is the uncomfortable connection.

Perhaps you are finding them.

You just aren't keeping them.

Recruit.

Induct.

Train.

Develop.

Lose.

Repeat.

Then complain about the labour market.

The CIPD's September 2026 survey found that 44 per cent of organisations believed talent had become harder to retain, while almost half had increased efforts to develop people internally.

The companies that become better at keeping capability need to buy less of it repeatedly from the market.

Retention is part of workforce capacity.

Do not wait for another resignation letter

Your best people rarely wake up one morning and spontaneously decide to leave.

The decision often develops over time.

A disappointing conversation.

Another promotion that never materialises.

Another late night.

A manager they stop trusting.

A recruiter message.

A salary comparison.

A job advert.

An interview.

An offer.

By the time the resignation lands on your desk, you are seeing the final step of a process that may have been running for months.

You cannot prevent every departure.

Nor should you.

But you can create a business where staying remains commercially, professionally and personally attractive.

Pay people fairly.

Manage them properly.

Give strong performers room to grow.

Deal with weak performance.

Listen before problems become resignations.

Create flexibility where the job genuinely allows it.

Protect good people from becoming the permanent solution to everybody else's shortcomings.

And accept that eventually some excellent people will still leave.

That is employment.

Retention is not about making people unable to go.

It is about making staying a choice they continue to want to make.

How Should A Business Owner Plan Their Week?

Mon, 05 Oct 2026 13:58:27 GMT

A business owner should plan their week by deciding what needs to be different by Friday , then protecting enough time for those outcomes before the week fills itself with meetings, emails, employees, customers and other people's priorities.

Not by writing a 47-item to-do list.

Not by scheduling every fifteen minutes.

And not by pretending Monday morning will somehow remain exactly as planned until Friday afternoon.

A useful weekly plan should contain:

The few outcomes that matter most
The work only you can reasonably do
Fixed commitments
Time for management and decision-making
Protected time for important work
Deliberate buffer for the unpredictable
Space for your actual life outside the business

Then the rest of the work fits around that.

The purpose of weekly planning is not to control every minute.

It is to stop everybody else controlling every minute by default.

A to-do list is not a weekly plan

This distinction matters.

A to-do list tells you what exists.

A weekly plan tells you what is going to happen, when, and in what order .

You can have an immaculate task list containing:

Review pricing.

Call accountant.

Prepare board meeting.

Write proposal.

Review recruitment.

Speak to Sarah.

Analyse margins.

Plan marketing.

Complete expenses.

Respond to customer.

Read contract.

Prepare quarterly presentation.

Every task may be legitimate.

But you still have not answered:

What matters most?

How long will it take?

Which pieces require uninterrupted attention?

What must happen this week?

What can wait?

Where will the work physically fit?

Without those decisions, the list becomes a menu you repeatedly scan whenever you have a spare moment.

Then the easiest or loudest thing wins.

That is not planning.

Weekly planning should connect strategy to Monday morning

Article #66 looked at the value of a 90-day plan.

This is where that plan becomes real.

Suppose one of your 90-day priorities is:

Reduce owner involvement in routine operational decisions by 50 per cent.

Excellent.

What are you doing about it this week ?

Perhaps:

Tuesday morning, define purchasing authority with the Operations Manager.

Wednesday, document the five most common escalation scenarios.

Thursday, return routine scheduling decisions to the team rather than answering them yourself.

Now strategy has entered the calendar.

If your quarterly priorities never appear in the weekly plan, they are unlikely to survive contact with normal business activity.

Start by reviewing where you are

Do not plan next week in isolation.

Review the previous one first.

Ask:

What did I intend to achieve?

What actually happened?

What remains unfinished?

What changed?

What am I waiting for?

What commitments did I make?

What became urgent?

What repeatedly interrupted me?

Which important work got pushed out?

Why?

This is the Review stage of The DROP System.

It is where planning becomes learning rather than simply resetting the task list every Monday.

If the same priority has moved from:

Last Monday.

To Wednesday.

To Friday.

To this Monday.

To next Thursday.

something needs confronting.

Perhaps it is not actually important.

Perhaps it needs delegating.

Perhaps it is too vague.

Perhaps you do not know how to start.

Perhaps your week has no capacity for it.

Moving it forward another seven days solves none of those problems.

Get everything out before choosing

Before prioritising, Dump .

Capture the open loops.

Tasks.

Promises.

Ideas.

Emails requiring action.

Calls.

People to chase.

Decisions.

Problems.

Things you are waiting for.

Personal commitments affecting the week.

Anything sitting in your head whispering:

Don't forget me.

This is not yet your weekly plan.

It is the raw material.

The reason I separate Dump from Plan is simple.

You cannot make sensible choices while simultaneously trying to remember everything.

Get the information out first.

Then think.

Do not ask “What do I need to get done?”

Ask:

What do I need to achieve?

Those questions sound similar.

They produce different weeks.

Imagine your list contains:

Call five customers.

Review CRM.

Speak to sales manager.

Look at pipeline.

Prepare sales meeting.

Your real outcome might be:

Understand why qualified opportunities have fallen and agree the corrective action by Wednesday.

Now the activity has a purpose.

You might discover that only three of the original five tasks are necessary.

Outcomes reduce activity for activity's sake.

For an owner, I would usually identify three meaningful weekly outcomes .

Not because three is a magical productivity number.

Because once you already have normal operational responsibilities, meetings and inevitable interruptions, there is a limit to how many substantial changes you can realistically push forward in five days.

Some weeks it might be one.

Occasionally four.

But if your list says:

My 14 priorities this week...

they are not priorities.

They are contestants.

Define what “done” means

Weak weekly priority:

Work on recruitment.

Better:

Approve the Operations Manager role, salary range and advert by Thursday so recruitment can launch Friday.

Weak:

Sort cash flow.

Better:

Complete the 13-week cash forecast and agree action on the three largest projected shortfalls by Wednesday.

Weak:

Look at marketing.

Better:

Identify why website enquiries have fallen and decide whether the problem is traffic, conversion or lead quality by Friday.

The clearer the outcome, the easier it becomes to determine what action belongs in the week.

Goal-setting research has consistently found advantages to clearer, more specific goals over vague intentions, although results depend on factors including task complexity, commitment and feedback. More broadly, a meta-analysis of 158 time-management studies covering more than 53,000 participants found moderate positive relationships between time-management behaviours and work performance, while the relationship with wellbeing was at least as important.

The useful lesson is not that planning guarantees success.

It is that vagueness is rarely helping.

Decide what only you can do

This should happen before your calendar gets full.

Ask:

Which outcomes genuinely require me?

Not:

What could I do?

You can probably do almost everything.

That is part of the problem.

Owner-only work might include:

Setting strategic direction
Major capital decisions
Senior recruitment
Important leadership conversations
Significant commercial negotiations
Reviewing business performance
Developing key relationships
Resolving genuinely exceptional risk
Thinking about what the business needs next

Routine administration is rarely owner-only work.

Neither are dozens of approvals created by habit.

If half your weekly plan could easily be completed by competent employees, your planning problem may actually be a delegation problem.

Offload before you schedule

This is why Offload comes before Plan in DROP.

Review every meaningful task and ask:

Can someone else own this?

Can it be automated?

Can it be removed?

Can the deadline be renegotiated?

Does it need me at all?

Do not spend twenty minutes finding the perfect slot in your calendar for something that should never have been yours.

That is organised inefficiency.

Put fixed commitments in first

Now look at reality.

Meetings already booked.

Customer visits.

School commitments.

Appointments.

Travel.

Board meetings.

Networking.

Existing delivery work.

Anything genuinely immovable.

Put those into the week first.

Not because they are automatically the most important activities.

Because they consume real capacity.

You cannot make an honest plan while pretending the three-hour customer meeting on Wednesday does not exist.

Personal commitments count too

This matters.

Your family does not exist outside the planning system.

Neither does exercise.

Medical appointments.

Dog walks.

Your child's school event.

Dinner.

Anything that actually matters to the life you are supposedly building the business to support.

I spent years treating work as the fixed object and everything else as whatever fitted around it.

That is one route to 60-plus-hour weeks and permanent availability.

It is also completely unnecessary in many cases.

A business plan that assumes you are available every waking hour is not ambitious.

It is badly designed.

Whole-Life Profit means treating time, health, family and presence as part of the return the business should create.

Put reality into the calendar.

Then build the working week around reality.

Protect the important work before the urgent work arrives

Once fixed commitments are visible, block time for your weekly outcomes.

This is where the calendar becomes useful.

Suppose one priority requires:

Two hours analysing customer profitability.

Do not write:

Analyse customer profitability

on a task list and hope you feel inspired at some point.

Put:

Tuesday 8:30–10:30: customer profitability review

into the calendar.

Research into implementation intentions gives useful support to this principle. A major meta-analysis of 94 independent tests found that plans specifying when, where and how someone would act improved goal attainment compared with relying on intention alone.

A calendar block is not exactly the same experimental intervention.

But the management principle is obvious.

“I need to do this”

is weaker than:

“I am doing this Tuesday at 8:30.”

Schedule thinking before communication

Most owners have more communication available than they could consume in a lifetime.

Email.

WhatsApp.

Teams.

Slack.

Phone.

Meetings.

People physically appearing.

If you begin the day inside communication, there is a good chance other people's priorities will establish the agenda before yours has started.

For work requiring concentration, I prefer planning it deliberately rather than hoping a quiet hour emerges.

That might mean:

Thinking first.

Writing first.

Analysing first.

Reviewing numbers first.

Then opening the communication channels.

Your exact routine will depend on your business.

A retail owner and a consultant have very different mornings.

The principle is simply:

Do not automatically give your best attention to incoming information.

Match the work to your attention

Not every hour of the day is equal.

You probably already know when you think best.

Some people are exceptionally sharp first thing.

Others become more useful later.

Use your best cognitive periods for work requiring:

Judgement.

Writing.

Analysis.

Strategy.

Creative thinking.

Complex decisions.

Use lower-energy periods for:

Routine admin.

Straightforward calls.

Expenses.

Simple approvals.

Low-concentration tasks.

Again, this does not need to become a scientific optimisation project.

Just stop scheduling your hardest thinking for the time of day you are consistently least capable of doing it.

Group similar work where possible

Context matters.

Three separate 20-minute finance tasks scattered across three days can create more disruption than one focused finance block.

Likewise:

Employee conversations.

Sales calls.

Approvals.

Content.

Administration.

Decision-making.

Try to create some logical grouping.

Not because every minute of switching destroys productivity.

But task switching does carry cognitive cost, particularly where attention remains partly attached to unfinished previous work. Sophie Leroy's experimental research on attention residue found that switching away from unfinished tasks could impair performance on subsequent work.

Business owners cannot eliminate switching.

You probably should not even try.

But you can stop designing your week to maximise it.

Create decision windows

This can transform an owner's week.

Instead of being available for every non-critical question the moment it appears, create regular times when managers can bring decisions that genuinely require you.

Perhaps:

Late morning.

Late afternoon.

Or one structured management block.

The exact timing does not matter.

The principle does.

You are still available.

But normal decisions stop fragmenting the entire day.

Genuine emergencies remain emergencies.

Everything else joins the queue.

This is Availability Architecture.

People learn when and how they can access you.

The business gains your attention without owning it continuously.

Put management time into the plan

Management should not happen accidentally.

If you have direct reports, plan for:

One-to-ones.

Performance conversations.

Coaching.

Decision-making.

Reviewing numbers.

Removing obstacles.

You cannot complain that managers need developing while giving management whatever time remains after operational work.

Leadership requires capacity too.

Protect commercial time

Owners often become internally focused as businesses grow.

Employees.

Operations.

Problems.

Meetings.

Processes.

Meanwhile nobody speaks properly to customers.

Build deliberate time for:

Important customer relationships.

Sales.

Partnerships.

Referrals.

Market conversations.

Commercial thinking.

The owner should not necessarily remain the salesperson forever.

But somebody needs to remain externally connected.

Your weekly plan should not become so efficient internally that you forget where the money comes from.

Leave buffer

This is where many beautifully planned weeks die.

Monday morning:

Calendar 100 per cent full.

Monday 10:15:

Reality arrives.

A customer issue.

Employee absence.

Urgent quote.

Supplier problem.

School phone call.

Technical failure.

Now every hour is displaced.

A business owner's week needs some empty space.

Not because empty time is lazy.

Because unpredictability is predictable.

If your role regularly contains interruptions, I would rather see a week deliberately planned to something like 70 to 80 per cent of usable capacity than one scheduled to 100 per cent and destroyed by Tuesday lunchtime.

That is a practical starting point, not a universal scientific formula.

Your role may need more or less buffer.

The principle is:

Do not plan as though nothing unexpected will happen.

It will.

Buffer is not permission to fill the calendar later

This happens quickly.

You create two free hours.

Someone sees white space in the diary.

Meeting.

Another meeting.

Then your buffer has disappeared before the week begins.

Protect it.

That space can absorb:

Overruns.

Urgent decisions.

Unexpected conversations.

Travel delays.

Problems.

Or, beautifully, nothing.

If nothing arrives, use it for the next important piece of work.

Unused capacity is not failure.

It is resilience.

Stop meetings colonising the week

Meetings breed.

One becomes recurring.

Someone adds another person.

Then another.

Six months later nobody remembers why nine people attend every Tuesday.

During the weekly review, look at upcoming meetings and ask:

Do I need to attend?

Does this meeting need to exist?

Could somebody else represent me?

Could the decision happen asynchronously?

Could it be 30 minutes instead of 60?

Does it have an outcome?

Meetings are not free because they were already in the calendar.

They consume the most finite resource the business has:

People's attention.

Avoid the “meeting sandwich”

You have:

9am meeting.

11am meeting.

2pm meeting.

4pm meeting.

Technically there are gaps.

Practically, the day is shredded.

Each gap looks long enough to do something.

None feels long enough to properly begin the complex piece of work you actually care about.

Where possible, cluster meetings.

Maybe Tuesday afternoon becomes meeting-heavy while Wednesday morning remains protected.

You will never achieve perfect separation.

You do not need perfect.

You need better.

Decide when communication happens

Email is particularly dangerous because it appears productive.

You answer 35 messages.

Things move.

People receive responses.

You feel useful.

Meanwhile the strategic work remains exactly where you left it.

Try checking communication deliberately rather than continuously.

Maybe morning after focused work.

Lunchtime.

Late afternoon.

Whatever suits your role.

If your business genuinely requires immediate email response, design around that.

Most do not.

Even where responsiveness matters, the owner does not necessarily need to provide every response personally.

Plan the next action, not just the project

Another reason tasks stay unfinished is that they are not really tasks.

Website.

Not a task.

Recruitment.

Not a task.

Strategy.

Definitely not a task.

You need the next physical action.

For example:

Call web developer and approve homepage wireframe.

Send Operations Manager job description to recruiter.

Review Q4 margin by service line and identify two priorities.

Implementation-intention research is useful again here because specifying the action and circumstances makes an intention more executable.

Your weekly plan should contain work you can actually start.

Distinguish deadlines from preferences

Business owners create fake urgency for themselves too.

I want this done Tuesday.

Why Tuesday?

Is something dependent on it?

Does a customer need it?

Does a deadline exist?

Or did Tuesday simply sound disciplined?

You can absolutely create internal deadlines.

They are useful.

But know which dates are genuinely consequential and which are planning devices.

That helps enormously when the week changes.

Move flexible work before missing genuinely important deadlines.

Look ahead further than Friday

Weekly planning should not stop at the week.

During your review, scan at least the following couple of weeks.

What is approaching?

Board meeting.

Payroll.

Tender deadline.

Employee review.

Holiday.

School break.

Customer launch.

Tax payment.

Conference.

Major project start.

Travel.

This gives you a chance to pull work forward while capacity exists.

The worst planning happens when something becomes visible only once it enters the current week.

By then it is often urgent.

Review waiting-for items

Owners often plan only their own actions.

But much of business involves things other people owe you.

Proposal from supplier.

Figures from Finance.

Customer approval.

Employee document.

Solicitor response.

Recruiter shortlist.

Track them.

During the weekly review ask:

What am I waiting for?

Does it need chasing?

When does waiting become a problem?

This stops dependencies remaining invisible until somebody suddenly says:

“We can't proceed because we never received X.”

Build a default week

A default week can be extremely useful.

Not a rigid timetable.

A starting architecture.

Perhaps you decide:

Monday morning focuses on business performance and priorities.

Tuesday contains customer and commercial work.

Wednesday morning protects strategic or creative work.

Thursday includes management and coaching.

Friday includes review, loose ends and next-week planning.

Your exact version may look nothing like that.

The value is reducing the number of decisions you repeatedly make.

You do not begin every week from a completely blank page.

You have a normal rhythm, then reality adjusts it.

Do not over-engineer the system

You do not need:

Seven apps.

Four coloured calendars.

Twenty-two tags.

A complicated scoring algorithm.

Three different task-management systems.

The system should disappear behind the work.

You need somewhere trusted to capture.

A way to review.

A way to assign ownership.

A calendar.

Enough visibility to make decisions.

That is all.

Complexity is not sophistication.

A productivity system so demanding that maintaining the system becomes one of your largest tasks has missed the point.

The calendar and task list have different jobs

I would not put every two-minute action into the calendar.

That becomes ridiculous.

Use your task system to hold actions.

Use the calendar for:

Time-specific commitments.

Protected work requiring meaningful time.

Meetings.

Appointments.

Travel.

Important recurring routines.

Tasks can then live within suitable blocks.

For example:

Friday 2:00–3:00: finance and admin

might contain:

Approve invoices.

Review expenses.

Reply to accountant.

Update forecast note.

You do not necessarily need four separate calendar events.

Plan to capacity, not optimism

This might be the biggest weekly planning skill.

You estimate:

Proposal: one hour.

Actually: three.

Management meeting: one hour.

Actually: ninety minutes plus follow-up.

Customer visit: two hours.

Forgot 90 minutes of travel.

Strategic work: three hours.

You gave it ninety minutes.

Then you wonder why the plan failed.

Weekly planning improves when you compare estimates with reality.

If reports repeatedly take two hours, stop planning one.

If customer visits consistently consume half a day, treat them as half a day.

Your future plans should learn from your previous weeks.

Planning is a feedback loop.

Do not carry everything forward automatically

Friday arrives.

You have seven unfinished tasks.

Do not simply move all seven into Monday.

Ask again:

Is this still important?

Does it still require me?

What happens if it waits?

Should it be delegated?

Should it disappear?

A task's age does not increase its value.

Sometimes the best thing you can do with a repeatedly postponed task is admit that you are never going to do it and remove it.

Monitor progress during the week

Planning once and disappearing until Friday is not enough.

A major meta-analysis of 138 studies involving almost 20,000 participants found that interventions increasing progress monitoring also increased goal attainment. Effects were stronger in some circumstances when progress was physically recorded or reported.

For a business owner, this does not require a performance ritual every afternoon.

Take five minutes.

What has moved?

What is slipping?

What changed?

What needs replanning?

If Tuesday changes the entire commercial picture, waiting until Friday to acknowledge it is pointless.

Replanning is not failure

This is important.

Some people create a plan and then treat any deviation as poor discipline.

Business does not work like that.

A major customer calls.

A genuine problem happens.

The commercial opportunity of the year appears.

Of course the plan can change.

The discipline is not:

Never deviate.

The discipline is:

Change deliberately.

If something new enters, ask:

What moves?

What gets delegated?

What gets delayed?

What consequence does that create?

A plan should help you make those decisions.

Not prevent them.

Protect one important non-urgent piece of work every week

If I had to reduce the whole article to one habit, this might be it.

Every week, move something forward that matters but is not yet screaming.

Manager development.

Pricing.

Recruitment.

Succession.

Systems.

Strategy.

Writing.

Cash forecasting.

Customer concentration.

Business continuity.

These are the things that prevent future emergencies.

Yet they lose constantly to today's problems.

Protecting even one substantial piece of important non-urgent work each week creates enormous compounding value.

Fifty weeks later, you have moved fifty things before they became crises.

That is a different business.

Your week should include work that removes future work

This is where agency becomes especially useful.

Most people plan what needs doing.

Also plan what could make something stop needing doing.

For example:

One hour answering purchasing questions.

Or:

One hour creating purchasing authority so the questions stop.

Two hours fixing project schedules.

Or:

Two hours improving the scheduling system.

Thirty minutes repeatedly correcting the same employee.

Or:

One proper conversation and training plan.

These activities may initially take longer.

They change the workload itself.

That is the distinction between productivity and better business design.

Schedule recovery before exhaustion schedules it for you

This is not a wellness lecture.

It is practicality.

You cannot plan every evening.

Every weekend.

Every early morning.

Every holiday.

Then act surprised when concentration, judgement or patience deteriorates.

The 2021 time-management meta-analysis is interesting here because time management showed a stronger relationship with wellbeing than many people might expect, alongside moderate associations with performance.

Time management is not merely about squeezing more output from yourself.

A useful system should create control .

Space.

Predictability.

The ability to finish.

That was the entire reason I developed DROP in the first place.

Not so I could fit 70 hours of work into 50.

So the unnecessary work would stop consuming my life.

A practical 30-minute weekly review

You can make this longer where necessary.

But it does not need to consume half your Friday.

First: Dump

Capture everything still open.

Loose tasks.

Ideas.

Promises.

Notes.

Emails requiring action.

Anything in your head.

Next: Review the previous week

What completed?

What didn't?

Why?

What changed?

What keeps returning?

Review the business

Look at the few numbers or issues that matter.

Sales.

Cash.

Delivery.

People.

Whatever deserves attention.

Review your 90-day priorities

What should move this week?

Review the next two weeks

Deadlines.

Meetings.

Travel.

Family.

Customer commitments.

Offload

Delegate.

Automate.

Delete.

Renegotiate.

Move work away from yourself where appropriate.

Choose the week's outcomes

What three things would make Friday meaningfully better than Monday?

Plan

Put the important work into actual time.

Leave buffer.

Then stop planning and go live your life.

A simple weekly planning structure

By the time you finish, you should be able to answer these questions clearly:

What are my three most important outcomes this week?

What work genuinely requires me?

What have I delegated?

What fixed commitments already consume capacity?

When will I do the important work?

Where is the buffer?

What am I waiting for?

What is coming next week that I should prepare for now?

What will I deliberately not do this week?

That final question is important.

Every useful plan contains exclusion.

Plan the week before the week plans you

There will always be unpredictability in running a business.

That is not the problem.

The problem is allowing unpredictability to consume everything.

A good week is not one where every task was completed exactly according to a beautifully arranged calendar.

It is one where:

Important things moved.

Genuine emergencies were handled.

Work that did not require you went elsewhere.

The business got enough of your best attention.

And your life was not treated as a scheduling error.

Dump.

Review.

Offload.

Plan.

Then execute.

Replan when reality changes.

Review what happened.

Repeat.

You do not need perfect control of your week.

You need enough deliberate control that the business stops deciding, minute by minute, where your life goes.