How do I show non-technical teammates what our Claude Code agents are building?
By Soumen Sarkar · October 2026
Short answer: Publish it to them in plain words, with a link: plans before the work, test results and sample outputs as it lands, and a short daily update. Let them answer the questions that are theirs from the same page, so their answer reaches the agents too.
Why don't demos and tickets work any more?
When agents ship in a day what used to take a week, a weekly demo shows work that's already old, and a ticket status says "done" without saying what it does. The founder, the product manager and support find out what changed when a customer asks. And the product questions agents run into wait for the next meeting.
What should they see, and when?
Three things, each written for someone who doesn't read code:
- The plan, before the work. What's going to change and why, in a few sentences, so anyone who knows better can say so while it's cheap.
- Test results and sample outputs, as the work lands. "All the refund tests pass, including partial refunds." "Here's a sample export: one row per invoice." Proof they can understand, not a diff.
- A short daily update of what landed, in plain words. See landed.
Each one is a page with a link. People talk about it wherever they like, in Slack, in a meeting or on a call, but everyone looks at the same page.
How do they answer back?
From the same place. When an agent makes an assumption about something that's theirs, such as pricing, a customer promise or a deadline, they confirm or correct it in a line, and the next session follows the answer. Nobody has to pass it on.
How do you set it up?
With Campfyrr, a Claude Code session can publish a plan, test results or a sample output as a page with one command, and share the link. The day's work goes out in plain words, and business teammates who only read and answer are free. See how product managers keep up with what agents are building, and the team's Activity page.
Words used here
- Activity: Activity is Campfyrr's one page per project: a read-only feed of the team's decisions, actions and status updates, each written as what happened and why it matters.
- Assumption: An assumption is the best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
- Landed: Landed means work that finished, shown with what it turned out to be compared with its plan.
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).