Enterprise DNA

Instead of Salesforce Manufacturing Cloud

Stop renting Salesforce Manufacturing Cloud. Own your sales agreement desk.

We build your version around the products you supply and the commitments your customers make. We bring your Salesforce agreement records across and run the system for you.

Salesforce lists Manufacturing Cloud Sales Core at US$275 per user per month, billed annually. That is US$3,300 per user per year.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

An industry platform around your supply agreements

Salesforce sells a broad manufacturing platform. Compare the agreement work you use with the platform you pay for. Your quoted contract determines your actual bill.

group

Licences for each user

Sales Core lists US$275 per user per month. Adding people adds licences.

calendar_month

An annual commitment

The published monthly rate is billed annually, equivalent to US$3,300 per user for the year.

description

Sales agreement management

The manufacturing feature comparison includes agreement management and its industry records.

bar_chart

Forecasting and account targets

Advanced forecasting and account manager targets sit in the broader product comparison.

layers

A wider platform bundle

The current Sales Core offer includes collaboration, analytics and a support plan alongside manufacturing records.

settings

Edition choices and additions

The pricing page lists Core and Max editions and features available for separate purchase. Check which ones your business actually needs.

The desk you own

Make the weekly supply conversation specific

Commitments

Read the agreement by product and period

See the customer promise alongside the actual quantity recorded for that same period.

  • check Customer, product and owner in one record
  • check A start and end date for each commitment period
  • check Quantities labelled with their product unit
  • check Original imported fields retained with their source record

Reconciliation

Find shortfalls and check the evidence

A low actual quantity means little if the order figures have not been checked. Show both before acting.

  • check Closed periods below the planned quantity
  • check A dated actuals snapshot for each period
  • check Old or missing actuals dates called out
  • check Separate currency totals without an assumed exchange rate

Renewals

Prepare the next agreement conversation

Bring the term, performance and unfinished follow-ups into the renewal brief.

  • check Agreements ending within the next 60 days
  • check Named owners for renewal work
  • check Overdue follow-ups and their due dates
  • check Draft performance statements with your business name

Your rules

Keep the reason behind each change

Ask for evidence checks and reports that match the way your supply desk works.

  • check Before-and-after records for local quantity changes
  • check Evidence references when terms or actuals change
  • check A weekly brief joining shortfalls, renewals and overdue work
  • check Custom fields, review rules and read-only reports added to your version

Make it yours

Design your own Salesforce Manufacturing Cloud replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Manufacturing Cloud. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Manufacturing Cloud replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Manufacturing Cloud data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Sales Agreements for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Sales Agreements for Claude Code

Connected to your own database

Which customer commitments are behind, and are the actuals current?

Harbour Components

Reement pr
Harbour annual supply
Oduct en
Filter housing
Ds_on un
2026-09-14
It pl
pieces
Anned ac
1000.000
Tual ga
650.000
P cu
350.000
Rrency ga
NZD
P_value ac
4375.00
Tuals_freshness
stale

Harbour Components

Reement pr
Harbour annual supply
Oduct en
Filter housing
Ds_on un
2026-10-14
It pl
pieces
Anned ac
1200.000
Tual ga
1000.000
P cu
200.000
Rrency ga
NZD
P_value ac
2500.00
Tuals_freshness
current

Ask it anything

Ten questions this version answers today

These answers come from the working demo. They show the agreement desk you can own, without claiming that Salesforce cannot answer them with configuration.

chat_bubble Which closed periods are below the agreed quantity?
chat_bubble Which shortfalls rely on old actuals?
chat_bubble What quantities are committed in upcoming periods?
chat_bubble Which agreements need renewal work in the next 60 days?
chat_bubble Which customer commitments have the largest overdue value in each currency?
chat_bubble Which follow-ups are overdue and who owns them?
chat_bubble Which active agreements lack evidence of their terms?
chat_bubble What changed in a schedule and what evidence was recorded?
chat_bubble What is the complete history we imported for this agreement?
chat_bubble What needs a decision in the weekly supply review?

Switching

How to switch from Salesforce Manufacturing Cloud

A move involves exporting related agreement records, mapping them to your own fields and rules, checking the imported data, and reconciling both systems before you switch.

  1. 1

    Export the related records

    Use Salesforce Data Loader, which Salesforce documents for exports, or the export path your account allows, usually CSV or Excel. Check with Salesforce Manufacturing Cloud if you are unsure what your account can export. Bring out the five related record types the importer supports: accounts, products, agreement terms, product lines and schedules. Keep the exports together so the references between them can be checked.

  2. 2

    Load a test run

    Load the five exports into the new system and run the import preview first. The preview lets you check the records before you make the import. The free version reads the five related exports together, keeps their original fields with each record, and matches repeat imports using stable source IDs. Use the preview to confirm the records look right before completing the import.

  3. 3

    Review and fix import issues

    Check the preview and import results for broken references or rejected records. A broken reference rolls back the whole import, so fix the source records or exports and run the preview again. Compare agreement terms, products, product lines and schedules against Salesforce. Confirm that units and currencies make sense, and check how each actual quantity was calculated before treating a shortfall as meaningful.

  4. 4

    Run both systems briefly

    Keep Salesforce Manufacturing Cloud and the replacement in use side by side for a short period. Reconcile agreement terms, scheduled quantities, actual quantities and renewal work between them. Compare values separately by currency, and confirm the source and meaning of actual quantities because they do not prove delivery. Resolve differences before you rely on the new records for operating decisions.

  5. 5

    Switch off Salesforce Manufacturing Cloud

    Once you have reconciled the records and your team is ready to work from the replacement, stop making updates in Salesforce Manufacturing Cloud and switch it off for this work. Keep any records or access you still need under your own retention and operating requirements. The free version does not recreate attachments, signatures, custom calculations, permissions or live ERP connections, so confirm how those needs will be handled before switching.

construction

Where the real effort goes

The main work is usually mapping your own fields, product units, review rules and connections, then deciding how much agreement history to bring. The free importer covers five related exports, not every Manufacturing Cloud record or feature. If you have Enterprise DNA install and run your version, they map custom records, attachments and remaining history, and build the additional agreed work.

Not ready for a call?

Get your Salesforce Manufacturing Cloud switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Manufacturing Cloud, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and operates your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional agreement records
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Preview the five Salesforce exports, then reconcile your agreements and actuals
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your product units, commitment periods and review rules
  • check Your Salesforce agreement records mapped and checked
  • check A web front end and agreed business connections where needed
  • check A different technical foundation if it suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreement work alongside the rest of your business
  • check Your agreed order and reporting connections built for the team
  • check Ongoing changes, backups and operational support
Talk about your agreement desk

Questions

Instead of Salesforce Manufacturing Cloud, answered

Does this replace every part of Salesforce Manufacturing Cloud? expand_more

The free version covers customer agreements, scheduled products, actual quantities, follow-ups and renewal preparation. Enterprise DNA scopes the wider records, connections and screens your business needs before you switch.

Can I bring my Salesforce agreement history? expand_more

Yes, for the supported customer, product, agreement, product-line and schedule exports. The free version reads the five related exports together, preserves their original fields and rejects broken references. Do a test run first. Enterprise DNA maps custom records, attachments and remaining history as part of your version.

Do actual quantities prove delivery or accounting revenue? expand_more

No. Salesforce actual quantities can come from orders or another source. Confirm their meaning before acting on a shortfall. Displayed values multiply quantity by schedule price before discounts, with currencies kept separate. Enterprise DNA maps your exact commercial measures and accounting connections.

Can our team keep its order connection and get a screen? expand_more

Enterprise DNA builds the agreed order connections, shared access and screens into your version. We check the data against the existing system before the owner accepts the switch.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed ongoing work. The scope follows your agreements, history, connections and operating needs. The software itself is free under the MIT licence. Hosting and coding-agent usage have separate costs.

Put your supply agreements to work

Book 30 minutes with Sam. Bring your Manufacturing Cloud bill and one agreement your team manages every month. We will look at the records, the weekly work and what your own version needs to do.

Sales Agreements for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Manufacturing Cloud?

Get your version built