As an AI and Software Engineer, I often see clients ask for a "quick coding test" or a "sample design" before they sign a contract. While vetting is normal, asking for free custom work is a major red flag.
1. The Professional Standard
Professionals don't work for free. Your portfolio, LinkedIn, and past case studies should be your "test." If a client needs more proof, suggest a Paid Discovery Phase or a small, paid trial project.
2. Setting Boundaries
If you do agree to a test, ensure it is:
- Time-Capped: No more than 2 hours of effort.
- Non-Commercial: The client cannot use the output for their business without paying your full invoice.
3. Protecting Your Identity
Sometimes, "Test Tasks" are just a ruse to harvest data or IDs.
🛑 The Problem: The Privacy Nightmare of Online Resizers
Have you ever applied for a Visa or a Government Exam? The final step is always a nightmare: "Upload a photo exactly 413x531 pixels, under 200KB." Most people Google a solution, click the first link, and blindly upload their highly sensitive personal IDs, signatures, and face photos to a random backend server. In the age of AI scraping and data theft, this is incredibly dangerous.
💡 The Solution: DocuFix
I built DocuFix to completely flip the paradigm. DocuFix is a Zero-Upload Application. Utilizing WebAssembly (WASM), 100% of the image processing happens on your local device.
Frequently Asked Questions (FAQ)
Can I watermark my test work?
Yes. If you are a designer, send low-resolution, watermarked files. If you are a developer, show a video demo of the code running locally rather than sharing the source files before the invoice is settled.
What if the client is a 'Big Brand'?
Big brands have the budget to pay for your time. If they refuse to pay for a test, they are likely to be difficult payers later on.
Is a 'Trial Period' better?
Yes. A 1-week trial period with a signed contract and a 50% deposit is the safest way to "test" a relationship.