BOS

BOS CRM

A CRM that holds your process, not just your contacts.

The pipeline, the rules that govern it, and the decisions it raises all live in one place.

A BOS pipeline with two control points A single path runs left to right through five stages: lead, qualify, proposal, negotiate and won. The path is interrupted twice. The first interruption, after qualify, is the qualification gate. The second, after negotiate, is the approval gate. At each interruption work stops until a decision is taken. A lighter branch returns from the qualification gate back towards qualify, representing work sent back for more evidence. LEAD QUALIFY PROPOSAL NEGOTIATE WON QUALIFICATION GATE APPROVAL GATE RETURNED FOR EVIDENCE A BOS pipeline with two control points The same pipeline shown as a vertical flow: lead, qualify, the qualification gate, proposal, negotiate, the approval gate, and won. At each gate the line is broken, meaning work stops until a decision is taken. A branch on the left returns from the qualification gate to qualify, for work sent back for more evidence. LEAD QUALIFY QUALIFICATION GATE PROPOSAL NEGOTIATE APPROVAL GATE WON ← RETURNED FOR EVIDENCE WORK STOPS UNTIL APPROVED

Conceptual diagram · not a screenshot of the application

Scope

What is in it

PIPELINE

Opportunities and forecasting

A board and a list view, stage history on every record, and a weighted forecast with a commit threshold. Closing lost is recorded against a reason you define.

DEMAND

Leads and qualification

Lead scoring, territory-based routing and a distinct qualification stage, so a lead becomes an opportunity by passing a step rather than by someone changing a dropdown.

ACCOUNTS

Accounts and contacts

Account records with their open pipeline rolled up, and a contacts directory scoped by the visibility of the account.

STRUCTURE

Teams, territories, quotas, capacity

Define who owns what, what they are carrying, and the ceiling beyond which work should not be assigned.

CONTROL

Governance and approvals

A queue for what needs a decision, with the exception and approval history attached to the record it belongs to.

Control points

Where work is allowed to stop

Qualification, approvals, exceptions and capacity ceilings are separate, configurable parts of the CRM rather than conventions your team is asked to remember.

The places where work should pause are places in the system, not places in somebody's judgement.

Qualification

A lead becomes an opportunity by passing a step, not by someone changing a dropdown. Where the evidence is thin, the work goes back rather than forward.

Approval

Discounts, terms and exceptions stop here and wait for a named decision. The approval and its reason stay attached to the record afterwards.

Run it against your own pipeline.