Blank task cards and a folder illustrating an organized administrative handover.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

Start with one administrative result you can demonstrate, rather than offering to handle anything a client needs. Define the input, the work you will return, the response window and the decisions that remain with the client. A small, reviewable service is easier to explain and price than an open-ended promise of availability.

This is an independent service-planning guide. Fovza has not managed a client's inbox, sold a virtual assistant package or verified marketplace approval or payment. The samples below are proposed exercises using fictional information, not customer work or a claim of professional experience.

Choose the task before the marketplace

Fiverr's virtual assistant category lists administrative work such as scheduling, data entry, file conversion and coordinating meetings. That establishes a service category, not demand for your offer or eligibility to sell from every location. Specialized tasks can need expertise beyond ordinary administration.

Source: Fiverr virtual assistant services. Checked 2026-10-26.

Choose a task whose result you can inspect. A spreadsheet cleanup might return a consistently formatted file and a list of entries needing the client's decision. An appointment service might return proposed time slots and a conflict list. Neither description gives permission to change prices, commit the client to a meeting or resolve a business dispute.

Write down what must arrive before work starts. If a cleanup needs a column definition or a scheduling task needs time-zone information, make that dependency visible. The service should not rely on guessing what the client meant by a vague label or an incomplete instruction.

Make a sample with fictional information

For an editorial inbox-triage example, create a few fictional messages: a meeting request, a supplier question and an issue requiring the owner's decision. Return a proposed label plan, draft responses and an escalation list. Keep the sample separate from a real mailbox so demonstrating the service does not require access to someone else's information.

Explain the choices. A message asking for a date can become a proposed reply; a message asking for a price exception may need escalation. The point is to show that you can recognize the decision boundary, not simply move every item into a folder.

For a data-cleanup sample, keep the original file and identify what changed in the returned version. Describe ambiguous cells instead of silently inventing missing information. A tidy output that hides assumptions can create more work for the client than an unfinished item clearly marked for review.

Do not attach a famous company's name or an invented testimonial to the sample. Describe it as a demonstration. No outcome from this exercise establishes that a paying customer would choose the service.

Agree on the response window and handover

A task completed in a scheduled batch is different from continuous customer support. State when you review new inputs, when the client can expect a handover and what happens to a request that arrives outside that window. Avoid calling a service immediate if your actual process includes waiting for another person to review it.

Define the unit of work. It could be a particular file, a stated batch of records or a recurring review period with an agreed workload. Include the format of the deliverable and how the client will accept or query it. A revision that corrects an error in the agreed work differs from a request to add a new task.

Use a short handover record: work completed, assumptions made, decisions still needed and the next agreed step. Keep urgent or blocked items visible. If progress depends on the client's answer, say so rather than presenting an estimate as a finished result.

Separate technical access from permission to act

Google's Gmail delegation documentation says a delegate can read, send and delete email, while being unable to change the account password. Those capabilities can be broader than an inbox-labeling assignment. A tool allowing an action does not establish that the client authorized it for this job.

Source: Google's email delegation documentation. Checked 2026-10-26.

Agree which actions you may take and which need review before enabling access. For example, preparing a draft, sending it and deleting the original message are separate actions. Start with the access needed for the agreed task and use the service's supported permission process. Do not make password sharing a demonstration requirement.

Discuss where work files will be kept, what information may be copied and how access will end. Use fictional or properly anonymized information in your portfolio. A completed assignment does not create permission to publish the client's messages, contacts or internal procedures as examples.

This guide has not assessed an actual client's account settings or data obligations. Resolve those requirements for the real arrangement before accepting work involving information you cannot handle appropriately.

Price the work around the full process

Include time learning the workflow, checking the input, doing the task, reviewing the result and answering questions. If a task needs access setup or repeated clarification, those are part of the commitment even when they do not produce a visible output cell.

A fixed package needs boundaries that make the workload predictable. An hourly arrangement still needs a definition of authorized work and a way to record time. Neither model makes an unclear brief disappear. Do not choose a price by copying a marketplace's lowest visible listing without checking what it includes.

Before using a marketplace or billing service, read the current fees, location eligibility, dispute and payment rules that apply to the account. This guide does not verify a net hourly rate, tax treatment or first-payment date. A displayed seller price is not money a new provider has received.

Use the first completed assignment to revise the offer

After an assignment, compare the agreed scope with the actual work, questions and time involved. Keep acceptance and payment as separate events. A file being delivered, a client approving it and a payment arriving answer different questions about the service.

If the task repeatedly needs decisions outside your brief, narrow the offer or agree on a different service before continuing. If the same question appears in each handover, improve the input instructions. The useful measure is a process you can repeat accurately, not the number of unrelated duties on your profile.

The remote-work guide compares client services with employment and occasional research. Virtual assistance belongs in the client-service category: its flexibility comes with duties, communication and boundaries that still need to be agreed.