[Shorrock]

In this type of transaction both parties end up achieving their goal going into things. The seller wants to sell, and the buyer wants to buy. Both parties likely disagree with the potential of the product.

With that in mind, a question for the buyer - What do you understand about the business that the seller doesn't that makes this seem worth while? And for the seller - What aspect of the business makes it a target for sale rather than growth?

[kareemm]

Good q, thanks Shorrock.

> What do you understand about the business that the seller doesn't that makes this seem worth while?

We were guessing that the seller was getting too busy running his day job at Drip to devote enough time to Codetree. It seemed reasonable because we'd been following Drip via Rob Walling's podcast and blog for years and Drip sounded like it was doing well.

We'd been in a similar spot with a previous business we sold. A seller may want to sell for a variety of reason, not just because the business is destined for failure.

But broadly, we think the PM market is huge, GitHub is huge and seems as good a partner as you could want given the platform risk, if "Software is eating the world" is true (we think it is) then the # of devs is only going to increase and they're going to need tools. And we're devs and love serving devs. So it was a good fit.

[derrickreimer]

The bottom line for me was time and focus. If I had more hours in the day, I would have kept Codetree and grown it. My other business Drip was experiencing crazy growth and Codetree had always been a side business, taking the back seat to the needs of Drip. At the time of sale, I had at least 50 different feature ideas/growth opportunities written down but very little time to implement them. Rather than watch the product slowly fade away, the next best outcome for me was to see someone else realize that potential.