Monday
Slack · #auth-eng
The bug is reported, argued about and narrowed down in a thread.
Private beta · One context layer for work
The workspace where work keeps its context
Work lives across conversations, tasks, documents, code, decisions and dozens of tools. IL Co connects the context so work can move without losing the why.
The problem
Your work is scattered across dozens of tools.
Conversations in chat and email. Tasks in a tracker. Code in a repository. Reasoning in documents. Follow one piece of work and it touches four of them — then it moves to someone else.
Tuesday
Linear · ENG-142
It becomes an issue with a title, a status and an owner.
Wednesday
GitHub · acme/api #418
The fix is written, reviewed and half-merged.
Thursday
Token rotation runbook
The reasoning is written down somewhere else again.
Next Monday
Marco Silva picks it up
- Why fifteen minutes?
- Is #418 safe to merge?
- Who decided that — and where?
The information exists. The context doesn't.
Connect
Connect the tools your team already uses.
IL Co connects the context scattered across your tools and keeps it attached to the work. Today, the handoff layer starts with Slack, Linear and GitHub.
Nothing to migrate
Your tools stay where the work happens, and stay the systems of record. IL Co keeps the context between them.
Starts where handoffs happen
Connected today: Slack threads, Linear issues and comments, GitHub pull requests and commits — scoped to what you connect.
Writes only what a person approves
A handoff reaches Slack or Linear only after its author has reviewed it. GitHub is never written to.
The difference
Context stays attached to the work.
IL Co isn't a window onto your tools. It keeps the why attached to each piece of work as the work moves — between tools, and between people.
- Context
- Work
- Handoff
- Continuation
Not a chat window you prompt for answers. Context, kept with the work, carried through every handoff.
Handoff
Hand off the work, and the why.
Handoff is where context matters most. IL Co turns the conversation, the work, the code and the decisions around it into a handoff the next person can act on — and its author approves it first.
01
Around the work
- The conversation · Slack thread
- The work item · Linear issue
- The code · GitHub pull request
- Decisions · recorded in the workspace
- Documents & notes · linked to the work
- Ownership · who has it, who gets it
02
IL Co context
Gathered and kept together. Today a handoff reads Slack, Linear and GitHub; decisions and documents stay linked beside it.
03
Handoff
What was done, why, and what is left — every claim citing its source. Its author reviews and approves it first.
04
The next person continues
With the why, not just the what: accepted from the Inbox, questions asked on it, linked to the work.
- Every claim links to the Slack message, Linear issue or pull request it came from.
- What the sources don't say is marked unknown — never filled in.
- Nothing is posted to Slack or Linear until its author approves it.
One workspace
Then bring the work together.
Handoffs are where IL Co starts. Around them is one workspace, where each piece connects to the others.
Work
What needs to get done — and everything behind it.
A work item has an owner, a status, a priority and a due date. It also keeps what explains it: the handoff it came from, the decision it follows and the Linear issue or pull request it matches.
- Solid rows are IL Co objects. Dashed rows live in Linear, GitHub or Slack — and open there.
- Paste a Linear issue, GitHub pull request or issue, or Slack message link to connect it.
Projects
Where the work comes together.
A project states the outcome it exists to reach, then gathers its work, the people on it, the conversations about it and the handoffs between them.
Conversations
Conversations shouldn't disappear into a chat history.
A conversation in IL Co can be about a work item or a project, and stays attached to it. Mention a teammate, reply in a thread, and link the handoff or Slack thread it continues.
Knowledge
Knowledge stays with the work it belongs to.
Documents, notes and decisions live in one place. Record a decision with what was decided and why, then connect it to the work items and projects that depend on it.
Search
Find the context, not just the document.
One search covers handoffs, work, projects, conversations, documents, notes, decisions and linked Slack, Linear and GitHub objects — and shows where each answer came from.
When nothing in the sources backs an answer, search says “Not enough evidence found” instead of guessing.
The loop
Context that moves with the work.
Every handoff leaves the workspace knowing a little more about how the work got here.
- 01ConnectThe tools your team already uses — starting with Slack, Linear and GitHub.
- 02CaptureConversations, work, decisions, documents and code — attached to the work they explain.
- 03Hand offA source-backed handoff when work changes hands.
- 04ReviewIts author checks it and approves it before anything is posted.
- 05ContinueThe next owner accepts it, asks what is unclear and carries on.
- 06RememberHandoffs, decisions and conversations stay searchable for next time.
Private beta · Currently working with engineering teams
Join the IL Co beta.
We're working with a small number of engineering teams using Slack, Linear and GitHub.
IL Co connects the context around the work so handoffs carry the why — not just the what.
IL Co is currently in development. Early teams will help shape what we build next.
Already have a workspace? Sign in