Why this role exists
WE-DO runs an AI-native agency serving 100+ clients. We've built an internal operating system (Claude Code skills, MCP servers, scheduled agents, automated reporting pipelines) that lets a small team punch way above its weight.
What we haven't been able to automate is the judgment, communication, and QA layer in the middle. Every client email, every AI-generated deliverable, every WordPress edit, every parallel-subagent dispatch still funnels through the founder. The bottleneck isn't capacity. It's having a trusted human owner in the loop.
We need someone who owns a portfolio of client accounts end-to-end: writes the client emails, runs the check-ins, coordinates the work (internal team, our outsourced dev partner, AI agents), QAs the deliverables before they go out, and handles the steady stream of small-to-medium web edits without escalating every keystroke for approval.
The right person is part account manager, part AI operator, part web technician. Three jobs in one, which is exactly what an AI-native agency makes possible.
What you'll do
Client Account Management
≈30%- Own a portfolio of 8 to 12 client accounts as their day-to-day contact at WE-DO
- Write and send client emails: status updates, project responses, scope clarifications, deliverable handoffs
- Run client check-in meetings (weekly or bi-weekly), prep agendas, capture action items, follow up
- Translate client requests into actionable tasks for the internal team, our outsourced dev partner (E2M), or AI workflows
- Keep clients informed proactively when something slips. Never let them be the first to notice.
- Maintain a polished, on-brand voice in every client touchpoint (we'll train you on WE-DO's voice)
AI Workflow Operations
≈30%- Run and monitor our existing Claude Code skills, agents, and scheduled jobs
- Triage the proactive-assistant queue daily. Turn AI-suggested actions into completed work, or kill them if they're not useful.
- Review the output of autonomous workers (claude-user-worker, parallel subagents) before anything reaches a client
- Spot when AI is wrong: hallucinated URLs, fabricated SEO claims, schema conflicts, mis-targeted CSS, wrong client context, made-up file paths
- Document recurring AI failure modes so we can patch them into skills and memory
Web QA + Small Edits
≈25%- Execute WordPress edits across 13+ client sites via SSH and WP-CLI: content updates, redirects, schema patches, plugin config, CSS tweaks
- Execute Shopify edits across multiple stores: products, collections, menus, theme tweaks, blog posts, redirects
- Validate every deployment against the live site before marking complete: screenshots, HTTP 200 checks, structured-data validators, visual diffs
- Maintain rollback discipline: snapshot before menu/schema/theme changes; revert cleanly when needed
- Handle deploys to WordPress (WP Engine + Flywheel), Shopify, and Vercel. Never to production without verification on staging.
Coordination & Project Management
≈15%- Manage tasks in Notion: create, prioritize, hand off, and close
- Write clear technical specs for E2M (our outsourced dev partner): scope, acceptance criteria, examples
- QA E2M deliveries before client handoff
- Surface blockers early; escalate the right things at the right time
Who you are
Client-facing and polished.
You write the kind of emails clients actually want to receive. Clear, warm, specific, no fluff. You've owned client relationships before and you know the difference between "managing up" and "actually managing." You can run a client call without notes if you have to.
AI-native, not AI-curious.
You build prompts, chain agents, and write skills/tools. You've shipped meaningful work with Claude, GPT, or both. You can read an AI's output and know within 10 seconds whether it's right, wrong, or hand-wavy. You see AI as a teammate to direct and verify, not a magic box to trust.
Web-comfortable in the trenches.
SSH and WP-CLI don't intimidate you. You know what CSS specificity is, why `!important` matters on page-builder defaults, and how to read a serialized PHP meta value without breaking it. You've worked inside Shopify Admin and at least one WordPress page builder (Beaver Builder, Elementor, or Divi). Browser devtools are your friend.
Independently productive.
You read the docs, try the thing, verify it worked, and move on. You ask sharp questions when blocked. You don't ask check-in questions to feel productive. You can run a full day on three Slack messages.
Wired for verification.
"Done" means proven: screenshot, live-site check, validator pass, or it doesn't count. You catch the agent's "task complete" lies. You diff before/after. You don't trust summaries; you trust artifacts.
Async-default communicator.
Writing-first. Quick, clear, and structured. You leave a paper trail in Notion and Slack so your work is auditable without a meeting. When a meeting is needed, you make it count.
Nice to have
- Prior account management or project management experience at a digital agency
- Hands-on with Claude Code (skills, MCP servers, agents) or comparable agentic tools
- Notion API, Google Workspace APIs (GA4, GSC, Ads), DataForSEO, Playwright
- Light scripting: JavaScript / Node, bash, JSON-wrangling, jq
- SEO instincts. You can spot a thin page, broken canonical, or missing H1 without being told.
- Email marketing platform experience (Brevo, Klaviyo, Shopify Email, Mailchimp)
- RankMath, Beaver Builder, or Shopify Liquid experience
What you don't need
- A CS degree
- Deep coding chops. You're operating a system, not building it, but you'll write some scripts.
- A formal marketing degree. We care more about clear writing and verified deploys than campaign-brief jargon.
- Years at a big agency. If you've owned client relationships at a small shop or in-house, that's perfect.
Stack you'll live in
- Claude Code
- Notion
- Slack
- Google Workspace (Gmail, GA4, Search Console, Ads)
- Vercel
- WordPress (WP Engine + Flywheel + SSH/WP-CLI)
- Shopify Admin
- Playwright
- Brevo / Klaviyo
- GitHub
- macOS terminal (zsh)
How to apply
Apply through the form below. We're evaluating your written voice from the first sentence, so write the way you'd write to a client. No cover letters. No resumes in PDF unless you really want to. Show us the work.
Prefer email? Send your application to mike@wedoworldwide.com with the subject line “AI-Native AM Application, [Your Name]”.