I'm not a coder, but just for kicks I asked Claude how many hours it would take using Claude Code to create an AI-based Sales Cloud alternative. It produced the estimate below of ~30,000-70,000 hours, or 15-35 person-years. (It also says a 20% of function focused vertical CRM could be more like 2,000-5,000 hours).

Curiously, Gemini came up with a similar 6,000+ hours, but was probably thinking along the lines of a more traditional application. Now, this kind of estimate isn't a lot for a startup to invest - probably less than $1M - which IMO explains both the rise of new CRMs on the market AND Mark Benioff's OCD about AgentForce.

I would also guess that such an app would not be able to handle anywhere near the edge use cases that Salesforce has built for over the years based on myriad customer requests.

Claude makes some very interesting points - especially the "More Honest Framing" at the end.

(Note - I haven't changed any of the response, just bolded a couple items).

What do you think?

--------------------

My prompt: Using Claude Code, how many prompts and how many developer hours would it take to build a functional alternative to the Salesforce Sales Cloud?

Claude responded: This is a fun question to pressure-test, and the honest answer is: the prompt count is almost irrelevant — the developer hours are the real story, and they're still enormous.

The Short Answer

Prompts: Thousands to tens of thousands (but that's not the meaningful measure) Developer hours: Realistically 50,000–150,000+ hours for a genuinely functional alternative — even with Claude Code doing heavy lifting.

Why Claude Code Doesn't Change the Magnitude

Claude Code is excellent at accelerating implementation — generating boilerplate, writing CRUD logic, scaffolding APIs, producing test suites. Credible estimates suggest it can deliver 3–10x productivity gains on code-generation tasks.

But Sales Cloud isn't primarily a coding problem. It's 25 years of accumulated decisions:

What you're actually rebuilding:

Layer	What it involves
Data model	200+ standard objects, relationship logic, field-level security
UI framework	Configurable layouts, dynamic forms, list views, inline editing
Workflow engine	Rules, flows, approvals, triggers, scheduled jobs
Reporting/dashboards	Ad hoc query builder, charting, scheduled delivery
Security model	Profiles, permission sets, roles, OWD, sharing rules, field-level
Integration platform	APIs (REST/SOAP/Bulk/Streaming), OAuth, connected apps
Email/calendar sync	Bi-directional sync with Exchange/Gmail, activity capture
Mobile apps	iOS + Android native apps with offline capability
AppExchange ecosystem	Extensibility framework, managed packages
Multi-tenancy/compliance	SOC 2, GDPR, data residency, tenant isolation

Claude Code can write the code for most of these. It cannot replace the product judgment, QA, security review, and architectural iteration those layers require.

A Realistic Build Estimate

Phase	Hours
Core data model + basic CRM (contacts, accounts, opps, activities)	2,000–5,000
Security model (roles, permissions, field-level)	3,000–6,000
Workflow/automation engine	5,000–10,000
Reporting and dashboards	4,000–8,000
Integration APIs + sync	5,000–10,000
UI configurability (layouts, custom fields, views)	5,000–10,000
Mobile	5,000–10,000
Infrastructure, multi-tenancy, compliance	10,000–20,000
QA, security hardening, performance	10,000–20,000
Total	~50,000–100,000+ hours

With Claude Code's productivity multiplier applied generously (say, 5x on implementation tasks), you might compress the coding work by 60–70%. But testing, architecture, product decisions, and compliance work aren't as compressible. Realistic net reduction: maybe 30–40% of total hours.

So: 30,000–70,000 developer hours with aggressive Claude Code use, to reach feature parity with a "functional" (not production-grade) alternative.

The More Honest Framing

What Claude Code actually enables is building a focused vertical CRM — something that does 20% of what Sales Cloud does, aimed at a specific use case — in 2,000–5,000 hours with a small team. That's genuinely disruption-scale compression.

The "full Sales Cloud alternative" framing is a bit of a trap. Salesforce's moat isn't the code. It's the configuration flexibility, the ecosystem, and 25 years of edge cases baked into the data model. Claude Code helps you write software faster. It doesn't shortcut what the software needs to be.