Knowledge base

The five questions your CFO will ask before buying Pinion.

These are the objections every industrial distributor raises — and the honest, earned-trade answers Pinion was built around. Agents own the paperwork your reps burn out on. Reps stay on the relationship. Everyone else gets a cleaner line item on the invoice.

01

Objection 01

Integration risk

Will Pinion break our ERP?

Pinion does not sit in front of your ERP — it sits next to it. Connectors for NetSuite, SAP Business One, Epicor Kinetic, and Infor Distribution are native and read-only by default; writes only happen after a rep hits send. Your change-control board, your approval thresholds, and your integration team’s authority over ERP fields are unchanged. Agents follow them, never bypass them. When a connector hits an edge case the rules don’t cover, the quote pings a senior rep for review rather than writing back.
02

Objection 02

Pricing precision

Can an AI really price this right?

Pinion doesn’t guess prices. Every dollar on a quote traces back to your PIM record, your contracted rate, your freight table, or your discount ladder — and confidence is rule-bound, not aspirational. The agent drafts the easy lines, then marks anything past the rule boundary as rep review. Your reps see exactly which lines they’re signing for, with the source row beside each price. The rep is still the price.
03

Objection 03

Roles & relationships

How is this not replacing our sales team?

Agents own the paperwork; reps own the relationship. Pinion is an earned-trade bet, and the trade is explicit: Pinion does the inbox, the draft, the tracker, the reorder — the work that burns your reps out — and hands off to a human exactly where a human matters. Your reps still run key accounts, still own the exceptions, still close the deal. The number of accounts a rep carries doesn’t shrink; the volume of quotes they ship triples, and the time they spend on pure paperwork drops to almost zero.
04

Objection 04

Customer & pricing data

What about our customer and pricing data?

Single-tenant by default, deployed into your VPC or ours — your choice. Customer records, pricing overrides, and quote history never cross tenant boundaries. There is no AI training carve-out on your data; the contract says so, the deployment enforces it. Every agent action writes an audit-log row — who ran the rule, what was priced, who approved, who saw what — alongside the rep’s approval, so chain-of-custody is intact. Inside the org, reps remain the gatekeepers of who-sees-what; permissioning rides through your existing IdP, not a new one.
05

Objection 05

How Pinion is priced

Why doesn't Pinion's pricing map to ours?

Pinion doesn’t take a cut per quote, doesn’t mark up, and doesn’t resell your data. Pricing is per-tier on RFQ volume and connector count — a clean line-item your CFO can read on one screen. The variable that grows with your operation is connectors (because each one is real engineering work), not the number of quotes your reps ship. Your reps and your finance team keep a predictable, dignity-preserving invoice, with no surprise scaling as the operation expands.

Ready to see it?

Run your SKUs through the same questions.

Send us your catalog, your ERP, and the three workflows eating most of your reps’ time. We’ll come back with a demo on your data — with the agent drafting the quote, the rep holding the override, and the audit row sitting underneath.

Pilot runs in your environment in two weeks.