Processes written down
Every recurring task documented as we learn it. That document is yours, it is the actual deliverable, and it is what makes cover possible.
Virtual Assistant
RunNot one assistant. A desk that does not go on holiday.
Virtual assistant services run as a staffed desk — inbox, calendar, data entry, research and follow-up worked to a turnaround you set, by a trained pool rather than a single person.
Typical stack
- HubSpot
- Google Workspace
- Microsoft 365
- Notion
- Claude
- Zapier
Written for: An owner or operator losing their week to admin, who has been quoted for a dedicated VA and is unsure it is the right shape.
Who it is for
Is this built for a business like mine?Built for businesses where the admin is recurring, not creative.
Delegation works where the work is rule-shaped and repeats. Where it needs your judgement every time, no assistant model helps — it just moves the decision.
What we see
Engineers and founders are doing CRM hygiene, scheduling and inbox triage because it is nobody’s job and it never stops.
What we build
A desk taking the recurring admin — pipeline upkeep, scheduling, research, follow-up — with the process documented rather than learned by one person.
The detail that matters
The documentation is the deliverable. It is yours, and it survives us.
What we see
Listing admin, document chasing and follow-up sit between viewings and get done at nine at night.
What we build
Listing and document workflows worked as a standing queue, with chasing that actually happens on a schedule.
The detail that matters
Chasing is scheduled work here, not something remembered when quiet.
What we see
Product data, supplier emails and order admin expand with every SKU and every channel added.
What we build
Catalogue upkeep, supplier correspondence and order admin handled against your live commerce platform.
The detail that matters
Worked in your systems, so nothing lives in a spreadsheet we own.
What we see
Fee earners are formatting documents, chasing client paperwork and updating the case system between matters.
What we build
Document preparation, client document chasing and case-system upkeep taken off billable people.
The detail that matters
Filed to the right matter with an audit trail, because in this work the filing is the record.
What we see
Client paperwork, renewals and data entry sit with qualified staff whose time is worth several times the task.
What we build
Document handling, renewal chasing and data entry worked to a written standard with a review threshold you set.
The detail that matters
Anything below confidence stops for a person. Approximately right is wrong in this work.
And who it is not for
If you want one named person who becomes part of your team culture, we are the wrong shape and we will say so on the first call. That model has real advantages; consistency of cover is not one of them.
The problem
Do they understand what is actually going wrong?The dedicated assistant is a single point of failure.
One person learns your business, and for a while it works better than anything. Then they take leave, get ill, or leave — and the processes go with them, because they were never written down anywhere except in that person’s memory. You start again, and the second onboarding is slower than the first because nobody documented the first.
Your assistant is on holiday and the work simply stops for two weeks.
Processes live in one person’s head, so cover means re-explaining everything.
When they leave, the context leaves with them and you rebuild from nothing.
Volume doubles for a month and one person cannot absorb it, so the backlog is yours.
What we build
What exactly would I be buying?Document the work, then staff it properly.
The advantage of a dedicated assistant is context. The way to keep that advantage without the fragility is to write the context down — so it belongs to your business rather than to one person — and then put a trained team behind it.
A named lead, a trained pool
One Team Lead who knows your account, with trained people behind them. Continuity comes from the standard, not from one person never being ill.
The AI layer takes the repetition
Data entry, extraction and routine drafting absorbed automatically, so paid hours go to work that needs a person.
A turnaround, not an hours bundle
You buy work completed inside a window rather than a block of hours somebody logged.
How it works
How does this actually function?How a task becomes something the desk can run.
The first time is slow because it is being documented. Every time after that is the point.
Hand over
Document
Run
Exception → back to youReview
Refine
Documentation happens during the first run, not as a separate project nobody funds.
Anything outside the documented case stops and comes back to you rather than being guessed.
Recurring exceptions become new documented rules, so the desk needs you less over time.
What changes
What is different afterwards?What is different afterwards.
The work continues through absence
Cover is a trained pool working a written standard, so leave, illness and turnover stop being your problem.
Turnaround held through holidays and staff changes.
Your processes become an asset
Every task is documented as it is handed over, and that documentation is yours — including if you take the work back in-house.
Documented processes delivered, and owned by you.
Hours go back to the business
Recurring admin leaves the calendar of whoever was absorbing it, which is usually someone whose time is worth considerably more.
Hours returned, by task category.
How we deliver
How does this start, and what do I get at each step?Six stages, and every one has an exit.
You can stop after any stage with something useful in hand. That is the point of naming the artefacts rather than the activities.
- 01
Task inventory
What actually eats the week, how often, and how much of it is genuinely rule-shaped. The tasks we recommend keeping are part of the output.
- Scored task inventory
- Estimated hours per task
- The tasks we recommend you do not delegate
- 02
Access and boundaries
Tool access set up properly, and a written line on what the desk may never do alone.
- Access configured through your systems
- Never-do list
- Confidentiality terms agreed
- 03
Documented handover
Each task run once alongside you and written down as it happens. This is the step that makes the rest work.
- Process documentation per task
- Templates and standards
- Escalation triggers
- 04
Shadow run
The desk runs the work and you review the output before it goes anywhere, until the standard is clearly transferred.
- Reviewed output sample
- Corrections folded into the documentation
- Turnaround baseline
- 05
Run
Full handover with a turnaround target and a weekly report of what was completed.
- Weekly completion report
- Turnaround against target
- Exception log
- 06
Refine
A monthly review where recurring exceptions become rules and the automated share grows.
- Updated documentation
- Automated share reported
- Monthly review
Who runs the desk
How does this start, and what do I get at each step?Every desk ships with a lead and a QA function.
A pool of agents with no accountable owner is how outsourced quality degrades — slowly, invisibly, and then all at once. Four roles exist on every account, and the smallest engagement gets all four.
- 01
Agents
Trained on your product, your tone and your escalation boundaries, and assessed before they touch live work. Named and consistent on dedicated plans.
- 02
Team Lead
Accountable for the queue rather than working in it — coverage, SLA, escalations and the shift handover. One person you can name when something goes wrong.
- 03
QA
Samples completed work against a written rubric, independently of the lead. Disagreements between agents are treated as a defect in the knowledge base, not in the agent.
- 04
Account lead
Runs the weekly report and the standing review where the knowledge base actually changes. The person who tells you the number went the wrong way.
QA sampling rate and the review cadence are agreed during onboarding and reported weekly against target — including the weeks it was missed.
Questions
But what about the thing that worries me?The questions people actually ask.
Do I get a dedicated virtual assistant?
No, and that is deliberate. You get a named Team Lead who knows your account and a trained pool behind them, working from processes documented for your business. A single dedicated person gives you deeper context and a real single point of failure — when they are on leave or they leave, the work and the knowledge both stop. If a dedicated individual is what you want, we are the wrong provider and will say so.
What tasks should I delegate first?
The recurring, rule-shaped, time-consuming ones — inbox triage, scheduling, data entry, document preparation, follow-up. They transfer fastest and free the most hours. Keep the judgement-heavy work until the desk has enough context to be useful on it, which usually takes a few weeks.
How is a virtual assistant service priced?
Against volume and turnaround rather than a block of hours, because hours logged and work completed are not the same measurement. We size it from your real task inventory during the first stage, so the number comes from your work rather than from a rate card.
Who owns the process documentation?
You do. It is written for your business, held in your systems, and it stays with you if the engagement ends — including if you take the work back in-house. A provider whose documentation leaves with them has made you dependent by design.
How is this different from your Data Entry desk?
Data Entry is one task type run at volume with a confidence threshold and sampled accuracy. This desk is broader and more varied — inbox, calendar, research, document work, follow-up — where the value is coverage across many small recurring tasks rather than throughput on one. Businesses with a single high-volume document process usually want that desk instead.
The other half
Most of this work should not need a person at all.
Inside a typical admin queue, a large share is extraction, routing and routine drafting — work an agent completes end to end with a gate on anything consequential. Building that layer is what stops this desk being priced by the hour forever, and running the desk is what tells us where the layer actually breaks.
AI AgentsStart
What is the next step?Tell us the volume, we will tell you the shape.
Send us a week of real numbers — calls, chats, tickets, documents — and we will come back with a coverage model and what it would cost.
Related desks
- TransactionData Entry & ProcessingDocument processing and data operations where extraction handles the volume and trained reviewers handle everything below the confidence threshold.
- ConversationEmail SupportShared inbox and ticket handling with drafting automation and trained agents, worked to a first-response target rather than to inbox zero.
- TransactionOrder TakingOrder capture across phone, chat and email — validated against live stock and written into your system, not into a spreadsheet.