Build the baseline and send
Sell your first SAL service · Step 4 of 5
This is the proof layer for the selected proposal, not a second product. Capture what happens today so the client can see the current path and compare it with the launched version later.
Observe three operating gaps
Response
Enter through the same source a real lead uses. Record the sent time, first-reply time, whether the response came inside or outside business hours, and who answered. Do not turn one test into a universal response benchmark.
Build the evidence sheet
Use Coworker to turn the observations into a concise baseline attachment. It must preserve timestamps and evidence types and leave unknown values blank.
Use Coworker skill sal_proposal. Continue the selected draft with operator-observed baseline evidence and create a complete CCS only when every required input is supplied.Screenshots and timestamps are evidence. A benchmark without a source, an assumed close rate, or a guessed number of lost leads is not.
Attach, send, and book the meeting
Put the baseline beside the selected SAL path in the draft, finish the scope and price review, then send the proposal. Book the proposal meeting only after the client has the document.
In the meeting, agree on the first operating measures before launch: for example first-response time and qualified handoffs. Add bookings or sales only when the client reliably records them. After launch, repeat the same check; that before-and-after becomes the evidence for the monthly service.