Who can use this
- Super Admins can configure or update pricing context.
- Non-super-admin users may see the onboarding step as informational and can continue without editing it.
Before you start
- Confirm the approved internal pricing model with the rollout owner.
- Keep confidential customer-specific discounts, legal terms, and negotiated exceptions out of the generic pricing description unless your team intentionally wants Ergo to use them as workspace context.
- Make sure related CRM amount, package, discount, or pricing fields are mapped separately if you expect CRM records or reports to use those fields.
Steps
- Open the pricing configuration step during onboarding or from the Field Mapping setup area when available.
- Enter a concise pricing description in plain language. Include the pricing model, package structure, units, tiers, or assumptions that help Ergo reason about deal amounts.
- Save by leaving the field or completing the step.
- Revisit the description when your packaging or pricing model changes.
- Test deal amount reasoning on a small set of records before relying on pricing-informed automation or reports.
What to expect
- Pricing configuration stores one organization-level text description.
- Super Admin access is required for the pricing configuration API.
- The description helps Ergo infer or explain deal amounts, but it does not replace CRM amount fields, quote approvals, or billing systems.
- If no pricing configuration exists, the step can still be completed by users who are not allowed to edit it.
Common issues
- A user expects to edit pricing but is not a Super Admin.
- CRM fields for amount, package, or discount are unmapped, so downstream reports still lack structured pricing data.
- The pricing description is too broad, stale, or includes exceptions that should not apply to every deal.
- Someone treats this page as customer-facing pricing. Keep public pricing and contract language in the approved commercial source of truth.