The systems you already run, connected into one loop.
Outcome reads who owns what, the numbers, the work and the cost from your own systems, and sends each decision back to where the work happens.
Each system answers one part of the question.
- Where you stand
Who owns what, the numbers each goal is judged by, and the goals you already keep.
StructureMeasuresGoals+24 - What is moving
What customers and systems are telling you, and the work under way.
SignalsWork+9 - What it costs and earns
What each goal costs, and how much business stands behind each request.
FinancialCommercial+8 - Where the decision goes
Decided work goes back to the tool your teams already use.
Write-back
Outcome judges each goal, decides what to do, and reads the number again.
Three systems, one picture
- BambooHR+Atlassian+Snowflake
The teams, the work they own, and the number it should move.
- Salesforce+ServiceNow+Power BI
What customers raise, the demand it creates, and the figure the board reads.
- GitHub+Cursor team usage+Claude Code usage
What your AI tools cost, and the goals that work served.
Eight things a connection can bring.
- Structure14Teams, people, reporting lines, cost centres, products and servicesEach goal gets an owner, and each piece of work a team.
- Measures32The numbers your goals are judged byA goal's number is read on a schedule, with its history.
- Goals2Goals and plans you already keepThey arrive as proposals, and a person accepts each one.
- Signals11Feedback, calls, cases, incidents and usage patternsGrouped into themes and put in front of the goal they bear on.
- Work10Issues, pull requests, deployments, changes and agent runsPlaced under the goal it serves, so a goal with nothing behind it shows.
- Financial15Tool, cloud and licence spend, and cost figuresCost lands on the goals it served, and spend that served none shows too.
- Commercial3Accounts and pipelineEach customer theme carries the business behind it.
- Write-back9Decided work, sent to where the work happensA decision becomes an item in the team's own tool, signed by whoever approved it.
Financial: 15 connections
| Connection | Structure | Measures | Goals | Signals | Work | Financial | Commercial | Write-back |
|---|---|---|---|---|---|---|---|---|
| Data and BI | ||||||||
| Power BIPreview | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| TableauPreview | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| Google BigQueryPreview | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| SnowflakePreview | Structure: no | Goals: no | Signals: no | Work: no | Write-back: no | |||
| DatabricksPreview | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| People and teams | ||||||||
| Microsoft Entra IDPreview | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | |||
| OktaPreview | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | |||
| AI spend | ||||||||
| AWS and Azure billingPreview | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | |||
| KiroPreview | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| Claude Code usageLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| Cursor team usageLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| Claude Code telemetryLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| Claude Enterprise usageLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| GitHub Copilot usageLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
| OpenAI API usageLive | Structure: no | Goals: no | Signals: no | Work: no | Commercial: no | Write-back: no | ||
18 live, 21 in preview. Each only reads, unless you approve work to send.
Live In the product today. Preview Working, refined with customers.
- Your tools change every quarter
New AI tools arrive faster than a fixed catalogue of connectors can follow.
- The numbers live everywhere
A goal’s measure may sit in a product database, a finance system or a spreadsheet.
- Agents can do the plumbing
An agent reads the API’s documentation and wires the connection, and a person approves it.
- Integration builderAsk for a system. The agent drafts the connection for you to try before it is switched on.Preview
- Metric hunterDescribe the number you want. Outcome finds it in your connected tools, or builds the measure.Live
- Any system with an APIGive Outcome an address, a key and the numbers you need. It feeds a goal the same day.Live
Four ways in that most companies already have open.
- ClaudeLive
Add Outcome as a connector, and your team asks about goals inside Claude. Usage and spend are read daily.
Try askingUsing Outcome, show me which company goals have no work behind them, and what we spent on AI against each one this month. - ChatGPTPreview
ChatGPT connects through the same connector standard. OpenAI spend and usage are read daily.
Try askingUsing Outcome, draft this quarter’s board memo from our goals, and check every figure against the record before I send it. - CopilotLive
Copilot usage, seats and spend are read daily by team. Its pull requests land on the goals they served.
Try askingWhich teams are using Copilot most, and which goals did that work move? - AtlassianLive
Connect Jira, and Outcome reads your work, your Atlassian goals and your plans in Confluence.
Try askingConnect Jira, then accept the goals Outcome drafts from the work your teams already have in flight.
A workspace is set up within one working day of asking. Each of these then takes a few minutes. Before then, your assistant can draft your goals: see the sentence to paste.
Using Outcome, which of our company goals have no work behind them?
Two of Kestrel’s fourteen company goals have almost no work behind them.
A mortgage offer in a day: five pieces of work cover about two thirds of the improvement needed. The remaining third has no work yet.
Switching made easy: no work is linked. The measure, switch completion rate, has been flat for six weeks.
Would you like me to propose work for either, for the goal’s owner to review?
An example on the site’s fictional bank. The assistant can propose a change, and a person accepts it in Outcome.
Most companies we work with run on Atlassian, so it is the best-supported path.
- Jira work under every goalLive
Issues and epics are read as work and placed under the goal they serve.
- Atlassian goalsLive
Goals kept in Atlassian are read with their status, so nothing is typed twice.
- Plans in ConfluencePreview
Confluence pages are read as your plans, and goals written there are proposed with their source line.
- Work created in JiraLive
When a person hands work off from a goal, the issue is created in your Jira project.
- Outcome in the Teamwork GraphPreview
The Outcome app puts your goals in the Teamwork Graph, with cards in Jira and Confluence that Rovo can read.
- Teams in stepLive
Teams and structures come from TeamForm, an Atlassian Cloud Fortified app.
Connect your AI coding tools, and the spend lands on the goals it served.
- 01Connect
Claude, Cursor, Copilot or OpenAI, with a read-only admin key.
- 02Read
Spend and usage arrive daily, by team and by tool.
- 03Place
Each pull request carries what it cost, and lands on the goal it served.
- 04Decide
You see what each goal has cost and which spend reached no goal.