The week engineering outran the company
By Soumen Sarkar · October 2026
Story. When agents help engineering ship five features in a week, sales, support and product hear about them in whatever order the news happens to reach them. Give the whole company one shared record and one "where are we" link, and everyone learns what shipped at the same time, from the same page.
What happens when engineering ships faster than the company can hear?
This story is a scene, built from how teams work with agents today. What comes after it is real.
It's Monday, a little after nine, and I'm sitting in the corner of Priya's office with a coffee going cold. Priya is the CTO of a company that sells scheduling software to clinics. Six engineers, a product manager called Leo, a sales team of four led by Grace, and Omar, who runs support on his own most days.
Priya is reading the week's plan off her screen. Five things the clinics have asked for: a waiting list, text reminders, a printable day sheet, a faster search for patients, and a setting to block out lunch breaks. Last quarter, that list would have been a month. She says this out loud, half to me, half to herself.
By eleven, the engineers have their sessions running. I walk the floor and watch over shoulders. The agents are a joy. One reads the booking code and lays out a plan for the waiting list in six clear steps. Another finds the old search, explains why it's slow, and fixes it before lunch. Nobody is waiting on anybody.
On Tuesday afternoon, the faster search ships. The engineer who built it posts a line in the engineering channel. Priya reacts with a rocket. Nobody outside that channel sees it.
On Wednesday morning, Omar gets a ticket from a receptionist at a dental clinic. "The patient search looks different. Did something break?" Nothing broke. Omar doesn't know that. He spends forty minutes testing it himself before he walks over to ask an engineer, who says, cheerfully, "Oh, that shipped yesterday."
On Wednesday afternoon, text reminders ship. Grace is on a call with a clinic group that's been asking for exactly that for months. She tells them it's on the roadmap for next quarter. She means it. It's what the roadmap said when she last looked.
On Thursday, the lunch-break setting and the day sheet ship, an hour apart. A clinic manager emails Omar to say thank you for the day sheet. Omar forwards it to Leo with one word: "What?"
Leo reads it twice. He wrote the brief for the day sheet three weeks ago. He knew it was coming. He didn't know it was this week, because his status meeting with engineering is on Friday.
On Thursday evening, Grace's clinic group gets a newsletter from the marketing site with "Now with text reminders" in the header. Their buyer forwards it to Grace with a question mark. Grace closes her laptop and goes home.
On Friday at ten, the status meeting. I sit at the back. Priya walks through the five features, one by one. Every one of them works. Every one of them is something a customer asked for. And around the table, I watch three people learn, for the first time and out loud, what their own customers learned on Tuesday, Wednesday and Thursday.
Nobody did anything wrong. The agents built exactly what they were asked, well and fast. The engineers posted where engineers post. Leo held the meeting he always holds. The news simply travelled at the speed of each person's habits, and the habits were built for a month, not a week.
Priya asks me afterwards what she should change. I tell her to change one thing.
I come back two weeks later.
Every session now writes down what it did and why, in plain words, to one shared record. Each evening, every engineer's day is added to the project's daily update without anyone writing it. Each finished task posts a line to a shared channel, the one sales and support already sit in. And there's one link, pinned at the top of that channel: "Where are we?"
It's Tuesday, eleven in the morning. The waiting list ships. A line appears in the shared channel: what finished, and what it means for a clinic, in words a receptionist would follow.
Omar sees it before any ticket arrives. He opens the "where are we" page, reads two lines about how the waiting list works, and writes a short reply he can paste when the first question comes in. It comes in at two. He pastes it.
Grace sees it from a client's waiting room. She opens the link on her phone, scrolls past what's being built to what landed this week, and adds the waiting list to the deck for her three o'clock. I'm on that call. Her client asks about it before she gets to the slide.
Leo doesn't wait for Friday. He's already read the plan the session published on Monday, and he answered one of the agent's assumptions from its link while he was on the train: "Clinics want the waiting list ordered by who asked first, not by urgency." The agent read his answer at its next turn and built it that way.
On Friday, the status meeting is twenty minutes shorter. Nobody reads a list of what shipped. Everyone has read it. They spend the time on the one call only people can make: which clinics to tell first.
I leave as Grace and Omar are writing that announcement together, from the same page.
Here's what I want you to notice
The agents were brilliant both weeks. The engineers were too. Speed was never the problem. What broke was the order in which people found out.
In the first week, every team learned about the work from whoever happened to reach them first. Support learned from customers. Sales learned from marketing. Product learned from a forwarded email. Each person's way of hearing news was fine for a month of work. It failed for a week of it.
Stop relying on the status meeting to tell the company what shipped. At agent speed, the meeting arrives after the customers do. Put the news in one place, in plain words, as it happens, and send everyone the same link.
And notice what the change cost. No new meeting. No new sign-off. Nobody slowed engineering down to let the company catch up. The record was written by the work itself, so the company caught up on its own.
What's the proof?
- Faster building exposes the gaps between teams. Google's DORA team, in its 2025 report announcement, says "AI doesn't fix a team; it amplifies what's already there," and that "AI accelerates software development, but that acceleration can expose weaknesses downstream."
- Finding things out already costs a lot of time. Atlassian's State of Teams 2025, drawn from 12,000 knowledge workers and 200 executives, found that leaders and teams lose about a quarter of their time just searching for answers.
- The pace in this story is our own pace. In the week of 13 to 19 October 2026, our own repository recorded 84 commits, and the features in it landed days apart, some hours apart (our field note for that week).
- The habit in this story works today. Campfyrr adds each person's day to the project's daily update at 18:00 in their time zone, in plain words. It posts each new decision and each finished task to a Slack channel you connect. And one "where are we" page per project shows what's being worked on, what's waiting on whom, what landed in the last two weeks, and the latest published plans and results (how people outside engineering follow agent work).
What Campfyrr doesn't do: it only reports what is recorded in it, so work nobody logs doesn't appear. It posts to Slack but doesn't read Slack. It doesn't know what's deployed; "landed" means finished and recorded. It doesn't replace your tracker, your release notes or CI. People who only read and answer join free (pricing).
What do I do on Monday?
- Connect your engineers' Claude Code sessions on /connect.
- Ask each session to log what it did and why, in plain words.
- Connect the project to the Slack channel sales and support already read.
- Open Activity and copy the "where are we" link.
- Pin that link in the channel.
- Send it to product, sales and support before the next status meeting.
- Keep the meeting for the decisions only people can make.
Then, at the end of the week, ask your support lead one question: how many features did a customer tell you about first?
For the problem in full, read silos at agent speed and what shipped. The idea behind it is let the work speak.
The problem this answers: Silos at agent speed: "Engineering moves at agent speed, but product, design, QA and the business still work in separate silos."
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).