Launch is not maintenance unless you priced maintenance.
8 min readWhy post-launch trips up VAs
You finish a big push. The client goes live. Then the pings start: small bugs, content tweaks, "can you just check this."
Each ping is small. Together they eat a free retainer. Filipino VAs building sites, funnels, or launch campaigns see this often.
Define support before launch
| Term | Example |
|---|---|
| Launch date | When you hand off final files |
| Included support window | 14 days, bugs tied to your delivery only |
| Response time | Next business day, not instant |
| Exclusions | New features, third-party outages, training |
| After window | Hourly rate or new maintenance package |
Put this in the agreement or launch recap email.
Launch handoff checklist
- Deliver final assets and admin access list.
- Document known limits ("form does not integrate with X yet").
- State support end date in writing.
- Show how to request support (email ticket, not random DMs).
- Invoice final milestone tied to launch approval.
Support boundary message
Launch is complete as of [date]. Included support covers bug fixes on delivered work through [date]. New requests after that are billed at [rate] or via our maintenance block.
Common mistakes
- No support end date so "launch week" becomes launch quarter.
- Fixing third-party plugin issues for free forever.
- Training the whole team without training hours in scope.
- Starting phase two before final launch invoice is paid.
Final thoughts
Launch is a milestone, not a blank check. Clear post-launch boundaries help clients plan maintenance and help you move to the next paid project.
How Salag helps
- Freelance Readiness Checker. Check agreements for support windows before go-live.
- Late Fee Calculator. Price ongoing support blocks after included days end.
- Scope Creep Detector. Flag small post-launch asks that are really new scope.
Move safer. Not faster.
In short
Post launch support freelance work needs a written end date and clear rules. Launch means the site, campaign, or deliverable goes live. Support after that is either included for X days or billed separately. Do not assume "launch" covers forever fixes.
Common questions
Post launch support freelance work needs a written end date and clear rules. Launch means the site, campaign, or deliverable goes live. Support after that is either included for X days or billed separately. Do not assume "launch" covers forever fixes.
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.