4 ms·

So from one consultant to another consultant, what do you say when a potential client starts to say "Actually, we don't think we can do this engagement, because

by patio11 14y ago

So from one consultant to another consultant, what do you say when a potential client starts to say "Actually, we don't think we can do this engagement, because $X is too much" where $X is some number in three digits?

orangethirty 14y ago
Exactly. They can just create a new account for each new client for peanuts. No client is going to bark for an extra $20 for the github account.
RobAley 14y ago
I don't think he's saying that its too much, its that there is a cheaper option with better financial predictability, and that is why he's not using github. Its more of a heads up to github, paraphrasing : "if you want our business, this is the kind of plan that we like to buy, it solves our pain points, which for us is stability of pricing" or similar.
- imsofuture 14y ago
  That's a bit of an abstract point though. I don't know how many private repos I will be using in a year, so I pay for what I'm currently using. It may go up or down, and my plan will be adjusted accordingly. If the problem isn't the on-my-credit-card-statement cost for the service that you'd use, and is instead a philosophical disagreement with how the cost is calculated... that's just a little bonkers.
  - lifeisstillgood 14y ago
    Thank you for stating clearly what was bothering me.
  - RobAley 14y ago
    Its not an abstract point. My costs may go up, without my income going up, if I need more repos, which I can't necessarily predict in advance. I then either have to eat the extra cost or go cap in hand to the client because part way through the project or starting the next stage we've restructured the way we're using repos. Maybe we should plan better in advance, but with the other service he is using he doesn't have to.
lifeisstillgood 14y ago
I have to agree with this - yes, the limitations are frustrating (talking to a guy with 25 repos.) but I am not in the business of finding cheap ways to deal with a pretty core piece of useful functionality when its barely the cost of my home internet.

by patio11 14y ago

orangethirty 14y ago

Exactly. They can just create a new account for each new client for peanuts. No client is going to bark for an extra $20 for the github account.

RobAley 14y ago

I don't think he's saying that its too much, its that there is a cheaper option with better financial predictability, and that is why he's not using github. Its more of a heads up to github, paraphrasing : "if you want our business, this is the kind of plan that we like to buy, it solves our pain points, which for us is stability of pricing" or similar.

imsofuture 14y ago
That's a bit of an abstract point though. I don't know how many private repos I will be using in a year, so I pay for what I'm currently using. It may go up or down, and my plan will be adjusted accordingly. If the problem isn't the on-my-credit-card-statement cost for the service that you'd use, and is instead a philosophical disagreement with how the cost is calculated... that's just a little bonkers.
- lifeisstillgood 14y ago
  Thank you for stating clearly what was bothering me.
- RobAley 14y ago
  Its not an abstract point. My costs may go up, without my income going up, if I need more repos, which I can't necessarily predict in advance. I then either have to eat the extra cost or go cap in hand to the client because part way through the project or starting the next stage we've restructured the way we're using repos. Maybe we should plan better in advance, but with the other service he is using he doesn't have to.

lifeisstillgood 14y ago

I have to agree with this - yes, the limitations are frustrating (talking to a guy with 25 repos.) but I am not in the business of finding cheap ways to deal with a pretty core piece of useful functionality when its barely the cost of my home internet.