The whole journey, end to end

How a customer moves through Beacon describes two stage rails. The full journey is longer than both — it runs from first marketing contact to the revenue that eventually lands, and the two rails are its middle.

​

Four handovers

The first two are the seams Beacon runs on today. Stages are published for the sales and customer parts only — the marketing handover is defined as the point where authority over a deal passes, but no marketing stages are published. The last two activate when the product and finance connections do.

​

What the journey record actually holds

Order, handovers, and the moment authority passed at each one. Nothing else. No figure is born here. A journey view points at each part’s own stage and each part’s own numbers; it does not recalculate them, hold a copy, or produce a total that none of them published. That is what makes it safe to read across parts — there is no second version of anything on it.

​

A part that is not running does not guess

Where a handover is inactive, the journey shows the parts that are available and says so. It does not estimate the missing stretch, carry the last known state forward, or shorten the journey to hide the gap.

​

You see the parts you have access to

A whole-journey view is not a wider door. It resolves across the parts you already hold access to, and its sensitivity is that of the most restricted part you cross — reading several parts you are entitled to never adds one you are not. If a stretch is beyond your access it stays unresolved, and the view says so rather than quietly omitting it.

​

Disagreements are raised, not settled

Where two parts describe the same record differently, the journey flags it and routes it to both owners. See When two systems disagree about a stage.

​

Related