Someone in the room asked if we were using AI. A board member. An investor. A partner. Same question.
They did not want a diagram. They did not want to know what a model would read, or what we would do when it was wrong. They wanted a yes they could put on a slide. In 2026, that word is how a company looks current. If you do not have it, you look late. If you have a chat box in the screenshot, you look fundable.
I have sat in that meeting more than once. The product was already a path: a person does a job, the screen tells them what happened. Nobody in support was asking for a conversation. The room was asking for a story.
I almost said yes and added a box.
What the word does to the build
The pressure is real. Partners ask. Investors ask. People who will never use the product ask. They have seen the same decks. A company without the word looks like last year’s company. A raise is a story, and this year’s story wants AI on the product, not in the background.
So you stop asking whether a user is stuck. You start asking whether the homepage can say assistant. You put a chat next to a form that already works. The chat answers questions the page already answered. It looks like progress in a demo. In reality, you added a second place to get the same answer, and a new place to get a wrong one.
I have used models where they earn their keep. Drafting. Sorting a pile of text. Reading something a person was going to read anyway. That work does not need a box on the product. It also does not show up in a screenshot. So it does not count, in that room, as using AI.
They do not want the work. They want the word on the homepage.
The box I did not add
The product did not need a conversation. It needed the path to finish. A chat box would have given us a screenshot and a new support line: the model said one thing, the page said another.
I said we were using models where a person was already doing the reading. I said we were not putting a chat on the product so the slide would look current. That is harder to say in a meeting than yes. It is also the only honest answer if the user does not have a question the page cannot answer.
The meeting wanted a feature they could screenshot. I told them where we already used a model. Those are not the same thing.
I did not promise an assistant for the next board pack and figure it out later. That is how you spend a quarter on something nobody opens.
What I say now
If they mean can we say it in the raise, I say what we actually do, in one sentence, and what we will not do. We use a model to draft, to sort, to read a pile. We do not add a chat to a path that already works.
If they mean should the product talk, I ask what job the user cannot finish today. If they can already finish it, the product does not need a conversation. It needs the path to stay clear.
If there is a real job — a pile of text, something someone is sorting by hand, a draft nobody has time to write — we use it there. The user should save time. They should not get another screen to talk to.
A product is investable because someone finishes a job and comes back. Not because we bolted on a chatbot for the meeting.
I still want the raise. I still want the meeting to go well. I do not buy the meeting with a feature the product did not ask for.