Skip to the page

Solutions · Product

How did it move? Sprints, tickets and what sells, from the systems you already run.

Your tracker shows today. nexibi keeps a dated copy of the lists you choose from a system with a web API, so a board can show how things moved: a sprint burndown, open tickets by status, week by week. And ask what sells and who buys it, in your own words.

Each point is a copy kept that night

Tarnwick Supply Co.Boards · Sprint 14Sample data
Sprint 14Sample tracker · Issues
Daily copy of Issues, 02:00 · 60 days of history
1Starts the day you turn the copy on
Share Edit
2An ordinary board you can edit
Story points left
Story points leftEven pace
020406080Day 0Day 2Day 4Day 6Day 8Day 10today · 30 left
Open tickets by status, week by week
To doIn progressIn review
0204060Wk 38Wk 39Wk 40Wk 4155Wk 42Wk 43Wk 4436Wk 45
  • 1Starts the day you turn the copy on
  • 2An ordinary board you can edit

Six questions product people ask.

  1. 01

    “How did open tickets move by status, week by week?”

    Your tracker shows today's tickets. A daily copy kept by the history engine lets a board draw how they moved, from the day the copy starts.

  2. 02

    “How is Sprint 14 burning down?”

    Ask the assistant for burndown, burn-up and velocity rows for each sprint, by day, from the same copy, and draw them on a board.

  3. 03

    “What changed in the tracker since yesterday?”

    Each new version records what changed, field by field ("status: In review → Done"). A ticket that disappears is marked, not erased.

    Built withHistory engine
  4. 04

    “Which ten products sold the most in October, by units, cancelled orders left out?”

    A ranked list, ready to download.

    Built withAI Assistant
  5. 05

    “Who are the top customers for Electrical and lighting?”

    The biggest buyers of one product line, and the answer says which orders and dates it counted.

  6. 06

    “What minimum order quantity does the Varnholm contract set, and on which page?”

    Attach the PDF; it names the page.

    Built withAI Assistant

Counts and totals are calculated from the rows it reads, not estimated by the AI. It reads a whole list, up to 20,000 rows, and tells you when a list is longer. Ask a follow-up, such as "only the Power tools line" or "now by customer", and it carries on from the last answer. Say what you mean by "sold": units or order-line value, ordered, delivered or invoiced. It says which list it used, and you can tell it what you mean.

One question, all the way to the follow-up.

On Tarnwick's sample tracker, connected through its web API (history and flows read systems with an API, not a connected database).

  1. 1

    Ask.

    "How many open tickets are there in Sprint 14, by status?" The answer: 36 open tickets (To do 12, In progress 16, In review 8), with the list.

  2. 2

    Keep its history.

    Say "keep a daily copy of our open tickets and chart them by status". The assistant proposes the copy on a card: the list, every night at 02:00 your time, kept 90 days, counted by status. Nothing starts until you approve it. It measures the list first and checks the first copy before it draws a chart.

    Nothing starts until you approve it.

    AssistantSample trackerSample data
    Keep a daily copy of our open tickets and chart them by status.
    Assistant
    Keep a daily copy of Issues
    Every night at 02:00your time zonekeep 90 dayscounts: by statusburndown rows: per sprint
    ApproveChangeNot now
    ≈ 1 run a day — comfortable
  3. 3

    See it move.

    The board shows one column for each copy, and the sprint's burndown line beside it. History starts on the day the copy starts; as the Track history window puts it, "A chart needs one column per capture — twelve weekly columns take twelve weeks."

    Sprint 14BoardSample data
    Sprint 14Sample tracker · Issues
    Daily copy of Issues, 02:00
    Story points left
    Story points leftEven pace
    020406080Day 0Day 2Day 4Day 6Day 8Day 10today · 30 left
    Each point is a copy kept that night
    Open tickets by status, week by week
    To doIn progressIn review
    0204060Wk 38Wk 39Wk 40Wk 4155Wk 42Wk 43Wk 4436Wk 45
    • Each point is a copy kept that night
  4. 4

    Follow up.

    A company owner builds a flow in the flow designer: every Monday at 09:00 it reads the open tickets from the tracker, sums them up in one paragraph and e-mails the team. Try it first: nothing is sent and nothing is changed.

    Monday sprint noteFlow designerSample data
    Every Monday at 09:00Starts the flow
    Read open tickets
    Sum it up in one paragraph
    Send the e-mailthe team

    Test run done

    Started by handstep 1
    Read 36 rowsstep 2
    Wrote one paragraphstep 3
    Would send the e-mailstep 4
    Each step keeps what it received and passed on.

Build it your way.

Product people often finish a board by hand. The designer is built for that.

  • 48 kinds of chart, table, map and filter, on pages, sections and tabs. Undo goes 40 steps back, and Preview shows the board as a reader would.
  • Measures defined once and reused by every chart. Calculated fields, such as margin = amount − cost.
  • Top 10 with "Others", sorting by another measure, and 19 ways to group dates.
  • Make the data for a board without SQL: pick a connection and a table, tick columns, filter, and see the first rows as you go. Or describe the data in a sentence; nothing is saved until you press Add.
  • In Query Studio, place lists on a canvas, draw the joins, and get join suggestions with a check that each is valid.
  • Make your own copy of any board you may only read, and change the copy.
Dashboards
Product linesDesignerSample data
Product linesEditing in the designerUndoRedoPreviewSave
Find a widget…
TablesComparePartsOne numberContentFiltersRelationsOver timeAssistMaps
48 kinds, by hand
SankeyRibbonNetworkTree diagram
Product line to customer segmentPower toolsElectrical and lightingFastenersPlumbingBuildersRetailHospitality
  • 48 kinds, by hand

History you can trust.

  • Keep linked lists as one plan: every project and each project's issues, kept linked.
  • Leave some records out of a count, such as the rejected ones.
  • Chart a field that is only on each record's detail page. It is fetched only for records that changed.
  • If a copy cannot read the whole list, it stores nothing that day, rather than a number that looks right and is not.
  • Each copy comes with ready saved queries: every version, as it stands, a daily rollup and a daily breakdown.
  • The History page says, in plain words, whether each copy you own is still feeding its charts, and what to do if not.
History engine
HistoryYour copiesSample data
Issues · Plan · per projectdaily 02:00 · 90 days kept · 60 days of history
Healthy
No bar, rather than a wrong one
Releasesfirst copy tomorrow
Waiting
Changes · Issues3 changed · 1 removed
TRK-412status: In review → Done TRK-398story points: 3 → 5 TRK-405priority: Normal → High TRK-377removed marked, not erased
  • No bar, rather than a wrong one

What you can share, and with whom.

  • Share a board with people, teams or roles, each to view, edit or delete. Everyone in the company means view only.
  • A colleague who may only read a board can make a copy to edit. The copy names any data that was not shared with them.
  • Share a saved query to view, edit, run or delete.
  • A history copy shows up as its own "History" source, seen by whoever its connection is shared with. If the connection sits in a sealed department, the history stays there too.
  • Give boards your company's look: font, background, header band, tile frames, titles and colours.
  • Export a board as a picture, a PDF or an Excel workbook, one sheet per chart. An owner can switch downloads off.

What it does not do yet.

So you know before the demo.

  • History starts on the day you turn a copy on.It cannot fill in the past.
  • History covers systems with a web API and the ready-made connectors, not databases, files or mailboxes.
  • A board card cannot yet show a list as it stood on a past date, beside today.
  • In the chat, it does not rank what rose or fell.Draw it on a board instead.
  • It does not compare two fields of the same row yet, such as stock against its reorder level.

The engines behind these answers.

AI Assistant

Ask what sells and who buys it, in your own words.

AI Assistant

Bring the chart your tracker cannot draw.

In the demo we connect one of your systems, and you ask the questions.