Run the proposal meeting
The proposal is sent. Make one scoped decision, then carry the selected playbook into setup.
Meeting contextBeauty & Aesthetics · Consult to BookedTurn WhatsApp ad inquiries into booked consultations · United States · English proposal
Change selectionSell your first SAL service · Step 5 of 5
The proposal and baseline are already with the client. This meeting is not another discovery round. The client should leave with one clear decision: approve the selected package, adjust its scope, or stop.
Before the meeting
- Confirm that the client received the proposal and baseline.
- Bring the observed evidence and know which statements came from the client.
- Decide the setup and monthly price before the meeting.
- List the real setup inputs: channel access, business information, qualification fields, business-hours behavior, and the human handoff owner.
Rehearse it in Coworker
Ask Coworker to play the client, raise realistic objections, and force a scoped answer. It should use the selected offer and price context without inventing loss metrics.
Role-play the proposal meeting for this SAL service. The proposal and baseline are already sent. Act as the client, raise realistic objections, and help me reach one scoped decision without invented loss metrics.The walkthrough
- The client outcome. Name the selected playbook in plain business language.
- The current path. Show only observed response, qualification, recovery, and handoff evidence.
- The prepared package. Explain what SAL handles and what the client’s person continues.
- The operating scope. Confirm channels, questions, handoff destination, follow-up, agency responsibility, and proof plan.
- The decision. Confirm the price and ask whether the client wants to adjust or start setup.
A clean close is: “If this scope is right, we can start setup and establish the first baseline with your team.”
Common objections
- “We already reply fast.” Compare that belief with the timestamps you collected; do not argue from a benchmark.
- “We tried a bot before.” Show the actual path: one useful question at a time, then a human handoff with context.
- “It is expensive.” Reconfirm the implementation and monthly operating responsibility. Do not defend the price with invented lost revenue.
- “We need everything integrated first.” Offer the smallest useful version that can run safely, and list the integration as a later scope item.
- “Let me think about it.” Agree on one follow-up date and send the scoped decision in writing.
After the yes
Create the client company, connect the required channel, load the client’s business information, configure the selected qualification and handoff, then test the complete path before launch.
