The first 90 days with a new Shopify VA determine whether the hire works out. Most founders treat onboarding as a one-week activity, hand over login credentials, drop a Slack message saying "let me know if you have questions," and then wonder six weeks later why operations are not as smooth as they hoped. The pattern is so common it is almost the default.
This piece is a structured 30-60-90 day onboarding plan that flips that default. It covers what to prepare before your VA\'s first day, what the first week needs to look like, the milestones to hit at the end of each 30-day block, and the warning signs that the hire is not going to work out so you can correct course early instead of late.
Before day one: the founder prep work
Onboarding begins before your VA logs in. A week of founder prep work pays back many weeks of smooth operations later.
Document your current process
Spend two hours writing down what you do each week operationally. Not a polished SOP, just a stream of consciousness: what you check every morning, what tools you log into, what you do when an order has an address issue, how you respond to a refund request, what your monthly review looks like. Bullet points are fine. The act of writing it down surfaces decisions you have been making by habit that the VA will need to learn explicitly.
Create the access list
List every tool the VA will need: Shopify admin, helpdesk, Klaviyo, Pinterest, your bank for purchase order verification, project management, password manager. For each, decide what role or permission level they need (the lowest that allows the work, never an admin account by default).
Decide your communication rhythm
Daily async update? Weekly 30-minute call? Slack channel? Email summary? Pick a rhythm before they start. Changing it three weeks in feels like instability.
Prepare your brand voice document
If you do not have one already, write a one-page document covering: how you address customers, words you never use, words you always use, tone in different scenarios (refund denial, product inquiry, complaint, complement). Real examples from your past emails work better than abstract descriptions.
Days 1 to 7: shadow week
Your VA should NOT take ownership of any operational work in week one. They should shadow. This is counterintuitive (you hired them to do the work), but it is the most leveraged week of the entire 90 days.
Daily plan:
- Day 1: Tool access verified. Brand voice document reviewed together. They watch you handle 10 representative tickets. You explain each decision out loud.
- Day 2: They draft responses to 10 new tickets; you review every one before sending. Discuss what they got right and where their judgement differed from yours.
- Day 3: They handle order monitoring with you watching their screen via shared session. You point out what to look for that they would have missed.
- Day 4: They write their first draft SOP for one recurring task. You critique and refine.
- Day 5: They handle 50 percent of tickets with light supervision. Friday review: what worked, what surprised them, what they still need clarity on.
By the end of week one, they should be able to handle most tickets independently, know where to look for answers, and have begun the SOP documentation.
Days 8 to 30: progressive ownership
Weeks two to four are about handing off ownership systematically, one workflow at a time, never all at once.
Week 2: customer support
Full ownership of the support inbox. You review their first 50 sent replies and give written feedback. By Friday, target first-response time of under 4 business hours, in brand voice, with appropriate escalation of edge cases.
Week 3: order monitoring
Full ownership of daily order monitoring and exception handling. They produce a daily 3-line operational summary by 10am their time. You review the summary, not every order, for the first few days; then drop to a weekly review.
Week 4: inventory and supplier coordination
They take ownership of inventory monitoring and supplier follow-ups. They draft any outbound supplier communication and you approve before it goes out for the first two weeks; after that, they send directly.
Milestone at day 30: SOPs documented for every recurring task. Founder no longer needs to log into the helpdesk or check daily orders. Weekly 30-minute review call established as the standing operating rhythm.
Days 31 to 60: refinement and depth
Month two is about depth and judgement, not new responsibilities. The VA gets better at the work they already own, surfaces patterns you did not know about, and starts proposing improvements rather than just executing.
What to look for:
- They start spotting patterns: "We have had 12 customers ask about [topic] this month, should I add it to the FAQ?"
- They propose process changes: "I noticed we resolve return tickets faster when we include the return label in the first reply. Want me to update the macro?"
- SOPs are being refined, not just authored once and forgotten
- The weekly summary becomes more analytical: not just "47 tickets, 12 returns" but "12 returns, with 8 driven by sizing on the X product, possibly a fit guide issue"
Milestone at day 60: the VA can articulate which workflows are running well and which need attention. The relationship feels collaborative, not transactional.
Days 61 to 90: the steady state forms
By month three, you should be able to stop thinking about operational work entirely. The VA has rhythms, you have a review cadence, SOPs cover the work, and the operational layer of the business has lifted off your shoulders.
What good looks like at day 90:
- You spend under 1 hour per week on operations
- You read the weekly summary on Friday morning, ask 2 to 3 follow-up questions, and the week is done
- The VA proactively flags issues before they reach you
- SOPs are documented for every recurring task; a backup VA could pick up in under 60 minutes if needed
- You can take a one-week holiday without operations breaking
If you are not at that state by day 90, the issue is almost certainly one of three things: the VA is not the right fit, the founder has not let go enough, or the role was scoped too broadly. Diagnose and fix it in month four; do not let it drift.
Red flags by week
Catch problems early. Specific warning signs by phase:
- Week 1: Asks no questions during shadow week. Either they think they already know everything (often wrong), or they are intimidated and will not raise issues later. Either way, address it.
- Week 2: Sent replies feel templated, not in brand voice, after written feedback. Either the brand voice document is too thin or the VA cannot adapt; one of those needs to change fast.
- Week 4: No SOPs written. Foundation problem; the documentation is what makes the operation survive their absence.
- Week 8: Still asking you to make every decision. Either you are not delegating, or they lack judgement. Have a direct conversation.
- Week 12: You still feel operationally responsible. The hire is not working. Be honest with yourself and them, and either rescope or rematch.
The shortcut: hire through an agency that has done this 50 times
Every milestone in this plan can be hit by a well-prepared founder onboarding a strong individual hire. It can also be hit faster, more reliably, and with less founder time when you hire through an agency that does this dozens of times per year.
At ScaleWise VA, our standard onboarding sequence is built around exactly this 30-60-90 plan. Brand voice document, SOP library, weekly summary cadence, escalation matrix, and backup coverage are not things you build yourself, they come with the engagement.
The weekly review template
Your standing Friday review meeting is the rhythm that makes everything else work. A template that consistently delivers:
- Numbers (5 minutes): orders, revenue, support ticket volume, average response time, refunds, current inventory alerts
- Wins (5 minutes): what went well this week, what got better, what is now off your plate
- Issues (10 minutes): what slipped, what surfaced as a pattern, what is unresolved going into next week
- Next week (5 minutes): any unusual context (launches, promotions, supplier delays), priorities, escalations expected
- Founder asks (5 minutes): anything you want the VA to dig into, decisions you need from them, anything they need from you to be productive
Keep the meeting under 30 minutes ruthlessly. Long weekly meetings are a smell that the cadence is wrong; you should be operating between meetings, not in them.
What changes after the first 90 days
The right outcome at day 90 is that operations feels boring. Boring is the goal. Boring means the system works without crisis, you stop firefighting, and the brand can compound predictably.
What changes for the founder:
- You stop checking the helpdesk app on weekends
- The morning operational scan that used to take 45 minutes takes 5 minutes (the summary)
- You can plan a holiday without coordinating coverage personally
- Decisions that used to interrupt your day get queued for the Friday review
- You have time to think about growth instead of about today\'s orders
What changes for the VA:
- They own the operational layer and have the authority to make day-to-day calls
- They feel like part of the team, not a contractor on the outside
- They are confident raising issues and proposing changes
- They have the documentation and tools to scale into a larger role as the brand grows
If you would prefer to skip the build and start your 90 days with the system already running, book a free discovery call. We will scope what your first 14 days would look like and share a quote within 48 hours.