4 ms·

The $800 was just an example number. In some cases I've asked "how much to get you to just pair-program with me using your library for four hours" then our bus

The $800 was just an example number. In some cases I've asked "how much to get you to just pair-program with me using your library for four hours" then our business is concluded. It's a deal that I felt would be very low hassle -- however, I guess the supply-side didn't think so. (for reference I've been coding and consulting around open-source stack for like 20+ years). I've been on both sides of these cut-and-dry type of deals. However, the more common scenario when consulting -- and I'm sure many are nervous about this type of play-out -- is the client drags the deal on and on and on...and argues about the price...and pays late...and has endless change requests...and is surpirse that ECRs cost money...and needs just one more meeting about $THING..and...and...and. I've always assumed that's why we've been rejected...how can someone tell we're NOT LIKE 90% of the consulting buyers and mostly know what we're doing and have a straight-forward deal?

sangnoir 5y ago
> It's a deal that I felt would be very low hassle -- however, I guess the supply-side didn't think so. Were they administratively prepared to accept payments? For instance, did they have business bank accounts, invoicing, tax numbers, record keeping - if not, then it would be a hassle to do all that in order to receive a once-off payment for a days work, even if the rate is generous. Indeed, they'd need to "go commercial" to make the hassle worthwhile. So it may not be as cut-and-dry as you thought.