Yes there are some flaws
a) Its not me testing the CMS its my clients
b) what if you want to show how it works with two languages
c) what if you want to show some workflow
d) what if you want to invest the time to create a demo project for the client - Not the whole project just a demo.
(SF can be a big part of selling your solution)
Again its not me who has to make a decition. I know that SF is the way to go. But the clients must have an opertunity do decide (or I want to give him an opertunity) if SF is the right tool for them. And that's why sometimes I go the extra mile with setting up a small demo project with the future design so the client can play around and be supriesed how easy SF is to use.
Imagin a car sales person who is selling BMW. You have 3,5,7 but in the showroom you have only the 3-er version and just tell the client that the 5 and 7 are very simmiliar but they are just bigger, stronger and faster.
I am sure they want to testdrive the 5 or 7 if they want to buy. Again the sales person (developer) knows that the BMW 5 or BWM 7 is the right car but sometimes it is still nice if the client can at least look at the bigger cars or even test drive it. The sales person could have a proof of concept that BMW is a car that drives nicely by having the client test drive the 3 version.
To me the only explenation why to limit a trial version is to have the client buy faster. Again I had projects where we were working on the site for 12 month before going online. So I understand Telerik on this matter. After all it's a lost revenue.
The current licensing model actually was chosen based on a lengthy discussion in our forums, tickets and e-mails .
I am not about to read the whole thread there but I would be supriesd to find any comment from a developer like
1) I would like telerik to limit the SBE to 50 pages
2) How about limiting the trial version to 30 days