Mike Oeth's guest appearances

Mike Oeth

VUC: IP Communications Community

Talk About Know Priorities

Allison Smith

Justin Jackson

Kathleen King

Allan Branch

Doc Searls

Richard Stallman

Jamie King

Mark Spencer

Olle Johansson

Dan Jenkins

Tom Cheesewright

Stefan Wintermeyer

Paul Vixie

Ben Ward

Marc Grabanski

OwlTail

OnSIP CEO Mike Oeth, a longtime supporter of VUC, will discuss the strategy behind app integrations in the UCaaS space and how they fit into the larger product roadmap. OnSIP recently released a Slack integration with their WebRTC user interface, the OnSIP app.

#VUC613 - OnSIP CEO Mike Oeth

Mike Oeth is the CEO of OnSIP Business VoIP and winner of the Telecommunications Executive of the Year in the 2013 American Business Awards. Mike graduated from Harvard College in 1991 with a degree in Economics and has since worked for technology companies, cofounding OnSIP in 2004. Mike is an active community member and father, balancing his roles as board member of the local YMCA, member of the father-daughter Y-group Adventure Princesses, and basketball coach for his three daughters’ basketball teams. Mike also enjoys rock climbing with his teenage son.  Find &amp; Follow: @VoipCEO Extra links:  OnSip Business VoIP Lighthouse Good to Great - Jim Collins   Notes:  Sales/support &gt; engineering estimates &amp; provides 2 cents &gt; executive team (mkt potential vs time to mkt) It’s rare to get a completely 1-off request Sync up with very active resellers (to help harmonize with the consumer base) Biggest thing to worry about, customer who is yelling the loudest or the most recent thing you heard Loudest or recent is not the best way to figure out what your product should be Have, follow, and stick with a process We are not going to get this deal without X feature, okay pass on the deal Interrupting engineering for 1-off features is like a commercial break, you have to go back and recap Best thing you can do is have a very clear idea of where the product is going and end result is and stick with it Do all of your research ahead of time before they write that first line of code A good engineering team will go pick the best tools, database, interface, etc Have a process, stick to it, and have some consistency once it gets going Emails are best because it's in the customer's own words Tough/flawed: not being thorough enough and not thinking through all the way to how the customer is going to interact Like a director shooting a movie, get down to the little story boards before you even start Get down to the detail before starting otherwise there is too much ambiguity or the result is not what's expected Hedgehog concept (book:  good to great), nucleus of the company...what is the core idea If they don't fit into your hedgehog concept, you pass on those features Have to figure out how these products mesh where you want them to be in 5-10 years Internal back office projects are tougher to get priority compared to revenue generating projects Pitching a product, easier to talk about revenue versus cost savings with execs Interesting to have a voting system to get the wisdom of the crowd Nice to have a crystal ball to see what the market impact would be   Good Job:  Apple Google Dell Juniper

Mike Oeth is the CEO of <a href="http://onsip.com/" rel="nofollow" target="_blank">OnSIP Business VoIP</a> and winner of the Telecommunications Executive of the Year in the 2013 American Business Awards. Mike graduated from Harvard College in 1991 with a degree in Economics and has since worked for technology companies, cofounding OnSIP in 2004. Mike is an active community member and father, balancing his roles as board member of the local YMCA, member of the father-daughter Y-group Adventure Princesses, and basketball coach for his three daughters’ basketball teams. Mike also enjoys rock climbing with his teenage son. <a></a> Find &amp; Follow: <a href="https://twitter.com/VoipCEO" rel="nofollow" target="_blank">@VoipCEO</a> Extra links: <ul> <li><a href="https://www.onsip.com/" rel="nofollow" target="_blank">OnSip Business VoIP</a></li> <li><a href="https://lighthouseapp.com/" rel="nofollow" target="_blank">Lighthouse</a></li> <li><a href="http://www.amazon.com/Good-Great-Some-Companies-Others/dp/0066620996/" rel="nofollow" target="_blank">Good to Great - Jim Collins</a></li> </ul> <a></a> Notes: <ul> <li>Sales/support &gt; engineering estimates &amp; provides 2 cents &gt; executive team (mkt potential vs time to mkt)</li> <li>It’s rare to get a completely 1-off request</li> <li>Sync up with very active resellers (to help harmonize with the consumer base)</li> <li>Biggest thing to worry about, customer who is yelling the loudest or the most recent thing you heard</li> <li>Loudest or recent is not the best way to figure out what your product should be</li> <li>Have, follow, and stick with a process</li> <li>We are not going to get this deal without X feature, okay pass on the deal</li> <li>Interrupting engineering for 1-off features is like a commercial break, you have to go back and recap</li> <li>Best thing you can do is have a very clear idea of where the product is going and end result is and stick with it</li> <li>Do all of your research ahead of time before they write that first line of code</li> <li>A good engineering team will go pick the best tools, database, interface, etc</li> <li>Have a process, stick to it, and have some consistency once it gets going</li> <li>Emails are best because it's in the customer's own words</li> <li>Tough/flawed: not being thorough enough and not thinking through all the way to how the customer is going to interact</li> <li>Like a director shooting a movie, get down to the little story boards before you even start</li> <li>Get down to the detail before starting otherwise there is too much ambiguity or the result is not what's expected</li> <li>Hedgehog concept (book: good to great), nucleus of the company...what is the core idea</li> <li>If they don't fit into your hedgehog concept, you pass on those features</li> <li>Have to figure out how these products mesh where you want them to be in 5-10 years</li> <li>Internal back office projects are tougher to get priority compared to revenue generating projects</li> <li>Pitching a product, easier to talk about revenue versus cost savings with execs</li> <li>Interesting to have a voting system to get the wisdom of the crowd</li> <li>Nice to have a crystal ball to see what the market impact would be</li> </ul> <a></a> Good Job: <ul> <li><a href="http://www.apple.com" rel="nofollow" target="_blank">Apple</a></li> <li><a href="http://www.google.com" rel="nofollow" target="_blank">Google</a></li> <li><a href="http://www.dell.com" rel="nofollow" target="_blank">Dell</a></li> <li><a href="http://www.juniper.net" rel="nofollow" target="_blank">Juniper</a></li></ul>