The best response I’ve found to “But can’t we just build your tech in house?” is no answer. Hash that out, make that call, and when you decide partnering with us and supporting our product is valuable come back. It’s important not to grovel for basic respect.
-
-
There’s more aggressive ways to play it (e.g. you could explicitly forecast project failure and offer to debug that failure in the future), but I think one of the joys of being high-end is that a certain aloofness w/r/t any particular contract does all the talking for you.
-
Another option: “Oh you’ve budgeted and staffed this already! Awesome! Who’s the team?” “Well not so much.” “... Oh, cool, cool. So what you’re saying is you are going to cut one project that is budgeted and staffed for this one. Which one, out of curiosity?” “...”
- 4 more replies
New conversation -
-
-
Yeah, this is what I do too. Sometimes it works out for them, and good for them! If not, well, we're not going anywhere. :-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.