MyVA Go-To-Market — Implementation Plan

Created 2026-11-10. Research-backed, owner/VA split marked per step. [ME] = UberVA does it · [YOU] = owner decision/input · [BOTH] = I prepare, you approve.

Rule that governs this whole plan: nothing goes out without your approval, and no proof point, price or customer claim gets invented. Gaps are marked, not filled.

What the research says (with sources)

Research gaps (honest): browser search was unavailable this session and several planned sources 404'd or blocked access (a16z, Paddle, HubSpot, SaaStr, G2, Lenny's, Manus, OpenAI business pages). SMB-buyer-behavior statistics and competitor pricing beyond Claude are unverified. The plan below is built on the sources that did load plus the existing outreach/ kit — treat market-size numbers as unknown until checked.

Phase 0 — Decide what we're selling (this week) [YOU]

The kit's open question is still open, and it blocks everything downstream.

1. [YOU] Choose the offer: (a) the MyVA product itself (subscription), or

(b) a done-for-you VA/operations service built on MyVA (higher price, more hands-on). Recommendation: start with (b) for the first 5–10 customers, productize later. Reason: the ICP buys relief, not software; service also generates the proof points the product needs. Sources above show audience/service→product paths working.

1. [YOU] Approve pricing — see pricing.md for the recommended two-layer

structure: DFY wedge now (pilot $500–750, then $1,200–2,000/mo), tiered SaaS ladder to productize into later (Solo $39–49 / Studio $99–149 / Firm $299–499 / Enterprise custom + capped overflow packs). Open to revision after Phase 2.

1. [YOU] Give me 2–3 real proof points or explicitly approve the line

"early stage — pilot results pending." I will not manufacture numbers.

Phase 1 — Assets and foundations [ME], 1–2 days after Phase 0

1. [ME] Fill every [FILL IN] in positioning.md and one-pager.html with your

approved offer, price and contact details. Re-run the site check afterwards.

1. [ME] Rewrite the one-pager headline around the strongest verified differentiator

(approval-gated outward actions + real artifacts). Keep the Trust Boundary page (trust/index.html) linked as proof — it's our most credible sales asset.

1. [ME] Build a 3-case "what I can do this week" demo pack: one email-triage brief,

one sourced research brief, one built document/page. Real artifacts sell this product better than adjectives. (Drafts only — nothing sent.)

1. [ME] Set up tracker.csv conventions in practice: I log every touch with

source_of_contact recorded. No guessed email patterns, ever.

Phase 2 — Manual recruitment: first 10 customers (weeks 2–6) [BOTH]

This is the core of the plan. Per the research, the first users are recruited individually and onboarding is deliberately unscalable.

1. [YOU] Give me your warm list — people who know you (past clients, colleagues,

communities). Warm beats cold at this stage by a wide margin.

1. [ME] For each name: research pass into tracker.csv — real role, one verifiable

observation, best channel, likely pain, qual score from icp.md. Pursue at 18+.

1. [BOTH] Personal outreach, 5–10/week. I draft each message individually from the

research (never a mail-merge), you approve each send. Sequence in emails.md and linkedin.md is the fallback structure, not a blast.

1. [ME] "Collison installation" equivalent: for anyone who says yes, I prepare

their workspace setup in advance — connected accounts checklist, first three tasks queued, so the trial starts with work already done, not a blank screen.

1. [BOTH] Concierge onboarding for the first 10: weekly check-in brief from me,

you (or I, drafted) ask what nearly stopped them buying. Log objections verbatim in tracker.csv notes — that's Phase 4's copy.

Phase 2b — Pain-signal outreach (weeks 2–8, runs alongside Phase 2) [BOTH]

Method: find people publicly complaining about the exact problems MyVA solves, help them first in public, move to DM only after a real exchange. This is the "recruit manually" pattern applied to strangers instead of the warm list.

Why it fits (reasoning, not measured): a complaint is a self-qualified lead with a live pain and a timestamp. It beats a purchased list on relevance, and it pays twice — even non-buyers hand us their exact words for copy and objections.

Three conditions that make it work:

1. Help first, never pitch in public. The offer lives in DMs, and only after a

genuine exchange. "I saw you complaining" is creepy; "here's what worked" is not.

1. Search by pain language, not product language. Nobody searches for "agentic

AI." They write about the symptom.

1. Low volume, high quality — 5–10 genuine interactions/week. The moment this

becomes scraping or automated engagement it violates platform ToS, risks bans, and reads as predatory — which poisons the trust story we're selling.

Pain → message map:

Hunt hardest for the "I don't trust AI to send my email" and "AI sent something embarrassing" rows — those people already believe the problem is real and have already been failed by the alternative. Warmest possible leads.

Split:

• [ME] Maintain the pain-phrase search list; monitor the communities you name;

draft every reply and DM; log each interaction in tracker.csv with source_of_contact; turn recurring complaint language into a copy bank.

• [YOU] Approve each public reply and DM before it goes out. Choose which

communities you're willing to appear in as yourself.

Honest limits: no conversion data exists for this method — it's a hypothesis, same as the rest of Phase 2. The market stats in pricing.md measured adoption, not buying behavior, so they don't validate it. Platform ToS is a hard constraint: I read public pages and draft replies; I will not run bulk scraping or automated engagement. Manual and low-volume is the method, not a compromise.

Phase 3 — Pricing and the first paid conversion (weeks 3–6) [BOTH]

1. [BOTH] Pilot offer: 30 days, fixed price, defined scope (see pricing.md),

paid — free pilots attract tire-kickers and produce no commitment signal.

1. [ME] Prepare the pilot agreement outline: scope, what's approval-gated, data

handling (point to trust/index.html), what happens at day 30. You review before anything is sent.

1. [YOU] Take the money. I can draft, schedule and remind — the close is yours.

Phase 4 — Channels that compound (weeks 6–12) [ME] mostly

Only after 5+ real conversations — otherwise we're publishing into a vacuum.

1. [ME] Turn the top 3 logged objections into content: one page or post each,

answering the actual words prospects used. Publish only with your approval.

1. [ME] Niche community presence (where the ICP actually is — owner/agency

communities, not AI Twitter): helpful answers, no pitching, profile links to the one-pager. I draft, you post or approve my posts.

1. [ME] Case study #1 from the first paying customer — with their permission and

their numbers only. This replaces "pilot results pending."

1. [BOTH] Referral ask: at pilot end, one specific ask from you to a happy customer.

Warm intros are the cheapest channel available to us.

Phase 5 — Measure and decide (week 12) [BOTH]

1. [ME] Weekly metrics brief from tracker.csv: conversations, replies, meetings,

pilots, paying, and weekly growth rate. Honest numbers, including zeros.

1. [YOU] Decision gate: if 3+ paying and retention looks real → productize and

raise price. If not → the logged objections tell us whether it's offer, price or market. Do not scale a channel that hasn't worked once manually.

What I can start right now

• ✅ Done: this plan, pricing.md, research with sources.
• Ready on your word: fill the [FILL IN] fields, build the demo pack, research your

warm list into the tracker, draft individual outreach.

• Blocked on you: the offer choice, pricing approval, proof points, the warm list.

Metrics that matter (weekly)

Targets are planning assumptions, not forecasts. Adjust from real data.