Build the brief around the work you need done.
Tell us what needs to get done, the hours you need covered and the tools your team uses. You can choose a role or describe a blend of related responsibilities.

What would make the biggest difference?

Start with the work. Be specific about the outcome.
“Help with billing” is a starting point. “Prepare invoices from approved job files, flag missing approvals and maintain a weekly follow-up list” gives the conversation a clear direction.
Before you share your hiring brief.
Can I ask for offshore or part-time support?
You can describe the working location, budget range, time-zone overlap and hours you need. The working arrangement, cost, candidate fit and availability must be confirmed for your brief. The directory does not promise a particular rate or saving.
Will the person use our existing software?
List the tools your team uses and the tasks performed in each one. Agree training, access levels and review responsibilities before work begins. Naming a tool on a role page does not mean every candidate has that experience or that a software licence is included.
Who makes technical or financial decisions?
Keep approval authority explicit. A support professional can prepare records, draft estimates and follow agreed processes. Your authorized reviewer remains responsible for technical scope, pricing, payment approval and other decisions assigned to your business.
What happens after I prepare a brief?
Review the details and choose how to share them with our team. The next discussion should establish responsibilities, workload, working hours, access, supervision and commercial terms. Preparing a brief does not confirm a placement or start date.
