What the company record says about AI

What the profiles contain

Every published company profile was read for an AI operating practice: a described way the company uses AI in how work, hiring, or decisions run. Product category labels are not that.

This overview was reconciled on 16 October 2026 with the eight AI sections reviewed on 5 October. The counts describe this site's evidence, not how many companies use AI or which company gets the most value from it.

Shopify: a resourcing rule and shared work

Shopify’s profile documents AI in resourcing, shared work, and review. These are company accounts, not an independent measure of productivity.

The resourcing rule

In April 2025, Tobi Lütke made reflexive AI use a baseline expectation. Teams asking for more headcount had to show why AI could not meet the need. AI use went into performance and peer reviews. The profile reads this as a planning constraint, not a tooling suggestion. The instrument was a founder memo, the same form Shopify has used for other resets. (Wall Street Journal, 8 April 2025, as cited on the Shopify profile.)

Shared work, with the decision left to a person

River is an AI agent used in shared Slack channels rather than private messages. Teammates can join the threads, and the work stays searchable. At publication on 28 May 2026, Shopify reported that River coauthored one in eight merged pull requests. The profile treats that as contribution share, not a causal productivity gain. (Under the River.)

Quick, documented 10 June 2026, is the internal host for interactive tools and other web artifacts. Shopify reported more than 50,000 created sites and participation from over half its employees, with sites accessible to all employees. Those figures are dated and company-reported. (Quick.)

A 2 September 2026 security account keeps the decision with engineers. River validates findings against current code, keeps the investigation in a shared thread, and escalates approval and merging to engineers. After merge, it checks whether the vulnerability is resolved. (How River takes security work from a fix to merge.)

The September Helix account adds checkpointed app migration: behavior tests, visual review, two independent agent code reviews, and engineer approval by default. Engineers can choose autonomous mode; the other gates still apply. (Helix.)

Zapier: fluency becomes a people process

Zapier’s January 2026 account describes early experiments that became a company-wide program. It reports daily-work AI usage of 63% in late 2023, 77% at the end of 2024, and 97% more recently. In March 2026 the company reported 100% adoption. The posts do not establish a shared denominator for those readings. Theprofile treats them as company-reported usage, not measured productivity gains. (How Zapier rolled out AI,Raising the AI fluency bar.)

The process the profile documents, beyond the usage number:

• In late 2025 Zapier created a Chief People & AI Transformation Officer. The profile treats that as an organizational change, not as proof that every project uses one ownership template.
• By March 2026, AI fluency was assessed throughout hiring. AI use was part of onboarding and performance expectations.
• The March hiring update adds accountability for outputs as an explicit assessment dimension.

Inference. Decide how a new capability enters hiring and onboarding, and track use separately from whether quality, delivery, or customer results improved.

Buffer: a bounded build week

Buffer’s August 2026 Build Week recap describes 72 participants directing their own AI-assisted projects. The company reported 112 projects completed and 57 internal tools live by the end of the week. The profile treats those as company-reported event outputs, not a controlled measure of productivity. (Build Week 2026, on the Buffer profile.)

Access preceded the event: in February 2025 Buffer made every teammate eligible for $250 a year for AI tools and encouraged sharing experiments. That post does not establish uptake or whether the allowance was unchanged later. (AI tools stipend.)

The Build Week account also records limits: two help-center editing tools were paused over security and write-access questions, and an application-screening agent stayed local during security review. The 57 live tools are event output, not proof of lasting adoption or lower maintenance cost. (Build Week 2026.)

Automattic: literacy and documentation review

Automattic’s profile records an expectation of AI literacy and competency that varies by role. The current hiring page is undated; it does not establish when that expectation began. (How We Work.)

A July 2026 WooCommerce account describes an internal plugin that watches releases and documentation requests, drafts updates, and checks their quality and formatting. A writer reviews each draft in a preview and approves it before publication. A terminology automation also inserted writing guidance into live pages by mistake. This is a documented review workflow with a reported failure, not a net time-saving study. (AI documentation project.)

37signals: prompt-first work with senior review

In the July 2026 account on the Basecamp profile, DHH says most fixes and feature upgrades now start with a prompt. Designers and product managers can make an idea work on a branch and show it on a beta with real data. Ruby or JavaScript changes from a designer or junior programmer need a more senior review before merge; some generated code was discarded after creating technical debt. These are founder statements, not an adoption or productivity study. (REWORK, 1 July 2026.)

Fried also describes a larger menu of candidate work as a reason to limit how much the product changes at once. Faster implementation did not remove the need to choose. (Same episode.)

Todoist: shared context through DoistOS

The Todoist profile documents the April 2026 launch of DoistOS. Chase Warrington, who led the launch squad, describes a shared AI workspace connecting internal tools, company context, and reusable workflows through plain language. He describes a company-wide launch. This is an employee account of availability and purpose; it does not establish usage, output quality, or time saved. (Warrington.)

GitLab: platform and functional ownership

GitLab’s profile separates the central platform from each function's priorities. Enterprise AI owns platforms, standards, and the interface to security, legal, and privacy. Each function has an AI Transformation Owner; champions help colleagues experiment and adopt the shared patterns. The handbook describes the intended model, not proof that every function follows it. (Enterprise AI.)

Its September 2026 training account combines a self-assessment with role-specific learning paths. Daily interactions with the primary internal coding tool rose 22.3% one month after AI Ladders launched. The post does not name the tool, sample, or comparison group. It measures activity, not a productivity gain. (AI fluency playbook.)

Linear: agents work inside the issue

An April 2026 account on the Linear profiledescribes engineers delegating a first pass to an agent while keeping the issue assigned to themselves. A coding agent reviewed every pull request, with a human engineer giving final approval. Customer Experience and product managers also use agents to scope issues, group requests, and draft specifications. (How we use Linear Agent.)

A June account reports 50% more issues created and pull requests merged between January and March on one team. Another describes an unsuccessful attempt to fix every incoming bug, followed by two narrow automations that still require human review and merge. These are scoped operating accounts, not a company-wide productivity result. (Reviewing code,Teaching an agent to auto-fix bugs.)

GitHub: a reporting change, not a practice

On 11 August 2025, Thomas Dohmke announced he was stepping down as CEO. The announcement placed GitHub and its leadership team within Microsoft’s CoreAI organization. The profile’s inference is that this leadership transition does not show whether GitHub’s documented engineering communication practices continued, and it does not describe an internal AI adoption process. (Goodbye, GitHub.)

The profile’s industry line names AI pair programming as part of what GitHub sells. That is a product description, not a record of how GitHub’s own teams work with AI.

Learnings

These follow from the profiles above. They are labeled inference where the profiles do not state them as a company practice.

• Usage is not an outcome. Zapier’s profile says its adoption percentages do not measure productivity. Shopify’s profile says River’s pull-request share and Quick’s site counts do not establish effects on hiring, retention, morale, or total productivity. Buffer’s Build Week numbers are event outputs.
• The eight accounts describe different changes.Inference. Access, a shared workspace, a review gate, functional ownership, and a hiring expectation solve different operating problems. Compare the mechanism and its limits; the record does not establish one adoption sequence or a ranking.
• Delegation still needs a review boundary.Inference. Shopify, 37signals, Automattic, and Linear give concrete examples of where a person reviews or approves work. Use those examples to specify who accepts a result in a local trial; they do not prove one approval rule fits every task.
• Name who carries the change after rollout.Inference. GitLab names platform and functional owners; Zapier connects fluency to hiring, onboarding, and performance. Their accounts justify examining ownership and reinforcement separately from access. They do not isolate which step caused an outcome.

Two profiles without internal operating evidence

The GitHub andWolfram profiles do not document an internal AI operating practice. GitHub's CoreAI placement is a reporting change; Wolfram's AI product descriptions do not establish how its own workforce uses those products.

Absence from a profile is not a claim that the company does not use AI. It is a claim about what this site has published. A practice gets added here when it is sourced on the company profile first.