[sgentle]

I am confused about "Splinch Pro" - is there going to be a non-pro version? If not, perhaps it's worth removing that distinction.

As for your pricing, is it based on research? Corporate IT is one of those magical environments where sometimes more is more - ie, your service won't be taken seriously if it's priced too low.

I think it would be worth your time creating a second page with more details. I don't know what "collaborative maintenance" means, nor "community extendable", so having some more information would be helpful. Specifically, I would point out the advantages of your service over the existing approaches. Keep in mind this won't just be read by network admins, but by non-technical managers to whom the benefits may not be immediately obvious.

[jamesotron]

Hi.

Thanks for your feedback. I will be adding more details about the difference between free and pro over the next week or so. I am hoping that I can get engineers to use splinch for their configuration management for free and then find a reason why it is essential for them to upgrade to a Pro - ie more devices or multiple environments (production, DR, etc). You're right, the pricing is based entirely on my gut feel, and unfortunately my guts are wildly oscillating between "people pay hundreds of grand for one of the existing solutions" and "if I price it too high no one will buy it."

I was planning on waiting until I had some screenshots and maybe a screencast available before putting too much effort into the sales side of the site but I'm waiting for a few of the features to be a bit smoother around the edges before I do that.

Thanks for your feedback, I'll give a few network operations managers I know a call and see what the think about pricing.