Horizon. Opportunities surfaced from customer, market, and team signal.
An opportunity board fed by customer, market, and team signal — with value estimated and pursuit recommended.
The shift
Before Horizon, and after.
Same office, same people — different operating posture.
Before
- — Opportunities surface in someone's head, not on a board.
- — Pipeline mixes wishful thinking with real signal.
- — Pursuit decisions feel like vibes, not math.
After
- — An opportunity board grounded in real signal.
- — Value estimated; integration lift assessed.
- — Pursue / hold / decline — with a paper trail.
How it runs
The Horizon workflow.
A short loop the office actually runs every day.
Step 01
Detect
Pulls signal from Scout, Echo, CRM, and stated bets.
Step 02
Estimate
Sizes opportunity and lift; assigns confidence.
Step 03
Recommend
Suggests pursuit posture and routes to leadership.
Inputs · outputs · artifact
What goes in, what comes out.
Inputs
- Scout, Echo, CRM
- Stated growth bets
- Resource constraints
Outputs
- Opportunity board
- Value estimates
- Recommended pursuit
Sample · Opportunity
Mid-market expand · Northeast
Est. $4.2M ARR · low integration lift · pursue Q1.
Trust posture
The same approval gate as every other module.
Helm never sends, schedules, or commits anything externally without an explicit office decision. Every action is logged in Verdict with diff and approver identity.
Approval-gated execution
Tamper-evident audit
Customer-owned memory
Works with
Modules that pair with this one.
See what's next