The demo goes really well. The dashboard is easy to understand, and the reporting capabilities generate some good questions from the customer about how they could be used. Everything is dialed in. Then I get an email from the prospect saying that they are excited about moving forward, but can’t figure out who on their team will own getting Cedarline set up. For a long time, our focus at Cedarline was on features that helped people get more out of the product after getting started. We’d polish up the filters and reporting options, make tweaks to the UI. But we didn’t think hard enough about the person who would bridge the chasm between demo and setup. We asked eight of our customers to do the initial Cedarline setup with no hand-holding. Instead of asking about clarity of individual steps, we focused on who they’d invite to Cedarline and what they’d expect to happen next. And we had them import a project. Every single time, there was a hitch in the baton pass between the Cedarline owner and their co-workers. The answer wasn’t another video tutorial. We boiled down onboarding to three tasks with clear owners, and made the invite step more explanatory. And we changed our demo to walk through setup instead of starting with a pre-populated dashboard. Products can seem simple, yet still place an onerous ask on customers to coordinate among themselves. Rather than think “reduce friction,” it’s helpful to ask, what work are we making our customer do to orchestrate among their colleagues before they see value? We ask this every time we review our onboarding process at Cedarline, and it sparks much better conversations than asking whether we should build another feature.



