For sales and support: seeing what's coming before customers ask
By Soumen Sarkar · October 2026
For you. When agents build fast, sales and support often meet a change at the same moment as the customer. With Campfyrr you open one page to see what's being worked on, read plans before they ship, add a customer's words to the part of the product they affect, and answer the agents' questions from a link. It doesn't read your inbox, calls or CRM.
What does a sales or support day look like right now?
You find out about a change when a customer does. A ticket arrives asking why the export button moved. A prospect asks on a demo call whether the new pricing screen is live yet, and you aren't sure. The change was planned and built in an engineer's session, often in a single afternoon, and the first place you could read about it is the release note, if there is one.
Meanwhile, you know things the agents building the product don't. A customer told you on Tuesday that refunds must include shipping. A prospect needs an export that opens in their accounting tool. That knowledge sits in your notes, a ticket or a Slack thread. Claude Code's own docs say each session "begins with a fresh context window", so the next agent working on refunds starts without it.
None of this is anyone's fault. Agents are the best collaborators a team has had, and they build what they're told, fast. What breaks is the path between the people who talk to customers and the work. So the review falls on you, or on the customer (when review falls on the business).
What changes for you with Campfyrr?
- You see what's coming on one page. Each project has a "Where are we?" view written in plain words. It lists what's being worked on now and what each change will do when it lands, what landed in the last two weeks, what's waiting on someone, and the latest published plans and sample outputs. It has a link you can pass around (how people outside engineering follow the work).
- You read the plan before it ships. A session can publish its plan or a sample output as a page with its own link (publishing plans and results). You read it and say "a customer will ask about this" while it's still a sentence to change.
- Your customers' words reach the agents. From the "Where are we?" view, choose Tell the agents something. Pick "A customer said", "Pricing", "A deadline" or "Something else". Pick the part of the product it affects, or the whole project, and add what it means for the work if you know. Before an agent changes that part, its area brief lists your words under From the business.
- You answer from a link, not a meeting. When an agent isn't sure, it states an assumption and keeps building. Each assumption has its own page. If it's a customer question, it can be sent to you. Choose "Right, keep going", one of the likely answers, "Correct it…", or "Not mine to check" to pass it on. Claude Code lets a hook add context before each prompt (Claude Code hooks), and Campfyrr uses that so the session reads your answer at its next turn (feedback that reaches the agent).
What doesn't Campfyrr do?
Be clear about this before you try it:
- It doesn't read your inbox, listen to calls or pull from your CRM. Someone adds the customer's words, in a sentence.
- It isn't a support tool or a tracker. Tickets and deals stay where they are today.
- It doesn't write release notes or tell customers anything. It tells you, early, so you can.
- It has no audit logs yet. Don't use it as a record of what you promised a customer.
What are the first three things to try?
- Open the project's "Where are we?" view. Read what's being worked on now, and note one change a customer will notice.
- Choose Tell the agents something. Add one thing a customer said this week, against the part of the product it affects.
- Ask a developer to send you the next assumption about customers. Answer it from the link.
The idea behind this is build on what's coming: you prepare for a change while it's being built, not after a customer finds it. For how customer context reaches the work, read getting what the business knows to the agents.
What's free for sales and support?
Everything, right now: Campfyrr is free for everyone during early access. When paid plans start, teams pay for developers. Business teammates who only read and answer stay free (pricing). A developer on your team installs it from /connect and invites you.
The problem this answers: Review falls on the business: "Building is so easy that reviewing the output has fallen on our customers and business teams."
The principle behind this: Build on what's coming: Unfinished work is a promise, and a promise can be built on.
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).