Six months ago, I gave a product demonstration that I thought had gone extremely well.

The customer nodded at the dashboard, asked thoughtful questions about reporting, and said our platform looked far more organized than their existing process. I left the call feeling that the next step would be a straightforward trial. Instead, the customer sent a short email explaining that they could not work out who on their team would set everything up.

At Cedarline, we had spent most of our time improving what users could do after onboarding. We had added filters, refined the interface, and made the reporting more flexible. We had given much less attention to the person who had to turn a promising demonstration into a working account.

That email changed our priorities.

We watched eight new customers attempt the initial setup without a live walkthrough. We did not ask whether the screens looked clear. We asked them to invite a colleague, import one project, and explain what they expected to happen next. Several hesitated at the same handoff between the account owner and the rest of the team.

The solution was not another introductory video. We reduced the first session to three tasks, assigned a clear owner to each one, and made the invitation step explain why the colleague was needed. We also changed our sales demonstration so it included the setup process rather than beginning with a fully populated dashboard.

The lesson for me was that a product can look simple while still demanding too much coordination from a customer.

Founders often hear that they should reduce friction. I now find that advice more useful when it becomes a specific question: whose work are we asking the customer to organize before they can receive any value?

That is the question we bring to every onboarding review now. It has led to better conversations than asking whether we need another feature.