Forge Configure#

Forge Configure deploys turn-key Salesforce configuration packages — best-practice fields, validation rules, and reports — into an org before anyone logs in. It's the "install" leg of assess → install → migrate.

Packages#

Each package is a versioned bundle of configuration items: fields on standard objects, validation rules to enforce discipline, and board-ready reports. The catalog ships 16 packages spanning the sales + service + post-sale lifecycle — examples:

• MEDDPICC qualification fields on Opportunity.
• ARR/MRR reporting on Contract start/end dates, with an exec report.
• Territory & Quota — a shared territory picklist on Opportunity + rep, quota fields, and a "won deals must roll up to a territory" guardrail for attainment.
• Customer Success & Onboarding, Win/Loss analysis, Partner deal registration, Discount governance, BANT / lead lifecycle / forecast hygiene, Stage hygiene, Case SLA, Renewals & churn, Attribution, Data quality — each a guardrailed, deployable package.

Versioning and conflict handling#

Config-as-product has to answer "what if the org already has this field or report?" Configure is built for that from the start:

• Preview is read-only — it snapshots the org and shows the deploy plan before anything changes.
• Deploy records what it did, so it can be rolled back (three-way aware, like Forge Load).
• Upgrade-diff compares a deployed package against the current catalog, so you can see what a new version would change.

Built on the metadata path#

Configure runs on the same selectable-API foundation as Forge Load (Tooling and Metadata), so a config deploy is a managed, recorded, reversible operation — not a fire-and-forget script.

Note: The deploy engine is kind-agnostic — fields, reports, and validation rules all flow through the same preview → deploy → rollback path.