Compare hourly and per-task VA pricing, when hybrids work, and how Filipino freelancers protect quality and income with ALIGN boundaries.
12 min readIntroduction
Clients often say "pay me by the hour." You want income you can plan around. Task pricing sounds neat until revisions never stop.
Most pricing fights are not about greed. They happen because the billing model never matched the job.
This guide explains hourly vs per task virtual assistant pricing for Filipino freelancers who work with clients abroad. It is not a rate list. You already have market numbers in Filipino VA hourly rates 2026 and rates by niche. Here we focus on structure: which billing unit stops unpaid extra work for this client?
When important details left unwritten stay out of the quote, hourly can feel like a open permission to bill unlimited time for the client. Per task can push you to work faster for less. ALIGN ties your model choice to your costs, your boundaries, and proof of what you delivered.
Why this matters
Many Filipino VAs serve US or AU clients across time zones while living costs are in PHP. The way you bill changes where hidden work shows up.
Hourly with no clear definition of an hour can turn into "just stay online" pressure.
Per task with no revision limit can turn into endless polish for one flat fee.
Hybrid with no rules can let clients pick the cheaper option after you already did the work.
The wrong model does not always mean less money right away. It often means unpaid minutes, guilt discounts, and clients comparing you to the lowest marketplace rate. Read the real cost of undercharging when someone says your task fee should match a $3/hour listing.
Your floor rate (the lowest hourly rate you can sustain after costs) from how to calculate virtual assistant hourly rate still applies no matter what model you use. The model is how you package that floor for this client.
Key concepts
Hourly billing
Hourly billing means you charge for time spent inside agreed scope. It fits messy, interrupt-driven work: inbox triage, CRM updates, scheduling, research that loops back.
To stay protected, write down what one billable hour includes and what counts as extra billable work.
Per task billing
Per task billing means you charge for one defined output. Examples: one blog post formatted and uploaded, one week of social posts scheduled, one batch of CRM records cleaned.
It fits work that repeats with a clear "done" state. To stay protected, set revision limits, input deadlines, and rush fees when the client changes direction.
Hybrid billing
Hybrid billing means you keep a small hourly block for variable admin plus per task fees for repeat deliverables. It fits retainers where most of the week is predictable and some of it is reactive.
To stay protected, use separate caps so clients cannot treat finished tasks as "quick hourly favors."
| Model | Best when | Primary risk if unstructured |
|---|---|---|
| Hourly | Scope shifts weekly; reactive support | Unpaid availability |
| Per task | Repeatable outputs; clear acceptance | Unlimited revisions |
| Hybrid | Mixed admin + deliverables | Client picks cheaper side retroactively |
Salag's ALIGN Protocol framework
ALIGN is a five-step way to turn vague pricing into written numbers and boundaries. Use it before you stack up billable work on the wrong model.
Step 1: Ask how the work actually behaves
Look at the client's last two weeks of requests. Count how many were open-ended versus clear deliverables. If you cannot sort at least 60% of the work, hourly with a cap may be safer until scope settles.
Checkpoint: Can you label last week's work as either time blocks or finished outputs without guessing?
Step 2: List cost drivers for each model
Hourly needs honest hours you can actually invoice. Per task needs time studies for each output. Hybrid needs both. Run floor math before you pick a model just to look "premium."
Checkpoint: Did you connect the model to your floor rate, not to a competitor's screenshot?
Step 3: Install scope boundaries per model
For hourly: define included channels, response windows, and what is out of scope. For per task: define inputs, revision rounds, and turnaround. Link payment timing to VA payment terms examples.
Checkpoint: Could a client skim your quote and know what triggers extra fees?
Step 4: Guard quality and rush rules
Per task pricing breaks when "quality" means unlimited polish. Hourly breaks when "quality" means you must reply instantly. Write rush fees, approval windows, and pause rules if inputs arrive late.
Checkpoint: Is there a written rule for "we need this tonight" that is not your default?
Step 5: Name the model in the agreement
State hourly, per task, or hybrid in the quote and contract. Give examples: "Hourly block covers inbox and scheduling. each blog upload is a separate task fee." If the model is unclear, extra work often goes unpaid.
Checkpoint: If the client forwarded your quote to their cofounder, would the billing unit still be obvious?
Step-by-step guide: choose hourly, per task, or hybrid
- Map two weeks of real tasks. Use time ledger or a simple spreadsheet. Tag each item: open-ended time or defined output. 2. Calculate floor hourly need. Follow how to calculate virtual assistant hourly rate. This number is your anchor no matter which model you sell. 3. If outputs dominate, time-study three deliverables. Record start-to-finish minutes including average client wait you cannot control. Price tasks so that time pays at or above your floor when you spread it over the month. 4. If reactive work dominates, quote hourly with a weekly cap. A cap is the max billable hours included in the retainer. Caps protect you from an "infinite inbox" while the client still gets predictable spend. State the overage rate before work starts. 5. If mixed, split the retainer. Example: 10 reserved hourly admin hours plus task fees for content batches. Do not bundle everything without caps. 6. Write clear rules for when a task is done for tasks. "Scheduled in Buffer with client-approved copy" beats "social media help."
- Write hour inclusions for hourly. Comms, file organization, and reasonable clarifications inside scope. net-new projects outside. 8. Add revision and rush language. Two rounds included. extra rounds billed hourly or per round. Rush under 24 hours needs approval plus a fee. 9. Compare to retainer vs project pricing. Retainer rhythm often pairs with hourly caps or hybrid blocks. 10. Present one recommended model plus one fallback. Clients respect a clear recommendation with reasons, not a confusing menu. 11. Pilot for 30 days. Track the gap between what you quoted and what you actually spent. Adjust task fees or hourly caps with real data. 12. Revisit when scope changes. A new funnel, new brand, or new exec hire usually changes the right model.
Decision rules (illustrative, not market stats)
- Choose hourly when more than half of weekly work cannot be defined as a done state without rewriting scope every Monday.
- Choose per task when the same deliverable repeats with stable inputs and you can time-study it twice without wild variance.
- Choose hybrid when a retainer includes both standing admin and a content calendar with fixed posts per week.
- Avoid pure per task for brand-new clients until inputs and approval habits are proven.
Quality risks to price explicitly
Per task models attract speed pressure. Hourly models attract availability pressure. Write quality as measurable acceptance, not feelings without numbers. Example: "Newsletter draft includes one research pass and one client revision. additional research billed hourly.".
Hybrid billing week map (illustration)
Imagine a week with 12 hourly admin hours reserved and 4 blog uploads priced per task. Monday inbox and calendar sit in hourly. Wednesday uploads sit in task fees. If the client adds "quick" uploads without calling them tasks, your hourly block absorbs unpaid work. Write a rule: new upload batches beyond the included task count trigger task fees or hourly overage with approval.
Common mistakes
Mistake 1: Picking per task to look "simple" while work is reactive
Clients love flat fees. You may absorb chaos. If tasks change daily, hourly with caps is more honest.
Mistake 2: Quoting hourly without defining the hour
"Hourly" with no inclusions can become 24/7 chat duty. Define channels, response windows, and excluded work.
Mistake 3: Hybrid with no classification rules
Without rules, finished tasks get reopened as "small hourly favors." Write which bucket new requests use.
Mistake 4: Ignoring unpaid wait time in task prices
If clients slow approvals, your per task rate must include average wait time, or you add input deadlines and pause clauses.
Mistake 5: Switching models mid-engagement without a written reset
Scope changes justify a pricing talk. Silent switches teach clients that boundaries are optional.
Real-world example
Situation: Jon, a Cebu-based VA, quoted $8/hour for a US ecommerce founder. Work shifted from inbox to product listing uploads to "quick" influencer outreach. Jon billed hours but felt guilty itemizing.
What went wrong: Hourly had no cap or exclusions. Per task was never introduced for repeatable listings. The founder compared Jon to a $4/hour marketplace profile.
ALIGN Protocol fix: Jon tracked two weeks, moved listing uploads to a per task fee with two revision rounds, kept 12 weekly hourly hours for inbox and ops, documented rush fees, and tied payment to payment terms examples.
Outcome: Monthly spend stayed similar for the client. Jon's effective rate rose because repeatable work stopped expanding unpaid. He used rate negotiator language to explain the structure without apologizing for protecting scope.
Final thoughts
Protect your rate with structure before the first invoice. When pricing stays vague, Filipino VAs absorb unpaid rework, midnight requests, and client comparisons to the cheapest bidder. ALIGN keeps the model tied to scope, proof, and payment timing so the number you quote matches the work you can sustain.
You do not need the perfect model on day one. You need a written model you can adjust with data. Start with two weeks of honest tracking. Quote one primary structure. Pilot for 30 days. Then refine task fees, caps, or hybrid splits when you see where time actually goes.
If a client pushes back, treat it as scope talk, not as proof that you are "too expensive." Clear inclusions help good clients say yes faster and help bad fits self-select out before you burn unpaid hours.
How Salag helps
- Pressure-test hourly, task, and package math with rate calculator and rate negotiator
- Compare structure choices against retainer vs project pricing without copying random marketplace numbers
- Track billable reality in time ledger so your chosen model matches logged work
Additional professional context
Global clients often arrive with a preferred billing habit from a past VA. Your job is not to mirror their habit if it breaks your floor. Present the model that protects delivery quality, names boundaries, and matches how the work actually behaves week to week. If a lead refuses written scope either way, treat that as qualification data, not a personal failure.
Filipino freelancers compete on trust and clarity, not on being the lowest line item. A structured quote with explicit inclusions signals professional remote talent. That framing helps during first sales calls calls when clients compare you to anonymous marketplace profiles.
On a phone screen, short bullets and plain labels matter. Name the model in the subject line of your quote email. Repeat the cap or task list in the invoice memo. Small habits reduce "I thought that was included" messages that eat your evening.
When you explain hybrid pricing, use one concrete week example. Clients understand "10 hours admin plus four uploads at $X each" faster than abstract theory. When you explain hourly, lead with the cap and what happens after it. When you explain per task, lead with what "done" looks like and how many revisions are included.
Comparison: structured vs unstructured hourly vs per task pricing
| Dimension | Structured ALIGN pricing | Unstructured guess |
|---|---|---|
| Scope fit | Matched to work behavior | Assumed from marketplace habit |
| Boundaries | Written before work starts | Argued after frustration |
| Revision / availability risk | Named caps and acceptance | Absorbed by VA |
| Effective income | Tied to floor and time studies | Hope-based |
| Client relationship | Easier payment enforcement | Invoice guilt spiral |
When to apply ALIGN Protocol again
Re-run ALIGN when scope shifts, a client adds a second brand, you change from hourly to packages, payment delays eat billable hours, or you niche up and need higher offer rates. Any time important details left unwritten reappear as unpaid tasks, pause and rewrite the model before accepting more work.
Definitions
Floor rate: The lowest sustainable hourly rate given your costs and realistic billable hours. Calculate it with how to calculate virtual assistant hourly rate.
ALIGN Protocol: Salag's five-step method for turning vague pricing into written, protect yourself first numbers and boundaries.
Offer rate: What you quote after floor math, adjusted for niche, urgency, and client risk.
Per task fee: A flat price for a defined output with stated inputs, revisions, and clear rules for when a task is done.
Hourly cap: Maximum included billable hours in a period before overage rules apply.
In short
Hourly vs per task virtual assistant pricing is about matching how you bill to how the work really runs. Hourly fits work that changes day to day. Per task fits work with a clear finished product. As a Filipino VA, pick the model that protects your paid time and your scope. Then write it down with Salag's ALIGN Protocol before you send the first invoice.
Common questions
Hourly vs per task virtual assistant pricing is about matching how you bill to how the work really runs. Hourly fits work that changes day to day. Per task fits work with a clear finished product. As a Filipino VA, pick the model that protects your paid time and your scope. Then write it down with Salag's ALIGN Protocol before you send the first invoice.
Use hourly when work is reactive, shifting, or hard to define as a finished output each week. Admin support, inbox management, and executive assistance often fit hourly with caps and clear inclusions.
Use per task when deliverables repeat with stable inputs and clear clear rules for when a task is done. Examples include weekly social batches, podcast show notes, or CRM cleanup tranches.
Hybrid pricing combines a reserved hourly block for variable work with flat fees for repeatable outputs. It fits retainers with both standing admin and content deliverables.
Neither model automatically pays more. Per task can raise effective hourly income when outputs are efficient. Hourly can protect income when scope expands. Floor math decides sustainability, not the label.
Time-study the task multiple times, include average client wait, add revision buffer, then divide total minutes by 60 and multiply by your offer hourly rate. Add a margin if inputs are unreliable.
Two rounds is a common default for drafts and creative work. State what counts as a round. Additional rounds bill hourly or per round.
Yes if you recommend a primary model and explain when each applies. Do not offer an unstructured menu that lets clients cherry-pick after delivery.
A cap is a maximum billable hours per week or month included in the retainer. Overage requires approval at your stated rate. Caps reduce "infinite inbox" risk.
That is a signal the work is not task-shaped yet. Propose hourly with a cap until scope stabilizes, then introduce task fees for repeatable outputs.
It can, but raise risk until approval habits are proven. Use shorter pilots, stricter input deadlines, and higher rush fees until trust is documented.
ALIGN forces factual capture of how work behaves, cost-linked pricing, written boundaries, quality rules, and named models in agreements before billable work stacks up.
Often yes. Rush fees can be hourly multipliers or flat rush surcharges. Write the trigger: less than 24 hours notice, weekend delivery, or same-day pivot.
Frame tasks as predictable line items within a monthly budget. Show an example week. Clients fear surprise hours more than they fear listed deliverables.
Specialized deliverables (design, copy, bookkeeping batches) often suit per task or hybrid. High-interruption executive support often suits hourly with caps. See niche rate context for how you present your rate to clients, not for picking the model blindly.