Programmatic SEO
Pricing virtual assistant services and support
A client asking for "general support" may expect inbox cover, research, scheduling, customer replies, document work, and urgent availability. Convert that broad need into task families, capacity, access rules, and response boundaries before quoting.
Who this is for
This page is for a virtual assistant or solo operations specialist preparing an offer for a real client.
The pricing question
Which recurring tasks, service hours, systems, response times, and approval limits belong in the support package?
Practical example
For example, Grace quotes $1,600 per month for 35 hours covering 2 inboxes, 1 calendar, weekly research, document formatting, 2 status updates, and a 1-business-day response target, with unused hours expiring monthly.
What to decide before you send the price
Ask before quoting: Which tasks recur? Which tasks are occasional? How much volume exists? Which systems are used? What access is required? Which actions need approval? Who sets priorities? What response time is expected? Are fixed coverage hours needed? Who handles urgent issues? Also confirm data sensitivity, customer contact, languages, meeting load, documentation quality, reporting needs, holiday cover, handover rules, and purchasing authority.
A defined scope can include inbox triage, calendar coordination, research, data entry, document formatting, meeting preparation, travel research, and weekly status reporting. Assume working access, documented processes, a named priority owner, and timely approvals. Exclude bookkeeping, legal work, specialist design, sales closing, personal errands, round-the-clock coverage, cash handling, account ownership, complex automation, and tasks requiring unapproved purchases unless specifically included.
Offer a Task Block for a fixed list and capacity, an Operations Support option adding recurring coordination and reporting, and a Coverage option with agreed daily windows. Use one onboarding review for process corrections and require feedback on completed task samples. Unclear priorities, fragmented instructions, repeated context switching, extra meetings, shared passwords, urgent weekend requests, and approval bottlenecks can reduce usable capacity.
A weak scope says, "Provide flexible admin help as needed." A clear scope says, "Use the monthly capacity for the named inbox, calendar, research, and document tasks during agreed service hours, report remaining capacity weekly, and request approval before external commitments or purchases." Define whether unused hours expire and how urgent work is queued. Capacity reserves time; it does not create unlimited availability.
- Group recurring tasks by system, volume, and approval level.
- Set service hours, response targets, and urgent-work rules.
- Use named client accounts and secure access methods.
- Track capacity and report remaining time consistently.
- Require approval before purchases and external commitments.
FAQ
Should virtual assistant work be sold by hours or tasks?
Use the model that makes capacity and outputs clearest. A package can combine named task families, a time allowance, response targets, and rules for unused capacity.
How should a VA handle access to client systems?
Use client-owned accounts, individual permissions, secure credential sharing, and clear approval limits. Avoid shared personal logins where the client can create proper access.
How can I check a virtual assistant offer for gaps?
Use the free OfferForBusiness preview to surface missing task, capacity, access, approval, and availability decisions before you edit the complete offer.
Pricing for other services
Useful glossary terms
Read next
Prepare your own offer
Describe the service and the client situation, then see a free preview with the gaps, the scope creep risks and a draft of your packages before you send a price.
See a free preview of your offer