Skip to content

Connect the dots.

The brief, the decision, the heads-up, the cash forecast, the board update, the postmortem, the answer, the onboarding, the launch plan, the weekly recap and the skill, delivered.

Hatchling is your company brain. It learns from everything, everywhere your team works, and delivers finished work, not chat replies.

See how it worksTry the demo

A company brain: a dot for every message, document, meeting and commit from your tools, linked into one network, with a path lighting up from the source of each result.
Hatchling connects four sources into a brief before the Acme renewal call.

Acme renewal call

Today, 2:00 PM. Ready at 9:41 AM.

What they need

SSO. Their security team won’t sign the renewal without it.source 1

What we promised

SSO by the end of Q4. Priya said it on the September QBR call.source 2

The risk

SSO is set to ship December 8,source 4 eight days after the renewal date of November 30.source 3 If SSO slips, the renewal slips with it.

Next step

Ask Sam, who owns SSO-212, if it can ship by November 30. Bring Priya to the call.

Built from 4 sources you can open.

  1. Slack, #acme, October 2

    “Security won’t renew without SSO.”

    Visible to members of #acme

  2. Zoom, Acme QBR, September 12

    Priya: “We’ll have SSO by the end of Q4.”

    Visible to the Acme account team

  3. HubSpot, Acme

    Renewal date: November 30

    Visible to sales

  4. Linear, SSO-212

    SAML SSO. Target: December 8

    Visible to everyone at the company

Your company brain.

A company brain remembers everything your company knows and puts it to work.

The shared memory of an organization, made usable. A company brain reads everywhere work happens (chat, documents, email, tickets, code and meetings), connects the people, customers and decisions in it, and turns what it knows into results: the answer, the brief, the next step. Every line cites its source, and everyone sees only what they’re allowed to see.

Your company’s memory is two people.

In most 20 to 200 person companies, the real answers live in the heads of a few long-tenured people. Everyone else interrupts them. When they’re busy, work waits. When they leave, the answers leave with them.

The dots are all there. Nobody has time to connect them.

Results, not replies.

A chatbot waits for a question, then hands you a paragraph to check. Hatchling does the work. It gets the brief ready before the call, writes down why a decision was made, and tells you when two sources disagree.

  1. 8:30 AM

    The catch-up.

    Back from a week off? Here’s what changed, before your first meeting.

    While you were out

    October 13 to 17

    • Decided

      The launch moves to November 4.source 1

    • Changed

      Marco now owns onboarding.source 2

    • Waiting on you

      Two design reviews.source 3

    1. Slack, #launch, October 15
    2. Notion, Team page
    3. Linear, DES-41 and DES-44

  2. 11:20 AM

    The heads-up.

    Two sources disagree. It says which one is newer and drafts the fix.

    The billing runbook is out of date

    Runbook, October 2025source 1

    5 retries

    Code, January 14source 2Newer

    3 retries

    Approve the edit

    Drafted for Sam, who owns the runbook.

    1. Notion, Billing runbook, edited October 2025
    2. GitHub, billing/worker/retry.ts, commit 4f2a91c

  3. 2:05 PM

    The decision, and why.

    Someone asks why we dropped the annual plan. They get the record, not a guess.

    Why we dropped the annual plan

    Decided
    March 4, in #pricing.source 1
    Because
    38% of annual customers asked for a refund within 60 days.source 1
    Instead
    Quarterly plans, proposed by Maya.source 2
    Since then
    Refunds fell by half.source 3
    1. Slack, #pricing, March 4
    2. Notion, Q1 pricing review
    3. Stripe, June refund report

One brain. A pack for every team.

Each team turns on its own pack: the tools it reads, the results it gets and the actions it can take. Every pack shares one memory and the same permissions, so adding a team never opens anything new. Pick one.

Choose a team

The deal, with its history.

Before you answer a discount request, you see how the last ones went.

Northwind asks for 20% off

Last two like this
Approved, with a 12-month term.source 1, 2
Decided by
Maya, both times.source 1
Suggested reply
Offer 15% on a 12-month term.
  1. Slack, #deals, March 4
  2. Slack, #deals, April 18

The why, next to the code.

Open a file and see why it’s built that way, and who decided.

billing/worker/retry.ts

Why
Retries are capped at 3 after duplicate invoices.source 1
Decided by
Sam, in #incidents, January 14.source 1
Out of date
The billing runbook still says 5.source 2
  1. Slack, #incidents, January 14
  2. Notion, Billing runbook

The answer, with the policy.

Customers get answers your team can stand behind.

Can Acme get a refund after 60 days?

Answer
Not in full. Offer a move to a quarterly plan.source 1
Over $5,000
Ask Maya before you reply.source 2
  1. Notion, Billing policy
  2. Skill, Refund requests

The week, on one page.

What was decided, what slipped and what needs you.

Week of October 13

Decided
The launch moves to November 4.source 1
Slipped
SSO now ships December 8.source 2
Needs you
Northwind’s discount request.source 3
  1. Slack, #launch, October 15
  2. Linear, SSO-212
  3. Slack, #deals, October 16

Day one, the whole story.

New people learn how things work without interrupting anyone.

Welcome to billing, Lena

Read first
Why we dropped the annual plan.source 1
Ask Sam about
Webhooks and retries.source 2
Ask Maya about
Pricing and refunds.source 3
  1. Notion, Q1 pricing review
  2. GitHub, billing/worker
  3. Notion, Billing policy

How it works

  1. Connect your tools.

    Your tools connect with OAuth, from Slack to Stripe. Nothing to migrate, and nothing for anyone to write.

  2. It connects the dots.

    It reads every message, document, meeting and commit, and links the people, projects, customers and decisions into one graph that knows what changed and when. Every source keeps its permissions.

  3. Results arrive where you work.

    In the desktop app, in Slack, in your inbox, next to the file or the deal, and in the AI agents you already use. Every line cites its source, and you only see what you could already open.

  • It writes itself. Nobody has to document anything.
  • It connects the dots. “The Acme deal” and #acme‑renewal are one story.
  • It shows its work. Every line points to where it came from.
  • It stays current. When sources disagree, it says which is newer.
  • It grows team by team. Each team adds its own pack, and every pack shares one brain.
  • It keeps secrets. If you can’t open a doc, it won’t show it to you.

Connects to everything.

Your tools connect with OAuth. Your agents connect over MCP, A2A, Agent Skills or the API. Nothing to migrate.

  • Slack
  • Microsoft Teams
  • Google Workspace
  • Microsoft 365
  • Notion
  • Confluence
  • GitHub
  • Linear
  • Jira
  • HubSpot
  • Salesforce
  • Zendesk
  • Stripe
  • Zoom

Tech specs

Modules
One core holds every source, fact and permission. Each team adds a pack: the tools it reads, the results it gets, what starts them and the actions it may propose. A pack can run on its own stack. Packs share the core’s memory and permissions, so you add, swap or remove one without touching the rest.
Connectors
Slack, Microsoft Teams, Google Workspace, Microsoft 365, Notion, Confluence, GitHub, Linear, Jira, HubSpot, Salesforce, Zendesk, Stripe and Zoom, through OAuth.
Formats
Messages, documents, PDFs, slides, spreadsheets, screenshots, code, and meeting recordings and transcripts, in one index.
Retrieval
Keyword and vector search over passages, plus a walk of the graph of people, projects, customers and decisions. A reranker keeps only the strongest evidence.
Memory
Every fact keeps when it was true and where it came from, so Hatchling can say what changed and which source is newer.
Permissions
Access lists sync from every source and apply before retrieval. Text you can’t open never reaches the model.
Reasoning
Hard requests are worked in steps: plan, search several tools, draft, check every line against its sources, cite.
Actions
Updates the doc, files the ticket or sends the follow-up in the tool where the work lives. You approve each kind of action, and every change is logged with its sources.
Delivery
The desktop app, Slack, email, the web app, a REST API and webhooks.
Desktop app
For Windows, macOS and Linux. A notification when a result is ready, and a shortcut to ask from anywhere. The web app is the same, in a browser.
Agents
MCP for context and tools, A2A to hand over a whole task, and the open Agent Skills format for playbooks. Every request carries the permissions of the person it works for.
Hosting
In the EU: the app, the database and every model call. One company’s data never reaches another.

One more thing.

Every agent gets the same brain.

Hatchling isn’t another agent, and it isn’t just an MCP server. It’s the brain your people and your agents work from. Claude, ChatGPT, Cursor and your own agents connect the way they already work: MCP, A2A, Agent Skills or the API. Every request carries the permissions of the person it works for.

And it writes down how your team actually works, as skills that people and agents follow the same way.

Skill

Refund requests

Written from resolved Zendesk tickets and the billing policy.

  1. Find the customer’s plan in Stripe.
  2. Within 60 days of purchase, refund in full.
  3. After 60 days, offer a move to a quarterly plan.
  4. Over $5,000, ask Maya before you reply.
  5. Log the outcome in #billing.

Followed by your support team, Claude and your own agents.

Why now

Three things changed. Models can now read a messy thread and say what was decided. Almost every company’s work now lives in tools with APIs. And AI agents can do real work, if they know how your company works. Together, they make a company brain possible now, and needed.

Join the waiting list.

Hatchling opens to a few companies at a time. Join the waiting list and Gianni will email you a link to the live demo: pick a person at a made-up company and ask it anything.

Join the waiting list

Or email gianni.pojani@proton.me

Who’s building it.

  • Gianni Pojani

    Founder