Jilu

Ninety days. One team. A record that stays.

The pilot is how a team produces its own evidence: one team runs Jilu on its real work for 90 days, against success criteria both sides agree before any data connects.

One team. Ninety days.

What is included

One team, up to 50 seats. The team gets full platform access for the agreed scope.

Length

90 days from kickoff to the end-of-pilot review.

Next step

Request access, then a scoping call. The call names the team, the workflow to evaluate and the criteria before any data connects.

Review

An end-of-pilot review against the agreed criteria. The team decides the next step with the record in front of it.

Setup

Hands-on. Jilu builds the first boards with the team and agrees the success criteria before any data connects.

A working company brain for one team.

01

First boards, built with the team

Jilu builds the team's first knowledge boards alongside the people who will use them, from the team's real work. The boards organise by topic from the start, so the team reads a map of its own work instead of a pile of summaries.

02

Collecting across the team's tools

From the start, Jilu collects in the background, across the tools the team already uses. Nobody stops to write anything down, file summaries, or mark decisions by hand.

03

Decisions carry their sources

Every decision carries the reasoning behind it: who decided, when, and what the decision rested on, with the sources attached. Anyone can follow the path instead of trusting a summary.

04

The agent, answering in the thread

The team mentions the agent where the work happens. It answers from the record and shows its sources, and it says so when the record does not hold the answer.

05

Onboarding from the boards

Anyone who joins the team during the pilot learns how the team works by reading the boards. The record carries the context a handover meeting cannot.

From daily work to a record people can trust.

One piece of knowledge takes the same path every time. The steps below show the full route: the review loop that decides what becomes record, and the updates that flow back as the work changes.

Step 1

The work happens

The team works as it already does. A pricing call runs over chat, a decision lands in a document, a ticket changes hands, a meeting settles a question.

ChatDocumentsTicketsMeetings
Step 2

Jilu keeps collecting

Jilu follows the connected tools in the background and gathers the work as it happens. The team adds no step to its day.

Step 3

The sources are kept

Decisions and facts are taken out of the work with their proof attached: the message, document, ticket or meeting each one rests on, who was involved, and when. A claim with no source does not join the record.

Step 4

Sorted into boards

Knowledge sorts into boards by topic. A decision sits beside the work it changed, the people who made it, and the decisions that came before it.

Step 5

Every page passes draft, review and publish

Pages the agent builds from the stream start as drafts. An owner checks the draft against its sources and approves it, or sends it back. Only approved pages become company record.

FirstDraft

The agent builds a page from the work Jilu collected, with the sources attached.

ThenReview

A named owner reads the draft, checks the evidence, and corrects what is wrong.

ThenPublish

The approved page joins the boards as record, dated and sourced.

Step 6

People reach it two ways

The record serves the team directly, with no agent in between, and through the agent when a question is faster to ask.

Read the record

Any employee with permission opens a board and reads how the company works: decisions, facts, and the reasoning behind them.

Ask in the thread

The team mentions the agent in chat. It answers from the record, shows its sources, and names the gap when the record runs out.

Step 7

Updates flow back

Work changes, and the record changes with it. A new fact extends the entry and carries its own date; the earlier entry stays visible. When two sources conflict, Jilu shows both versions and a person resolves the conflict in the open.

Loop

Collecting keeps running from step 2, so the record shows the work as it stands this week. Nothing on the record is overwritten silently.

Ninety days, in four phases.

The four phases below are the plan for how a pilot is designed to run. The pilot runs hands-on. Jilu works with the team directly while the record takes shape, and a short weekly check-in clears the review queue, open conflicts, and stale pages.

Days 1 to 7

Kickoff

Choose the sources and the work to test. Confirm the permissions. Agree how success will be measured, and write it down. No data connects before those measures exist.

Days 8 to 30

First boards

Jilu starts collecting from the agreed sources. The first boards take shape with the team, and decisions land on the record with their sources.

Days 31 to 75

The working rhythm

The team works as usual while the record builds. The agent answers in the thread, drafts wait for review, and anyone who joins onboards from the boards.

Days 76 to 90

Review

Both sides score the pilot against the criteria agreed at kickoff. The team decides with the record in front of it.

The record stays either way.

01

The boards

Every board built during the pilot, with the pages the team reviewed and published.

02

The decision record

Ninety days of decisions with their reasoning, people, dates, and sources: the trail the next quarter starts from.

03

A portable archive

If the team does not continue, the archive exports with its source references, and Jilu deletes its copy after the agreed handover period.

Continue, and the record carries over.

At the end-of-pilot review, the team chooses. If the company continues, the published per-seat pricing applies to the seats the company runs, and the boards, the record, and the permissions carry over unchanged. Nothing rebuilds and nothing migrates. A team that starts alone can add further teams once the first one has proved the record works.

Start with one team.

Request access and name the team and the work you want to test. The kickoff sets how success will be measured, before any data connects.

Request access