I've done extensive programming with Twilio.
Venky points out not following their API allows Plivo more
flexibility. I agree with this 100%
For instance, when you are doing an IVR with Twilio you must program
all of your error handling for inputs. I.e.
"Press 1 for sales, 2 for technical support" Twilio has nothing that
would allow you consider 3 as a key press to be invalid. You'd have to
code that yourself, not a big deal but it would make sense to expose
this via the API
There are subltle differences like that make programming cleaner,
easier and less prone to regressions with Plivo potentially.
Verboice looks interesting, I know nothing about it but it looks like
SaaS so you would not have the developer functionality per se. Twilio
is a great product, and has allowed me to incredible things in
rediculously low amounts of time. Of course the Twilio premium is well
worth it to many people. Their pricing is competitive and they give
you their APIs. Our company is starting to spend almost 500 a day
though on Twilio so we are looking into Plivo as a possible
alternative to save costs and also because it would allows us to
connect sip devices directly.