Skip to content

Platform · Kanban

What gets decided becomes a card with an owner.

A Kanban board inside Skyller, in the same place as your documents, agents and conversations. The difference is that the AI does not just answer here: when you ask, it opens the card, fills in the fields, moves it along and comments — always with your login and your access, and stopping to ask for confirmation on any action your company marks as sensitive.

Try it freeBook a demo
See how it works
Skyller · Kanban

Customer onboarding

In progress1

Validate received documents

High

Check customer details, contract and attachments.

Docs
1/2
AAna

Done0

Demonstration · illustrative data

BOARD · TABLE · CALENDAR

three views of the same board; each person picks one and Skyller remembers it

6 READY-MADE BOARDS

Tasks, CRM, Recruiting, Content, Logistics and Accounts payable, with stages and fields included

15 FIELD TYPES

from currency and due date to assignee, rating and multi-select

DUE-DATE ALERTS

due within 24h and overdue reach whoever is responsible, once at each threshold

Where this shows up in your day

The decision was made in the conversation. And died there.

Every company has the same leak: someone asks, someone answers, what to do gets agreed — and nobody writes it down. Next week the same question comes back, because the agreement never became anyone's task.

Finance

The invoice that arrived and nobody claimed

The supplier emailed the bill, someone forwarded it to the group chat, and it went past due. Information was not missing: what was missing was a place where “who pays this” is a field, not an assumption.

Every bill has an owner

Sales

The pipeline that only exists in the rep's head

What stage is that client at? Who spoke to them last? How much is it worth? The answer is split between one person's memory and a spreadsheet nobody updates after Tuesday.

Stage in plain sight

Operations

The routine that only moves when someone remembers

Weekly checks, month-end close, procedure reviews. Tasks that repeat forever and today depend on someone waking up remembering them.

It shows up on its own

How it works

An ordinary board. With the AI inside it.

The stages, the fields and the people are the usual ones — what changes is that Skyller can see this board and act on it when you ask, without you leaving the conversation.

  1. 01

    The board starts

    Begin with one of the six ready-made boards — Tasks, CRM, Recruiting, Content, Logistics or Accounts payable, each with the stages and fields of that process — or describe your own process and let Skyller propose the stages and the fields it tracks.

  2. 02

    The fields are yours

    Beyond title and assignee, each card carries the fields your operation actually uses: currency amount, due date, supplier, rating, source, phone. There are fifteen types, and a field can be required before a card leaves a stage.

  3. 03

    Work moves

    Drag on the board, edit in bulk in the table, or look at it by due date in the calendar — the same board in three views, with the same filters. The numbers at the top (urgent, overdue, completed today) are buttons: clicking one filters the board.

  4. 04

    Skyller works alongside

    In chat you ask in plain language: open a card with what just came out of the conversation, move it to the next stage, comment, add a column. It acts with your login and your access — never with administrator privilege.

  5. 05

    The due date chases on its own

    Whoever is responsible is alerted when a card is less than 24 hours from its due date and when it goes overdue — once at each threshold, not every day. And a repeating routine can be set up so the card is born at the right time, with nobody remembering.

Skyller · Kanban

Customer onboarding

In progress1

Validate received documents

High

Check customer details, contract and attachments.

Docs
1/2
AAna

Done0

Demonstration · illustrative data

Live proof

The conversation ended with a card, not with “I'll write it down later”.

The most honest Kanban scene is not dragging a card: it is the moment information leaves the conversation and becomes a task with an owner — without anyone retyping what was already said.

  1. Starting point

    In chat, the accounts payable team has just reviewed an invoice with Skyller: supplier, amount and due date are on screen. The “Accounts payable” board exists, with the stages Received, Under review, Awaiting approval, Approved, Paid and Rejected.

  2. What happens

    1. 01You ask: “open a card in Accounts payable with this and make Marina the owner”. Skyller builds the card with supplier, amount and due date in the right fields — not buried in the description.
    2. 02Creating a card is reversible, so by default Skyller just creates it — stopping at every card would turn building a whole board into a queue of approvals. The card lands in Received, Marina is told it is hers, and anyone who wants the brake can require it for that function.
    3. 03Two days later Marina drags it to Awaiting approval. The Invoice field is required at that stage, so Skyller asks for what is missing before letting the card through.

  3. Result

    What was discussed became a task with an owner, a due date and a stage — and the history shows it was born from a conversation, with who approved it and when.

What this scene does not promise

  • Skyller does not decide on its own what becomes a card or what is a priority: it acts when someone asks. There is no automatic reading of what “should” become a task.
  • There are three views — board, table and calendar. There is no timeline, Gantt chart or gallery; if your process depends on those, check first.
  • Confirmation is the default on what cannot be undone — creating a board, removing a column and archiving a board. Creating, moving and commenting on a card are reversible and go straight through; your company can tighten or loosen the rule per function, in either direction.

Scene with a fictional company, supplier and people; the stages, the required fields and the notice to the owner are the product's.

To evaluate carefully

What the board keeps, who sees it, and what the AI may touch.

Select a topic to see its capabilities, conditions, and limits.

Three views, one board
Board with drag and drop, Table with filters and bulk actions, Calendar by due date. The starting view is each person's preference; switching on the spot does not change anyone else's.
Fifteen field types
Text, long text, number, currency, date, date and time, checkbox, single select, multi-select, person, URL, email, phone, rating and relation.
Filters that match the numbers
Search by text, assignee, status, priority and due-date window (overdue, today, next seven days, no date). What the filter returns is exactly what the number at the top counts.

Getting it running

From the first board to a routine that runs itself.

This is not a project: it is picking one process that today lives in the group chat and giving it stages, fields and an owner. The rest comes with use.

  1. 01Whoever knows the routine

    Picks a ready-made board or describes the process so Skyller proposes the stages and fields.

    The six ready-made boards already bring stages and fields; describing it builds a board to measure.

  2. 02Whoever knows the routine

    Adjusts the fields the operation actually uses and marks which are required at each stage.

    Required fields are per stage — they keep a card from advancing without the missing information.

  3. 03Administrator

    Decides where the board lives (hub or workspace) and who can see it.

    Visibility can be private, inherited from the workspace, or shared person by person.

  4. 04The team

    Uses the board day to day and asks Skyller, in chat, to open and move cards.

    Sensitive actions stop for confirmation; the per-function policy is set by the company.

  5. 05Whoever follows up

    Filters by the numbers at the top and sets up the routines that should appear on their own.

    A recurring card respects the card limit of its target stage.

Included

  • Six ready-made boards with stages and fields: Tasks, CRM, Recruiting, Content, Logistics and Accounts payable.
  • Board, Table and Calendar with the same filters and the same numbers.
  • Due-date alerts for the people responsible: due within 24 hours and overdue.
  • Comments, change history and simultaneous editing without overwriting.

Your company decides

  • Which fields exist, which are required, and at which stage.
  • Where the board lives and who sees it: private, workspace-wide or shared.
  • Which AI actions ask for confirmation before they happen.
  • Which routines become recurring cards, at what time, and with what limit per stage.

Frequently asked

What usually holds the decision back.

Start with the board that hurts

Pick a process that today lives in the group chat.

Accounts payable, sales pipeline, candidate screening, the weekly check. Build the board in minutes from a ready-made one and see the difference between having owner, stage and due date as fields — instead of in someone's memory.

Try it freeBook a demo