PLATFORM · SALESFORCE

They invented per-seat.
Now they rent you AI on top of it.

Sales Cloud, Service Cloud, Marketing Cloud, Agentforce — per-seat licences compounding on every hire, with an AI tier priced beside each one. You do not have to start by cancelling any of it.

  • You own the code from commit one
  • No per-seat licence
  • Runs where you choose
Explore Salesforce AgentforceSalesforce's own AI builder layer — Agentforce and the Atlas Reasoning Engine
The estatereplaceable
  • Sales CloudPipeline workflows
  • Service CloudService workflows
  • Marketing CloudMarketing pipelines
  • Commerce CloudCommerce workflows
  • Data Cloud · Customer 360Customer data model
  • Flow · MuleSoftAudit-trail ledger
Sales · Service · Marketing · Commerce · Data Cloudyours on commit one
Why this domain exists

You are not buying software.
You are renting access to your own customers.

Not the Clouds — their commercial shape: priced per seat, stacked with an AI tier per Cloud, and holding the customer schema in the vendor's own data model.

Salesforce is the company that invented the per-seat SaaS relationship. Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud, Data Cloud and now Agentforce — sold as a customer-360 platform, licensed as a per-seat stack with AI add-ons priced separately on top. The customer schema lives in Salesforce's own data model, so the exit conversation and the data conversation are the same conversation.

Priced per seat

Sales Cloud, Service Cloud, Marketing Cloud and Commerce Cloud licence per user. Hiring grows the bill whether or not anyone uses more software.

Stacked with an AI tier

Sales Cloud Einstein, Service Cloud Einstein, Einstein Personalization and Agentforce price separately on top of the seat you already bought. Each is small alone; together they are their own budget line.

Holding the customer schema

Accounts, contacts and interaction history sit in Salesforce's data model, reachable through Data Cloud on Salesforce's terms. That asymmetry is leverage, and it does not sit on your side of the table.

Seat meterSalesforce's published pricing model. The meter is theirs, not ours.
Per seat, per CloudEach Cloud meters the same person again.
  • A rep joins — one seat, on every Cloud they touch
  • Sales, Service, Marketing and Commerce licence separately
  • Einstein and Agentforce price on top of the seat already bought
STAGE 01Ignite

Start with an agent that bills on nothing.

New agents beside the Clouds you already run. Nothing retired, nothing migrated — every seat keeps doing what it does today. Confidence starts here, in weeks.

Sales-coaching agent

Call summaries, next-best-action and deal-risk scoring drafted by agents running on your own win criteria and your own sales playbook, writing back only when a rep approves.

Runs beside Sales Cloud and Sales Cloud Einstein

Service triage agent

Case triage, draft response and escalation routing handled by agents that read your knowledge base and hand the work to a rep for sign-off.

Runs beside Service Cloud and Digital Engagement

Campaign agents

Segmentation, content drafting and channel orchestration by agents that read your customer data and hand the work to marketing for approval.

Runs beside Marketing Cloud Engagement and Account Engagement (Pardot)

Audit-trail ledger

Every customer interaction, every model call, every workflow change logged and readable. GDPR and PDPL evidence gathering becomes continuous instead of quarterly.

Runs beside Salesforce Flow and your GDPR/PDPL reporting

STAGE 02Reforge

The estate you already own, rebuilt AI-native.

The Flows your admins wrote, the integrations your engineers maintain, the forecast model they tune, the customer schema under it all. Same logic, modern substrate — every line yours.

IN — what you run today
  • Sales Cloud
  • Service Cloud
  • Marketing Cloud
  • Commerce Cloud
  • Data Cloud · Customer 360
  • Flow · MuleSoft
SAIF

the saasinator AI Factory — glass-walled delivery

  • Brief
  • Build
  • Evals
  • Deploy
  • Transfer
OUT — what you own afterwards
  • Pipeline workflows
  • Service workflows
  • Marketing pipelines
  • Commerce workflows
  • Customer data model
  • Audit-trail ledger

Product names are Salesforce's own. What comes out the other side is yours — source, models, data and pipeline, transferred on commit one.

Flow and integration rebuild

Process automation and the integrations into non-Salesforce systems rebuilt as typed contracts on infrastructure you operate. Downstream systems see the same shape; the per-integration licence does not follow.

Salesforce Flow · MuleSoft

Forecast and pipeline model rebuild

Forecast hygiene, slip analysis and pipeline coverage rebuilt against your own model, so sales ops read a pipeline rather than a licensed dashboard.

Tableau CRM (Einstein Analytics)

Customer data model rebuild

The customer schema, identity stitching and audience activation rebuilt on your own warehouse, so reading your own records is not a per-record event.

Salesforce Data Cloud · Customer 360 · Genie

Coverage

Five customer teams. The same pattern in each.

Wherever the seat count is highest is where the licence bites hardest. These are the areas we rebuild, and what sits inside each.

Sales
  • Sales Cloud replacement — lead, opportunity, quote, contract
  • Sales-coaching agents on your own win criteria
  • Forecast hygiene, slip analysis and pipeline coverage on your own model
Service
  • Service Cloud replacement — case routing, knowledge, omnichannel
  • Triage, draft response and escalation routing as agents your team operates
  • Field service — dispatch, scheduling and mobile workforce without a per-technician licence
Marketing
  • Marketing Cloud replacement — email, SMS, journey orchestration
  • Campaign agents reading your customer data, writing back on approval
  • Loyalty tiering and redemption rules as data, not vendor admin panels
Commerce
  • Commerce Cloud replacement — storefront, cart and order management for B2B and B2C
  • Recommendation, content ranking and basket-level offers on your own warehouse
  • Renewal management, dunning and subscription billing as one pipeline
Platform & IT
  • Flow and integration — typed contracts on infrastructure you operate
  • Agentic workflows on your data, your prompts and your eval suite
  • Audit-trail platform — continuous evidence, not quarterly gathering
Functional areas this domain touches
STAGE 03Liberate

The Clouds come out. The workflows stay — as software you own.

Liberation is earned, not sold. By the time we replace a Cloud, you have watched us build. Hiring stops being a licensing event; your customer data stops being their schema.

The licence ledger

Illustrative

The commercial shape of a Salesforce estate, as a buyer reads it

Basis of charge
Per user, per Cloud. Coverage is additive; so is the invoice.
AI tier
Each assistant and each reasoning tier prices separately on top of the seat already bought.
Discount condition
Conditional on term length and on committing across Clouds together rather than one at a time.
On exit
The customer schema, the Flows and the integrations sit inside the vendor's platform — not in an asset you hold.
Cost of staying————

Shape only — the direction of travel, not a quantity. Your own curve comes from your own renewal schedule and your own headcount plan.

Illustrative. This is our reading of a commercial pattern, not a quotation from any Salesforce agreement — no contract text, no clause references, no figures.

Sales Cloud replacement

Pipeline, opportunity, quote and forecast rebuilt as agentic pipelines on your data, retired into only once the replacement is carrying the work.

Sales Cloud · Sales Cloud Einstein · Revenue Cloud · CPQ · Billing

Service Cloud replacement

Case routing, knowledge management, omnichannel and field service rebuilt without a premium seat tier standing between your team and the workflow.

Service Cloud · Service Cloud Einstein · Field Service Lightning

Marketing Cloud replacement

Journey orchestration, content personalisation and lifecycle communication rebuilt on your own data, so reaching your customers is not priced per contact.

Marketing Cloud Engagement · Personalization · Account Engagement (Pardot) · Loyalty Management Cloud

Commerce Cloud replacement

Storefront, cart, order management and subscription billing rebuilt as one pipeline your commerce team operates.

Commerce Cloud · Order Management

How it is built

Glass-walled from brief to transfer. Nothing behind a black box.

SAIF is our delivery method and it runs in the open. You watch the build as it happens, read the evals that gate every release, and keep every artefact — including the ones that record what did not work.

  1. 01

    Brief

    One workflow, scoped against your own data and your own renewal position.

  2. 02

    Build

    Agentic delivery against your systems, visible while it runs.

  3. 03

    Evals

    Every release gated on tests you can read and re-run yourself.

  4. 04

    Deploy

    Into infrastructure you control, alongside the system it stands beside.

  5. 05

    Transfer

    Your team runs it. We do not leave until they can.

You own it from commit one

Source, models, prompts, evals and pipeline. Not a licence to use what we built — the asset itself.

Two weeks to a working build

A working build against your own systems in two weeks. Fixed scope, fixed bill.

It runs beside the Salesforce Cloud first

Nothing is retired on faith. The Salesforce Cloud goes when the replacement is carrying the work.

Proof

Not a claim. A delivered platform.

Our commitment

Every engagement starts with a scoped working build against your own systems. If it doesn't convince you, you pay nothing — and you keep the code either way.

The ask

Bring one Cloud and your seat count.

Ten working days. Which capability to build first, what the per-seat line costs as you hire, and what the replacement costs to build. You keep the analysis.

Fixed feeTen working daysNo commitment beyond the diagnostic