Validating an idea: "Glassdoor for freelance clients" — would you use it?
Quick context: I'm a solo founder. Over the last few weeks I've been talking to freelance developers about one specific pain — getting burned by bad clients (non-payment, scope-creep, ghosting).
The insight I keep coming back to: every platform vets the freelancer for the client. Nobody vets the client for the freelancer. The information asymmetry runs entirely one way.
So I'm building Vettly — search a client before you accept the project, see reports from other freelancers, get an AI read on their brief.
I've had a few freelancers tell me they'd pay for it. Now I'm testing that signal more broadly before I build the MVP.
Landing page / waitlist: https://vettly-waitlist.netlify.app
Two things I'd love feedback on from this community:
Is the "vet the client" framing immediately clear, or did it take a second?
If you freelance — would you actually pay for this, or is it a "nice to have"?
Brutal honesty welcome. That's why I'm here.
The "vet the client" framing is immediately clear. "Glassdoor for freelance clients" is one of those rare analogies that lands in two seconds and doesn't need explaining. Good sign.
The harder question is whether it's a business or a feature.
Two structural challenges worth pressure-testing:
The cold-start problem is brutal for this category. The product is only valuable when it has enough reports on enough clients to be useful. Freelancer searches a client name, gets zero results, leaves and doesn't come back. You need density before the product works, but you need the product working to get density. Every review marketplace hits this. Glassdoor solved it by scraping public company data first, then layering reviews on top. What's your equivalent? Without a solve for day-one empty results, the waitlist converts to signups that churn immediately.
Willingness to pay is the real test. Freelancers will say "I'd pay for this" in a conversation because it sounds obviously useful. But the check-a-client moment happens before a project starts, which is infrequent (maybe monthly for active freelancers), and the pain of bad clients is retrospective ("I got burned last time") not acute in the moment of deciding. That's a tough combination for subscription pricing. It might be a one-time-check model, or it might be a feature inside a broader freelance tool, not a standalone product.
The "AI read on their brief" piece is interesting but worth separating. Vetting a client (reputation data from other freelancers) and analyzing a brief (AI red-flag detection) are two different products. The first needs a network. The second works on day one with zero users. Worth considering whether the AI brief analysis is actually the MVP and the review network is the long-term vision.
Who are the freelancers telling you they'd pay? Platform freelancers (Upwork/Fiverr) or independent? Platform freelancers already have some client rating data. Independent freelancers have zero, which makes the pain sharper but the cold-start harder.
If you want to pressure-test which of these angles to lead with, that's what HiveMind is built for: https://hivemind.myosin.xyz
This is some of the most useful feedback I've gotten on this — thank you for taking the time.
The cold-start problem is the one I keep circling back to, and you named it perfectly: empty results on day one kill retention before the network exists. I don't have my "Glassdoor seeded public company data first" equivalent yet, and that's exactly the gap I need to solve before the review network means anything.
The split you and another commenter both pointed to is making me rethink the whole thing: AI brief analysis works on day one with zero users, while the review network needs density to matter. I'm starting to think the brief analyzer might be the actual MVP, and the review network the long-term vision layered on top.
On willingness to pay — you're right that it's the real test, and that the "check a client" moment is infrequent and the pain is retrospective. That's the hardest part of the pricing puzzle and I don't have it solved. Chewing on whether it's a per-check model vs. subscription.
Genuinely grateful for this. Mind if I follow up if I go deeper on the brief-analysis angle?
Of course, follow up anytime.
Since you're leaning toward the brief analyzer as the MVP, one thing worth getting ahead of: it solves the cold-start problem but it also changes who you're competing with. A standalone "AI reads your client's brief and flags red flags" is closer to a ChatGPT prompt than a defensible product. Any freelancer can paste a brief into Claude and ask "what are the red flags here." So the brief analyzer gets you to day-one usefulness, but you need a reason it's better than the free alternative everyone already has.
The defensible version: the brief analyzer gets sharper because of the review network, not instead of it. "This brief has the same vague-scope language that preceded 12 non-payment reports in our database" is something ChatGPT can't do. That ties the two pieces together — the analyzer is the day-one hook, the network is what makes the analysis progressively better and uncopyable. The brief analysis is the wedge, the pattern library behind it is the moat.
So the sequencing might be: launch the brief analyzer to get users and solve cold-start, but design it from day one to feed and draw from the review data, so every analysis makes the next one better. That way you're not building two separate products, you're building one product where the free-on-day-one piece compounds into the defensible piece.
On pricing — per-check probably beats subscription for exactly the reason you named. The pain is infrequent and retrospective. People won't hold a subscription for a monthly-at-most check. But they'll pay $5-10 in the moment when they're about to sign a sketchy $5K contract and want a gut-check. Price it as insurance, not a tool. "Spend $9 before you spend three weeks on a client who might ghost you" is easy math.
The willingness-to-pay test that actually means something: put a real price on the waitlist page and see who pre-commits, not who signs up free. Free waitlist signups tell you the idea sounds good. A pre-order or deposit tells you the pain is real.
Reading this, I found myself less interested in whether freelancers would pay for it and more interested in what they believe they're paying for.
Protection from bad clients.
Faster trust decisions.
Better client selection.
Leverage in negotiations.
Those can all sound similar while pointing to very different products.
The reason that stood out to me is that a lot of validation conversations can look positive before that distinction is actually resolved.
This reframe is sharp — "less whether they'd pay, more what they think they're paying for." That distinction hadn't fully landed for me until you wrote it.
You're right that protection from bad clients, faster trust decisions, better client selection, and negotiation leverage all sound similar but point to different products. And that validation conversations feel positive precisely because that ambiguity hasn't been forced to resolve yet.
That's probably the next thing I need to pressure-test: not "would you use this" but "which of these jobs are you actually hiring it for." Thank you — this gave me a clearer question to go ask.
Glad it was useful.
I think the interesting part now is deciding which of those "jobs" deserves to become the lens for future product decisions. Happy to explain what I mean over email if that's useful.
What's the best email to reach you on?