"I'll check with the owner"

Leadership · D. Scot Nattrass · 3 min read · 2026-11-03

How many times does your business say that in a day?

A customer needs a delivery date. A supplier offers a substitute. Someone needs to approve a small purchase.

Individually, each question takes two minutes. Together, they can fill the owner's day and leave everyone else waiting.

Sometimes the decision genuinely needs you. Sometimes your team has never been told where their authority begins and ends.

"Use your judgment" is difficult to follow when nobody has explained the limits.

Try one small experiment this week

Pick a recurring decision that keeps coming back to your desk. Choose something with manageable consequences, then agree on:

• Who owns the decision.
• What information they need.
• What they can approve without asking.
• Which exceptions must come back to you.
• When you'll review how it went.

For example, someone handling a delayed delivery could be authorized to offer an alternative within agreed cost and timing limits. Anything outside those limits comes to you.

Now the person has something they can actually use when the phone rings.

Review the decisions afterward. Adjust the boundaries where needed. Give people feedback while the details are still fresh.

This is part of the operational work we do at Focal Dynamic: making responsibility, information, and decision-making clear enough that the business can move without every question landing on one desk.

If your team is capable but everything still waits for you, that's worth a conversation. Book a Clarity Session.

Where did this ingredient come from?

AI · D. Scot Nattrass · 3 min read · 2026-10-27

For a food manufacturer, that question needs an answer you can check.

In October 2026, Goldman Sachs profiled McClure's Pickles in Detroit. According to co-owner Bob McClure, tracing ingredients through the company's reporting system used to take 30 to 45 minutes.

After integrating AI models with its business management system, he reported that a trace could be completed in less than two minutes.

That's a useful example of where AI can earn its keep: helping people find operational information when they need it.

It also raises a question every owner should ask: can we verify the answer?

A quick answer needs a dependable trail back to the records. Especially when the next decision affects a customer, a shipment, or someone's safety.

Where I'd start

For an owner considering something similar, I'd start with one recurring lookup:

• What question does your team keep asking?
• Where does the information live?
• How long does finding and checking it take?
• Who confirms the answer before anyone acts on it?

Then test against cases where you already know the answer. Measure accuracy and completeness alongside time saved.

At Focal Dynamic, that's the kind of work we look for: a specific task, a clear purpose, and a way to tell whether the change helped. The judgment stays with the people responsible for the business.

What information does your team spend too much time hunting down?

The new system went live on Monday

Operations · D. Scot Nattrass · 3 min read · 2026-10-22

By Friday, someone had brought back the spreadsheet.

Before you call that resistance to change, ask what the spreadsheet is doing that the new system isn't.

Maybe it handles an exception nobody asked about. Maybe the information arrives too late. Maybe the person responsible for the next step can't see it.

Or maybe the team never got enough practice to feel comfortable.

The workaround is information. Find out what it's telling you.

This is why our methodology at Focal Dynamic includes debugging after deployment. Once a change meets real customers, busy days, missing information, and unexpected requests, you learn things the planning meeting couldn't tell you.

Before calling it finished

Before calling an improvement finished, I want to know:

• Can the people doing the work use it without someone standing beside them?
• What happens when the usual process doesn't fit?
• Who owns the problem when a handoff fails?
• Has the original delay or error actually decreased?

Then we adjust, test again, and make sure someone inside the business can keep it running.

A launch date is easy to put on a calendar. Reliable daily use takes more attention.

If a recent change has left your business with more chasing, duplicate work, or spreadsheets than before, bring that to a Clarity Session. We can talk through where it's getting stuck.

Before you buy another tool, put a number on the waiting

Technology · D. Scot Nattrass · 3 min read · 2026-10-19

Waiting for a prototype. Waiting for an approval. Waiting for someone to enter the same information into a second system.

World Magnetics, a Michigan manufacturer, had a specific version of that problem. Customers needed prototypes before placing production orders. Outsourcing those prototypes took time and money.

With help from the Michigan Manufacturing Technology Center, the company assessed its needs and brought in 3D printing. A matching grant supported the investment, and employees' existing experience with automation helped them learn the equipment.

This wasn't our engagement. But the sequence is worth paying attention to: understand the constraint, assess what the team can use, then choose the equipment.

Four questions before you buy

For an owner considering new technology, I'd ask:

• Which exact delay will this remove?
• What does that delay cost us today?
• Who will learn, operate, and maintain it?
• How will we know the investment helped?

Those questions apply to a 3D printer, scheduling software, or an AI assistant.

At Focal Dynamic, technology has to earn its place in the operation. An impressive demonstration is a start. A measurable improvement in the work is the point.

Where does work spend the most time waiting in your business?

What went right in your business this week?

Operations · D. Scot Nattrass · 2 min read · 2026-10-15

And could your team repeat it without you?

That's a useful place to start when operations feel harder than they should.

Pick one job that went smoothly. An estimate that became an order. A project delivered on time. A customer issue resolved without three phone calls to the owner.

Then ask:

• What made it work?
• Who had the information they needed?
• Which decisions were clear?
• Could someone else follow the same steps next week?

You may find a solid process. You may also find one capable person quietly holding the whole thing together.

Both deserve attention. They need different kinds of support.

Before buying another tool or rewriting every procedure, understand that successful job. Write down the steps, the handoffs, and who makes which decisions. Try them again. See what holds up.

That's how I approach operations at Focal Dynamic: understand the business, build on its strengths, and stay involved while the changes take hold.

If you'd like a starting point, our five-minute operational health check asks six questions about how your business actually runs. You can see your score without providing an email address.

What runs reliably in your business today, and what still depends on you being there?

Start with what works: a field guide

Operations · D. Scot Nattrass · 6 min read

When I walk into a business for the first time, the owner usually wants to show me what's broken. I get it. The broken stuff is loud. It's what kept them up last night, and it's why they called.

But the first thing I want to find is the part that's working. Not to be polite about it. Because it's the most useful information in the building.

Why start there

Every business that's still open is doing something right. Maybe it's the way the front desk handles a rush. Maybe it's one salesperson who closes twice as often as everyone else. Maybe it's a supplier relationship that's held up for fifteen years. Something is keeping the lights on, or they'd already be off.

That working part is proof. It shows what this particular business, with these particular people, can do when things line up. And it's a much better guide than any framework I could bring in from outside.

I learned this the slow way. I spent years inside big companies like Goldman Sachs, Merrill Lynch, Delta, and Bristol-Myers Squibb, then five years across the table from more than 400 small business owners in 46 states. The pattern held at every size. The organizations that improved fastest weren't the ones that tore everything down. They were the ones that figured out why their best parts worked, and spread that.

What "working" actually looks like

It's rarely a whole department. It's usually smaller than that, and easy to miss. Here's where I look first:

• A process nobody complains about. If a task gets done on time, every time, and nobody mentions it, that's a system worth studying.
• A person everyone goes to. Every business has someone who "just knows." What they know is usually a process that was never written down.
• A customer who keeps coming back. Ask why. The answer tells you what you're really selling.
• A number that stays steady. Consistent margin on one product line, reliable collections from one type of client. Steady doesn't happen by accident.
• A habit the owner takes for granted. The Monday check-in they've run for years. Reading the bank balance every morning. Owners often have better instincts than systems.

How we document it

Finding it is half the job. The other half is writing down why it works, in plain words, so it can be repeated. Here's the order we follow.

1. Talk to the people doing the work. Not just the owner, and not just managers. The person running the task knows things the org chart doesn't.
2. Map how it really flows. Who touches it, in what order, what they check, what they skip. How it actually runs, not how it's supposed to.
3. Ask why it holds up. This is the step most people skip. Is it the tool? The person? A rule someone set years ago? Usually it's a mix, and you need to know which parts are carrying the weight.
4. Write it down as a benchmark. A short description anyone could follow. This becomes the standard the rest of the business gets measured against.

That last step matters more than it sounds. Once you have a written benchmark from your own business, you stop comparing yourself to some ideal company in a book. You're comparing yourself to your own best day.

Then, and only then, the fixes

Once we know what's working and why, the broken parts start to make sense. Very often a weak area is weak because it's missing the one thing that makes the strong area work. The strong team has a checklist and the weak one doesn't. The healthy product line has a clear owner and the struggling one has three.

So the fix isn't to import something foreign. It's to bring the weak part into line with the strong one. Your people already know how to do it, because they already do it somewhere else in the business. That makes change easier to accept, and a lot more likely to stick.

Why this beats the usual approach

Most consulting starts with a template. Here's the ideal structure, here's the software, here's the playbook. Now fit your business into it.

The trouble is that templates don't know your customers, your people, or the reasons you've survived this long. Force a business into someone else's shape and you often break the very things that were holding it up. Then you're worse off, and you paid for the privilege.

Starting with what works protects those things. It also gives your team a reason to believe in the change, because the change is built out of their own best work.

Try it this week

You don't need a consultant to start. Pick one thing in your business that just works, something you never have to think about. Then ask three questions:

1. Who makes it work?
2. What do they do that other parts of the business don't?
3. Is it written down anywhere?

If the answer to the last one is no, write it down. That one page might be the most valuable document you own.

And if you'd like a hand finding the rest, that's exactly how we start every engagement.

Where AI actually earns its keep in a small business

AI · D. Scot Nattrass · 5 min read

Every owner I talk to right now has been told AI will change everything. Most of them have also paid for at least one tool that changed nothing.

Both things are true. AI is genuinely useful in a small business. It's also genuinely easy to waste money on. The difference usually comes down to one question: did you start with a problem, or with a tool?

Here's my honest list, based on what I've seen work and what I've watched quietly get cancelled.

Where it earns its keep

Drafting the first version of anything. Proposals, follow-up emails, job posts, policies, the reply to an unhappy customer. AI is very good at getting you from a blank page to something you can edit. You still do the editing. But the hardest part of writing is starting, and that part just got a lot cheaper.

Reading what nobody has time to read. Contracts, long email threads, supplier terms, a stack of customer reviews. Ask it to summarize, pull out the dates and dollar amounts, or flag anything unusual. It won't replace your lawyer, but it will tell you which page to show your lawyer.

Spotting patterns in your own numbers. Export your sales or expenses and ask what changed month over month, which customers are ordering less, which costs crept up. It's faster than scanning rows by eye, and it tends to catch the slow drift people miss. Always check the math it hands back.

Watching the routine stuff. Sorting the inbox, flagging overdue invoices, reminding someone a license renewal is coming. The boring checks that eat an hour a day and fail the one week someone is out sick.

Taking repeatable tasks off your team. If someone does the same ten clicks every morning, that's a candidate. Copying order details from email into a spreadsheet. Sending the same onboarding packet. This doesn't replace the person. It gives them their morning back.

Where it mostly adds noise and cost

Tools bought before the problem was named. This is the big one. A subscription that was supposed to "transform operations" and now gets opened twice a month. If you can't say in one sentence what the tool fixes, you probably don't need it yet.

Automating a broken process. If the process is a mess by hand, automating it gives you the same mess, faster, with fewer people watching. Fix the process first. Then automate it.

Customer conversations that need a human. A chatbot is fine for "what are your hours." It's a liability with a customer who's upset, confused, or about to spend real money. People can tell, and they remember.

Decisions that need judgment. Hiring, firing, pricing, whether to take on a big client. AI can lay out the options and the numbers. It can't weigh your values, your relationships, or what you know about the person across the table. Those calls stay with you.

Anything you can't check. AI sounds confident even when it's wrong. If you can't verify what it gave you, whether that's a number, a legal point, or a fact about a competitor, don't build on it.

A simple test before you buy anything

Before you sign up for another tool, run it through four questions:

1. What exact problem does this solve, and what does that problem cost us now in time or money?
2. Who will own it day to day?
3. How will we know in 90 days whether it worked?
4. What happens if we turn it off?

If you can't answer all four, wait. The tool will still be there next quarter, and probably cheaper.

How we use it

We use AI in our own work the way we'd use any good tool: to see patterns faster, catch things earlier, and take the busywork off the table. Inside a client's business, we only bring it in after we've diagnosed the problem, and we pull it back out if it's adding noise or cost instead of clarity.

The technology should fit into your business. Your business shouldn't contort itself to fit the technology.

If you're not sure a tool is worth it, or you have a few subscriptions you suspect aren't pulling their weight, that's a good conversation for a Clarity Session.

The four numbers every owner should know cold

Finance · D. Scot Nattrass · 7 min read

Ask most owners how the business is doing and you'll hear about sales. Sales matter. But I've sat with plenty of owners whose sales were climbing right up to the week they couldn't make payroll.

Sales tell you how busy you are. These four numbers tell you whether you're okay. The principles that keep a three billion dollar company solvent are the same ones that keep a corner shop alive, and they start here.

The examples below use one made-up business with round numbers, so the math is easy to follow.

1. Gross margin

What it is: what's left from each sale after the direct cost of delivering it. Materials, the labor on that job, shipping, card fees.

How to figure it: sale price minus direct costs, divided by sale price.

Say you sell a job for $10,000 and it costs $6,500 to deliver. That's $3,500 left, a 35% gross margin. That $3,500 is what pays rent, salaries, insurance, and eventually you.

Why it matters: margin is where most businesses leak money quietly. One product line might run at 45% while another runs at 12%, and the busy one isn't always the good one. Know your margin by product or service, not just the overall average. The average hides the problem.

2. True cash

What it is: your bank balance minus what's already spoken for.

How to figure it: take today's balance, then subtract payroll, rent, loan payments, taxes, and bills due in the next 30 days.

If the bank says $120,000 and $55,000 goes out over the next month, your true cash is $65,000. That's the number you can actually make decisions with.

Why it matters: the bank balance lies by leaving things out. Owners who read only the balance tend to feel rich the day after a big deposit and broke the day before payroll. True cash flattens that ride and stops you from spending money that already has a name on it.

3. Runway

What it is: how many months you could keep the doors open if sales stopped tomorrow.

How to figure it: cash on hand divided by your monthly fixed costs. Fixed costs are the bills that show up whether you sell anything or not.

With $120,000 in the bank and $40,000 a month in fixed costs, your runway is 3 months.

Why it matters: sales don't stop often, but they slow down. A key customer leaves, a season is soft, a supplier raises prices. Runway tells you how much time you have to respond. Three months feels like plenty until you're in month two. Knowing the number early means you make calm decisions instead of desperate ones.

4. How long it takes to get paid

This is the one most people forget until it's too late.

What it is: the average number of days between doing the work and having the money in your account.

How to figure it: take what customers owe you right now, divide by your average monthly sales, and multiply by 30.

If you sell $100,000 a month and customers owe you $150,000, you're waiting about 45 days to get paid. Every extra 10 days of waiting ties up roughly $33,000 of your money in other people's pockets.

Why it matters: this is how profitable businesses run out of cash. You pay for materials and people up front, then wait weeks to collect. Growth makes it worse, not better, because every new job means more money out before any comes back in. A business can be winning on paper and still bounce a check.

The fixes are usually simple and a little uncomfortable. Invoice the day the work is done, not at the end of the month. Ask for deposits on big jobs. Follow up on day one past due, not day thirty. Make it easy to pay you.

Put them on one card

You don't need a finance department for this. You need about fifteen minutes a week and the discipline to look.

Write the four numbers on an index card. Update it on the same day every week or month. After a few rounds you'll start to feel the business differently. The surprises get smaller, and the decisions get easier.

If any of these numbers are hard to pin down in your business, that's usually the first thing worth fixing. It's also a very normal place for us to start.