Sales
The Deal Lifecycle Engine (DLE). Deals move through BHG's sales methodology, held to its gates, ceilings and approvals.
Sales runs on the Deal Lifecycle Engine (DLE). The DLE moves each deal through BHG's sales methodology and holds it to the methodology's rules: what must be done before a deal advances, how long it may sit in a stage, and who must approve exceptions.
Everything in the sidebar sits under Deal Lifecycle.
The methodology is data
Stages, their order, the checklist for each stage (the rubric), stage minimums, time limits (ceilings), margin tiers, loss reasons and custom fields all come from the active methodology. Admins edit it on DLE Methodology. The pages below follow whatever it says, so your stage names may differ from these examples.
A typical methodology runs Leads Inbox → Qualify → Discover & Map → Align & Scope → Propose → Negotiate & Close → Closed Won or Closed Lost.
Pages
| Page | What it is for |
|---|---|
| DLE Dashboard | Active deals, total estimated value, ceiling alerts, the stage distribution and recent deals. |
| Deals | Every deal you can see, as a Board (by stage) or a Table. Search, filter by status and owner, and create a deal with New Deal (or import a CSV). |
| Leads & Contacts | The inbox before the pipeline. Leads can be converted to a deal; Contacts are the people and companies. |
| DLE Methodology | The methodology itself: stages, rubric, custom fields, the field library and loss reasons. Admins edit it. |
| Readiness | Each deal's latest readiness score, recommendation and decision. |
| Ceiling Monitor | Deals that have been in a stage too long, with days in stage, the ceiling and any override. Checked daily. |
| Catch-Up Protocol | The checklist a vendor-sourced deal must complete before it can advance. |
| Overrides | Pending requests for exceptions to a DLE rule, for people with authority to decide. |
| DLE Mutual Action Plans | Mutual action plans (MAPs) with customers: milestones and whether each plan is On Track, At Risk or Stalled. |
| DLE Partner Alignment | The vendor partner registry and protocol compliance. |
Working a deal
Open a deal from Deals. The deal page has tabs for Overview, Details, Knowledge + AI, Activity, Stage History, Readiness, Edit, Catch-Up, Overrides and Mutual Action Plan. The header has Advance, Regress, Pause or Resume, Close Won, Close Lost and Disqualify.
Advancing and gates
Advance moves the deal to its next stage, but only when the current stage's rubric is met. If a required item is not done, or too few items are done, the deal is held and Infra lists what is missing. Complete the items, or request an override.
Other things that hold a deal:
- A Stalled mutual action plan needs an override.
- A vendor-sourced deal needs its catch-up checklist done, or a lead's approval.
Regress moves a deal back to an earlier stage and asks for a reason.
Readiness
On a deal, Evaluate Readiness scores the stage's rubric and recommends ADVANCE or HOLD. An optional AI second opinion says whether it agrees with the rubric. The deal owner or an admin then records the decision: Mark Advanced or Mark Held.
Margin and overrides
- A deal's margin below the methodology's top tier needs approval from a minimum role. Use Request Margin Approval. Lower margins need more senior or more approvers.
- An override is an approved exception to a DLE rule (a gate, a stage skip, a ceiling, the catch-up, the margin, a disqualification or a stalled MAP). Use Request Override; someone with authority decides on Overrides.
Who sees what
- Reps see and act on their own deals.
- Managers also see their direct reports' deals.
- Admins see all deals.
- Viewers can read but not change anything.
Leads follow the same rule by who they are assigned to; unassigned leads are admin-only. A mutual action plan can be edited only by the deal owner or an admin.
Agents and the DLE
An agent connected to Infra can read and work deals as you, with the same rules. See Connecting agents and the dle_* tools in the tool reference.