[dmkirwan]

Congratulations on the launch! I don't have much constructive feedback, other than the custom launch plan idea resonates well with me. It's something that other vendors miss IMO.

I have two questions if you don't mind:

1: onboarding is something that users should do once only. Unfortunately, engineers only see it once also. It's easy to forget there's an onboarding flow in your app as you build it. Do you have mechanisms in place to detect if somebody releases a breaking change? For example: an element you expected to exist is now gone, a url has changed, etc.

2: Can you share how you came up with the problem and if the product evolved over your time in YC? I think most engineers or PM's have had to think about onboarding at some stage so I'm curious about that.

[jeffepp]

Thanks. You are right, none of the other vendors do custom launch plans. They are all building templates, which is what everyone is used to -- we built custom launch plans because we spent nearly a decade onboarding Enterprise SaaS -- we know that's what is needed ;)

To answer your questions:

1) We don't have those types of elements right now, it's an interesting idea though!

2) Yes, we faced the problem of customer onboarding as we built my last company (Ambassador Software), especially as we moved up market and realized that "lots of people needed to do lots of things" before the buyer of our SaaS could actually use it.

The product has certainly evolved during YC thanks to all of the conversations we've had with customers and prospects. We came into YC with more traction than some companies (and many paying customers) so, we had some market validation, however, it's been turbo-charged while being in YC and getting such great intro's & connections.

Thanks again for your comments, happy to discuss further!