A client recently came back to me with a question about something that had come up during an earlier meeting.

My first thought was that I needed to go back and look at the meeting where this started. Not because I was trying to figure out how to justify additional work, but because I wanted to understand what led to the question.

The meeting lasted more than an hour. There had been a lot going on, with questions, demonstrations, discussions about the current process, and movement between different parts of the system. Nothing about the meeting had left me thinking that there was one moment that would eventually lead to another conversation about what might be possible.

That is one of the challenges of consulting. You can leave a meeting with pages of notes and still do not know which details will matter later.

I had a specific question about something that had come up during the meeting, so I went back to the recording. Rather than going through an hour-plus recording manually, I asked AI to help me find any discussion about Sales Order Enquiry or Sales Order Inquiry.

It quickly identified a 26-second section of the meeting.

Those 26 seconds had not stood out to me during the meeting. They were not a major discussion, and nobody had identified them as an opportunity for improvement. The client simply opened the Sales Order Enquiry screen to find an order and pick list number because another screen was taking too long to load. The information was found, the number was copied, and the meeting continued.

It was a perfectly ordinary moment in a long meeting.

If I had been asked immediately afterward which part of the meeting might eventually lead to another idea, I would not have picked those 26 seconds. There was nothing about them that suggested they would become significant.

The AI review also helped answer the question I had originally asked. I did not miss a request to modify the Sales Order Enquiry screen. There had been no discussion about adding functionality to it or changing the way it worked. It had simply been used to find information when another screen was taking too long.

That was important for me to establish, because there is a difference between missing a client request and discovering something after the fact.

---

The Moments We Overlook

When we are in a meeting, we naturally pay attention to the things that appear important. We listen to decisions, requirements, questions that need answers, and changes that someone wants to make. Those are the things that usually make it into our notes.

The less obvious moments are harder to capture.

Someone takes an extra step because the normal process is inconvenient. Someone opens another application to find information that should be readily available. Someone explains a workaround that has become so routine that nobody thinks of it as a workaround anymore.

Those things often do not get written down because, at the time, they are simply part of getting the work done.

That does not mean they are unimportant.

One of the things I enjoy about consulting is getting beyond what a system is supposed to do and seeing what people do with it. Those are not always the same thing.

A process may technically work, but that does not mean it works well. A system may provide the information someone needs, but that does not mean the information is easy to get to. A workaround may solve an immediate problem, but that does not mean it is the best long-term approach.

Sometimes the person using the system has stopped noticing the inconvenience because they have been working around it for so long. Sometimes the consultant does not notice it either.

That is why these small moments can be useful. They give you a glimpse into how the work is really being done.

And sometimes they spark an idea.

That does not mean the idea needs to become a project. It may not make sense financially. It may not be a priority. There may be other work that is more important.

The value can simply be in recognizing that the possibility exists.

---

An Idea Is Not a Commitment

That distinction has become more important to me as I continue building Vogel Consulting.

A conversation can lead to an idea. An idea can lead to an estimate. An estimate can lead to a proposal. And a proposal can still be the right answer even when the client decides not to move forward.

Recently, I had that experience with a client.

A question that came out of our discussions led to a separate idea for improving how users could see relationships between orders. I worked through what would be required, put together the preliminary estimate, and documented it as a separate SOW so that the information was there if the client decided there was a path forward.

They ultimately decided that the ROI was not there, at least not right now.

That is okay.

It is easy to think of consulting relationships in terms of work that gets awarded. A proposal gets accepted or it does not. A project moves forward or it gets put on hold.

But that is only one part of the relationship.

The more important part is what happens while you are getting to that decision.

We put our best effort forward. We explained what we saw. We were clear about what was included and what would require additional work. The client asked questions. We answered them. They considered the potential benefit against the cost and decided it was not the right time.

There was no pressure to make the numbers work.

There was no need to force a project into existence simply because we had already invested time in defining it.

Sometimes the right business decision is not right now.

---

The Relationship Matters More Than the Project

That experience put the consulting relationship into perspective for me.

Good consulting is not about finding a way to turn every observation into billable work. It is about having enough trust to have honest conversations about what makes sense.

That means being open about what I see, even when the answer may be different from what the client expected.

It means setting boundaries around scope and respecting the client’s boundaries around priorities, budgets, timing, and expected return.

Those boundaries work in two ways.

I must be willing to say when something is outside the current scope. The client must be able to say when something is not worth doing right now.

Neither one of those things can be allowed to damage the relationship.

In fact, I think they can strengthen it.

A client should not have to worry that every question they ask is going to turn into a sales opportunity. At the same time, I should be able to point out a potential improvement when I see one without having to pretend it does not exist simply because it was not part of the original conversation.

That is where relationship becomes important.

The goal is not to win every project.

The goal is to understand the business well enough to have the right conversation when the opportunity does make sense.

---

Twenty-Six Seconds

There is still something fitting about the number itself.

We are in 2026, and a 26-second section of a client meeting ended up being important enough for me to go back and examine more closely. I did not plan that connection. It just happens to be the way the numbers worked out.

What I find more interesting is what those 26 seconds represent.

Twenty-six seconds is almost nothing in an hour-plus meeting. It is easy for a small interaction like that to disappear among everything else that was discussed.

But those seconds captured something about how the work was being done.

That is often where the value of consulting comes from. It is not always in the formal request or the written requirement. Sometimes it comes from understanding why someone has developed a particular way of working, what they have had to work around, or where the system is making something more difficult than it needs to be.

Those observations can lead somewhere.

Or they may not.

You do not always know when you notice something whether it will matter six days from now, six months from now, or not at all.

That is part of the work.

---

Seeing What Was Already There

The opportunity was not created by the recording, and it was not created by AI. The information was already there in the meeting.

What changed was my ability to go back and examine it after I had a reason to ask a different question.

AI made finding those 26 seconds much faster. My experience helped me understand what I was seeing and decide whether it meant anything.

Neither one replaces the other.

Technology can help find the moment. The consultant still needs to understand the business, ask the right questions, and determine whether there is something worth pursuing.

And sometimes the answer is that there is an idea, but the timing is not right.

That is not a bad outcome.

Not every idea is a project. Not every proposal is going to be accepted. Not every opportunity is a slam dunk.

Sometimes you put your best effort forward, have an honest conversation, respect the decision, and leave the door open for another time.

For me, that is part of building the kind of consulting relationship I want with my clients.

We are open and honest.

We set boundaries, and we respect boundaries.

We look for opportunities to improve the business, but we also recognize that an opportunity needs to make sense for the client.

Sometimes the timing is right.

Sometimes it is not.

And sometimes all it takes is 26 seconds of an hour-long meeting to spark an idea that may become important later.

You never really know what might come from a conversation.