We wrote a post about this recently[1]. It really depends on how you want to use them, but here are three things that might not be obvious about Projects on first glance:
* GH Projects exist within a repo, so you can only have Issues from a single repo on a Project.
* A Project contains a subset of issues within a repo - they need to be added manually to the project. This would make it tough to manage a whole project with a Project because you'd have to manually add any issue you created to it.
* You can't filter issues in a Project. Fundamentally a Project is not driven by a query, it's driven by manually adding issues to a Project. So slicing and dicing issues on a Project isn't possible.
I think GH Projects could be used to manage the release of an Epic (e.g. a subset of issues grouped together within a repo). But I think it'd be challenging to manage an entire project with one.
What's your status on integrating with other platforms? any plans for integration with other platforms in the future (gitlab, gogs, other platforms...)
Integrations with other platforms are on our list, but right now we're focused on improving the product for existing GitHub customers. The GitHub market is so large that to split our focus right now wouldn't make sense.
what are your thoughts on aqui-hiring a side project instead of just purchasing a side project, but incorporating the sole developer(creator) too?
how would you estimate the valuation in that case? would you offer him/her the price to purchase the side project in addition to a salary? or offer a unique compensation package that takes into account of the valuation of the side project?
> what are your thoughts on aqui-hiring a side project instead of just purchasing a side project, but incorporating the sole developer(creator) too?
I'd want to feel good about the reasons the creator wanted to sell and keep working on it. I think it would be hard to take the product where we wanted without the creator getting frustrated - if s/he had the vision and ability to execute, why did they need to be hired?
That said, I'd be open to it.
> how would you estimate the valuation in that case? would you offer him/her the price to purchase the side project in addition to a salary? or offer a unique compensation package that takes into account of the valuation of the side project?
Hard to say because I think it depends on the situation.
I'd read a few prospectuses and make sure you understand them (especially the profit and loss statements - lots of info online about these). Sign up for FE's mailing list to get some prospectuses.
Otherwise, it depends what you want to learn. I'm sure a quick search on Amazon would be fruitful.
Are you asking about valuations? FE has a post on how valuations work. It's pretty simple. Basically a multiple of how much cash you can take out of the business. If that number is small and not growing then the multiple is small. If the number is big and/or growing fast then the multiple will be larger. The key is it's about how much cash the business makes now vs. traditional tech VC land is about... how big this might be some day maybe.
If you're interested in buying a business the people who know how all this stuff works are the private equity people (PE). These guys do this stuff all day long (obviously at much larger scales. If you search you can find a fair amount of info on PE. On a smaller scale there is good info from people researching search funds. Search funds are basically small scale PE. Here's a good starting point: http://www.gsb.stanford.edu/faculty-research/centers-initiat....
Warren Buffett's annual shareholder letters are one of the better ways to learn about these things. Easier to read than textbooks with plenty of real life examples.
It's not obvious to me why price was a function of earnings in a situation like this, the goal of the purchase seemed to be to save resources of developing the tracker inhouse and save time building up a customer-base, earning seems mostly irrelevant in this case.
If the codetree was looking to raise funding, it seems like a reasonable metric for valuation.
The goal of the purchaser was to save cost of development but the goal of the seller was to get as much as possible. In that case, basing the selling price on earnings makes more sense for the seller. After all, he can always look for another buyer if the deal doesn't work out.
I guess I thought the cost of development would be higher than $128k, so it would be beneficial to the seller to use that as a metric.
One month of an average engineer's time costs an employer around $20k. Could one engineer recreate this product in 6 months working full-time? The maker of codetree probably has a really good idea of how long it takes. If the answer is yes, does the buyer have someone on hand to take this on? if not, you have to hire someone, that takes time. If you don't want to do that, contract it out at double the cost. Then at the end of the day you're now delayed however long it takes to finish the product plus maybe hiring time.
Codetree's initial blogpost says the developer took 6 months working part-time to launch the initial product. Supposing it could be done in 3 months working full-time to get to the latest iteration, cost to develop is $60k + 3 months + 1 engineer or $60k + 3 months + 3 month hiring process + 1 engineer(new hire) or $120k + 3 months + 1 contractor. Pulling an engineer off of a project also adds cost to the project they would have been on had they not left.
I would guess the effective cost of development is $120k + 3 months time, if you want to acquire the product instead, the question becomes how much money would you be willing to pay to have it now (plus negotiation time) instead of 3 months from now?
The issue is that to a buyer, the inputs don't matter. We're buying the outputs in the form of business results.
If Codetree was doing $120 in ARR after 2y of FT development, he's not going to be able to sell it for 2y * salary_to_build_app. He's going to sell it for some multiple of $120 minus expenses.
As a seller you may not know that much about the buyer's BATNA - in particular, are they looking for "my product or something like it" or are they looking for "a solid product with customers and a seller unable/unwilling to grow it."
They may be fully willing to walk away and in many cases probably will, because if they were THAT gung-ho about competing in your niche market there's a good chance they'd already be involved with something competing with you and much more likely to decide to just build it themselves.
Actually having more than a nominal number of paying customers is also a huge factor - how long did it take codetree to get those customers? Add customer acquisition time to your development time estimates.
From the seller's perspective you've got to have a buyer and buyers at this price point buy on a multiple of SDE vs. development cost. If dev cost is greater than what buyers will pay then as the seller... you're probably going to have to eat it and take less.
Importantly as the buyer a big part of what you're buying is customers that you can talk to and work with vs. just the code. If we thought Codetree would have taken twice as long to build but had zero customers we wouldn't have bought it at half the price. Having paying customers proves that you've bought something that other people value. Buying code just gets you code and you may find out that no one will ever pay to use it.
Issue trackers have substitutability. Not much maybe, but certainly some. As less pompous way of putting this, is to say 'if they don't buy this one, they'll buy another'. Yet another way is saying 'buyer BATNA is buying another product'.
I don't think we were even in danger of losing the deal because we always moved when the seller said no to terms they didn't like. We never stood firm and forced the seller to move on their position.
very interesting read. We looked at github issues mgt tools a while ago and settled on huboard. We didn't find codetree during our search for tools... so it's definitely a challenge to reach developers. Fine posts like this can do the trick ;-)
Yes, we looked at huboard.com, zenhub.io, waffle.io and blossom.io. There are really a lot of tools out there. But I can't remember the reasons we choose huboard over blossom. In addition, the tools evolve quite quickly. So the reasons might be outdated anyway.
No, of course not. But the price was listed as "$128k". The closest power of 2 to the actual full price is 2^17, but I doubt most technical people would recognize that as 131,072.
It's great to read the details about what it takes to buy a small business. Thanks for posting this and being so open about what went into the negotiation. I always thought (if I were to one day run into money) buying an already-running business would be a better, less risky path towards entrepreneurship than starting with a blank text editor!
A few questions:
Is it common to have to fork over all cash for these sized deals? Is it possible/acceptable to finance? What alternatives to seller financing have you seen? I don't imagine it's possible to just waltz into your local bank and say hi guys I need $100K to buy a website!
I'd be interested in learning more about finding these deals. You found this one through FE. Are there other common places to find tech listings? Do you ever approach companies that you like but aren't actively looking to sell? I'd love to see a play by play of how one of those conversations go.
> Is it common to have to fork over all cash for these sized deals? Is it possible/acceptable to finance? What alternatives to seller financing have you seen? I don't imagine it's possible to just waltz into your local bank and say hi guys I need $100K to buy a website!
I've discussed this with my local Belgian bank (well, not $100k, closer to $1-1.5m), and they'd be happy to do it if I put up 25-30% of the capital. So should definitely be doable. The issue is finding a good and viable asset that won't deteriorate. Usually there's a reason why people sell.
The reason might be that the owner gets bored with the business? Maybe the owner liked the getting started part, but doesn't enjoy all the analytics and marketing stuff that's necessary to grow the business to it's full potential?
Absolutely. But buying an asset can be quite hard, especially if you're at least trying to align it with your personal skill set. For example, I've probably looked through 30-40 prospectuses and have only once found something moderately interesting.
See my comment above on the alternative approach. The short answer is to approach the problem the other way. Build a list of businesses you'd buy and start emailing.
> Is it common to have to fork over all cash for these sized deals? Is it possible/acceptable to finance? What alternatives to seller financing have you seen? I don't imagine it's possible to just waltz into your local bank and say hi guys I need $100K to buy a website!
Bank loans, equity partners, seller financing, and cash are the options I've seen. Equity is harder for a deal this small. But bank loans are a definitely option. If you're in the US I think there are SBA loans that are available too.
The problem with many small business loans is that they need to be guaranteed by "tangible" goods, e.g. land, building, machinery etc.
Banks and other financing providers often also require an appraisal by a 3rd party.
Unless you are buying an already established business it can be very hard to find good financing for things like software since there will be nothing for the bank to repossess and evaluating it's worth might not be easy.
See my comment up the thread. It seems like that might be changing at least in Canada. I've heard similar things about SBA loans in the US though so perhaps similar changes are afoot in the US as well.
(I'm one of the purchasers of Codetree) I had also thought that banks wouldn't be interested in lending in cases like this but surprisingly enough when we talked with our bank after we made the purchase they mentioned they'd be very interested in financing us if we were looking at buying other software businesses in the future. When I had talked with them a few years ago there was no way they'd have loaned money for a purchase like this because it has no tangible assets. They told us straight up that they understand the world is changing and they are now interested in making these types of loans. They get that small businesses owners today are just as likely to be software companies as they are to be restaurants. We're Canadian and our bank is TD.
Question: Did you acquire the assets with a Canadian entity? I'm assuming so. Did you have any problems transferring the billing subscribers? I'm EU based, and one of the concerns I've had / I have is that some US based customers seem to be getting auto rejects by their credit card provider (i.e. Stripe) when billing. Not exactly sure how I discovered that -- I think some guy wrote about it on a SaaS forum somewhere.
Yep, we acquired the assets with a Canadian entity.
We had this problem with a previous business when we moved from a US Stripe account to a Canadian Stripe account (when we started the original business Stripe wasn't available in Canada).
We were concerned about CC rejections, but shockingly didn't deal with a single one. In the past customers would just call up their CC provider and tell them to expect a recurring change from vendor_name and it ceased being an issue.
One MAJOR problem we had was transferring subscriptions from the US Stripe Account to the Canadian account. Stripe used to do this service for you (it has for us twice, once when we moved from US ==> Canada, and once when we sold the Canadian assets to another US corp). But they don't anymore, and their documentation and process around this is WOEFULLY lacking. Probably have a blog post in us about the process.
Thanks for the answer--it's very encouraging. Of course, I forgot the "find an equity partner" route. I could see approaching someone with money and an interest in technology but no time/talent to maintain the product. But even if you do that and negotiate an ownership share in whatever you're buying, you're more like employee #1 than a true partner. Did you guys each put up an equal amount of $ when you first started doing this?
Yep, we're all equal partners. Figured it's a lot easier that way.
But I've seen a couple situations where one partner brings the asset and the other brings sweat and they've been quite fruitful. One in particular I'm thinking of turned a 120k arr business into a 1m arr (and growing) business. So it's possible.
could also finance via an earn-out with founder involved for a period of time
IMO it's a good writeup on how a financial buyer dots the i's and crosses the t's on a deal but the main driver of a deal isn't that, it's just, can it be grown into a much bigger business, and what are the potential risks and rewards.
Do the buyers love the business and are they willing to do whatever it takes to realize that potential? If the buyers aren't thinking like founders and are thinking like financial buyers worried about the last few percent, it's a recipe for problems.
The risks are sufficiently large in taking over someone else's code and customers, that only reason to buy it is if you think you can make it worth multiples of what you're paying.
As a seller, it might make sense to do an earn-out or retain a small equity stake and involvement with the right buyers, but being a minority partner without the type of protection VCs get (board seat, liquidation preference, pro-rata follow-on rights / anti-dilution) is a terrible position to be in, unless you are very sure of who you are dealing with, so typically not with this type of financial buyer.
That's why "cash in hand" was one of their selling points.
If the buyers had to get loans, sell other assets, etc to make it happen, it would introduce risk - in delay, extra negotiations or even total failure - for the seller.
Having your financing together is going to give you a leg up in a competitive deal for sure. Of course not all deals are competitive so it might not matter. In some cases your bank will give you a letter saying they are willing to lend you $X under reasonable circumstances which might help you get in the door with with sellers by convincing them you can close even if you don't actually have the cash upfront.
kareemm has already answered the questions about financing but I actually think your second question about "where to find these deals" is really the more interesting and important question. The obvious answer is places like FE where we found Codetree but that was a total fluke and it's not the right way to approach it.
The truth of the matter is that many business are for sale if you ask. The right approach is to think about the type of business you want to buy, build a list of all of the ones that fit and to cold email them and see if they'd be interested in selling. Basically the same approach you'd take if you were trying to sell B2B software i.e. Predictable Revenue style.
I can already hear people saying, "No way people don't do that" or "That would never work" but it does and people do. In fact we know a number of people that bought their businesses using that approach and it is exactly what we were about to start doing before Codetree fell in our laps. It's also the way that a lot of PE, VC and search fund deals get done.
Exactly this. I want to present my business as being available for sale. However, it is difficult to start this dialog on HN because people seem to find it spamming to bring the subject up. HN could be more hospitable to finding these types of deals. Maybe a new section?
For sure. As a seller I think services like FE make a lot of sense. They have relationships with a lot of potential buyers to put your business in front of. Unless you're well connected it's going to be a lot harder to drum up buyers on your own. As a seller what you want is an auction where multiple buyers are competing to buy your business.
I'd bet cold-E-mailing could actually work, but how do you find comps to guesstimate the cost of the business if it's not for sale and not much is known about it. I could imagine E-mailing CLOSELY_HELD_SMALL_PROJECT I think I could run better and getting back, "Sure, I'll sell. We generate $5M in FCF and I'd take 3X that!". Me: Uhhhhh, aww shit.
Do your due diligence with financial statements. Any business will file taxes and any corporation will additionally have income statements, balance sheets, etc.
To clarify, I'm asking what are some clever ways to ballpark what a company's financials might be, to pre-screen out ones out of my league before I even contact them. Most companies don't publish anything about their finances at all.
Unfortunately, I don't think you're going to find a good way to ballpark their financials without them supplying them. It's common in the cold email to say something like, "Our sweet spot is companies with an EBIT of $X-$Y". So the person you're contacting knows if they are too big or too small.
For deals of this size you can also look for smoke signals e.g. you're looking to buy something for 200k-300k in EBIT and you go to their about page and find 50 employees you're probably barking up the wrong tree.
It's also worth pointing out that you're looking for one person to say yes. If you hit on folks that aren't a fit and never email you back or laugh you away so what. That's the nature of the game. You just need one.
Remember that an offer to buy is also a sales pitch, after a fashion. Unsolicited offers start to come in almost as soon as you feel like you have room to breathe.
No different than doing B2B sales and emailing a prospect that is 10x bigger than you expected and only buys IBM and Oracle. A failure to penetrate a single prospect just means you move on to the next one.
I know someone that recently bought a business that was for sale for 100k for something like 10k and x% revenue for 2 years. Basically if revenue was constant the cost ended up at 100k. If it dropped it would be less.
Kind of a neat way to not need all the money up front, and make the owner shows you his business is not on the decline.
There are lot of similar type formulas. For larger deals you'd have some form of vender (seller) financing which is what the above really is. It's a type of loan from the seller. For smaller deals that are reasonably competitive you're going to probably have to do an all cash offer.
If you think you're in a good negotiating position or if you've got concerns about the business then a vender take back or an earn out or both should definitely be on the table. It never hurts to ask ;).
Very good insights on buying a side project. I too have some side projects. But I never want to go fulltime into it because it's using APIs of some well known services. I always say " Never play soccer in someone else's ground ". You never know when they will throw you out of the ground. If you are basing the business out of github's resources you are at high risk.
Thank you for being so open and sharing the actual spreadsheets. It makes things a lot clearer for us dreaming for an acquisition someday :) - even though I worked for a company that went through an acquisition as an employee and even gave a talk on the subject, this is a new perspective for me :)
Wow, if you want to learn how not to negotiate a deal, this is the story to read!
This guy had you right where he wanted the entire time and he knew it. He didn't have to lift a finger or budge an inch. You clearly show your hand(s) way too much (which is clearly in your nature given this blog post, and that's not always a bad thing... although in this case it was).
If it was a really large deal, you'd need to be willing to walk and show it. Instead of reading a relatively overrated book that did you absolutely nothing, I'd recommend having someone be the bulldog/enforcer and have no qualms about it.
But ultimately, I have a feeling you're going to be so successful in something eventually (if not this!) that this money is meaningless in the grand scheme of things, so it's all cool and maybe you knew that.
But man, that was painful to read. Good stuff otherwise and great luck guys!
80 comments
[ 4.4 ms ] story [ 151 ms ] threadhttps://github.com/blog/2256-a-whole-new-github-universe-ann...
* GH Projects exist within a repo, so you can only have Issues from a single repo on a Project.
* A Project contains a subset of issues within a repo - they need to be added manually to the project. This would make it tough to manage a whole project with a Project because you'd have to manually add any issue you created to it.
* You can't filter issues in a Project. Fundamentally a Project is not driven by a query, it's driven by manually adding issues to a Project. So slicing and dicing issues on a Project isn't possible.
I think GH Projects could be used to manage the release of an Epic (e.g. a subset of issues grouped together within a repo). But I think it'd be challenging to manage an entire project with one.
1 - http://blog.codetree.com/articles/the-important-differences-...
I'd want to feel good about the reasons the creator wanted to sell and keep working on it. I think it would be hard to take the product where we wanted without the creator getting frustrated - if s/he had the vision and ability to execute, why did they need to be hired?
That said, I'd be open to it.
> how would you estimate the valuation in that case? would you offer him/her the price to purchase the side project in addition to a salary? or offer a unique compensation package that takes into account of the valuation of the side project?
Hard to say because I think it depends on the situation.
Otherwise, it depends what you want to learn. I'm sure a quick search on Amazon would be fruitful.
If you're interested in buying a business the people who know how all this stuff works are the private equity people (PE). These guys do this stuff all day long (obviously at much larger scales. If you search you can find a fair amount of info on PE. On a smaller scale there is good info from people researching search funds. Search funds are basically small scale PE. Here's a good starting point: http://www.gsb.stanford.edu/faculty-research/centers-initiat....
http://www.berkshirehathaway.com/letters/letters.html
Edit: Also, best of luck!
Edit: and thanks!
If the codetree was looking to raise funding, it seems like a reasonable metric for valuation.
One month of an average engineer's time costs an employer around $20k. Could one engineer recreate this product in 6 months working full-time? The maker of codetree probably has a really good idea of how long it takes. If the answer is yes, does the buyer have someone on hand to take this on? if not, you have to hire someone, that takes time. If you don't want to do that, contract it out at double the cost. Then at the end of the day you're now delayed however long it takes to finish the product plus maybe hiring time.
Codetree's initial blogpost says the developer took 6 months working part-time to launch the initial product. Supposing it could be done in 3 months working full-time to get to the latest iteration, cost to develop is $60k + 3 months + 1 engineer or $60k + 3 months + 3 month hiring process + 1 engineer(new hire) or $120k + 3 months + 1 contractor. Pulling an engineer off of a project also adds cost to the project they would have been on had they not left.
I would guess the effective cost of development is $120k + 3 months time, if you want to acquire the product instead, the question becomes how much money would you be willing to pay to have it now (plus negotiation time) instead of 3 months from now?
If Codetree was doing $120 in ARR after 2y of FT development, he's not going to be able to sell it for 2y * salary_to_build_app. He's going to sell it for some multiple of $120 minus expenses.
* the cost of development is higher than any multiple on earnings I can get
* I know the buyer's BATNA is developing the product themselves
anything that isn't a above expected development cost is leaving money on the table.
They may be fully willing to walk away and in many cases probably will, because if they were THAT gung-ho about competing in your niche market there's a good chance they'd already be involved with something competing with you and much more likely to decide to just build it themselves.
Actually having more than a nominal number of paying customers is also a huge factor - how long did it take codetree to get those customers? Add customer acquisition time to your development time estimates.
Importantly as the buyer a big part of what you're buying is customers that you can talk to and work with vs. just the code. If we thought Codetree would have taken twice as long to build but had zero customers we wouldn't have bought it at half the price. Having paying customers proves that you've bought something that other people value. Buying code just gets you code and you may find out that no one will ever pay to use it.
I saw this company on FE and requested more information.
In the end, I decided against making an offer because developers are notoriously hard to develop for.
That said, the business itself looked great, wish you the best of luck and good on you for taking a shot.
Codetree looks great! Good luck!
Wonder if prices like this are more attractive to techies.
A few questions:
Is it common to have to fork over all cash for these sized deals? Is it possible/acceptable to finance? What alternatives to seller financing have you seen? I don't imagine it's possible to just waltz into your local bank and say hi guys I need $100K to buy a website!
I'd be interested in learning more about finding these deals. You found this one through FE. Are there other common places to find tech listings? Do you ever approach companies that you like but aren't actively looking to sell? I'd love to see a play by play of how one of those conversations go.
I've discussed this with my local Belgian bank (well, not $100k, closer to $1-1.5m), and they'd be happy to do it if I put up 25-30% of the capital. So should definitely be doable. The issue is finding a good and viable asset that won't deteriorate. Usually there's a reason why people sell.
Bank loans, equity partners, seller financing, and cash are the options I've seen. Equity is harder for a deal this small. But bank loans are a definitely option. If you're in the US I think there are SBA loans that are available too.
Unless you are buying an already established business it can be very hard to find good financing for things like software since there will be nothing for the bank to repossess and evaluating it's worth might not be easy.
We had this problem with a previous business when we moved from a US Stripe account to a Canadian Stripe account (when we started the original business Stripe wasn't available in Canada).
We were concerned about CC rejections, but shockingly didn't deal with a single one. In the past customers would just call up their CC provider and tell them to expect a recurring change from vendor_name and it ceased being an issue.
One MAJOR problem we had was transferring subscriptions from the US Stripe Account to the Canadian account. Stripe used to do this service for you (it has for us twice, once when we moved from US ==> Canada, and once when we sold the Canadian assets to another US corp). But they don't anymore, and their documentation and process around this is WOEFULLY lacking. Probably have a blog post in us about the process.
But I've seen a couple situations where one partner brings the asset and the other brings sweat and they've been quite fruitful. One in particular I'm thinking of turned a 120k arr business into a 1m arr (and growing) business. So it's possible.
IMO it's a good writeup on how a financial buyer dots the i's and crosses the t's on a deal but the main driver of a deal isn't that, it's just, can it be grown into a much bigger business, and what are the potential risks and rewards.
Do the buyers love the business and are they willing to do whatever it takes to realize that potential? If the buyers aren't thinking like founders and are thinking like financial buyers worried about the last few percent, it's a recipe for problems.
The risks are sufficiently large in taking over someone else's code and customers, that only reason to buy it is if you think you can make it worth multiples of what you're paying.
As a seller, it might make sense to do an earn-out or retain a small equity stake and involvement with the right buyers, but being a minority partner without the type of protection VCs get (board seat, liquidation preference, pro-rata follow-on rights / anti-dilution) is a terrible position to be in, unless you are very sure of who you are dealing with, so typically not with this type of financial buyer.
If the buyers had to get loans, sell other assets, etc to make it happen, it would introduce risk - in delay, extra negotiations or even total failure - for the seller.
The truth of the matter is that many business are for sale if you ask. The right approach is to think about the type of business you want to buy, build a list of all of the ones that fit and to cold email them and see if they'd be interested in selling. Basically the same approach you'd take if you were trying to sell B2B software i.e. Predictable Revenue style.
I can already hear people saying, "No way people don't do that" or "That would never work" but it does and people do. In fact we know a number of people that bought their businesses using that approach and it is exactly what we were about to start doing before Codetree fell in our laps. It's also the way that a lot of PE, VC and search fund deals get done.
As a buyer that's the last thing you want because it drives the price up. See point 6: http://www.berkshirehathaway.com/2000ar/acq.html.
For deals of this size you can also look for smoke signals e.g. you're looking to buy something for 200k-300k in EBIT and you go to their about page and find 50 employees you're probably barking up the wrong tree.
It's also worth pointing out that you're looking for one person to say yes. If you hit on folks that aren't a fit and never email you back or laugh you away so what. That's the nature of the game. You just need one.
Kind of a neat way to not need all the money up front, and make the owner shows you his business is not on the decline.
If you think you're in a good negotiating position or if you've got concerns about the business then a vender take back or an earn out or both should definitely be on the table. It never hurts to ask ;).
> Github would improve its Issues product and render Codetree irrelevant
That seems like a very large risk, especially given GitHub's progress to date. How will it be addressed?
This guy had you right where he wanted the entire time and he knew it. He didn't have to lift a finger or budge an inch. You clearly show your hand(s) way too much (which is clearly in your nature given this blog post, and that's not always a bad thing... although in this case it was).
If it was a really large deal, you'd need to be willing to walk and show it. Instead of reading a relatively overrated book that did you absolutely nothing, I'd recommend having someone be the bulldog/enforcer and have no qualms about it.
But ultimately, I have a feeling you're going to be so successful in something eventually (if not this!) that this money is meaningless in the grand scheme of things, so it's all cool and maybe you knew that.
But man, that was painful to read. Good stuff otherwise and great luck guys!