Apex CPQ

CPQ that prices from the ERP you already run.

Most CPQ tools ask you to rebuild your catalog in a second system and then keep the two in step forever. Apex reads items, price lists and customer terms from SAP, NetSuite or Dynamics, quotes on top of them, and sends the signed deal back as a sales order.

Start with CPQ

Quote Q-20418 · v3Harlan Steel FabricatorsDraft

Price book US Industrial 2026Term 36 monthsCurrency USD

LineQtyPriceAmount

Press brake tooling set, 3 m3List $18,400$55,200

Install and operator training1Fixed$6,200

Service plan, 36 months36$1,150 / mo$41,400

Discount, tooling12%-$6,624

Service rampYr 1Yr 2Yr 3

Total $96,176Margin 38.4%floor 35%Discount over 10% · needs approval

What a quote carries

Every pricing model your sales team actually sells.

A quote in Apex is built from the same price book your invoices use, so what a rep promises is what billing charges.

Fixed, tiered and volume

List prices per currency and segment, volume breaks and graduated tiers, read from your ERP price lists or set in Apex on top of them.

Usage and minimums

Per-unit rates with a committed minimum, overage above it, and prepaid credits that draw down.

Ramps and phases

A three-year deal that steps up in year two, a pilot that converts to a full term, a free month at the start.

Good, better, best

Up to three options on one quote, each priced and margined, so the customer chooses and the rep does not rebuild.

Customer-specific terms

Contract price lists, payment terms and currency come from the customer record, not from a rep's memory.

Live margin

Cost from the ERP sits beside price on every line, and the quote shows margin before anyone sends it.

From quote to order

A signed quote becomes a sales order, in the ERP first.

01
Draft
The rep builds the quote from a template, or a quoting agent drafts it from the inquiry. Prices and terms come from the book.
02
Approve
Rules you set (discount, margin floor, term, total value, non-standard clauses) send the quote to the right approver. Nothing else waits.
03
Sign
The customer signs the quote with its order form and any MSA or SOW attached, with signers in the order you set.
04
Order
Apex writes the sales order to SAP, NetSuite or Dynamics, reads it back to confirm, and builds the billing schedule from the same lines.

Why on the ERP

One catalog, not two to keep in step.

	A separate CPQ catalog	Apex on your ERP
Items and prices	Copied in, then drift as the ERP changes	Read from the ERP's items and price lists
Customer terms	Re-entered per deal	Taken from the customer record
Signed deal	Re-keyed into the ERP by operations	Written to the ERP as a sales order, then confirmed
Billing	Rebuilt from the PDF	Built from the same quote lines
Audit	Two systems, two histories	One record, every change logged

Agents propose, people approve

The agent drafts. A person decides.

A quoting agent drafts a quote from an inbound inquiry, priced against your book, and suggests ramps or options from the customer's history. A rep reviews it and sends it.

Every agent stops at an approval gate until it has earned its way out of one. Nothing releases cash, commits spend or touches a customer without a person saying so.

Your dataModels that read your data run inside your environment, behind your firewall. No client data reaches a frontier lab.

Apex’s agents Why the approval gate

Start here, keep the foundation

Start with CPQ. Add the rest without starting over.

Start with quoting alone. Apex brings your customers, items, price lists and open invoices down from the ERP into your Ferrata foundation on day one. When you add billing or revenue recognition later, they work from the same records the quotes did. Nothing is re-implemented and nothing is re-keyed.

FAQ

Questions, answered plainly.

What is CPQ software?

CPQ stands for configure, price, quote. It is the software a sales team uses to put together what a customer is buying, price it correctly against the company's rules, and produce a quote the customer can sign. Apex does this on top of the items and price lists in your ERP rather than in a separate catalog.

Does Apex replace our ERP's pricing?

No. Your ERP stays the system of record for items, price lists and customer terms. Apex reads them, adds what the ERP does not model well (ramps, options, usage commitments, approval rules), and writes the signed result back as a sales order.

Which ERPs does Apex CPQ work with?

Apex is built to connect with SAP (Business One and S/4HANA), Oracle NetSuite and Microsoft Dynamics 365. The connection is configured when your instance is set up, against your own company codes, item masters and price lists.

Can a quote include usage-based pricing?

Yes. A quote line can carry a per-unit rate, a committed minimum, overage pricing above it and prepaid credits. When the quote is signed, the same line becomes the billing schedule, so usage is rated at the price the customer agreed to.

How are discounts approved?

You set the rules: a discount above a threshold, a margin below a floor, a term longer than standard, a non-standard clause. A quote that breaks a rule waits in the approval queue for the person your rules name. A quote that breaks none goes straight to the customer.

What happens when the customer signs?

Apex writes a sales order to your ERP, reads it back to confirm it landed as written, and builds the billing schedule from the signed lines. Operations does not re-key the deal, and billing does not rebuild it from a PDF.

Do we have to use Apex for billing too?

No. You can start with quoting only. Because the quote lines, customers and prices already sit in your Ferrata foundation, adding billing later is a matter of switching it on, not migrating data.

Related in Apex

From Ferrata Labs

Start with CPQ, or talk it through first.

Thirty minutes with Ferrata Labs on one workflow. You leave with a view of where Apex fits, and an honest answer if the sequencing is wrong and you should fix something else first.