When Customers Stop Admiring Your Product and Start Depending On It

For about twenty years, Christian Braun was the person enterprise software companies were trying to sell to.

He spent two decades at Porsche developing virtual design processes, then led Virtual Art and Design at Volvo Cars and Polestar. He sat through the demos. He approved or declined the purchases. He watched tools arrive with great fanfare and then go unused.

He now builds that software himself, as Chief Product Officer at Depix Technologies and founder of MAGING GmbH. Having stood on both sides of the same transaction has left him unusually unsentimental about what counts as traction.

“Product-market fit begins when customers stop admiring the product and start depending on it,” he says. “Interest, compliments and impressive demos are not enough.”

The signal is pull, and it sounds specific

Braun’s test for whether fit has arrived is not a metric. It is a change in the questions customers ask.

“An especially strong signal is when a design team stops asking, what can the software do, and starts asking, can we use this for our brand, our vehicle and our next program.”

That shift is the whole thing in one sentence. The first question is curiosity, which costs the customer nothing. The second is planning, which costs them something, because they are now imagining the product inside work they have already committed to.

Real pull looks like customers coming back with their own material, asking to use the product on the next real project, bringing in colleagues and requesting integration into their existing workflow. He watches repeat sessions, time to first valuable output, exports, conversion from pilot to paid, renewal and expansion. Underneath the numbers he is listening for something simpler: “evidence that the product has changed a decision or removed a bottleneck.”

The negative signals are just as legible, and more founders should recognise them: “pilots that generate excitement but no daily use, many feature requests without ownership or budget, and teams that need constant encouragement to come back.”

Three people have to say yes

The hardest lesson in his answers is one that catches enterprise founders repeatedly.

“The individual user, the budget owner and the organization must all see value,” he says. “A designer may love a tool, but there is no scalable product-market fit if procurement, IT, security or management cannot adopt it.”

Asked what he wishes he had understood earlier, he goes straight back to this.

“I wish I had understood earlier that user love and organizational adoption are different products. A professional can be convinced while the company remains unable to buy, deploy or support the solution.”

Then comes the reframe that makes it usable: “In enterprise markets, procurement, security, integration, change management and the internal business case are not obstacles around product-market fit. They are part of it.”

Most founders treat those things as friction to be endured once the product has won. Braun treats them as the product.

His advice for founders early in the search follows from it, and it is slightly uncomfortable. Start with a recurring problem that is expensive in time, money, quality or frustration. Work with a small number of users who feel it intensely. Ask for their real material. Then: “Sell earlier than feels comfortable, because willingness to pay reveals a different level of truth than willingness to praise.”

Watch what people do, not what they say

Depix validated its opportunity by sitting with professional designers during real briefs and real review sessions rather than surveying them.

“Live sessions were more useful than abstract surveys because we could observe where the process broke: where users hesitated, where they lost design intent, which results they trusted, and which outputs were useful enough to take into the next meeting.”

His conclusion is quietly damning of most customer research. “The decisive insights came from behavior during real work, not from asking whether people liked AI.”

The method changed over time, and the change is instructive. Early on the team asked users what they wanted the system to do. Later they asked what decision the user was trying to make, what they did before and after using the tool, and why a particular output was accepted or rejected.

“That evolution moved the conversation from features to workflow and value.”

Wow moments and work moments

Braun has felt the specific pain of being close to fit and mistaking it for the real thing.

“There were moments when customers produced stunning results in a session and the room was visibly excited. It felt like fit because the value was immediate and emotional. But after the session, daily adoption did not always follow.”

What was missing was consistency across outputs, control over design intent, integration with existing tools, and a clear internal owner for the next step.

Out of that came a distinction worth stealing: “the difference between a wow moment and a work moment. The first opens the door; the second creates a product.”

He has seen the failure version too, in technically impressive visualisation initiatives that produced a powerful first reaction and never became daily tools. “The demo solved for fascination; the product did not solve for habit.”

It prompted the one significant change of direction Depix has made, from positioning AI primarily as an image generator to positioning it as design intelligence. Image generation attracts attention, he says, but professional teams “do not primarily need more images; they need better direction, stronger consistency and a way to preserve design intent across iterations, products and media.”

So features that looked impressive but did not support a clear job were reduced or postponed, while integration, data protection, on-premise options, SSO and compatibility with existing visualisation tools became more important. Unglamorous work, chosen deliberately over the things that photograph well.

“A spectacular result can win a meeting, but only a dependable workflow can win a program.”

The thing founders overlook

Asked what gets missed most often, Braun does not name a tactic. He names a feeling.

“Founders often overlook the professional identity of the user. A product can improve efficiency and still fail if it makes people feel that their judgment, craft or status is being removed.”

One of the most important signals Depix received was designers saying that AI results did not feel like their own work. That could have been filed as resistance to change. Instead it was read as a specification.

“It revealed a product requirement: intention, control and authorship had to be visible in the workflow. Good product intuition is not ignoring evidence; it is recognizing the deeper problem behind what users say.”

It is why he refuses the framing of AI as a replacement for the designer. “I believe AI should be treated as a new material, the new clay, rather than an autonomous replacement. Product-market fit becomes stronger when the product amplifies intention and leaves the user more capable, more visible and more in control.”

And a final warning for anyone who thinks fit is a finish line.

“Product-market fit is often described as a moment, but in practice it is an operating relationship between product, customer and market. Technology changes, expectations rise and yesterday’s fit can disappear.”