The authorization belongs to a cloud you don’t buy
On ServiceNow, the United States government authorization does not sit on the commercial product a buyer signs up for. The Government Community Cloud holds FedRAMP High and DoD IL4, with a Privacy High overlay; a further IL5 authorization lives on NSC, a separate cloud hosted on Microsoft Azure Government. StateRAMP is absent from both, and neither offers a HIPAA BAA.
Salesforce draws the same line around its own product
Salesforce keeps a similar separation on its own side. FedRAMP coverage reaches only Government Cloud Plus, authorized up to FedRAMP High and DoD IL2, not Sales Cloud, the product most customers actually run. A HIPAA BAA does reach entry tiers, Pro Suite and Foundations, but only once three features are switched off. StateRAMP is absent; only TX-RAMP appears.
Tax is passed to the customer, and named nowhere
Neither vendor names a state or a nexus for United States sales tax. A clause in Salesforce’s Master Subscription Agreement puts “any taxes, levies, duties” on the customer and invoices where the law requires it, unless given an exemption certificate. ServiceNow excludes tax from its own prices the same way, with no dedicated tax-policy page, and delegates the actual calculation to Vertex, a third-party system, inside its Accounts Payable Operations module.
A purchase order needs no dollar minimum, on either side
Buying by purchase order opens with no floor at all. Salesforce’s own contract names the purchase order as a plain alternative to a card, with no dollar condition attached: billing runs in advance, net thirty calendar days, at one and a half percent of the balance per month once late, suspension at day thirty, day ten on a card. ServiceNow invoices its own subscriptions annually in advance on the same net-thirty terms, with the same one-and-a-half-percent monthly late interest, but publishes no price list at all: buying anything requires a sales conversation first.
The product boundary between an opportunity and a case
The two tools answer a different question by design. Salesforce structures a pipeline around the opportunity: an amount, a close date, a stage drawn from a configurable picklist. ServiceNow structures its case around an inbound customer request, entering through web, email, chat, phone or social media, worked inside Customer Service Management. The pipeline itself sits in a separate ServiceNow product, Sales and Order Management, distinct from CSM.
Neither one ships e-signature inside the licence
Salesforce has no native e-signature: even the paid Contracts module requires a separate DocuSign account outside the licence. ServiceNow shows the same gap from a different angle: electronic signature is absent from both CPQ pages tested, and CPQ itself is a separate product from CSM, so signing a contract on either platform means stepping outside what the subscription covers.
