3 weeks validating a client vetting tool for freelancers — here's what I've learned

What was the biggest lesson or surprise you discovered during the validation process?

Talking to 50+ freelancers in 3 weeks is genuinely impressive validation work. Most founders skip this step entirely.
One pattern I've noticed building in the same space: the pain freelancers describe in interviews often isn't the same pain that makes them actually open their wallet. "Client vetting" sounds like a problem until you realize most freelancers would rather take the risk than slow down the sales process.
What was the most surprising thing you heard across those 50 conversations — something you didn't expect going in?

Three signals from my notebook, back when I was freelancing in 2023 before going indie:

1. They ask for a "quick call" before any written brief. Friction-reduction at step 1 always becomes scope creep at step 8.

2. They negotiate price before the scope is defined. Means the number is anchored to their budget, not to your work.

3. Different people on their side reply from different addresses with slightly different versions of the same request. No single decision-maker, and "we" will mean "whoever shouts loudest" three weeks in.

The thread tying all three: information asymmetry that favors them. Your vetting layer feels most useful at the proposal stage, not the contract stage — that's where the warning signs are still recoverable.

my #1 nightmare signal is when they try to negotiate the deposit or upfront milestone payment.if a client starts making excuses about why they can't pay a standard 50% deposit before the github repo setup or coding starts, they are 100% going to ghost you during the final handoff or drag out the payments for months.another massive red flag is trying to move communication off a structured channel into frantic midnight whatsapp or telegram pings before the contract is even signed. talking to 50+ devs across dev.to and reddit is a solid way to validate this. there's seriously zero tooling out there to track shady client histories right now.

This is a real pain because freelancers usually only recognize the risk after the project has already cost them time, energy, or money.

The strongest angle here is not “client vetting” in a generic sense. It is pre-project risk detection. The product should help a freelancer see the hidden warning signs before they send the proposal, accept the call, or agree to the scope.

That could become very useful if you turn the common red flags into a simple decision layer: unclear scope, weak communication, budget mismatch, contract resistance, urgency pressure, and payment risk. Freelancers do not need another CRM. They need a quick “is this client likely to become expensive?” signal before committing.

The name will matter if you productize it. Keynition is okay as a builder/studio name, but for a serious freelancer risk product, Beryxa .com would carry the decision-intelligence side better. It feels more like a trusted screening layer than a small freelance utility.

The pain is strong. The trick is making it feel like protection before the project starts, not advice after the damage is done.