Sales Trajectory · Northstar
See the human system around the deal.
Six product frames follow five moments—from the leader’s first question, through Alex’s work, and back to the decision the leader must make.
- VectorFlow
- seller / vendor
- RelayOps
- VectorFlow’s product
- Northstar
- customer
- CurrentFlow
- Northstar’s incumbent alternative
Fictional account and seller. This demonstration shows Alex's private workspace and a separate leader view. In the product, each view is role-restricted. The experience uses precomputed LRA analysis and scripted dialogue.
The story
Can Alex find a real customer-owned path—without turning activity into progress that has not been earned?
Alex is a VectorFlow seller working to bring RelayOps into Northstar. Riley, Northstar’s executive sponsor, wants a visible Q4 result. But no one person can approve the path: Operations ownership, security, internal capacity, and any commercial decision sit with different people.
The story follows Alex and LRA as they correct the initial account read, determine who controls each decision, prepare the next customer interaction, learn from the response, and change the plan when reality changes.
People to remember
VectorFlow
- Alex
- seller responsible for Northstar; his pressure, correction, and rehearsal remain private.
- Maya
- Alex’s sales leader; controls forecast treatment and seller-side resources.
Northstar
- Riley
- executive sponsor; creates access and sponsorship but cannot approve the full path.
- Jordan
- defines what Operations can own and under what conditions.
- Priya
- defines the security and control path.
- Dana
- decides whether scarce internal capacity can be allocated.
- Morgan
- proposed half-time internal lead; being named and willing is not the same as being allocated.
Manual navigation. Captions on. No audio.