A structured kickoff converts enthusiasm into documented scope before billable hours start.
Why kickoff calls matter
Filipino VAs often get hired after a short chat. The kickoff is where you lock details before billable hours pile up.
Skip structure and you will rebuild scope from memory later. That is when scope creep and payment fights start.
45-minute kickoff agenda
| Block | Time | Goal |
|---|---|---|
| Intro and roles | 5 min | Who decides what |
| Goals and success | 10 min | What "win" looks like in 30 days |
| Task list and exclusions | 15 min | What is in / out of scope |
| Tools and access | 5 min | Logins, channels, file storage |
| Rhythm | 5 min | Hours, updates, meeting cadence |
| Next steps | 5 min | First deliverable and date |
Run new clients through the Client Red Flag Checklist before you deep-plan work.
After the call (same day)
Send a recap email:
Thanks for the kickoff. Here is what I captured: Scope: [bullets]. Exclusions: [bullets]. Tools: [list]. My hours: [PHT window]. First deliverable: [item] by [date]. Reply "confirmed" or edits by [date].
Do not start heavy work until they confirm or you note their silence and your assumptions.
Common mistakes
- No agenda so the call becomes a friendly ramble.
- Skipping exclusions ("we will figure it out later").
- No recap email within 24 hours.
- Promising dates before you check your other clients.
Final thoughts
A good kickoff call saves weeks of confusion. Clients feel heard. You get a paper trail. Both sides know what happens first.
How Salag helps
- Client Red Flag Checklist. Screen risky clients before you invest kickoff time.
- Payment Method Risk Check. Confirm how and when you will get paid for milestone one.
- Project Scope Calculator. Turn kickoff notes into hour and price estimates.
Move safer. Not faster.
In short
A freelance kickoff call should end with written scope, tools access, communication rules, and first deliverable date. Use a simple agenda so excitement turns into a plan, not vague hope.
Common questions
A freelance kickoff call should end with written scope, tools access, communication rules, and first deliverable date. Use a simple agenda so excitement turns into a plan, not vague hope.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
ALIGN means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.
