I have recently started working as a freelancer, and I just received my first relatively easy project. Although the customer didn't choose me as the performer, we are discussing the project via Skype. After reading through 3 pages, I informed them that I would provide a reset for verification, but I would like to receive payment for the entire layout first. The customer then asked me to reset the printed pages on a free hosting platform for the purpose of checking registration and cross-browser compatibility. However, this is essentially equivalent to sending them the completed layout directly. As a beginner in this field, I am unsure how to respond.
On another note, I have concerns that the customer may steal the layout (which currently consists of 3 pages) from the hosting platform, leaving me without payment and losing the customer altogether.
When it comes to working as a freelancer, it's important to establish clear communication and boundaries with your clients to protect your work and ensure fair payment. In this situation, it's understandable that you have concerns about sharing your completed layout without receiving full payment first.
One possible approach you can take is to express your concerns to the customer honestly. Explain that due to the nature of your work and the potential risk of your layout being stolen, you would prefer to receive payment before sharing the completed project on any platform. You can offer alternative options for the customer to review your work, such as sharing screenshots or using watermarked versions of the layout.
Additionally, you can emphasize that you are willing to make any necessary revisions or adjustments once the payment has been made. This shows your willingness to work with the customer and ensures that they will receive a satisfactory final product.
Remember, it's important to be professional, assertive, and clear in your communication while maintaining a positive working relationship with your client.
If you're still unsure about how to respond and would like more guidance, here's a suggested message you can send to the customer:
"Hi [Customer's Name],
Thank you for considering me for your project. I appreciate the opportunity to work with you. After reviewing your requirements and discussing it further, I have some concerns regarding the next steps.
While I am confident in my ability to deliver a high-quality layout, as a freelancer, it is essential for me to establish clear terms to protect my work and ensure fair payment. Sharing the completed layout on a free hosting platform without receiving full payment beforehand poses risks such as the potential theft of my work.
To address this concern, I propose an alternative approach. Once you provide the payment for the entire layout, I can share screenshots or watermarked versions of the pages for your review. This way, you can still verify the design while protecting my work until the final transaction is complete.
I want to assure you that I am committed to delivering a satisfactory final product, and I am more than willing to make any necessary revisions or adjustments once the payment has been made.
I hope you understand the importance of this precautionary measure and the need for both parties to work together to ensure a fair and successful collaboration. I value our working relationship and look forward to finding a solution that works for both of us.
Please let me know your thoughts on this matter. I'm open to discussing any alternative arrangements that you may propose.
Thank you for your understanding,
[Your Name]"
This message communicates your concerns while offering an alternative approach that protects your work. It also shows professionalism and willingness to work together to find a solution. Remember to adapt the message accordingly and maintain open communication with the client to resolve any issues.
Is the customer a serious individual or anonymous? How was the negotiation process with them conducted? Are there instances where you work without prepayment? It would have been necessary to arrange everything in advance!
If the customer is genuinely serious and there is still a considerable number of pages to be created, plus no mention of prepayment, one approach is to show them the layout on your hosting without revealing the source code. Then, request an advance payment for the work that has already been completed.
When dealing with an anonymous customer, it is advisable not to showcase all three pages at once. Instead, show them one page and attempt to secure an advance payment, even if it's just for the work on that particular page.
If the customer remains adamant about not making an advance payment, even after reviewing the layout and experiencing its functionality, you need to consider whether taking the risk is worth it. On one hand, they may have a point if prepayment wasn't agreed upon beforehand. On the other hand, there is a possibility that they might evade payment and abscond with the final product.
Option 1. Protecting the source
If you have extensive custom JS in your layout, you can utilize aaencoder for source protection. Unfortunately, CSS and HTML cannot be encoded in the same way, but they can be minified (and CSS can obfuscate class names to make them unreadable). These techniques are typically employed with project builders. While not foolproof, they add an extra layer of complexity to the work, making it more difficult to steal.
There's also an option to upload content to an iframe immediately after the page loads via JS. This prevents the code from being visible through "showing the source code of the page." Additionally, periodically reloading the code without updating the iframe can further protect against copying attempts. However, this method can be disabled by browser settings or plugins like NoScript, and it's considered an obvious perversion. It may also be ineffective against specialized software.
Option 2. Skype videos
Another approach is to show the customer a video by sharing your screen in the browser. This allows you to demonstrate the code and check specific sections upon request. In my opinion, if someone has no intention to cheat, they shouldn't hesitate to agree to this method. It's no different from a demonstration on a hosting platform, except with direct access to the code.
Option 3. Taking a firm stance or trusting, which comes with risks