Frequently asked questions

Start by understanding whether your current operation can handle more business.

I look at where employees spend their time, which activities create customer value, and where unnecessary work is consuming capacity. That includes duplicate data entry, rework, excessive approvals, and processes that depend on a handful of employees.

Then we examine what can be eliminated, redesigned, or supported with technology.

But there's another question: Do you have profitable customer demand to fill the capacity you create?

The objective is to increase profitable revenue and output without increasing headcount and operating costs at the same rate.

What we measureRevenue per employee, cost per completed transaction, operating capacity, and contribution margin.

Because more revenue doesn't always mean better business.

Some customers generate significant volume but consume too much employee time, require exceptions, or produce margins that don't justify the resources involved.

I work with leadership to define which customers and markets the company wants to pursue, what differentiates its offering, and what constitutes good revenue.

Then we examine customer profitability, pricing, cost to serve, and where resources are being allocated.

Sometimes the right decision is to pursue more business. Sometimes it's to stop pursuing business that doesn't produce an acceptable return.

What we measureCustomer profitability, contribution margin, cost to serve, and operating profit.

Start with the business direction and the financial outcome everyone agrees matters.

Leadership needs to define what the company is trying to accomplish. Finance needs to establish the current economics and help determine what improvement is worth.

For example, if the objective is lowering the cost of processing customer transactions, both groups should agree on the current cost, the target, the investment required, and how results will be verified.

A business executive owns the operating outcome and must have the authority to change the process. Finance validates the financial assumptions, total cost, and realized benefits. Technology specialists support implementation.

Before investing, agree on what happens to any capacity created. Will the business reduce overtime, avoid additional hiring, or serve more profitable customers?

I recommend documenting the baseline, target, owner, investment, capacity plan, and review milestones before approving a material project.

What we measureThe agreed operating metric, total cost of ownership, realized financial benefit, and variance against the business case.

Because buying technology doesn't mean you've changed how the business operates.

I've seen organizations focus on software while leaving the underlying problems untouched: unclear responsibilities, unnecessary approvals, inconsistent information, and manual workarounds.

I start by examining whether the work should exist in the first place. Then we determine how to simplify the process, who owns it, and what technology is actually needed.

Sometimes the best answer is using the systems you already have more effectively.

The question is whether the investment improved business performance, not whether employees adopted another application.

What we measureOperating costs, rework, cycle time, customer outcomes, and financial return.

First, verify that the hours were actually saved.

Then determine what the business can do with the capacity.

Can employees handle additional profitable customer volume? Can you reduce overtime or outside expenses? Can you avoid hiring additional people as the business grows?

Or can those employees be developed and moved into work that creates greater customer value?

Redeployment requires a real business need, the right skills, and a plan to make the change.

I distinguish between time saved, capacity available, capacity productively used, and financial value realized. Those are four different things.

What we measureCapacity redeployed, incremental profitable output, avoided costs, actual expense reductions, and revenue per employee.

Your employees often understand problems that leadership doesn't see.

They know where customers get frustrated, which processes create unnecessary work, and which systems require constant workarounds.

I believe in intrapreneurship: developing employees who think beyond their job descriptions and take responsibility for making the business better.

That requires leadership to establish direction, listen to employees, give them appropriate decision authority, and support their development.

I work with employees to identify improvement opportunities, test practical changes, and measure the results.

The objective is to build an organization where improvement becomes part of how people work.

What we measureEmployee-led improvements implemented, rework eliminated, process performance, and sustained operating results.

I start by asking what business problem we're solving and whether AI is the right solution.

Then we establish the current operating and financial baseline.

What does the work cost today? How many transactions are completed? What are the error rates? What resources are required?

We compare the expected improvement against the full cost of implementation, including software, integration, training, employee oversight, exception handling, and ongoing support.

We also compare the AI option against simpler process improvements or existing technology.

A projected return is only a business case. The return becomes real when the company demonstrates measurable financial or operating value.

What we measureTotal cost of ownership, cost per successful outcome, realized savings, incremental contribution margin, and return on investment.

The executive responsible for the business outcome.

If the objective is improving sales performance, commercial leadership owns the result. If it's reducing transaction processing costs, the executive responsible for that operation owns it.

IT, developers, and technology partners have important supporting responsibilities, but building a solution doesn't make them responsible for the company's profitability.

I also examine whether the accountable executive has the authority to change workflows, assign resources, establish controls, and address performance problems.

Accountability without authority doesn't work.

What we measurePerformance against the agreed target, implementation costs, operating exceptions, and sustained business results.

We start by aligning leadership on where the business is going and why.

That includes which customers and markets to pursue, what makes the business different, which revenue is worth pursuing, and what leadership is willing to prioritize, stop, or defer.

We establish measurable outcomes and identify the executives responsible for delivering them.

Then I work with leadership and employees to examine customer needs, operating workflows, decision-making, and opportunities to improve performance.

We identify practical changes, establish ownership and authority, and develop an implementation plan with measurable checkpoints.

Technology is evaluated where it supports those priorities.

The objective is to help leadership build the ability to execute and verify that the changes improve business performance.

What we measureProgress against agreed financial and operating targets, with clear executive ownership.

I've spent more than 25 years helping build and scale businesses. I've led teams, managed P&Ls, and been accountable for the decisions that determine whether a company grows profitably.

I approach an engagement as an operator.

I'll ask difficult questions about strategy, customers, profitability, talent, and how the business actually runs. I'm not interested in recommending technology simply because it's available.

I also believe strongly in intrapreneurship. Employees should be involved in identifying problems, improving operations, and developing the judgment to take greater ownership.

My experience has taught me that lasting improvements require leadership commitment and employees who can execute.

I bring that operating perspective to every engagement, along with the technical knowledge to evaluate where AI can help.