The Dienstleistung Support is the final link in a product development cycle, but also not infrequently Dasa mostly vernachlässigste.
In the coming days and weeks, I want you to bring this activity in various articles closer and illuminate from various perspectives.
Many software developers, web designers, programmers etc. develop your Kunden excellent products but forgot at the beginning of the contract,  that there is also a time after completion. Questions about use, small adjustments or even to troubleshoot small mistakes come as a rule always later, ie after the handover. As a good service to its customers will of course help (with bugs anyway).
But one wants to stay the same hand for every little thing?
Very few do this, and for good reason - Finally, one wants his customers not deterred, in which one of every half hour ("You never know if there is something.") Equal to an invoice writes.
But what is the alternative to labor in vain?
To only not to fall into such a conflict of conscience, it is advisable to take out the same from the outset a support contract, which governs all this. So you have yourself do not feel that you will be exploited and the customer does not feel that he gets the same for jeden handle an invoice, a perceived win-win situation so.
Here too I also download a tip for you: 22 sample contracts for self-employed and freelancers from the IT
But what should be in such a contract? What should be supported, what is not? How fast you should respond to support requests? How can you offer customers a good support, even if they have their headquarters far away? And how confident you complete a customer such a contract at all?
These questions and a few more I treatable in the following parts of this series.
"Successfully offer support" The other parts of the - series can be found here:
0 comments:
Post a Comment