teamRJEC · Digital horsepower

VAs own their name.
Clients get the OS.

Playbook for virtual assistants anywhere. You keep your domain and Cloudflare account. teamRJEC keeps the master stack, Stripe, and client workspaces. You do not need Cloudflare OS.

01 Three seats

Owner — teamRJECteamrjec.com master stack. Stripe for Lab Testing Solutions, J&M, and RJ Employer Consulting. Project board and client OS live here.
You — the VAYour personal domain in your Cloudflare account. Proposal page only. Free plan is enough. No OS required.
ClientWorkspace such as client.yourname.com, or Cloudflare OS on their brand. They can use the OS. You still run the loop.

02 Domain handoff

  1. Create a free Cloudflare account at dash.cloudflare.com with your email.
  2. Send teamRJEC your Account ID (dashboard home, right side).
  3. We move the registration RJEC → your account. You become owner and payer.
  4. Change WHOIS to your name. Put auto-renew on your card.
  5. No domain yet? Register it yourself. We should not keep it.

Names registered 27 Jul 2026 cannot transfer to another registrar for ~60 days. Move account-to-account inside Cloudflare instead. After a move: 30-day lock.

03 Cloudflare in plain words

04 How accounts talk

  1. Traffic: CNAME client.yourdomain.com → saas.rjemployerconsulting.com (or the host we give you).
  2. Data, only if needed: scoped API token for that one zone. Revoke anytime.
  3. Leave: delete the CNAME, revoke the token. Domain stays yours.

05 Billing

06 Project management

  1. Lead arrives on teamrjec.com or the client brand.
  2. You send the proposal from your domain.
  3. Client pays → we open the workspace and the task board.
  4. You work the board: inbox, calls, schedule, documents, proof.
  5. Owner approves money and records. You do not hold the vault.

07 Cloudflare OS rule

The client may get Cloudflare OS. The VA does not need it. Your job is the remote operating loop. The OS is a client tool, not a VA requirement.