Jilu

Decisions, kept with their reasons

We are the Company Brain for growing companies.

Decisions lose their why.
Know-how is scattered across heads, Slack threads, tickets and databases.
When people leave, what they knew leaves with them.

Jilu turns daily work into permanent company memory.

Slack logo
Gmail logo
Google Drive logo
Google Calendar logo
Microsoft Teams logo
Microsoft Outlook logo
Zoom logo
Discord logo
Webex logo
Loom logo
Notion logo
Jira logo
Confluence logo
GitHub logo
GitLab logo
Asana logo
Trello logo
Monday logo
ClickUp logo
Linear logo
Figma logo
Miro logo
Salesforce logo
HubSpot logo
Zendesk logo
Intercom logo
ServiceNow logo
Airtable logo
Dropbox logo
Box logo
Microsoft OneDrive logo
Microsoft SharePoint logo

One true record for the whole company.

One workspace for the whole record. New knowledge lands in the right place as work happens.

Ask once. Get the answer and its proof.

Bring Jilu into a Slack or Teams thread. It answers from the record, with its evidence, and only what the asker may see.

# client-onboardingSlack
Portrait of Maya

Maya
@Jilu why did we add a second check for new accounts?

JiluAPP9:41 AM

Jilu · working
  1. Found the original Compliance decisionWorking
  2. Checked the risk reviewWorking
  3. Compared the current policyWorking

The second check was added after the September risk review found gaps in the old process. Compliance will look again once the check has run for a full quarter.

Policy decision · Sep 18Risk review · Sep 12

Jilu joins in. It speaks up, asks, and remembers.

Jilu sits in your Slack and Teams threads and does not wait to be called.

# eng-incidents
Priya2:02 PM

Checkout is timing out again, since the 2.4 deploy.

JiluAPP2:03 PM

This matches the August 12 incident. The cause there was the connection pool, not the code.

August 12 incidentCause: the connection pool, not the codeOn the record
Speaks rarely

Only when a decision has no reasons, a claim clashes with the record, or, mid-incident, the fix being reached for was ruled out before. An admin can limit Jilu to speaking when called, or pause it at once.

# eng-incidents
JiluAPP2:03 PM

Who is leading this, and has the pool been checked before anyone rolls back?

Priya2:05 PM

I am leading. Pool is at 98 percent, same as August.

Incident record
LeadPriya
ApproverMissing — stays visible
Draft
Asks, never guesses

A missing reason, source or approver becomes a question in the thread. If nobody answers, the gap stays visible on the draft.

Incident taken from the threadCheckout timing out since the 2.4 deploy
Draft
Pattern flagged by JiluMatches August 12: the connection pool, not the code
Raised
Thread kept as a memoryKept, searchable, and citable as a source
On the record
Search“checkout timeouts”1 record · from the # eng-incidents thread
Conversations count as memories

Threads Jilu is part of are kept and searchable, under the same opt-in and access rules as every other source. Private one-to-ones stay out by default.

When Jilu joins a meeting, the decisions land on the record.

Jilu joins as a visible participant, or reads the transcript your meeting tools already produce.

Weekly delivery reviewJilu is in the meeting
Portrait of LenaLena · Delivery
Portrait of OmarOmar · Research
Portrait of PriyaPriya · Analysis
Jilu
JiluDecisionThen the draft goes out Monday, with the gaps named.
On the record

A company-wide web, inside the workspace.

The company's records, wiki and sources, browsed in tabs inside the workspace. Each page arrives cleaned down to readable text.

Start with one team. Expand when it works.

Simple per-seat pricing, with a 90-day pilot for teams that want to prove the value first.

Team

$288 per seat / year

$29 per seat / month

Billed annually Billed monthly

$24 per seat / month, billed annually.

$348 per seat / year on monthly billing.

  • Shared knowledge boards
  • The main connections
  • Agent that answers from the record
  • Decision records, kept with their reasons
  • Every draft reviewed and approved by a person
  • Ask Jilu answers, with sources attached

Business

$468 per seat / year

$47 per seat / month

Billed annually Billed monthly

$39 per seat / month, billed annually. For teams that need to control who can read what.

$564 per seat / year on monthly billing. For teams that need to control who can read what.

  • Everything in Team
  • Build the company wiki
  • The company wiki, browsed by hashtag
  • Keep this, captured from the browser
  • All connections
  • Single sign-on (SSO) and audit log
  • Permissions checked on every answer

Enterprise

Custom

For company-wide rollouts and specific requirements.

  • Everything in Business
  • Automatic account setup (SCIM)
  • Your choice of where data is kept
  • Data processing agreement (DPA)
  • Dedicated support

Prices are shown in your currency, converted from US dollars. Billing is in US dollars at this stage.