Pitch Guide
Making the case for One Horizon inside your organization starts with one idea: One Horizon captures progress from the tools your team already uses and turns it into updates, so nobody restates status by hand.
Core message
Lead with the workflow change, not the feature list:
- Teams keep using GitHub, GitLab, Linear, Jira, Slack, Google Calendar, and their existing delivery tools.
- Connected work activity becomes recaps, standups, planning views, release notes, and measurement.
- Developers see their own recap and can correct it. There is no keystroke monitoring, screenshots, or time tracking.
- Admins can review security practices, privacy terms, and connected tool access before rollout.
For plan details, see pricing.
Pitch to executives
Executives usually care about reporting quality, delivery visibility, and the cost of coordination.
Current reporting is expensive
Status updates, standup notes, sprint summaries, and executive reports take time to assemble. They also miss work that happens across commits, pull requests, issues, meetings, and Slack.
One place to see progress
Leaders can review planned work, completed work, blockers, roadmap progress, and release notes without asking each team to rebuild the story.
Pitch to engineering leads
Engineering leads usually care about security, rollout friction, and whether the product adds process.
Access follows existing permissions
Connected tools keep their own permissions. A person who cannot access a repository, channel, issue, or calendar event in the source system does not gain access here.
Setup starts with the tools the team already uses
Start with GitHub or GitLab, Slack, and Google Calendar. On the Enterprise plan, add Linear or Jira.
The lead moves from collection to unblocking
Instead of spending leadership time gathering status, use Recaps, Standups, and Blockers to find what needs a decision.
Pitch to developers
Developers usually care about whether the rollout creates extra work or watches them too closely.
Developers stay in control
Recaps are built from work activity, and each developer can see and correct their own. Admins decide which workspace and team features are enabled.
No keystrokes, screenshots, or time tracking
One Horizon reads activity from connected tools: commits, pull requests, issues, calendar events, and selected communication. Developers get credit for work already happening, without a parallel reporting chore.
Fewer repeated status questions
When recaps stay current, developers spend less time rewriting the same update for standup, Slack, planning, and stakeholder reporting.
Pitch to portfolio teams and agencies
Portfolio teams, agencies, and engineering partners usually need trusted progress evidence across multiple teams or clients.
Better evidence than manual summaries
Work activity connects to initiatives and taxonomy, so external stakeholders see what moved, what is blocked, and where support is needed. Release Notes, Stakeholder Updates, and Taxonomy Analytics summarize progress by product, goal, customer, or workstream for a customer, investor, or partner.
Start with a pilot
Do not ask the organization to decide from a slide deck. Pick one or two teams, connect their core apps, run a pilot for 1 to 2 weeks, and compare the results with the baseline. The pilot guide covers the surveys, metrics, and admin approval messages for third-party apps.