Advisory: A managed virtual marketing teammate

The next step up from MITL Pro — for marketing leaders who want a custom AI teammate built into their team and operated for them.

If you're here from the Pro page, you've already seen what the MITL MCP and the 47 skills can do. Plenty of marketing teams pick those up, install them in a few hours, and start running. That's the self-serve track. This page is the other track.

The Advisory engagement is for marketing leaders who don't want to install, configure, or maintain anything themselves. You hire me to build a virtual marketing teammate for your team, train it on the work you most want it doing, pilot it inside your team, and then operate it for you on an ongoing basis. The MCP and the skills are the toolkit. The Advisory is the team member who uses the toolkit on your behalf.

Book a consult to see if this service is right for you.


When this is the right fit

You should be on this page if:

  • Your marketing team is lean and your bandwidth for building anything new is close to zero
  • AI use across the team is currently ad hoc — pockets of experimentation, no shared system, no consistent operationalization
  • You want a real working virtual teammate inside your team within a few weeks, not a 6-month transformation project
  • You'd rather have a partner accountable for the output than learn to operate another tool yourself
  • You're comfortable committing to a 6-month relationship to make the build investment worth it

You should probably stick with Pro if:

  • You have time and interest in installing the MCP, learning the skills, and iterating on them inside your own team
  • You want to keep AI execution fully in-house and just want the tooling foundation
  • Your scope is small enough that 47 off-the-shelf skills is plenty

Both tracks pull from the same underlying system — MITL MCP, the skills, the methodology. The difference is who operates it.


The mental model: a teammate, not a tool

Think of the virtual teammate as a junior employee who reports to me but works with your team.

Your team gives it work — a campaign brief, a promo analysis, a piece of segmentation, a draft of next quarter's content calendar. The teammate does the work. Your team reviews, redirects, and approves. When something doesn't work the way you want, you tell me. I coach the teammate, fix the issue, and ship the improvement back to your team — usually within a week, often within a day.

You get the output. I own the operating responsibility.

That's the whole model. Everything else on this page is the structure that makes it work.


How it works

The engagement runs in two phases. The first is short and fixed. The second is ongoing.

Phase 1 — Onboarding & Launch (2–3 weeks, one-time)

The goal of Phase 1 is simple: get a working virtual teammate into your team's hands inside three weeks. You shouldn't need to learn how it's built or how it works. Only how to direct it.

What happens during Phase 1:

  • Fast-track discovery of your current marketing operations, tools, data sources, and workflows
  • Effort-vs-impact scoring on candidate use cases, segmented into "operationalize what we do today," "unlock what wasn't possible before," and "blocked until X is fixed"
  • MVP build of the virtual teammate, deployed in the surface of your choice (Slack, Microsoft Teams, web, GitHub, or alongside your existing AI tooling)
  • Light-touch onboarding for your team so they can direct the teammate from day one

What you walk away with at the end of Phase 1:

  • A working virtual teammate, live in your environment, handling the first prioritized capabilities
  • A prioritized implementation roadmap, scored for effort and business impact
  • A measurement framework that defines how we'll measure business impact for every capability built

Phase 1 is three meetings: a discovery workshop, a measurement workshop, and a launch session. That's it.

Phase 2 — Managed Virtual Teammate Service (monthly, 6-month minimum)

Phase 2 is the relationship. It's what most of the value is bought for.

Every month, I:

  • Operate the virtual teammate day-to-day — monitoring, performance tuning, prompt and skill refinement, fixing anything that doesn't work right
  • Build 2–4 new capabilities from the roadmap, shipped to your team as they're ready
  • Continuously improve existing capabilities based on usage feedback from your team
  • Run a service desk — any time someone on your team works with the teammate and it doesn't work right, ping me. Response within one business day; fix or workaround within three.
  • Track and report business impact every month against the measurement framework

We meet once a week for an hour. Review what shipped, talk about what's blocking, decide what to teach the teammate next.

After the 6-month minimum, the engagement continues month-to-month. Either party can end it with 60 days notice. If you ever want to take the teammate in-house, the configured instance and documentation transfer to you on final payment — you own what we built.


What this costs

Pricing is structured around the service relationship, not the build.

  • Phase 1 — Onboarding & Launch: from $1,500 (one-time fixed fee)
  • Phase 2 — Managed Virtual Teammate Service: from $2,500 per month (monthly build and enablement support)

The 6-month minimum on Phase 2 is what makes the lower Phase 1 fee possible. The build is the on-ramp, not the product.

Final scope and price are confirmed on an intro call, based on the size of your team, the complexity of your starting workflows, and the surfaces you want the teammate deployed into.


The business outcomes I'm aiming for

Specific things I look for in the first 90 days:

  • Output scales without headcount. Most engagements produce 2–3x more campaigns, content, or analysis at the same team size by month 3.
  • Faster cycle times. Workflows that used to take days run in hours. A recent client put it best: "By end of week two, watching four manual processes get turned into automations that ran in a twentieth of the time was unreal."
  • Decision quality goes up. When promo analysis, segmentation, and reporting all run through the teammate, the team makes faster and better-informed decisions about what to do next.
  • Your team stops doing the work it shouldn't be doing. Analyst hours come back. Senior people get their week back.

Every capability I build ties to a measurable outcome on the measurement framework. You can see what's improving and what isn't, every month.


What's not in this

Honest about scope:

  • Six-to-twelve-month enterprise transformation programs that need dedicated engineering and data-pipeline build-out. Those fit best with partners who bring embedded engineering horsepower. Happy to refer.
  • Replacing your team. The teammate makes your team faster and better. It doesn't replace them. Every workflow runs with human-in-the-loop review by default.
  • Buying access to the MCP alone. That's Pro. This is Pro on a custom build, plus a partner that helps you learn the ropes.

What happens next

If this sounds like the right fit, book a 30-minute consult. We'll talk through your team, your current AI use, and the capabilities that would move the needle most. If we're a fit, I'll send a scoped proposal within 48 hours.

Book a 30-minute intro call →

If you're not sure whether this or Pro is right for you, start with Pro. The MCP works. The skills work. And the upgrade path to Advisory is always open.


Advisory services are delivered through MultiplAI Growth Systems, the consulting practice behind Marketer in the Loop. Engagements are governed by a Statement of Work agreed at proposal stage.