This is great. The part I'm really curious about, maybe for another post, is how the discussion with the leader wanting to buy a tool goes, whether they really need to have a business case, and how much you poke at it. Do you end up having conversations like whether you really need Tableau or Miro, and how does "really need" end up getting defined? Do you diplomatically call BS if someone says the company growth rate will be 1% higher if you buy Podium (just picking an example out of the hat)?
In my experience, leaders often have pretty optimistic business cases. Many times, they're also difficult to define or measure. How can we tell if we're collaborating better with Miro?
Anyway, I know this topic could fill a book, but I'm mostly curious about the war stories.
Great advice! Out of curiosity, what do you think about ‘free’ tools that proliferate inside the org but don’t have an immediate budget request / approval tied to them?
Working in Procurement and Contract Management, these are my go to questions when a new request comes through - even when there is exec level approval of the spend.
I've seen Monday, Asana, Trello and MS Planner all being used in thew same way and requests coming in to increase the licenses of each - with people having multiple seats across the piste.
One insight I wanted to share was on your Fine Print point.
If the solution your buying has a good vibe and is a tool that you can use to promote "this is how we work here" it could be worthwhile letting them use the logo...BUT. I always get a discount for this. Easy discounts are 15% of first year fees. But I've often tied this into the full term regardless of the payment structure.
I've put in place contracts that ensure we get up to 25% discount for the term with the lowest I'd consider sitting at 10% (and that supplier has to be incredible and the benefit to us incredible).
One last though - implementations. You nailed this. So true.
Amazing post CJ! Super helpful for founders to understand how finance influences companies buying products!
This is great. The part I'm really curious about, maybe for another post, is how the discussion with the leader wanting to buy a tool goes, whether they really need to have a business case, and how much you poke at it. Do you end up having conversations like whether you really need Tableau or Miro, and how does "really need" end up getting defined? Do you diplomatically call BS if someone says the company growth rate will be 1% higher if you buy Podium (just picking an example out of the hat)?
In my experience, leaders often have pretty optimistic business cases. Many times, they're also difficult to define or measure. How can we tell if we're collaborating better with Miro?
Anyway, I know this topic could fill a book, but I'm mostly curious about the war stories.
Great advice! Out of curiosity, what do you think about ‘free’ tools that proliferate inside the org but don’t have an immediate budget request / approval tied to them?
Amazing write up here, CJ.
Working in Procurement and Contract Management, these are my go to questions when a new request comes through - even when there is exec level approval of the spend.
I've seen Monday, Asana, Trello and MS Planner all being used in thew same way and requests coming in to increase the licenses of each - with people having multiple seats across the piste.
One insight I wanted to share was on your Fine Print point.
If the solution your buying has a good vibe and is a tool that you can use to promote "this is how we work here" it could be worthwhile letting them use the logo...BUT. I always get a discount for this. Easy discounts are 15% of first year fees. But I've often tied this into the full term regardless of the payment structure.
I've put in place contracts that ensure we get up to 25% discount for the term with the lowest I'd consider sitting at 10% (and that supplier has to be incredible and the benefit to us incredible).
One last though - implementations. You nailed this. So true.