Unwrapped

Legacy SaaS dossier · salesforce

Salesforce

Salesforce

CategoryCRMSales Cloud Enterprise, 25 seatsSite ↗

A contacts list, a pipeline, and a notes field, sold back to you with eighteen modules, four certifications, and a consultancy tier.

01 · Data

Data the SaaS sits on

Gmail / Outlook
Gmail / OutlookYours
Google Calendar
Google CalendarYours
LinkedIn (contacts)
LinkedIn (contacts)API
Stripe / billing
Stripe / billingAPI

Internal Build Score

0.72

Feasibility of a useful internal substitute for the actually-used 20% of this SaaS, built with Claude and your own data layer.

IBS = 0.25·U + 0.25·C + 0.20·D + 0.15·I + 0.15·Mthis record · 72%
  • U

    User adoption gap

    weight 0.250.88

    How much licensed surface area sits idle.

  • C

    Core simplicity

    weight 0.250.85

    How small the actually-used 20% is when re-implemented honestly.

  • D

    Data portability

    weight 0.200.55

    How clean the exit is, exports, formats, audit lock.

  • I

    Integration burden (inverse)

    weight 0.150.40

    How few external systems must keep working through the SaaS.

  • M

    Moat erosion

    weight 0.150.80

    How much the original differentiator has been commoditised by LLMs + cheap infra.

Editorial heuristic. Not investment advice, not a procurement recommendation.

03 · Feature usage

Commonly used vs. rarely touched

Commonly used

05

  • Accounts + contacts list
  • Deal pipeline with stages
  • Activity notes per record
  • Forecast roll-up by rep
  • Email + calendar capture

Rarely touched

08

  • Lightning App Builder pages no one ships
  • Process Builder + Flow + Apex, three half-overlapping automation engines
  • Einstein scoring nobody trusts
  • Tableau CRM bolted on after MuleSoft
  • Knowledge / Communities / Experience Cloud
  • Salesforce Inbox + Sales Engagement + Sales Dialer SKUs
  • Validation rules a $400/hr admin maintains
  • Sandbox / change-set release process

Internal build

Build it yourself

01 · Stack & flow

Postgres
Postgres
Next.js
Next.js
Claude API
Claude API
Resend
Resend
Clerk
Clerk

Internal build map

Data in

Inbound email
Calendar
Accounts table

Agent layer

Note extractor
Weekly digest

Logic

route to deal
schema validate
upsert row
risk flag → Slack

Outputs

Updated deal row
Weekly digest
Forecast view
Build time
6 weeks
Run cost
$8/seat·mo
vs. SaaS
$180K / yr

Build outline

  1. Postgres schema: accounts, contacts, deals, notes
  2. Email + calendar inbox sync (Nylas / Postmark MX)
  3. Claude classifies + extracts to deal fields
  4. Weekly pipeline digest via Resend
  5. Forecast roll-up SQL view, no AI required

02 · Build it

Paste into Cursor or Claude Code in an empty repo. It scaffolds the working core, with the AI step embedded.

Build prompt · Salesforce

// Build: internal CRM (Salesforce replacement) # Paste into Cursor or Claude Code in an empty repo. Build an internal CRM covering the part of Salesforce a sales team actually uses: accounts, contacts, a deal pipeline, and notes. Ship a working v1 deployable to Vercel. Stack: Next.js (App Router) + Postgres (Drizzle) + Clerk auth + Resend. Data model: - accounts(id, name, domain, owner_id) - contacts(id, account_id, name, email, title) - deals(id, account_id, name, stage, amount_usd, close_date, owner_id, next_step, risk) - notes(id, deal_id, author_id, body, created_at) - stage enum: lead, qualified, proposal, won, lost Build, in order: 1. CRUD + a board view of deals by stage (drag to change stage). 2. Email capture: an inbound address (Postmark) appends notes to the matching deal by sender domain. 3. AI assist, on each new note call Claude and write the result back: """ Update one deal from a single note. Return JSON { next_step(<=8 words), stage_change("none"|stage), amount_signal(usd|null), close_date(YYYY-MM-DD|null), risk(bool), evidence(quote) }. Extract only what the note supports. Never invent values. """ 4. A weekly pipeline digest emailed per rep (Claude summarises deltas). Skip: Flow/Apex, Einstein, the page builder, anything not above. Done when: a rep adds a deal, forwards an email to it, and the fields update from the note with no manual typing.

03 · Result

Spoke w/ Acme CFO, needs $400k by EOQ, board meeting Sept 22.
deal:acme-q3

next_step: send EOQ-ready quote · amount_signal: 400000 · close_date: 2025-09-22