This is a though one. Usually the only / best shot i have on this is...
Linking it to long term delivery timeline (useful for continuous long running projects)
Long term schedule can be shorter : faster go to market
Linking it to perceivable user experience (eg, api being slow affects site load speeds)
User experience can be better : better revenue??
Generally though as many clients tends to view IT as a "cost center" as oppose to a "tech asset". I find that linking it to something that affects their business bottom line is the best way to get across the "cost center" barrier.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a though one. Usually the only / best shot i have on this is...
Linking it to long term delivery timeline (useful for continuous long running projects)
Linking it to perceivable user experience (eg, api being slow affects site load speeds)
Generally though as many clients tends to view IT as a "cost center" as oppose to a "tech asset". I find that linking it to something that affects their business bottom line is the best way to get across the "cost center" barrier.