Liftoff
Our Revenue Cloud management copilot and the key to admin enablement. Visualize the pricing waterfall, test scenarios against live Revenue Cloud APIs, and manage complex bundles from an agentic chat.
What Liftoff Actually Does
A Chat That Knows the Tools
Quick actions cover the requests admins make constantly: create a product, build a bundle, create custom fields, inspect a pricing procedure. Describe what you need in plain language and the agent calls the same tools behind those quick actions, confirming choices like which selling model to use before it acts.
One Field, the Whole Lifecycle
Creating a custom field runs it onto Product2, QuoteLineItem, OrderItem, and AssetStatePeriod in one job, grants field-level security on all four, then updates the ProductDiscovery and SalesTransaction context definitions: matching attributes, context tags, and the 7 hydration mappings that carry the value through quote, order, and asset lifecycle. ProductDiscovery deploys first, the order the cross-context mapping requires.
Products and Bundles, End to End
A product job resolves or creates the selling model and pricebook, creates the product, the selling model option, the standard pricebook entry, and the category assignment, logging each step pass or fail. Bundle components carry relationship type, component groups, min/max quantity, and quantity scaling, with a plan preview before anything is built.
See the Pricing Procedure, Then Test It
Visualize an active pricing procedure step by step, color-coded by action: decision tables, formula-based pricing, tier discounts, manual discounts, rounding, price revisions. Run real line items against it before anything ships, and modify a cloned version with a dry-run preview before you activate the new version.
Constraint Models, Explained
Liftoff lists the constraint models in your org, parses the CML into types, relationships, and rules, and opens a visual panel for each one. Ask what a rule enforces on a specific product and get the answer in plain English, not CML syntax.
Multiple Orgs, One Permission Set Flow
Connect more than one Salesforce org and mark one primary; each connection carries its own SalesTransaction and ProductDiscovery context definition names. Search existing permission sets or create one from the Connections page: Liftoff creates it in Salesforce and assigns it to your user, with the result on the Jobs page.
From a Sentence to a Deployed Change
Describe It
Type what you need in chat, or start from a quick action: create a product, build a bundle, add fields, inspect pricing.
Liftoff Plans It
The agent resolves the org context, selling models, pricebooks, context definitions, permission sets, and confirms the specifics with you.
It Deploys to Your Org
The change runs as a background job against your connected Salesforce org over the Metadata and REST APIs.
The Job Log Shows Every Step
Each step (Selling Model, Pricebook, Product, Selling Model Option, Standard PBE, Category Assignment, and the rest) is recorded pass or fail with details, visible on the Jobs page.
Born From 42 Manual Steps
Mapping one field from product through the Revenue Cloud lifecycle takes 42 manual steps: four custom fields, then a stack of context definitions and mappings. We built Liftoff because we refused to have our own team do that by hand. Then we gave it to our customers, with a chat that explains options and impact before you commit a change.
Implementation customers get free access and a perpetual license.
See the practice behind it