Run the kickoff within 48 hours of signature and keep it to 30 minutes. Here is the agenda, what to send beforehand, and the questions that pull the owner's rules out of their head.
Lumina8 min read
Run the kickoff call within 48 hours of signature, keep it to 30 minutes, and use it to get four things: who owns decisions on the client side, the real answers to your intake questions, a date for every item they owe you, and a plain statement of what the AI will and will not do. If you leave the call without those four, you did not run a kickoff. You had a nice chat.
Most agency owners skip this call or fold it into the closing conversation. That is a mistake, because the week after a signature is when a deal either gets momentum or quietly starts to cool. We covered the mechanics of that week in what happens after your client signs. This post is about the one meeting that sets up all of it.
What is a kickoff call for an AI buildout?
It is the first working session after the contract is signed. The sale is over. The goal is no longer to persuade anyone. It is to turn a client who said yes into a client who is sending you things.
Atlassian describes a project kickoff as the first meeting between the project team and the client or sponsor, held once the scope is final, and warns that it "shouldn't be an 'information broadcast'" (Atlassian Team Playbook). That is the right instinct. If you spend 30 minutes talking at the owner of a plumbing company about how AI works, you have used the call badly. They need to talk. You need to listen and write things down.
An AI receptionist or a chatbot build has a specific wrinkle. The thing you are building is a stand-in for the owner's own voice and judgment. It will answer their phone, quote their prices, and decide when to hand a caller to a human. So the kickoff has to pull out opinions and rules that live in the owner's head and nowhere else. A generic software kickoff does not cover that.
What should you send before the call?
Send two things 24 hours ahead. First, a one-page agenda with the four outcomes above. Second, the intake link from your onboarding path, with a note saying "skim this, we will go through it together."
Asana's kickoff guide makes the same point about preparation: send an agenda ahead of time and leave room for questions (Asana). Their guide suggests 30 to 45 minutes for simple projects and 60 to 90 for complex ones. A single-location service business with one phone line is the simple kind. Thirty minutes is enough if you are disciplined, and the discipline is the point. Owners of small trades businesses will give you one slot. Do not ask for an hour.
Invite the owner and whoever answers the phone today. That second person is the one who knows the ugly details: which callers are time-wasters, which jobs get double-booked, what the owner says when someone asks about a price. If the owner is the only one on the call, ask who that person is and get their name.
How do you run the 30 minutes?
Here is the sequence I use. Times are rough.
Minutes 0 to 5. Restate what they bought. One paragraph, in their words, not yours. "You wanted every call answered, missed calls texted back, and estimate requests booked." Then say what is not in scope. This is the cheapest scope protection you will ever buy, and it matters more for AI than for most work, because clients assume the system will do anything a human receptionist could. Asana puts it bluntly: clarifying scope early and often is the best way to prevent scope creep.
Minutes 5 to 12. Decision owner and the phone line. Who approves wording, prices and hours? One name. If two partners both think they decide, you will hear contradictory feedback in week two. Then the phone: which number do customers call today, who holds the account for it, and can they log in? HighLevel's own setup documentation lists an eligible phone number as a prerequisite for any agent that handles live calls (HighLevel). Who controls that number is a question owners often cannot answer without calling someone, so find out on the kickoff, not in week two.
Minutes 12 to 22. The rules in their head. This is the part no form captures. Ask these out loud and write down the exact words.
What do you say when someone asks "how much for a job like this?" Will you give a range, a flat fee, or a callback?
Which calls should always reach a human, and at what hours? Emergencies, existing customers, angry customers, anyone who says the word "lawyer."
What do you never want the AI to promise? Arrival windows, discounts, warranty terms.
Who calls you the most that you wish you could stop answering?
What is the last thing a customer complained about on the phone?
HighLevel's documentation says an agent needs approved business information for its knowledge base and tells you to test a question the agent should not answer. You cannot write that list without the owner. Question 3 is the list.
Minutes 22 to 28. Dates. Go through every item the client owes you and give each one a day. Logo, hours, service list with price bands, calendar access, the phone decision. Not "this week." Thursday. If they will not commit to a date, say what it delays. "If the calendar access slips to next Friday, go-live moves to the following week."
Minutes 28 to 30. Say the next two things out loud. What you will do tomorrow, and what the first test call will look like. Put a 20-minute test call on the calendar right then. It gives the whole project a deadline the client can see.
What goes wrong on kickoff calls?
Three things, mostly.
The owner does not show up. They send an office manager who says "I'll have to ask him." You can still run the call, but treat every answer as provisional and book a 10-minute follow-up with the owner for the rules section. Do not let that part get delegated, because the office manager is guessing at what the owner would want.
The client treats it as a second sales call. They start asking whether the AI can also do payroll. Write the request on a "later" list, say you will price it separately, and move on. If you start designing add-ons live, the 30 minutes disappears and you will have promised something at no cost.
You skip the written recap. Atlassian lists a written summary and action items sent to all attendees as a core output of the kickoff, and it is the part people drop. Send it within an hour. Five bullets: decision owner, phone plan, the rules they gave you, dates, and the test call time. Reply-all is fine. The point is that when they miss a date, you have a record that they agreed to it.
When is this too much process?
Be honest about the fit. If you are selling a single-service build, say a website with a chatbot for a solo operator, a full kickoff call is overkill. A 10-minute call or a well-written email covers it. The structure above earns its keep on voice builds, where phone numbers, transfer rules and wording all need real decisions.
It also does not fix a slow client. A tight kickoff makes a bad situation visible sooner, which is useful, but you still cannot force a business owner to find their EIN letter. We wrote up the items that usually hold things up in the client intake checklist, and two of them sit behind third-party review queues that no kickoff call can shorten.
When you order a build through the fulfillment platform, you get a 30-minute pricing call for each client build before anything is built, and the client moves into your branded portal afterward. The kickoff is yours, not ours. It is the conversation that makes the intake and the pricing call go faster, because by the time you are filling in the order you already know the client's answers. You can see how the pricing side works under pricing.
FAQ
How long after signing should the kickoff happen?
Within 48 hours. The client's attention is at its peak the day they sign and falls fast. If you cannot get 30 minutes inside two days, send the intake link anyway and book the call for the earliest slot, but do not let a week go by with nothing in motion.
Should the kickoff be on video or phone?
Phone is fine and often better for small trades owners, who are in a truck or a shop. Video helps if you want them to share a screen with their calendar or phone account. Whichever you pick, record it with their permission so you can pull exact wording for the agent later.
Who should be on the call besides the owner?
Whoever answers the phone now, plus anyone who controls the calendar or the phone account. Keep it to three or four people. More than that and decisions slow down.
What if the client cannot answer the rules questions?
Offer defaults and let them react. "Most plumbers we see hand emergencies to a human and give a callback window for quotes. Does that fit you?" People can reject a default faster than they can invent a policy.
Do I need a separate kickoff for each client?
Yes. Use the same agenda, but the rules section is where each business differs, and it is the part that makes the agent sound like theirs. Reuse the template, not the answers.
Your next step
Open your last signed deal, or your next one, and write the four outcomes at the top of a blank page: decision owner, real answers, dated commitments, stated limits. Send that page as the agenda. Then try it against a live build by starting your agency workspace and running a kickoff on the first client you close from the demo.
