Customer obsession

From a customer theme to planned work or an agent-built fix.

“Once we agree a customer problem matters, how long before anyone starts on it?”

A decision to act becomes a goal with the customer evidence attached. Outcome drafts the work, and a person approves each piece before it is sent.

In the product
Kestrel Bankdemo data

A mortgage offer in a day, not a fortnight

1 waiting on you · 3 moving · 1 stuck

Reaches no goal

2 moving

Needs you1

Working4

Reaches no goal

In review3

Reaches no goal

Stuck1

Done2

Work moves as people and agents move it. Outcome reads each change from the tools it happened in.

The work people and agents have under way, in rows by the goal it serves. Work that reaches no goal has its own row.

What you get
  • Customer words on the goalLive

    People working on a goal can read the customer comments that justify it.

  • Goal breakdownLive

    Outcome drafts the work that would close a goal's gap, for the owner to accept.

  • Send to be builtLive

    Send work to a coding agent, a ticket or a person, with a brief and the sender's name.

  • Coding agentsLive

    Hand work to Cursor or Claude and the pull request returns linked. Devin is in preview.

  • Preview builds from feedbackPreview

    Clear feedback can become a preview build, approved by a named person within a spend limit they set.

  • Fixes for errorsPreview

    A production error arrives with a brief for a fix, which an agent drafts once a person approves.

Live In the product today. Preview Working, refined with customers.

An example

Kestrel decides that applicants should be able to see their mortgage application status.

  1. 01The decision creates a goal to reduce status calls, with the customer comments attached.
  2. 02Outcome drafts four pieces of work. The product lead accepts three and sends one to a coding agent.
  3. 03The agent's pull request returns linked to the goal, and the other two go to the Jira backlog.

Kestrel Bank is a fictional example. The figures are calculated by the product.

What you connect
  • Jira and Atlassian
  • GitHub
  • Cursor agents
  • Devin
  • Claude
  • Sentry

If a system you rely on is not listed, ask for it. Outcome’s integration builder drafts the connection, and it is offered to you to try before it is switched on. How the agents work

Beside the tools you have

Work stays in Jira and GitHub. Outcome prepares the brief, records who approved it, and reads the result back.

See how Outcome compares

The time from agreeing a customer problem matters to starting work becomes short and visible.

More in customer obsession