(Cross-posted on the Commerce Blog)
This is the latest post in our series profiling entrepreneurial Googlers working on products across the company and around the world. In this post, you’ll read why one team decided to sell their company to Google, and how they went from acquisition to product launch in less than a year. - Ed.
The decision to sell your company is one of the hardest an entrepreneur can make, and as the CEO of Jambool, I thought long and hard about Google’s offer to acquire us when they came calling in August 2010. Ultimately, we decided to join Google for two reasons: one, we shared the goal of offering consumers and merchants unified online payment solutions, and two, we realized that Google was serious about helping us integrate our technology into their digital tools by providing us with infrastructure and other support. Less than a year later, we’ve already taken a major step to help Google deliver on this vision with Google In-App Payments, which we announced last month at Google I/O. In-App Payments enable web application developers to receive payments for digital and virtual goods without the user ever leaving the application.
When we first joined, we expected to spend a lot of time ramping up, meeting people and learning Google’s technology. In reality, our shared vision for the product enabled us to quickly partner with teams across the company to build out our product at scale. As a startup, you spend the majority of your time building teams from scratch to focus on functions like product, sales, marketing, operations and legal. At Jambool, I’d divide my time across operations, raising funds and meeting with outside developers. But at Google, we were able to combine our efforts with teams already in place who could manage those areas while we focused on the core product.
We set an ambitious goal of launching in-app payments nine months later at Google I/O, which motivated us to work quickly. We worked with Google’s established teams—especially Chrome, Android and Google Checkout—to build a simple API and intuitive user interface. During the last few weeks before Google I/O—when we were still working around the clock just to finish the product—we were invited to announce our launch as part of the day two keynote. That gave us even more drive to finish on time. And, thanks to the Chrome team, we found partners like Angry Birds and Graphic.ly, which really demonstrated the product’s usefulness and got developers excited about our broader vision of seamless digital payments.
As a startup, we never imagined we’d stand on a stage like the one at I/O and instantly reach consumers, businesses and developers around the world. In the first 24 hours after the announcement, thousands of developers signed up to use the API. This is something we wouldn’t have been able to do so quickly on our own, and it’s a testament to the big things a startup can accomplish by joining Google. We’re already looking forward to what the next year brings as developers around the world start to build great businesses on our platform.
If you’re interested in integrating your apps into Google’s In-App Payments API, we invite you to sign up and send us feedback.
This is the latest post in our series profiling entrepreneurial Googlers working on products across the company and around the world. In this post, you’ll read why one team decided to sell their company to Google, and how they went from acquisition to product launch in less than a year. - Ed.
The decision to sell your company is one of the hardest an entrepreneur can make, and as the CEO of Jambool, I thought long and hard about Google’s offer to acquire us when they came calling in August 2010. Ultimately, we decided to join Google for two reasons: one, we shared the goal of offering consumers and merchants unified online payment solutions, and two, we realized that Google was serious about helping us integrate our technology into their digital tools by providing us with infrastructure and other support. Less than a year later, we’ve already taken a major step to help Google deliver on this vision with Google In-App Payments, which we announced last month at Google I/O. In-App Payments enable web application developers to receive payments for digital and virtual goods without the user ever leaving the application.
Me on stage at Google I/O introducing Google In-App Payments
When we first joined, we expected to spend a lot of time ramping up, meeting people and learning Google’s technology. In reality, our shared vision for the product enabled us to quickly partner with teams across the company to build out our product at scale. As a startup, you spend the majority of your time building teams from scratch to focus on functions like product, sales, marketing, operations and legal. At Jambool, I’d divide my time across operations, raising funds and meeting with outside developers. But at Google, we were able to combine our efforts with teams already in place who could manage those areas while we focused on the core product.
We set an ambitious goal of launching in-app payments nine months later at Google I/O, which motivated us to work quickly. We worked with Google’s established teams—especially Chrome, Android and Google Checkout—to build a simple API and intuitive user interface. During the last few weeks before Google I/O—when we were still working around the clock just to finish the product—we were invited to announce our launch as part of the day two keynote. That gave us even more drive to finish on time. And, thanks to the Chrome team, we found partners like Angry Birds and Graphic.ly, which really demonstrated the product’s usefulness and got developers excited about our broader vision of seamless digital payments.
If you’re interested in integrating your apps into Google’s In-App Payments API, we invite you to sign up and send us feedback.
From acquisition to in-app payments in less than one year
![From acquisition to in-app payments in less than one year]()
Reviewed by MCH
on
June 06, 2011
Rating:
No comments: