For business and ops teams

Work your KPIs with Bicycle, day to day.

Know what changed. Understand why. Act safely.

Start from the change that matters, see the cause with the evidence, and take the next step inside the guardrails your data team set. Every move shows what you do and what Bicycle does for you.

Pick your vertical
Pillar 01 · Know

Know

Stop refreshing dashboards and pinging analysts. The change most likely to move your numbers finds you, ranked by impact, in your own terms.

You get: the changes that matter, before you askC3Always on KPI IntelligenceC2Vertical native contextC5Defensible answers
The agent doing the work

Pattern Engine

Runs governed patterns across your KPIs around the clock, groups related issues, and ranks them by impact so the one that matters reaches you first.

Surfaces first
every move is a handoffYou decide· Bicycle drafts

See what Bicycle found, before you ask

The alert inbox shows the KPI changes that matter on your segments, ranked by impact and routed to the right next surface, so you start from the answer, not a blank dashboard.

You decide
  • Scan owned KPIs, segments, impact, and severity
  • Open the detail, then jump to the explanation or action
Bicycle drafts
  • Runs governed patterns continuously and ranks by impact
  • Shows the affected segment and the recommended next surface
app.bicycle.ai alert inboxpreview
The other moves you makeclick a card to enlarge
Start in your own language

Home opens to your KPIs, owned areas, and the questions you ask most, with no table names or metric IDs to translate.

Governance

You see only the KPIs and segments your access allows. What surfaces runs on patterns the data team published.

In practiceThe change most likely to affect your numbers reaches you ranked by impact, before you open a dashboard.
Runs on Build the trusted foundation
Pillar 02 · Understand

Understand

Knowing a number moved is not the answer. See why, with the evidence and what was ruled out, and walk into the review with one story the room trusts.

You get: the cause, with evidence, and a story you can shareC4Multi factor cause AnalysisC5Defensible answersC2Vertical native context
The agent doing the work

Cause Engine

Evaluates the drivers and specific causes against the affected segment, pulls the supporting evidence, and shows confidence plus what it ruled out.

Evidence attached
every move is a handoffYou decide· Bicycle drafts

Understand why it changed

Open the explanation and see the ranked cause, the evidence behind it, the confidence, and the drivers Bicycle checked but ruled out, so you act on the cause that matters, not the first guess.

You decide
  • Review primary and contributing causes
  • Inspect the evidence and ask follow-ups in context
Bicycle drafts
  • Narrows to the affected segment and tests the drivers
  • Shows confidence, source links, and what it ruled out
app.bicycle.ai cause analysispreview
The other moves you makeclick a card to enlarge
Align on what changed

Turn the finding into one shared data story, definitions and evidence attached, for the weekly or the board review.

Governance

Every cause traces to the evidence and sources the data team validated. Confidence and ruled-out checks are shown in view.

In practiceSee the ranked cause with evidence and confidence, plus what was checked and ruled out.
Runs on Tune the intelligence layer
Pillar 03 · Act

Act

Move from cause to the next step with the scope already attached. Run what you are cleared to run; the rest routes through approval, rollback, and audit, automatically.

You get: the next step, scoped, with speed and safety both intactC6Governed self service and actionsC3Always on KPI IntelligenceC4Multi factor cause Analysis
The agent doing the work

Action Engine

Picks the action from the registry, inherits the scope from the cause, and generates a previewed request, ticket, or message bounded by your permissions before anything runs.

Scoped and reversible
every move is a handoffYou decide· Bicycle drafts

Act on what matters now

The recommended next step arrives scoped to the affected segment, with the owner and the context attached. Preview it, send it, request approval, or route it, without losing the evidence.

You decide
  • Preview the message, payload, scope, and owner
  • Send, request approval, or route to the owner
Bicycle drafts
  • Picks the action and inherits scope from the cause
  • Generates the previewed request and tracks the outcome
app.bicycle.ai action previewpreview
The other moves you makeclick a card to enlarge
Act safely within guardrails

Run what you are cleared to; higher-risk changes carry scope limits, a rollback path, and an approval, every attempt logged.

Governance

Business users act within the scopes the data team sets. Previews and approvals are enforced, rollback paths exist, every attempt is logged.

In practiceThe next step arrives scoped to the affected segment and ready to send, request, or route.
Runs on Govern self service and safe actions

Build your first agent.

Connect a source, apply the vertical pack, and review your first governed agent with the cause and the definitions attached. In days, not quarters.

Share the link or download the PDF to send this playbook to your team