u/Spdload

I’ve had my company profile on Clutch for around 8 years.
Recently, I decided to purchase their “Verify My Company” service, which costs around $500/year.
Here’s where it gets interesting.
My company is clearly listed on Clutch as a Ukrainian company. During the verification/payment process, Ukraine is available as a country option.
There was no warning saying Ukrainian companies were not eligible.
No restriction.
No message saying verification was unavailable in Ukraine.
Nothing.
So I selected Ukraine, paid the $500, completed the required steps — and waited.
The verification badge never appeared.
I contacted Clutch support and asked what was happening.
Their response:
“Through the conflict area, we’re unable to verify Ukraine companies.”
Seriously?
There are three things here that I find extremely problematic.
1. You accepted my money for a service you apparently knew you could not provide.
If Clutch does not verify Ukrainian companies, why is Ukraine available during the purchase process?
Why can a Ukrainian company pay $500 for verification?
Why is there no warning before payment?
If a service is unavailable to an entire country, customers should know that before their credit card is charged — not after they contact support asking where the service they purchased is.
2. “We’re unable to verify Ukraine companies.”
Not my company specifically.
Not “we couldn’t verify certain documents.”
Not “we need additional information.”
Apparently, Ukrainian companies as a category cannot be verified.
Ukraine has thousands of legitimate technology companies operating internationally, paying taxes, signing contracts, employing people, and working with customers around the world.
What exactly makes a Ukrainian company inherently “unverifiable”?
And if there is a legitimate compliance reason, why isn’t it disclosed before purchase?
3. Calling Russia’s full-scale invasion of Ukraine a “conflict area.”
This one particularly surprised me.
Ukraine has been defending itself against Russia’s full-scale invasion since February 2022.
Reducing that to some vague “conflict area” language while simultaneously using it as justification to deny verification to Ukrainian businesses feels incredibly tone-deaf.
Ukrainian companies have spent years trying to keep operating, employing people, paying taxes, serving international clients, and maintaining their reputations while our country is being attacked.
And now apparently we can still pay Clutch for verification — we just can’t actually get verified.
I’ve been on Clutch for around eight years, which is why this was especially disappointing.
I’d genuinely like to hear from other Ukrainian founders:
Has anyone else paid Clutch for verification and then been told that Ukrainian companies cannot be verified?
And more broadly — am I missing something here, or is accepting payment for a service and only afterward telling the customer that their entire country is ineligible as absurd as it sounds? 

I saw this coming, but in a year or two. Regulators were always going to push for a way to trace AI-generated content.

What changes now? From what I’ve read, anything generated with Claude (text, images, code) now carries a detectable signature. For publishing, marketing and anything that ends up on a public platform, that's something worth considering. For code, however, that's not something concerning.

But the watermark doesn't mean Claude wrote everything, and no watermark doesn't mean it's human-written. 

So, my next question was – what’s the point then? Just for the regulators?

I run a B2B software company and also build my own B2C SaaS, so I've lived both sides of this.

In B2B, I assumed the quality of my services would be the main factor. But, in fact, trust and relationships drive more decisions than any sales pitch. Most of my clients are coming from people I've already worked with. We've kept clients for 7 years, and I don't think that they always chose us because we are the best ones out there (we're good ones, definitely, but that's not my point). I think they have been working with us for so long because they know we'll tell them the truth even when it's uncomfortable.

B2C is harder in a different way. The product has to do all the work because there's no relationship to fall back on. Getting people to actually come back is the real problem.

Anyone can build and launch a SaaS in a weekend.

That sounds like a good thing, but it isn't always. Here’s how the software landscape looks now (my observations only):

There appear to be more and more tools that look just polished enough to charge for. However, like 90% of these tools, they fall apart the moment you start actively using them. Then, it becomes obvious that the flows are unnatural and broken, some of the features do not work, and asking for a refund or at least support turns into a side quest. 

We are in a timeline full of founders who shipped before they finished building the baseline of their product (I’m not talking about MVP, that’s an entirely different thing).

So, yes, I don’t think that the fact that almost anyone can build a SaaS now is a problem. But I do think that the problem is that launching got easy before the quality bar did.

Users are getting burned, and burned users are harder to sell to. And the whole market now pays for that.

For me, it was pushing back on a deadline you know is unrealistic instead of agreeing and then missing it.

When I started SPDLoad, the interview was quite simple. I asked developers what frameworks they know and asked them to show me what they have built.

Skills were the filter and experience was the proof.

But that model no longer works for IT services because the half-life of a specific technology is shrinking every year. As a result, the developer who spent 3 years mastering one stack can be outpaced in 6 months by someone who adapts faster.

Here's what I look at now when hiring developers:

• How quickly does this person learn something they have never seen before?
• Do they already use AI as a core part of how they work?
• Can they move between client work and product thinking without losing context?

The answers to these questions tell me everything I need to know before making a final decision.

I've been running an IT services company for 13 years now, and most of the projects take us around a year or two. With some companies, I've been working for 4 years, but 7 years of collaboration is the biggest milestone so far. My company is still the one they call when something important needs to get done.

What keeps a relationship that long? Apart from the obvious stuff like the tech, the price, and the delivery quality (that's just the bare minimum to stay in the game) is that I have always been on the side of their business.

That sometimes means telling the client their idea is wrong (always a hard conversation for both of us) or that the feature they want will not solve the problem they have. Or that the budget they allocated is not realistic for the outcome they expect.

These are the things nobody likes hearing. But looking back, those were exactly the moments that made them trust us more. Maybe, because they saw that I really tried to protect their outcome rather than secure my invoice.

And, after 7 years of this collaboration, I've realized that the fastest way to lose a long term client is to always tell them what they want to hear.

I run a software development company and also build my own SaaS. The switch nearly broke my brain. Switching between them sort of broke something in my brain.

In services, the path is clear: a client comes with a vision, you help them bring it to life, and the relationship moves forward step by step. There's structure and a partner on the other side.

But in products, nobody is asking you to build anything. You just wake up one day and have to decide:

• What feature matters?
• Who needs this?
• Why would they pay?
• Is this a real problem or just my idea?

In services, I move fast because deadlines are external. When it comes to building my own product, the deadlines are less strict. So you can spend 6 months polishing something nobody wants.

For me, building is still the easy part. Selling a product and communicating its value is a completely different sport.

So, to all those service founders thinking about launching a product, just be ready to unlearn 80% of what made you successful. I wish someone had told me this before I started.

Google just announced Gemini 3.5 Flash, AI agents that search and make purchases on your behalf, and an official guide on optimizing websites for generative AI features. The "SEO is dead" conversation is loud again, I don't think its true, but what concerns me is that content will increasingly be written for machines to parse rather than people to read.

Did someone identify a real internal problem and AI was the answer? Or did it come from somewhere else, like a competitor shipped something or the board saw a headline and decided you need AI now too?

I feel like many AI initiatives are driven by external pressure. They feel they have to rather than want to. Both options are OK in my opinion; the results matter only. Just thinking about the motivation behind the decision.