Patrick Gallagher

@ChrisJBakke @signulll That EA is dead then, right?

Well, as a founder I always paid myself minimum wage, often worked from the time I woke up until bedtime six days a week, and then would sometimes be unable to sleep over decisions I made. As a bigco exec, I made millions and millions of dollars per year for attending 15 meetings per week and approving some performance reviews, but one time my EA booked me economy instead of business class on a work trip to Japan. So I’d say it’s pretty equal.

which job is more difficult? vp/svp at a big co. or startup founder & why?

@rwalk_xyz So they sent you the same MSA as us, copy that.

Founder after discovering the enterprise agreement requires SOC 2 compliance, a 12-hour breach notice, unlimited indemnity, customer audit rights, and service credits for downtime caused by the customer.

@0xSero I'm pretty sure you are... ?

FFmpeg but for LLM inference, who's building this?

@DJ_CURFEW We either 100X or we almost die for the 5th time trying.

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

@nickfrosst @cohere Woah... How did you guys crack the hallucination rate?!?? You're more than 10 points better than the next closest model 🤯

Command A+ from @cohere is out now :) its our best model yet and its open source apache 2.0

@KatieKeithBarn2 You still have that pesky Kinsta Cache problem 😄

Here are before-and-after pictures of the WordPress 7.0 admin redesign. The left nav is a definite improvement, but the overall look and feel still looks dated due to the grey backgrounds in the main column. Hopefully that's the next phase.

@ivanburazin Plus they're expensive AF. You can't spend more money unless you're giving someone else margin on top of it.

Building agents on hyperscaler infrastructure is like building a sports car on a truck chassis. Hyperscalers were built for stateless workloads. You don't want your web app to change on the fly. You just want it to be stable, predictable, and immutable. Their entire architecture was designed around that assumption. Agents are the opposite. They need state. They need to pause and resume. And they need to run until the job is done (not until a timeout kills them)

Have you tried Hermes yet? I just discovered an easy way visualize the AA Omniscience benchmark across both programming languages and subject matter. That data was always there but it's easier to click through and see it now. Which means it's easier to automate a browser agent into keeping that information top of mind for future work. So, for example, you can see that you absolutely must use GPT5.5 for Rust... but Gemini is way better for PHP. (I might be remembering these specifics wrong but you get the idea) For healthcare they're all terrible etc. (That one I definitely have it right LOL) All of which is to say: the further I get down this rabbit hole the more clear it is to me that the harness definitely matters more than you think. Buuuut there is at least as much alpha to be scooped off the table by tightly coupling specific models with specific desired functionality outputs. Right harness for the model: probably 20% lift. Right model for the specific language: another 20% lift. Less context rot: always a meaningful win. Planning and scoping, planning and scoping. Thinking through building the right things and not getting lost in the weeds. You end up arriving at super narrowly scoped functions that you really wouldn't want to reduce and/or it's so little Repeating Yourself that it's probably OK. AKA: you're doing the same amount of programming but it's all in English.

I've been bouncing between Codex, Claude, OpenClaw, and I just took the new Gemini harness, aka Antigravity, for a spin yesterday. I think the term Polyagentmorous. With this workflow, I feel like my context often gets overloaded, and I've been finding myself hunting around and trying to remember which sub-project within which macro-project, within which harness I was working in. So I'm trying a new agent harness instruction approach. I am prioritizing an AGENTS.md file over a harness-specific file (CLAUDE.md). I am also adding a task to create and update a HUMANS.md file in global instructions across all harness apps. My hope is that I can jump into a project folder in Finder and quickly see where I used that project last and when. robb.ee/s/agent-harnes…

@ivanburazin It's only three orders of magnitude. You got this.

And here I thought Daytona was doing well

@mikhail_b_ I would caution against this. Get a domain that is your authentic brand, not your brand with an asterisk at one of the bookends. Better to get something like GetFireFighter.com and call your thing FireFighter. You should want to wear your own swag.

Finding a domain name for a WP-only product is a lot easier than finding one for more general software. You can just use {something}wp com and you’re good to go 😀

@Shpigford We have 10K+ servers on our platform and we're iterating on version 4 of how this should be done. Would love to know what you specifically need. I think dashboards show way too much. You should see nothing, unless you specifically want to see it. Fires or Nothing.

who's building sysadmin dashboards for people who hate sysadmin? like, grafana for humans.

@HankYeomans @Shpigford The name of my company is GridPane but I bought GridPain.com also.

@Shpigford like “single pain of glass?”

@Elliott_EcomMfg There's an utterly absurd concentration of ultra precision spline gage and master gear expertise literally in one three mile stretch of road in Warren, Michigan. Closest competition to those handful of companies is halfway around the world in Asia.

American supplier of high precision tooling component abruptly closed last year. Their pricing was very good, which leads me to believe it was an elderly person running the operation with pricing from 20 years ago. Everyone is calling around to get the part, turns out everyone was buying from the same guy.

So I used to buy a lot of real estate domains and thankfully I let all but a handful lapse. One I held on to is EverythingAgent.com It's not short but... I don't know. Seems like somebody might want that one. What with people building agents that can do everything.

@ClementDelangue Unfortunately nobody is able to run them fast. Nobody normal/non-enterprise anyway. Go give them $1500/month and see which models they'll let you run. It ain't this one. Nothing current. Their SotA model that you can buy today is GLM4.7 it's pointless.

I remember when people were saying "It's useless to open-source big models because nobody will be able to run them fast"....

@naval And my daughter is failing!!! 😩

The latest IQ test involves data centers and water.

Game, set, and match, Miss Navratilova!

@RinodeBoer @brendyn_m GridPane powers hundreds of thousands of WordPress websites. Our users have connected our platform to over tens of thousands of servers in 325+ datacenters in every major metro on the planet. Yes, we have a lot of data 😄

@gridpane @brendyn_m What kind of platform are you talking about? Because it sounds like you have a lot of data.

The biggest risk for WordPress may not be the platform itself. Maybe its the economics around it. WordPress itself can't really fail because it's open source, and it can adapt to agentic workflows. But if millions of small businesses need to rebuild their sites in the upcoming few years and realize WordPress is overkill for simple static or semi-dynamic websites, a lot of money leaves the ecosystem. Less money means less innovation, because you need money to keep great talent around. And you need enough customers for companies to justify investing serious time and energy into the ecosystem. That might be the bigger threat than any direct feature comparison. Please convince me otherwise.

@brendyn_m @RinodeBoer Not everyone experiences a slow backend or hard to use WP admins. I have anecdotal observations, just like yours. And biases too, I have plenty of those. But I also have hundreds of thousands of data points from 10K+ agencies/users on our platform.

@gridpane @RinodeBoer That’s fair. In our agency the number of clients wanting a better outcome than the clunky, hard to use WP admin UI and slow backend speed is exploding. We get weekly questions about what else is out there for them. So we’re switching them with each new rebuild Outcomes > tools

@Erwin_AI Have you seen the price of RAM recently? LOL Do you actually need that 256GB? Because you're pay through the nose for it, no matter where you go.

Wow I just found out that Hetzner changed some of their server types. My EX130R used to be 130eur/mo for 256GB RAM, 2x2tb. Now if you want 256GB RAM, the cheapest option is 1k eur/mo. That's 8x price increase 🤯