Quotes for assistant work depend mostly on hours, the mix of tasks and how much judgment the work needs. Entering data from clean source files is a different job from answering customer emails in your voice. A clear note in the form lets the service partner gauge that before they reply.
Mention any hard limits too, such as tasks that must happen during your business hours, software the assistant must already know, or data that cannot leave a certain system. The partner will come back with questions and, once the picture is clear, a written proposal you can accept or decline.
Information worth sharing up front
These points shape a proposal more than anything else, so mention them if you can.
- The weekly hours you expect the assistant to work
- The mix of tasks, from routine data entry to customer-facing replies
- How much judgment the work needs compared with following a checklist
- The tools and access the assistant will need
- The reporting you want back, such as a daily summary in Slack or by email
- Any confidentiality terms or NDA your business requires
- Whether you want one named assistant or a covered shift
What to expect next
Sending the form starts a conversation and nothing more. A service partner replies by email, often with a handful of questions. You might be asked how tasks are assigned today, who signs off on customer replies or payments, and which apps hold the data.
Many partners like a short call next so they can hear how the work runs in practice. After that comes a written proposal. If it does not fit, say so and ask for a revised one, or let it go. You are not bound to anything until you accept a proposal.