Claude and Jinxo: Get the Client Kickoff Agenda Out of One Person's Head and Into the Group Chat
A small consulting firm signs a new client. Good news. Now somebody has to write the kickoff agenda and the prep list, and the team chat fills up with "who is doing the agenda?" while nobody starts. It gets written from a blank page the night before, by whoever feels guilty first. The cost is small

Posted on Oct 30 • Originally published at learn.ynteractive.com
A small consulting firm signs a new client. Good news. Now somebody has to write the kickoff agenda and the prep list, and the team chat fills up with "who is doing the agenda?" while nobody starts. It gets written from a blank page the night before, by whoever feels guilty first.
The cost is small each time and it never stops. Every new client repeats it. And when one person drafts it alone in a private AI chat, the team still has not seen it until the morning of the call.
I run Stepthrough, free hands-on AI and software training for white-collar workers, and I tested a different setup: put Claude in the group chat with the team. The tool is Jinxo, a group chat for people and their AI bots. (This is my own lesson, not an official Jinxo course, and there is no partner link here. Its Terms say Jinxo is free right now but may not always be.)
The example firm, Quillfield Consulting, and its client, Henderson Dental, are made up. The screens I describe are real, captured in October 2026.
The usual flow is: open Claude alone, ask for a draft, copy it out, paste it in the chat, and explain what it is.
This flow is: ask in the room, and the answer lands in the room. Everyone reads the same draft, and the team edits one document instead of starting from nothing.
This is the part that trips people up, so it helps to know the shape first. One half is in Jinxo. The other is in claude.ai. Until both are done, the Claude row in Jinxo says Not connected yet.
Claude's Free plan allows only one custom connector, so check that you are not already using it.
Treat that connection link like a password. There is no sign-in step on this connector, so the link is what stands between your room and anyone who has it. Do not paste it into a ticket, a doc or a chat.
Once connected, Tool permissions lets you choose when Claude may use each Jinxo tool. Leave approval on while you are learning. You will see exactly what Claude is about to do, such as sending a message, before it does it. You can loosen it later, once you trust the pattern. Starting loose and tightening after a surprise is the wrong order.
In Jinxo, start your message with @Claude and say what you want back, with limits. Vague asks get vague agendas. The two details that help most are the length of the call and how many prep items you want:
@Claude We have a kickoff with Henderson Dental on Tuesday at 10. Can you draft a 30-minute agenda and three things we should prep? Enter fullscreen mode Exit fullscreen mode Then tell Claude to go read it This is the step people miss. Your message in Jinxo does not wake Claude up by itself in this setup. In a new claude.ai chat, check that the Jinxo connector is on under + and Connectors, then ask Claude to read the request and post its answer back in the room.
You will see a line like Using jinxo-...: Send a message. That is Claude using the connector to post. Depending on your permissions, it may ask you to approve first.
Back in Jinxo, the message showed Read by Claude, and the group chat had a new reply. In my run, the agenda had five timed blocks:
Below it were three prep items: research the practice, draft an access and data checklist, and bring two or three quick-win ideas. Claude ended by offering to tighten it once we knew who was attending from the client's side.
Claude writes a fresh answer each time, so yours will not match this.
It is a first draft. Read it and fix what does not fit the client. If the agenda lists a detail about the client you never gave it, check that detail and remove it if it is not true. Do not ask the client to confirm something your AI made up.
Every bot in the room can read the room. Keep private client details out, especially while you are learning. Practice on made-up or low-risk details first. A kickoff agenda needs the client's name and a time. It does not need their contract.
Keep it for low-stakes drafts first. An agenda is a good first job because a mistake costs a minute of editing. Get comfortable here before giving a bot anything that goes outside the team.
The time saved on one agenda is modest. The real change is that the blank page and the "who is doing this?" thread both go away. The next kickoff starts from a draft everyone can see.
The free lesson walks you through all of it in a practice copy built from real Jinxo and claude.ai screens. It checks your work as you go, and nothing touches your real accounts.
Practice adding Claude to a Jinxo room and drafting a kickoff agenda