Alkhai · Capabilities
Alkhai

How it works

From your records
to your next move.

Share a snapshot. See what’s slowing work down. Choose what to improve.

Every piece of work leaves a trail.

Share an approved 3–6 month export for one process. We connect its IDs, steps, and dates into a timeline.

Your approved exports
orders.csv

A104 · Created · 1 Sep, 09:00

approvals.csv

A104 · Approved · 1 Sep, 16:00

shipping.csv

A104 · Shipped · 2 Sep, 10:00

Alkhai builds the event logOne timeline. One row for each step.
Example event log for order A104, with all timestamps in UTC
case_idWhich itemactivityWhat happenedtimestampWhen it happened
A104Created2026-09-01T09:00:00Z
A104Approved2026-09-01T16:00:00Z
A104Shipped2026-09-02T10:00:00Z

The same ID links the steps. Z means UTC time.

CSV / Parquet exports · XES event logsIllustrative example
What should our team prepare?A small export. A clear starting point.Your data checklist
01 / The essentials

Three fields tell the story.

Each row records one step in the journey of an order, claim, or item.

  • Which item?case_id

    A consistent ID that connects the steps of the same order, claim, or item.

  • What happened?activity

    The step or status change, such as Created, Approved, or Shipped.

  • When did it happen?timestamp

    The date and time of that step, including its time zone.

Different column names are fine. We map them with your team and check the timeline together.

02 / Your starting file

One process. A few months of history.

Usually 3–6 months in CSV or Parquet. Already have an event log? XES works too.

CSVParquetXES
One order, three recorded stepsExample
  1. A104Created01 Sep · 09:00
  2. A104Approved01 Sep · 16:00
  3. A104Shipped02 Sep · 10:00

Same ID, one row per step. All times shown in UTC.

Download example CSV

Include the history. A current status alone won’t show the steps that came before it.

Adding financial estimates? We may also agree fields such as amount, currency, or processing cost.

We agree the fields, secure transfer, and retention first. Names, contact details, and passwords aren’t needed.

Plans & packages

Start once. Continue if it’s right for you.

Diagnose. Fix. Keep it fixed. Begin with a focused diagnostic, then add continuous monitoring when you’re ready, or take both together.

Step 1 · Start hereRecommended start

One-time diagnostic

30-day target

Our analysts turn your history into ranked priorities and an action plan. Your leadership team gets platform access.

  • One agreed process
  • 3–6 months of history
  • No system connection

What you get

  • Ranked bottlenecks, by business impact
  • An action plan with an estimated business case
  • Findings explained by our analysts
  • Platform access for your leadership team
Scope your diagnostic
Step 2 · When you’re readyOngoing

Continuous monitoring

Keep improvements on track

Watch for returning delays with approved connectors, weekly health reports, and monthly reviews with our analysts.

  • Approved connectors
  • Weekly + monthly cadence
  • Agreed with your IT team

What you get

  • Monitoring for returning delays
  • Weekly health reports
  • Monthly leadership reviews with our analysts
  • Ongoing platform access for your team
Ask about monitoring

30-day target from receipt of usable, approved data for one agreed process. Scope and timing are confirmed before work starts.

Start with one process. Your team approves the data. We guide you through the rest.
Get Your Free Report