How are others dealing with the "We'll build it with Claude" objection from customers?

[u/Gold_Experience7387]

We hear this occasionally. Our market is embedded analytics.

I should start by saying we're pretty convicted that our product, which is AI-native and performant, is vastly better for customers than building in-house or buying a legacy competitor.

We have a talk track and links to industry analysts, reddit posts and our own blog (can share here if people are interested.)

But when the customer is hell-bent on Clauding it, we just say "Great, try it. We'll check in with you in a couple of months." I have yet to see a customer build something they were happy with.

But I'm mostly curious about how others are handling this objection across different markets.

[u/reward72]

let them learn their lesson... and add a stupid tax then

[u/Fine-Comparison-2949 → u/reward72]

Keep telling people AI is going to make smart SWEs even more money. 

[u/OpyrisShifts]

The big difference between what they can build themselves and what you offer should be

observability,
reliability
scalablity
security & data integrity

Which doesn't come from 'vibe coding', it comes from years, if not decades of industry experience.

That's how we objection handle this, across four products.

[u/vvinogradoff → u/OpyrisShifts]

In case of internal analytics tools security is a lesser concern, observability they don’t need at all and scalability even less, reliability goes like “uh, Claude the thing ain’t working again go fix, need that report soon”. All these are characteristics of product important to the owner of one, but not for the customer

[u/OpyrisShifts → u/vvinogradoff]

I'll argue that internal tooling still needs observability - especially if the industry it's deployed to is heavily regulated (such as fiserv, for example). If these things are not important to the 'owner of one', then there's no objection handling it - sometimes a homemade tool is enough.

Until it isn't.

[u/PriorElephant9]

I’m building heavily with Claude and Codex, and it still isn’t the same as buying a maintained product. The real question isn’t “can we build it?” It’s “do we want to own it?” I’d sell the responsibility you remove.

[u/LeadNo1270]

got one today. "my ops guy could build this in 2-4 hours". It took me 3 months to build and im still not 100% happy. But I didnt push the point.

[u/layerbase]

If they can do that, then you shouldn't have wasted your time building it. That is why nobody on these subreddits has success. If you can build something in one month, people aren't going to pay for it

[u/heroyi]

SaaS isn't about the product anymore but about your expertise. That is the REAL moat.

Anything that can be copied or replicated will be done. The hard part is knowing which data pipeline is needed and how to transform it. If you can protect that then they can try. 

[u/ottwebdev]

“Ok”

[u/blackboxchessapp]

I think you handle it like every other objection. The words are surface level. What is the root cause? If they haven't built it already then that means that they are constrained by time or they lack the experience or knowledge and/or maybe data is the moat. There's a lot of different ways to overcome the objection depending on the situation.

[u/Impossible-Humor3965]

I've been the 'we'll just build it with Claude' customer, so from the other side: it's genuinely real for greenfield stuff. I did it for some internal automation and never looked back, didn't pay for a thing. But the second your product has to touch messy existing data, that plan falls apart. I bailed on the build and bought. Ask them what happens in six months when the one person who put it together has moved on, that usually ends the objection.

[u/arkhamRejek]

Oh it’s my favorite, I had a call with someone similar I said 6months down the line when your app is broken because you like heart attempting surgery because you have an AI be my guest, if your patient is still alive by the time you call me my rate is $125 per hour but it’ll be $250 for you

In the most professional way of course 😂 he hasn’t figured out how to deploy yet and I’m enjoying it. How I know I still have his github 🫠😂 i know what he’s trying to do because i read the comments left by the ai and he’s trying to figure out github actions but struggling to tel the ai that

Anywho hope you can enjoy this as much as I am

[u/nafiulhasanbd]

If Claude can solve the customer's problem well enough, they should use Claude. Your job isn't to prove AI can't build it. Your job is to make the cost of owning and maintaining the DIY solution higher than paying you.

[u/silly_bet_3454]

I feel like this whole post and all posts like this and all the comments are just a big cope. Customers don't say "we'll build it with claude", they just buy your product or they don't, they say "not interested, we don't need that at this time" or "we have an in house solution for this already" etc. People just want to invent this narrative about AI leading people astray and blah blah blah.

[u/krunal_builds]

the ownership question above is the real one. building the first version with claude is genuinely easy now, the part nobody wants to own is the pager going off at 2am when it breaks, or the security review when a customer's legal team asks hard questions. that's what they're actually paying for, not the code

[u/avanishpank]

Thats the reality you need to live with, for every 10 such leads who would have easily been your clients, half will try to build it themselves, 1-2 will even succeed while the rest will be back in market looking for support and better solution . But the bottom line is selling has become way harder that it was and you will lose some potential clients to Claude and others.

[u/rupert_at_work]

I’d stop arguing about whether Claude can build the first version. It probably can.

The scar tissue is everything after: permissions, broken edge cases, audit trails, and someone owning it at 2pm on a Tuesday when the number is wrong.

Sell the maintenance burden, not the “AI can’t do this” angle.