How Automattic Runs a 1,500-Person Global Company With P2 Blogs and No Office

Snapshot

Automattic is the company behind WordPress.com, WooCommerce, Tumblr, and Jetpack. They are also the principal commercial steward of WordPress, the open-source CMS that powers roughly 42% of all websites tracked by W3Techs. (Source) Automattic itself runs WordPress.com (Automattic’s hosted offering) and a smaller portion of self-hosted WordPress installs reach Automattic via Jetpack and WooCommerce — Automattic’s own footprint is a meaningful slice of that 42%, not the whole. About 1,495 employees across 81 countries as of the April 2025 restructuring. No offices, ever — not even pre-pandemic.

What makes Automattic distinct is not that they are remote. It is that they are large and remote: they have navigated the typical scaling breaking points — org bloat, communication fragmentation, culture dilution — without an office as the connective tissue. That makes them one of the most instructive case studies for any distributed company above 100 people.

Core Philosophy

The Automattic Creed is a published statement of operating values, not just an HR artifact. The line that matters most for how the company runs: “I will communicate as much as possible, because it’s the oxygen of a distributed company.” (Source)

Other operating principles that shape daily behavior:

• “I am in a marathon, not a sprint.” — the company actively resists urgency culture.
• “I am more motivated by impact than money.” — stated signal for whom the company hires.
• “I will never pass up an opportunity to help out a colleague.” — collaborative default.

These are not aspirational. They are behavioral expectations codified in a document every employee signs onto. (Source)

Communication Model

P2 blogs are the primary way Automattic communicates about work. P2 is a WordPress theme that turns any WordPress.com blog into a real-time discussion board — like a cross between a team blog and a Slack channel. Teams, projects, divisions, and special interests each have their own P2. The current published statement is that “in addition to Linear, we track our projects on P2-themed WordPress.com blogs, in private chat rooms, and on Slack.” (Source)

Earlier writings by Automattic employees describe ~70% of work happening across more than 150 P2 sites; the company has not published an updated breakdown since. [The specific 70/25/Slack split previously cited here is not present on the current “How We Work” page; treat as historical estimate, not a current published number.]

Explicit communication expectations are published publicly:

1. Communicate often and publicly. Not just occasionally. “It is impossible to over-communicate at a8c.” Be active on P2/GitHub/Slack wherever your project lives.
2. Check notifications at least twice daily. P2s, GitHub, Slack — you’re responsible for staying current. “Never miss a ping.”
3. Set timeframes for every commitment. “Communicate the moment you know you’ll miss a commitment. When you have to be asked twice, it signals you aren’t reliable.”
4. Provide high-level summaries. Clarity about what you’re working on and how it is going, not just status updates.

(Source)

Automattic does not use internal email. This mirrors Basecamp, and for the same reason: email is decentralized and non-searchable across the company. Everything important stays in P2s.

Planning and Cadence

Automattic operates differently from companies running fixed-cycle systems like Shape Up. They ship code to WordPress.com many times per day — historical Automattic engineering writeups have referenced a 60–80 deploys-per-day cadence, though the current published number is not on automattic.com’s how-we-work page — and they maintain multiple large products (WordPress.com, WooCommerce, Jetpack, Tumblr), so their cadence is product-specific rather than company-wide.

What is consistent:

• Data-informed product development. Every feature gets usage metrics collected and reviewed. Launch, iterate, launch again — often immediately.
• Continuous deployment. A one-button deploy system pushes WordPress.com to production. Not sprint-based; continuous.
• Division-level OKRs and planning. In January 2024, Automattic underwent a significant reorganization around three strategic “cards” — “Be the Host,” “Help the Hosts,” and “Neutral” — aligning all teams to their competitive positioning. (Source)
• Travel as a planning mechanism. Individual teams meet for 5–7 day “team meetups” for strategy and bonding. 3–4 weeks of travel per year is standard for employees. (Source)

Decision-Making Model

Matt Mullenweg (founder and CEO) is deeply involved in major decisions, including the 2024 reorganization and the controversial WordPress vs. WP Engine conflict that led to 159+ employee departures.

Below Mullenweg, the company has a relatively traditional executive structure for its size: CTO, CFO, CRO, CCO, and divisional leads (WordPress.com VIP, Jetpack, WooCommerce, Pressable). (Source)

For day-to-day decisions, the model is the same as the expectations document states: people are hired to exercise judgment. “Be brave” means making progress without waiting for permission. “Default to action” over waiting for someone to decide.

For major strategic decisions, the P2 system creates a paper trail: ideas get written up, teams comment, conclusions get documented. It is not consensus-driven — Automattic has real hierarchy — but the default is visible deliberation before decisions are made final.

Org Structure

• ~1,495 employees as of April 2025, after a 16% restructuring (~281 roles) on April 2, 2025. Pre-2024 the company was ~1,900; the October 2024 WP Engine-related severance program took it to ~1,777; the April 2025 layoff brought it to ~1,495. (Oct 2024 source, April 2025 source)
• Organized into product divisions: WordPress.com VIP, Jetpack, WooCommerce, Pressable, and Special Projects.
• Traditional management hierarchy exists — unlike Basecamp’s manager-less model. Directors, VPs, and C-suite are all present.
• Rotation is encouraged. Team members rotate across products. “One of the best things about working at Automattic is the chance to rotate across different teams.” (Source)
• Headcount is not a goal. Automattic deliberately controls growth, viewing team size as something to manage carefully, not maximize.

Tools and Stack

(Source, social post by Beau)

Rituals

Trial project before hire. Every candidate who passes interviews does a paid contract trial project lasting 2–6 weeks before getting a full-time offer. This is not an internship — it is a working engagement where candidate and company both evaluate fit. The trial is done remotely. (Source)

Two weeks in customer support at start. Every new full-time hire — regardless of role — spends their first two weeks in customer support for WordPress.com. This is not optional.

One week in customer support annually. Every employee, every year, forever, does a one-week customer support rotation. Engineers, designers, executives. (Source)

Team meetups, 5–7 days, 3–4x per year per employee. Division and team meetups happen regularly, in locations ranging from Edinburgh to Buenos Aires. The stated goal is bonding and strategy. (Source)

Grand Meetup, company-wide, once per year. Pre-pandemic: annual 7-day company-wide gathering. Post-pandemic: replaced with division meetups. The next Grand Meetup was planned for 2026. (Source)

What They Do Well

• P2s create a searchable, permanent record of decisions. Unlike Slack or email, P2 threads are permanent, indexed, and open to future employees. This compounds over time.
• Customer support rotation closes the empathy gap. Engineers who do support shifts understand user problems directly. No product team is fully insulated from customer reality.
• Trial projects filter for actual fit. Two to six weeks of real work reveals collaboration and communication style in a way that interviews cannot.
• Travel budget as cultural investment. Automattic spends significantly on in-person time for a fully remote company. They have learned — over 20+ years — that purely async remote does not sustain culture without periodic in-person investment.

Tradeoffs and Weaknesses

Founder dependency is real. The 2024 WP Engine conflict showed that Mullenweg’s personal decisions — including controversial public statements and the severance-with-exile terms — directly determined company culture and headcount. In a fully distributed company where the CEO’s voice is already amplified, founder-specific risks concentrate.

159 employees departed in October 2024. The cause was not operational failure but a governance and values conflict around the founder’s public campaign against WP Engine. The lesson: distributed culture is more founder-sensitive, not less, than colocated companies — because there is no physical institutional buffer. (Source)

Communication overhead at four-digit headcount is real. P2-as-primary works at 50 people. At ~1,500 people across multiple products and divisions, the P2 volume is enormous. Filtering signal from noise requires significant personal discipline.

The “communicate as much as possible” norm can invert. The expectation to be active and communicative on P2s, GitHub, and Slack — multiple times daily — can produce performative communication rather than real clarity. The risk at scale is communication quantity crowding out quality.

What Founders Can Copy

Automattic is a >1,000-person case, so most of these practices were built early and matured at scale. The scale notes call out where each is still cheap to start vs. where it requires real investment.

1. Trial project before hire. A 2–4 week paid real-work trial is the single most effective signal of fit, especially for remote roles where communication style matters more than in-person interviews can reveal. (Applies at any scale; cheapest to start at 5–50 because hiring volume is low and the trial coordination is light.)
2. Customer support rotation for everyone. Even one week per year per employee creates irreplaceable customer empathy that no amount of analytics substitutes for. (Applies at any scale; the structural value is highest at 50–500 where the founders can no longer be the customer interface themselves.)
3. Published behavioral expectations. Automattic’s public “Expectations” document is precise and actionable. It says what “good” looks like — not just what the values are. Most companies have values; few have behavioral specifications. (Cleanest to write at 20–100 — the size where you have enough behavioral surface to specify but not so much that the document becomes a spec manual.)
4. P2-style async project blogs. A dedicated async thread per project or team — organized like a blog, not like a chat channel — separates decision-making communication from social noise better than Slack can. (Cleanest at 30–500; above that you need explicit subscription / filtering norms or P2 volume becomes its own noise problem.)
5. In-person time as a cultural investment, not a perk. Budget for it explicitly. Automattic spends enough on meetups that every employee travels 3–4 weeks per year. That is a deliberate operating choice, not an optional benefit. (Most load-bearing at 30–300 — small enough that retreats can move culture, large enough that you actually need them. Above ~500 retreats become divisional rather than company-wide.)

Where This Model Breaks

• When the founder is also the editor of culture. Automattic’s 2024 episode is a cautionary data point: at scale, a distributed company’s culture reflects the CEO’s personal values and decisions more directly than a colocated company would. Cultural drift and founder overreach manifest faster.
• When P2 volume becomes noise. At ~1,500 people, the P2 system’s strength (everything is written down) becomes its weakness (too much is written down for anyone to read). Requires strong curation norms and the discipline to not-read most of it.
• When “communicate more” becomes “perform communication.” The explicit norm to communicate often and publicly can incentivize performative activity updates that create the appearance of alignment without the substance.

Related Practices

• Async Communication — the foundational practice enabling P2-based work
• Remote Onboarding — the trial project and customer support rotation are best-in-class onboarding practices
• Documentation Systems — P2s only work if people write clearly and consistently
• Retreats — Automattic’s meetup model is a masterclass in intentional in-person time

Related Frameworks

• Sync vs Async Decision Matrix — when to use Slack vs P2 vs Zoom

Sources

1. How We Work — Automattic: https://automattic.com/how-we-work/
2. The Automattic Creed: https://automattic.com/creed
3. Expectations — Automattic: https://automattic.com/expectations/
4. First Day at Automattic: https://automattic.com/fieldguide/welcome-to-your-first-day/
5. Automattic’s Big Re-Org (Matt Mullenweg): https://ma.tt/2024/01/automattics-big-re-org/
6. 159 employees leaving Automattic (TechCrunch, Oct 2024): https://techcrunch.com/2024/10/04/159-employees-are-leaving-automattic-as-ceos-fight-with-wp-engine-escalates/
7. W3Techs WordPress usage statistics (primary source for the ~42% CMS market-share figure; note this is WordPress-the-CMS, not Automattic-the-company): https://w3techs.com/technologies/details/cm-wordpress

Inferences

• The P2-first communication system works at ~1,500 people only because Automattic has been building and enforcing the norm since the company was 10 people. A company that tries to adopt P2-style async communication at 200+ people without the cultural foundation will likely see the system ignored or used performatively.
• The customer support rotation for all employees is more structurally important than it appears. At a company of this size with multiple distinct products, it is one of the few forcing functions that keeps all functions (engineering, design, marketing, finance) connected to the actual user experience. Most companies of this size have completely lost that connection.
• The 2024 departures are evidence that distributed companies accumulate organizational risk differently than colocated ones. In an office, employees can visibly observe cultural drift and intervene informally. Distributed, the signal arrives later — and when it does, it comes in the form of a mass resignation.

Work with Alex

If your company is struggling to maintain alignment and culture clarity as you scale beyond 50 people without a physical office, Alex helps leadership teams build the operating systems that prevent this kind of fragmentation.