Skip to main content
pulse
Talk to founder
blog · 5 cornerstones · 17 satellites

The company brain argument, in twenty-two pieces.

Five cornerstone essays make the case for team AI as a category. Seventeen satellite essays support and extend it. Each post is built around a single argument and the visual that proves it.

Cornerstones

5 arguments
Cornerstone 0111 min

The case for team AI over individual AI

Individual AI knows what one user told it. Team AI knows what the team did. The five capabilities that only emerge when an AI is attached to a team instead of a person.

May 14, 2026Read →
Cornerstone 0212 min

Process graph vs document graph

Why every enterprise AI search tool indexes documents, why that flattening loses the structure that makes team knowledge valuable, and what a process graph unlocks instead.

May 12, 2026Read →
Cornerstone 0310 min

The 5 to 500 software team segment

There are roughly 200,000 software companies globally that have outgrown consumer AI but cannot reach enterprise AI economics. The structural reasons the middle is empty.

May 10, 2026Read →
Cornerstone 0412 min

Auto extracted Skills from observed work

Human authored agent workflows go stale the moment they are written. Auto extracted Skills stay current because they reflect what teams actually do, and they travel across every Skills compatible AI tool.

May 8, 2026Read →
Cornerstone 0511 min

Why AI tools should never train on your company's data

Every AI vendor uses the same privacy language. The differences underneath are enormous. The four structural commitments worth looking for, and why policy promises rarely survive competitive pressure.

May 6, 2026Read →

Satellites

17 essays
Satellite 067 min

Why your team keeps re debating the same architectural decisions

Documentation drifts. Tribal knowledge decays. New employees do not trust documents they did not help write. The compounding cost of decision decay, and the structural fix.

May 4, 2026Read →
Satellite 077 min

The hidden cost of senior engineer departure

Salary plus recruiting is the line item companies measure. It is the smallest part of the actual cost. Architecture knowledge, decision rationale, and customer context walk out the door.

May 2, 2026Read →
Satellite 088 min

Glean vs Pulse, an honest comparison for software teams

Glean is genuinely strong in five categories. The structural reasons it cannot serve the 5 to 500 segment. How to decide which fits your team without adjudicating vendor politics.

Apr 30, 2026Read →
Satellite 097 min

Why Notion AI alone is not enough for engineering teams

Notion AI is strongest inside Notion; its connectors return search hits from the rest of the stack. Engineering teams need the decisions and commitments behind those hits, kept as records.

Apr 28, 2026Read →
Satellite 107 min

When does a software team need a company brain?

Seven concrete signals that mean your team is paying the institutional memory tax. Three signals that mean you should wait. A decision framework that prevents premature tool adoption.

Apr 26, 2026Read →
Satellite 118 min

The trust problem with enterprise AI tools

Four diagnostic questions every AI vendor should answer with a clean yes or no. The deflections to watch for. Why structural commitments survive competitive pressure and policy ones do not.

Apr 24, 2026Read →
Satellite 127 min

Five questions your AI tool should answer with sources

Sentence level attribution is the difference between a verifiable answer and a plausible one. Five concrete questions to ask any AI tool, and the architectural reason most tools cannot deliver it.

Apr 22, 2026Read →
Satellite 139 min

How a 50 person engineering team should evaluate AI knowledge tools

The five step buying framework: audit the pain, define the must haves, shortlist three options, do real evaluation, pilot before commit. Plus what to skip at this scale.

Apr 20, 2026Read →
Satellite 148 min

Beyond chat: why the next generation of AI tools will be proactive

Reactive AI waits for a prompt. Proactive AI surfaces what you did not know to ask. Five push patterns, the three reasons most teams ship proactive AI badly, and why it is the next wave.

Apr 18, 2026Read →
Satellite 157 min

The Anthropic Agent Skills standard

A portable file format for AI procedures, written once and loadable by any compatible tool. The three structural shifts the standard unlocks, and what to look for as a buyer.

Apr 16, 2026Read →
Satellite 167 min

How to onboard new engineers in weeks, not months

Three friction sources eat the first 60 days of every new engineer. None of them are solvable by writing more documentation. The structural fix changes the question from days to hours.

Apr 14, 2026Read →
Satellite 177 min

Why human authored AI workflows always go stale

Three mechanisms drift every documented procedure. Humans adapt to staleness; AI agents execute it literally. The structural fix is workflows extracted from current behavior, not human written specifications.

Apr 12, 2026Read →
Satellite 188 min

Atlassian Rovo vs Pulse, choosing team AI for the modern stack

Rovo's strengths inside Atlassian are real, and its connectors now reach beyond it. The difference is shape: search hits versus structured decision records. Plus the trust posture change of April 2026.

Apr 10, 2026Read →
Satellite 198 min

The new shadow IT, managing personal AI agents

Productivity pressure plus consumer priced AI plus capability gaps equals shadow AI agents at every software company. The four categories of new risk, and the three responses that actually help.

Apr 8, 2026Read →
Satellite 207 min

Calibrated confidence, why your AI tool should tell you when it is unsure

Most AI tools show confidence as absent or fabricated. Real calibration requires outcome tracking, recalibration, and per workspace adjustment. The three questions to ask any vendor.

Apr 6, 2026Read →
Satellite 216 min

Who keeps your company's facts true?

A captured fact slowly stops being true, and on most teams nobody is accountable for noticing. Stewardship routes one maintenance task to one owner when a fact ages, drifts, or two sources disagree, with a human always deciding truth and no per-person scores.

May 31, 2026Read →
Satellite 226 min

Your team's knowledge doesn't fit seven boxes

A vendor, an incident, an experiment rarely fits a fixed schema, so it gets flattened into a note and loses its structure. Custom entity types let teams define their own kinds with custom fields and optional extraction, as shared workspace types or types private to one person.

Jun 3, 2026Read →

See the argument in product.

Every essay describes a product invariant Pulse already enforces. The live demo is walkable end to end without signup.

Talk to founder
How it works